AI-Ready WP

agents.json is an emerging standard for AI agent discovery. It tells AI systems what your website offers and how to interact with it — like a machine-readable menu of your site's capabilities.

llms.txt is a structured text file that gives LLMs (Large Language Models) a concise overview of your website content — like a sitemap for AI.

A2A (Agent-to-Agent) is a protocol by Google (now under the Linux Foundation) for AI agent interoperability. The agent-card.json file lets agents discover and communicate with your site.

For most sites, yes. AI-Ready WP provides meta titles/descriptions, OpenGraph, Twitter Cards, canonical URLs, robots meta, XML Sitemaps, and focus keyword analysis. If you need advanced features like redirect managers or internal linking suggestions, keep a dedicated SEO plugin. AI-Ready WP notices it and stands down.

Yes. When Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Squirrly, SmartCrawl or Slim SEO is active, AI-Ready WP leaves titles, descriptions, social tags, the sitemap and the Organization, WebSite and breadcrumb schemas to that plugin, so your pages do not end up with two of each. The FAQ schema stays, none of those plugins builds it from your headings. The settings page says which plugin it found, and a checkbox brings the output back if you want it. The AI Discovery features (agents.json, llms.txt, JSON-LD, robots.txt, IndexNow) are not affected. Other SEO plugins can be added with the airewp_competing_seo_plugin filter.

Yes. If WooCommerce is active, the plugin automatically adds product catalog tools to agents.json, making your products discoverable by AI agents.

AI assistants like ChatGPT, Claude, and Perplexity are increasingly used to find businesses and services. If your site isn't AI-discoverable, you're invisible to this growing channel. AI-Ready WP makes your site speak the language AI agents understand.

Yes. Connect your AI through the hosted MCP server at wp.studiomeyer.io; the settings page lists the five steps. Reading is free: score and checks, settings, pages with their SEO fields, robots.txt, crawler statistics and a diagnosis with fixes. Writing needs AI-Ready WP Pro on this site: settings, titles and descriptions per page, rebuilds and IndexNow pings, plus the SEO tools. Every change your AI makes goes through the same validation as the settings page, and it needs an administrator's application password, which you can revoke in your profile at any time.

The only external connection is IndexNow (optional), which notifies search engines about content changes. All other features work entirely locally. See the Third-Party Services section below.

All of them, by default. robots.txt names 27 AI crawlers (GPTBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, Applebot, Meta-ExternalAgent, Amazonbot, DuckAssistBot, the Mistral crawlers and more) and allows each one explicitly, with a Content-Signal line that says what they may do with your content. A crawler reads only the group that names it, so every group repeats your site's own Disallow rules; naming a bot never opens a directory you keep closed. A bot that another plugin or a hand-written rule already addresses is left alone.

Yes. The AI Bot Policy section has two checkboxes: one turns away the training crawlers (your content then stays out of future models), the other the retrieval crawlers (your site then no longer appears in AI answers; not recommended). The Content-Signal line follows your choice.

No. The plugin writes agents.json, agent-card.json, agent.json and mcp.json into the .well-known directory of your site, and llms.txt and llms-full.txt into the site root, and when that works your web server hands them out without starting PHP. When it cannot write there, the same documents are built from your settings and content instead, the two text files from a cache that is refreshed whenever your content changes. Visitors and AI crawlers get exactly the same answer either way. The only difference is a little PHP per request, so it is worth fixing, but nothing is broken while you do.

The .well-known directory in the root of your site has to belong to the user your PHP runs as, usually www-data, nginx, apache or your hosting account name, with mode 755. The plugin writes files into it with mode 644. If the directory does not exist yet, the site root has to be writable so the plugin can create it. On servers with a Let's Encrypt certificate this directory very often belongs to root, because certbot created it before WordPress ever got there. That is the single most common reason for a write failure. The settings page names the directory, the owner and the PHP user, and gives you the exact chown command to hand your host.

That is a different problem from a failed write, and the settings page tells the two apart. A 404 means something in front of WordPress is answering the request. On nginx it is almost always a location block for /.well-known/ left behind by the SSL setup, which serves that path straight from disk and never reaches PHP. Ask your host to restrict that block to /.well-known/acme-challenge/. The rest of /.well-known/ then reaches WordPress again and the documents answer.