Seventeen checks across five categories. This is the same list the test runs, so what you read here is what your report will say.
The first file every agent asks for. No file means no rules, and several crawlers read no rules as a reason to stay away.
What we do: The plugin adds a robots.txt through WordPress, keeping whatever your SEO plugin already put there.
Still how a crawler finds every page rather than the ones it happens to link through.
What we do: WordPress publishes this already. We point at it from the Link header so an agent finds it without guessing the filename.
Everything below lives at a path an agent would have to guess. A Link header hands it over on the first request instead.
What we do: We send one RFC 8288 relation per document, on every page.
Lets an agent find your documents from DNS, before it fetches anything. Two records do the work: an SVCB index at _index._agents and a TXT catalog pointer at _catalog._agents. Both need DNSSEC, because an unsigned answer is one an agent is told to distrust.
What we do: PRO works out the exact records for your domain, checks whether they are live, and publishes them for you when your DNS is on Cloudflare.
A short, plain description of what the site is and which pages answer which question. A model reads it in one request instead of crawling forty pages.
What we do: Generated live from your pages and products, so it can never quote a price you stopped charging.
Your page as text, without the navigation, cookie banner and layout divs that make up most of the HTML a model has to pay for.
What we do: Same URL, same content, negotiated on the Accept header, with Vary set so caches keep the two apart.
A crawler that finds no group matching its own name has to guess. Naming them removes the guess.
What we do: We add a named group for eighteen AI crawlers, each with an explicit Allow.
States what AI systems may do with your work: appear in search, answer a question, train a model. Silence is read as consent by some and refusal by others.
What we do: We publish your three preferences inside every crawler group, so no agent has to infer them.
Lets a verifier check that a signed request really came from you. This is the direction agent identity is going.
What we do: We generate an Ed25519 key on your own server and publish only the public half, with the correct RFC 8037 thumbprint.
The RFC 9727 index of every API this origin offers. Without it an agent has to discover your API by trying URLs.
What we do: Published as a linkset, listing the WordPress REST API, the WooCommerce Store API and the MCP endpoint.
Tells an agent what it can call and what comes back, in the format every tool already reads.
What we do: Generated from your live endpoints, including the product API when WooCommerce is active.
How an AI assistant discovers that your site has tools it can call, and which protocol versions they speak.
What we do: Published to the current MCP schema, with the endpoint, capabilities and supported versions filled in.
A card that describes a server nobody can connect to is worse than no card. This is the server itself.
What we do: We run a read-only MCP server on your site: site info, content search, live products and prices. No key, nothing writable.
Short instructions telling an agent how to do a specific job on your site, rather than leaving it to work one out.
What we do: We publish skills for finding a product and for understanding the site, each with a content digest so an agent can verify it.
The ARD index: every machine-readable resource you offer, with the questions each one answers.
What we do: Built from what you actually publish, and announced in robots.txt as an Agentmap.
How software finds out whether it needs credentials and where it would get them.
What we do: RFC 9728 protected resource metadata, RFC 8414 authorization server metadata, and a readable auth.md alongside.
An agent can read your catalogue and still not buy anything. This says how a payment is made and where.
What we do: PRO publishes ACP, UCP, MPP and x402 discovery, and refuses to publish any of them until there is a real endpoint behind it.
The documents are served through rewrite rules. Activating the plugin flushes them for you, but if a path returns 404 with its setting on, go to Settings, then Permalinks, then Save. That is the whole fix.
Some hosts deny every dot-prefixed path with a rule meant for dotfiles. It needs
an exception for /.well-known/, which is a registered URI prefix
rather than a hidden file. The readiness check names this when it sees it.