Increase your WordPress site&#039;s AI Visibility with actionable SEO &amp; GEO recommendations and built-in MCP support for AI search engines.

42A AI Visibility – Agentic Enablement Layer (AEL)

Increase your AI Visibility in ChatGPT, Claude, Gemini, Perplexity and other AI search engines with 42A AI Visibility, powered by the Agentic Enablement Layer (AEL). Monitor how your website appears in AI-generated answers, receive actionable SEO and GEO recommendations, and enable built-in MCP support to help AI agents discover, understand and interact with your content. Connect your free 42A account to unlock advanced AI Visibility reports, competitor benchmarking, prompt-level analysis and continuous optimization.
The Agentic Enablement Layer ships on activation, with zero configuration:
<ul>
<li>Markdown twin of every public page &#8211; append <code>?format=markdown</code> to any URL (or use the <code>.md</code> suffix, or send <code>Accept: text/markdown</code>) and get a clean markdown version with YAML frontmatter. Every HTML page advertises it via <code>&lt;link rel="alternate" type="text/markdown"&gt;</code> and a <code>Link:</code> header.</li>
<li>llms.txt and llms-full.txt &#8211; a spec-compliant llms.txt map of your key pages (front page, navigation, recent posts, WooCommerce categories) with markdown links, and a byte-capped llms-full.txt with full page content, served at your site root.</li>
<li>Public read-only MCP server &#8211; a stateless Model Context Protocol (JSON-RPC 2.0, Streamable HTTP) endpoint at <code>/wp-json/42a/v1/mcp</code>, discoverable at <code>/.well-known/mcp.json</code>, <code>/.well-known/mcp</code>, <code>/.well-known/mcp/server-card.json</code> and <code>/.well-known/mcp-server</code> (all current draft discovery specs). Tools: <code>get_site_info</code>, <code>search_content</code>, <code>get_page</code> (markdown), <code>list_recent_posts</code>, <code>list_categories</code>, plus <code>search_products</code> and <code>get_product</code> when WooCommerce is active.</li>
<li>Local GEO vitals &#8211; the Agent Layer tab in wp-admin self-tests all endpoints, detects your sitemap and audits robots.txt against 87 known AI bots (training, search and agentic tiers), and shows local agent-traffic counters.</li>
<li>Full GEO vitals report (optional, free account) &#8211; connect a free 42A account for the full ~30-check AI SEO / GEO report with per-check scores and fixes, refreshed by 42A&#8217;s crawlers.</li>
</ul>
<h4>Why GEO / AI SEO matters</h4>
When someone asks an AI assistant &#8220;what&#8217;s the best X&#8221; or &#8220;does this store sell Y&#8221;, the assistant answers from the sites it can actually read and query. Classic SEO signals still matter, but AI search adds new ones: llms.txt, clean markdown content, structured data, AI-crawler access in robots.txt, and machine-readable endpoints like MCP. This plugin covers that layer for you &#8211; it&#8217;s SEO for the AI era.
<h4>How is this different from admin-automation MCP plugins?</h4>
Plugins like Automattic&#8217;s <code>wordpress-mcp</code> expose authenticated admin automation (create posts, manage settings). 42A AEL is the opposite: a zero-config, anonymous, read-only public-content MCP server &#8211; the same data any visitor sees, packaged for agents &#8211; bundled with the whole agent layer (markdown, llms.txt, vitals). The two can coexist; they use different routes.
<h4>Privacy first</h4>
The plugin makes zero external requests until you explicitly click &#8220;Connect to 42A&#8221;. Agent-traffic counters are stored locally only. Telemetry reporting to 42A is opt-in and default off.
<h3>External Services</h3>
This plugin can connect to the 42A API (<code>api.42a.ai</code>), operated by 42A. No request is ever made without explicit user action:
<ul>
<li>Register (<code>POST /api/v1/integrations/wordpress/register</code>) &#8211; only when you click &#8220;Connect to 42A&#8221; or paste a pairing code. Sends: the pairing code, your site URL, plugin version, WordPress version and the list of enabled agent-layer capabilities.</li>
<li>Site status (<code>GET /api/v1/integrations/wordpress/site</code>) and Vitals (<code>GET /api/v1/integrations/wordpress/vitals</code>) &#8211; only while connected, when the GEO Vitals tab loads or you click refresh. Sends: your site token.</li>
<li>Telemetry (<code>POST /api/v1/integrations/wordpress/telemetry</code>) &#8211; only while connected and after you enable the separate opt-in checkbox (default off). Sends one daily aggregate: date, MCP request count, markdown hit count, llms.txt hit count and per-tool call counts. Never any content, URLs or personal data.</li>
<li>Disconnect (<code>POST /api/v1/integrations/wordpress/disconnect</code>) &#8211; when you click Disconnect or uninstall the plugin, to revoke the site token.</li>
</ul>
Service terms: https://www.42a.ai/terms &#8211; Privacy policy: https://www.42a.ai/privacy

Alternative Plugins for

Discover the Lists with 42A AI Visibility – Agentic Enablement Layer (AEL)