WordPress AI Research Lab

Study AI-assisted WordPress systems as combinations of model, client, transport, identity, permission, task, evidence and verification rather than declaring winners from isolated demos.

This hub is organized around concrete WordPress decisions rather than around AI vocabulary. Start with the outcome you need, determine what evidence is authoritative, choose the narrowest access boundary and verify the result before any later stage changes the site.

What you can learn here

The guides in this section help readers move from a broad question to a controlled workflow. They explain what can be assessed from public pages or exported evidence, when an authenticated WordPress connection becomes necessary, which actions must remain prohibited and what a defensible result looks like.

The default progression is:

1. define the decision and evidence scope;
2. collect stable identifiers and authoritative records;
3. use AI for classification, comparison or drafting;
4. keep observations, inferences and recommendations separate;
5. obtain accountable review;
6. move approved work into a distinct implementation mandate;
7. verify the WordPress state and revoke temporary access.

Guides in this section

Claude Code vs Codex for WordPress Tasks: A Controlled Evaluation Protocol

A useful Claude Code versus Codex comparison must hold the WordPress site, task, evidence, permissions and scoring rubric constant and report variability instead of turning one demonstration into a universal winner.

• Best used when: Define a reproducible benchmark for comparing how Claude Code and Codex understand, plan, execute and verify bounded WordPress tasks under identical conditions.

REST vs MCP for WordPress Tasks: A Controlled Benchmark Protocol

A REST versus MCP benchmark should compare equivalent WordPress capabilities under matched identities and tasks, not confuse transport convenience with permission, correctness or product coverage.

• Best used when: Measure how direct REST and MCP-mediated workflows differ in discovery, setup, execution, evidence, error handling and human effort while holding the underlying WordPress authority constant.

WordPress AI Read-Only Task Study: Protocol and Reporting Framework

A read-only WordPress study should measure what useful work assistants can complete without writes and where missing evidence or permissions create legitimate limits, not treat refusal as failure by default.

• Best used when: Build a reproducible study of auditing, inventory, classification and planning tasks performed through a verified read-only WordPress identity.

WordPress AI Refusal Study: Measuring Whether Access Controls Fail Safely

A WordPress AI refusal study should test whether forbidden actions are blocked consistently, explained accurately and recoverable without permission escalation or unsafe workaround suggestions.

• Best used when: Measure the technical and interaction quality of authentication failures, authorization denials, validation failures and unsupported operations across controlled WordPress tasks.

How to Build a WordPress AI Task Coverage Matrix

A task coverage matrix should distinguish documented, exposed, permissioned, tested and verified WordPress operations instead of presenting a marketing list as proof that every assistant can perform every task.

• Best used when: Create a versioned matrix connecting WordPress tasks to evidence sources, connection methods, identities, capabilities, clients, test status and known limitations.

WordPress AI Failure Patterns: A Research and Classification Protocol

A WordPress AI failure catalog should preserve raw evidence and distinguish task-design, evidence, connection, permission, tool, model, implementation and verification failures instead of blaming every problem on the model.

• Best used when: Build a reproducible failure taxonomy and incident corpus that supports product improvement, safer instructions and more accurate public guidance.

How to Document a Controlled WordPress AI Workflow Case Study

A credible WordPress AI case study must document the initial state, mandate, evidence, identity, permissions, actions, refusals, human decisions and verified outcome without turning one controlled example into a universal performance claim.

• Best used when: Create a reproducible case-study package showing how one bounded WordPress task moved from evidence through approval, execution, verification and revocation.

Track WordPress AI access changes

Use the WordPress AI Access Watch for versioned, source-bound observations about plugin assistants, credentials, abilities, consent, permissions and revocation.

• WordPress AI Access Watch: Plugin Assistants, Credentials and Permission Changes
• Plugin AI Assistant vs Claude Code, Codex and MCP for WordPress

Choose the right starting point

Choose the simplest guide that can answer the current question. A public-page review may need no WordPress access. An inventory may require Read Only. Drafting may justify Draft only after the evidence and scope have been approved. Publishing, administrative work, code changes, commerce mutations and releases require separate controls and should never be introduced merely because an earlier analytical stage reached a limit.

Evidence and safety model

Every guide uses the same evidence hierarchy:

• authoritative source or system record;
• captured state with date, version and identifier;
• executed test or reproducible observation;
• inference with stated confidence and limits;
• recommendation awaiting approval;
• authorized implementation and independent verification.

A lower layer cannot enlarge the authority of a higher one. An assistant cannot create missing business facts, legal approval, accessibility conformance, security assurance or release authority through fluent language.

How PAGUP Agent Control fits

This is a general WordPress workflow, not a promise that Agent Control can edit every object or integration discussed here. For the guided path, start with public pages; plugin, theme, user, setting, file, deletion, WooCommerce, ACF and builder operations are not native guided tasks. Use separately qualified tools and permissions where required.

Get structured site information and inspect selected published pages after connecting. No temporary task is needed for this public reading. You can also browse public pages without the plugin; Agent Control adds structured access and a path toward authorized WordPress work.

Connect your AI: docs first profile · See features and compatibility: coverage

Continue through the hub

• Return to the parent hub.
• Review the first controlled workflow.
• Compare the task with the access-level guide.
• When authenticated work is complete, revoke the temporary identity.

Product path

Use the product overview to understand the controlled identity layer, the protected modes to compare boundaries and the pricing page only after the workflow and required access are clear.