42A AI Visibility – Agentic Enablement Layer (AEL)

FAQ

What is AI Visibility?

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 users ask relevant questions.

What is GEO?

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 and, with a free 42A account, adds actionable GEO recommendations.

How does MCP help AI agents?

MCP (Model Context Protocol) is an open standard that lets AI agents query a site in a structured way instead of scraping HTML. This 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 support MCP can find, understand and interact with your content directly and reliably.

Which AI search engines are supported?

The agent layer is built on open standards (markdown, llms.txt, MCP), so any AI engine or agent can consume it – including ChatGPT, Claude, Gemini, Perplexity, Copilot and 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 AI assistants.

Do I need a 42A account?

No. The entire agent layer (markdown, llms.txt, MCP server, local checks) works forever without an account. A free 42A account adds the full GEO vitals report and the AI Visibility dashboard: mentions, sentiment, share of voice, competitor benchmarking and prompt-level analysis.

Does it work with ChatGPT?

Yes. The markdown layer, llms.txt and the MCP server make your content easy for ChatGPT and OpenAI’s crawlers (GPTBot, OAI-SearchBot) to read and cite, and the robots.txt audit verifies they are not blocked. With a connected 42A account you can also monitor how ChatGPT mentions your brand.

Does it support Claude?

Yes. Claude and Anthropic’s crawlers (ClaudeBot) can consume your markdown pages, llms.txt and the MCP server, and Claude is one of the assistants tracked in the 42A AI Visibility dashboard.

Does it support Gemini?

Yes. Gemini and Google’s AI crawlers (Google-Extended) can read the same agent layer, and Gemini is tracked in the 42A AI Visibility dashboard.

Does it improve AI rankings?

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

Is it compatible with any WordPress theme?

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. It is compatible with classic themes, block themes and page builders alike.

What if my site already has an llms.txt?

The plugin checks first and never overrides content your site already provides. If an llms.txt, llms-full.txt or MCP discovery document already exists – as a real file on your server or served by another plugin – 42A AI Visibility detects it and leaves it untouched, generating only the pieces your site is missing. The Agent Layer checks show which files are generated by the plugin and which existing ones are being respected. If you remove the existing file later, the plugin starts serving its own version automatically.

Does the plugin slow down my site?

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

Can other plugins add MCP tools?

Yes – use the ael42a_mcp_tools filter. Tools flagged requires_auth are rejected until an authenticated transport ships in a future version.

Does it work with WooCommerce?

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

What about multisite?

v1 supports per-site activation only. Network-wide activation is not officially supported yet.