ChatGPT, Claude, Perplexity and Google's AI Overviews are much worse at reading websites than Google is. They download a page built for human eyes and guess which part was the answer — and when they guess wrong, they quote a competitor whose site was easier to parse. This plugin gives them a clean version of your site to read instead.
If you log in at yoursite.com/wp-admin and you can install plugins, you are done
checking compatibility. That is the entire requirement.
Wix, Squarespace, Shopify, Webflow, GoDaddy Website Builder and WordPress.com below the Business plan do not let any plugin add files to your site, so nothing can do this job there — not this, not anything. If that is you, we build the site instead: get a free quote. And if your site isn't WordPress but you control the files yourself, you want the file pack.
Once. Not a subscription. Install it on every WordPress site you own.
Secure checkout by Stripe. The download link and a receipt arrive by email immediately. No account to create. Nothing in the plugin ever phones home.
Start to finish, about two minutes. If you have ever installed a WordPress plugin, you already know how to do this, and if you have not, these are all the steps there are.
yoursite.com/wp-admin.Then open AI Indexing → Endpoints and press Check all. That screen fetches every address the plugin serves and tells you what came back. It exists because the one thing a plugin cannot control is whether your host or your security plugin is quietly blocking something — and that is invisible otherwise. A green row is proof. "The plugin is active" is not.
This is the part that is genuinely different from every other version of this idea, including our own file pack. WordPress already knows your site's name, your tagline, your pages, your posts and your URLs — so the plugin reads all of that and generates every document from it, on every request. There is no find-and-replace step. No placeholder to miss. No file to rename. Nothing on disk that can quietly go out of date while you think it is current.
Rename your business and /llms.txt says the new name on the next fetch. Publish a
page and it is in the Markdown sitemap immediately. Change your prices once, on one screen, and
every one of the 22 surfaces below agrees.
The settings screen holds only what WordPress cannot know: your contact details, what you sell, what it costs, and — the one worth five minutes — anything you are required to say. That last field matters more than it looks. The real risk with AI isn't that it can't find you; it's that it finds you, summarises you, and drops the sentence you're legally obliged to include. Whatever you put there gets attached to every answer the plugin serves, in five separate places.
22 surfaces, all live the moment you activate it, all generated from your own site.
| /llms.txt | A plain-text briefing on the whole business: what it is, the key pages, services, prices, and anything that must be repeated with an answer. |
|---|---|
| /llms-full.txt | The entire readable site as one document, so an agent understands everything in a single request instead of crawling page by page. |
| /sitemap.md | Every page, grouped by type, as Markdown. |
| /AGENTS.md | How to read the site efficiently, and what must travel with any answer taken from it. |
| /mcp | A working MCP server — Model Context Protocol, Streamable HTTP, JSON-RPC 2.0. Read-only tools backed by the site's real posts, pages and settings. Connect a client and call tools/list. POST only; a GET correctly returns 405. |
|---|---|
| /.well-known/mcp.json | Canonical MCP server card. |
| /.well-known/mcp/server-card.json | The legacy path scanners still probe. |
| /server.json | MCP registry publication manifest — what Smithery and the public registries read. |
| /agents.txt | The agents.txt capability declaration. |
|---|---|
| /.well-known/agent-card.json | A2A agent card. |
| /.well-known/agent-permissions.json | Per-path read and write policy, including the administrative paths agents are told to leave alone. |
| /.well-known/agent-skills/index.json | Skill index, plus a SKILL.md generated and named after the site's own domain. |
| /.well-known/acp.json | Agentic Commerce Protocol descriptor. |
| /.well-known/ucp | Unified Commerce Protocol profile. |
| /.well-known/ai-catalog.json | The catalogue, machine-readable, with representative queries. |
| /.well-known/api-catalog | RFC 9727 linkset indexing everything above. |
| /openapi.json | OpenAPI 3.1 covering every surface on this list. |
| /auth.md | Authentication guide. There is none to do — everything is public read-only, and this says so rather than leaving a client guessing. |
| /.well-known/oauth-protected-resource | RFC 9728 metadata declaring the endpoints open. It does not fabricate a login flow to satisfy a scanner — that sends clients hunting for a token endpoint that does not exist. |
|---|
| /license.xml | RSL 1.0. You choose whether search indexing, live AI answers and model training are permitted. Attribution — a real link back — is required either way. |
|---|---|
| robots.txt | Added to yours, not replacing it. The same three permissions as a Content-Signal line, plus an explicit welcome by name for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, CCBot and the rest. |
| Accept: text/markdown | Any page hands over a clean Markdown version of itself when an agent asks. Visitors still get the normal page, at the same address, unchanged. |
|---|
You're on WordPress · this page
$49
You control your own files · any PHP site
The WordPress edition costs more, which is the opposite of what most people expect — a plugin sounds like less work than a folder of files. It isn't. With the file pack, you do the find-and-replace, write the llms.txt content, rename the files and merge the .htaccess. The plugin does all of it for you, correctly, forever. The work moved from you to the software, and the price follows the work.
Four things this does not do, so you're not disappointed after paying:
Vary. It has
an off switch, and the plugin tells you so on the settings screen rather than letting you
discover it.Yes, if you can install plugins. Host, theme, domain extension, page count and page builder all make no difference. The only sites it can't work on are Wix, Squarespace, Shopify, Webflow and WordPress.com below the Business plan, because those platforms don't let any plugin add files to your site.
No. Everything is accurate the moment you activate it, generated from your site title, tagline, pages and posts. The settings screen only holds what WordPress cannot know.
No. Nothing is added to your pages and not a pixel changes. The documents live at their own addresses, and a page is only converted to Markdown when something explicitly asks for Markdown instead of HTML.
Not with the SEO plugins — it reads your per-post noindex settings from Yoast, Rank Math,
SEOPress and All in One SEO and honours them, and it points at whichever XML sitemap is
actually serving rather than assuming a path. Caching plugins are usually fine too; if
yours ignores Vary: Accept, switch off the Markdown feature and everything
else keeps working.
No, unless you deliberately switch that on, and it ships off. There is one optional write operation that lets an agent send you a message on a visitor's behalf; when enabled it is limited to 3 per sender per hour and 50 site-wide per day, and every message is stored in your admin as well as emailed. Everything else is read-only.
Every endpoint disappears cleanly. It writes nothing into your theme, your .htaccess or your web root, so nothing is left behind claiming your site has an MCP server when it doesn't.
Yes — every WordPress site you own or operate, including sites you build for clients. You just can't resell or redistribute the plugin itself.
Three ways. Visit yoursite.com/llms.txt and read it. Use the built-in
Endpoints checker. Or paste your domain into
isitagentready.com,
a free third-party scanner we don't run and can't influence, and get a score out of 100.
$49 once. Two-minute install. Works on your site.
Buy the WordPress edition