The AI visibility plugin that makes WordPress agent-ready.

Yes. The entire agent layer - the markdown twin of every page, llms.txt and llms-full.txt, the public MCP server, the local status checks and the AI-crawler audit - is free forever, licensed GPL-2.0-or-later, and works without an account, an email address or a sign-up. Connecting the site to 42A is a separate, optional step that adds the full GEO vitals report and the AI Visibility dashboard.

AI Visibility is how often and how prominently your website and brand appear in AI-generated answers, in tools like ChatGPT, Claude, Gemini and Perplexity. Just as SEO rankings measure your presence in classic search results, AI Visibility measures whether AI assistants find, understand, mention and cite your site when someone asks a relevant question.

GEO (Generative Engine Optimization, also called AI SEO or LLM SEO) is the practice of optimizing your site so generative AI engines can read, understand and cite it. Classic SEO signals still matter, but GEO adds new ones: llms.txt, clean machine-readable content, structured data, AI-crawler access in robots.txt, and agent endpoints like MCP. This plugin covers that technical layer for you on its own, and connecting to 42A adds prioritized recommendations on top.

No, and the plugin is not a trial or a teaser. The whole agent layer - markdown twins, llms.txt, llms-full.txt, the MCP server and discovery, the local self-tests and the AI-crawler audit - runs forever without an account, and the plugin makes zero external requests until you explicitly click "Connect to 42A". Connecting is optional and adds the outside-in view a plugin on your own server cannot produce: the full ~30-check GEO report and the AI Visibility dashboard, with mentions, sentiment, share of voice, competitor benchmarking and prompt-level analysis.

No plugin can guarantee placement in AI answers, and we will not pretend otherwise. What this one does is remove the technical barriers that stop AI engines from reading your site at all - no llms.txt, HTML-only content, blocked or unguided crawlers, no agent endpoints - and, with a 42A account, give you concrete prioritized fixes. Sites that are easy for AI to read, understand and verify are far more likely to be cited.

Yes, and it is built to sit alongside Yoast rather than compete with it. Yoast keeps doing classic SEO - titles, meta descriptions, canonicals, sitemaps, schema - and 42A AI Visibility adds the agent layer on top of it: markdown twins, llms.txt and the MCP server. The plugin works at the request layer and never modifies your theme output or anything Yoast writes into your pages. If Yoast is already generating an llms.txt, the plugin detects it and leaves it exactly as it is instead of overriding it. It can only ever add signals an AI engine can read - it never removes or weakens one.

No. Markdown documents are generated lazily, cached in transients and invalidated on save. The markdown, llms.txt and MCP paths short-circuit before theme rendering, so normal HTML page loads are untouched.

Nothing, until you connect. When you click "Connect to 42A" it sends a single-use pairing code, your site URL, the plugin and WordPress versions, and the list of enabled agent-layer capabilities. While connected it sends your site token to fetch your status and vitals. Telemetry is a separate opt-in checkbox, off by default; when enabled it sends one daily aggregate - date and counts of MCP requests, markdown hits, llms.txt hits and per-tool calls - and never any content, URLs or personal data. Disconnecting or uninstalling revokes the token.

Yes, and the same way it works with Yoast: Rank Math carries on handling classic SEO while 42A AI Visibility runs beside it and adds the agent layer. Nothing in your Rank Math settings, page output or sitemaps is touched, and any llms.txt or MCP discovery document your setup already serves is detected and respected rather than replaced. The two stay in sync and the plugin only ever improves what AI engines can see - it cannot hurt your existing SEO.

The agent layer is built on open standards - markdown, llms.txt and MCP - so any AI engine or agent can consume it, including ChatGPT, Claude, Gemini, Perplexity and Copilot, along with AI crawlers such as GPTBot, ClaudeBot and PerplexityBot. The robots.txt audit covers 87 known AI bots, and the 42A platform tracks your visibility across the major assistants.

Yes. The markdown layer, llms.txt and MCP server make your content easy for ChatGPT and OpenAI’s crawlers (GPTBot, OAI-SearchBot), for Claude and ClaudeBot, and for Gemini and Google-Extended to read and cite - and the robots.txt audit verifies none of them are blocked. With a connected 42A account you can also monitor how each of those assistants mentions your brand.

MCP (Model Context Protocol) is an open standard that lets an AI agent query a site in a structured way instead of scraping HTML. The plugin runs a public, read-only MCP server exposing tools like search_content, get_page and list_recent_posts - plus product tools when WooCommerce is active - discoverable at /.well-known/mcp.json. Agents that speak MCP can then search, fetch and navigate your content directly and reliably.

Yes. Markdown responses are served with a Vary: Accept header, so a CDN caches the HTML and markdown versions of a URL separately instead of serving one in place of the other, and llms.txt, llms-full.txt and the MCP discovery documents are ordinary cacheable GET responses. Worth knowing: a CDN or firewall can block AI crawlers before a request ever reaches WordPress - which is exactly what the connected GEO report’s CDN AI-block detection check looks for.

Your wp-admin gains data, and nothing else changes. The plugin sends a single-use pairing code along with your site URL, the plugin and WordPress versions and the list of enabled agent-layer capabilities, and receives a site token scoped narrowly to reading your vitals and writing telemetry. The GEO Vitals and AI Visibility tabs then start filling in: the full ~30-check report with a fix per check, plus your brand’s mentions, sentiment and share of voice across ChatGPT, Claude, Gemini and Perplexity - graded by 42A’s crawlers from the outside rather than self-tested on your server. The agent layer itself is untouched: same endpoints, same output, same performance. Telemetry stays off unless you tick the separate opt-in box, and one click disconnects and revokes the token.

Yes. The plugin works at the request layer: markdown, llms.txt and MCP responses are served before theme rendering even starts, and nothing in your theme’s HTML output is modified. Classic themes, block themes and page builders all work the same as they do today.

It is left alone. The plugin checks first and never overrides content your site already provides - whether that is a real file on your server or output from another plugin such as an SEO suite. It generates only the pieces you are missing, and the Agent Layer checks show which files it serves and which existing ones it is respecting. Remove the existing file later and the plugin starts serving its own version automatically.

Yes. Product pages get a structured details section in their markdown (price, currency, SKU, stock, categories), llms.txt includes your product categories, and the MCP server gains search_products and get_product tools automatically when WooCommerce is active.

Plugins such as Automattic’s wordpress-mcp expose authenticated admin automation - creating posts, managing settings - on your behalf. 42A AEL is the opposite: a zero-config, anonymous, read-only public-content MCP server, serving the same data any visitor sees, bundled with the whole agent layer of markdown, llms.txt and vitals. The two can coexist; they use different routes.

Yes, through the ael42a_mcp_tools filter. Each tool definition carries a name, description, JSON Schema for its input and a callback. Tools flagged as requiring authentication are rejected until an authenticated transport ships in a future version.

Per-site activation is supported. Network-wide activation is not officially supported yet.