For WordPress

WordPress agent readiness

Self-hosted WordPress is a full-code stack wearing a CMS skin: you have a filesystem, functions.php, and .htaccess (or nginx config) underneath the editor. Every one of the 14 checks is achievable, which puts WordPress closer to Next.js than to Shopify or Webflow, but a default install still ships almost none of them.

100

Native ceiling

Best achievable score without fronting

—

No Cloudflare fronting needed

Native ceiling is already 100

What agents currently see

A stock WordPress install already handles a few things reasonably: a virtual robots.txt that allows crawlers by default, and, with an SEO plugin like Yoast or Rank Math installed, a generated sitemap.xml and basic title and meta description control. Structured data coverage varies widely by theme and plugin stack; some ship Organization or Article JSON-LD, most do not.

What is almost never present: agents.md, llms.txt, an MCP server card, /.well-known/verified.md, explicit AI-crawler allow rules for GPTBot or ClaudeBot in robots.txt, markdown content negotiation on the Accept header, and any x402 signal. None of these require a new host or platform migration, just a plugin, a functions.php snippet, or a rewrite rule.

Your ceiling, and why

100. Root-level static files (agents.md, llms.txt, .well-known/verified.md, .well-known/mcp.json) can be dropped straight into the WordPress install's document root, and a rewrite rule or a small plugin can branch a request on its Accept header to serve markdown instead of the rendered page. Nothing about the CMS itself caps the score, the gap is entirely that these files are not part of a default theme or the core install.

Which delivery model fits

The Agent Ready Kit is the natural fit for most WordPress sites: every file with an exact path (wp-content root, functions.php snippet, .htaccess rule) that your developer, or the person who manages your hosting panel, can paste in without a plugin marketplace detour. Done for you is the better call if you want us in the wp-admin directly, following your staging workflow.

What is typically failing

  • agents.md
  • llms.txt / llms-full.txt
  • robots.txt AI crawler allow rules
  • MCP server card
  • .well-known/verified.md
  • Content negotiation (Accept: text/markdown)
  • x402 payment signaling

See where you stand

Run a free scan, or start with the self-serve kit if you already know you need it.

Scan for free Get the kit