42A AI Visibility - Agentic Enablement Layer (AEL)
| 开发者 | alon42a |
|---|---|
| 更新时间 | 2026年7月29日 00:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Markdown twin of every public page - append
?format=markdownto any URL (or use the.mdsuffix, or sendAccept: text/markdown) and get a clean markdown version with YAML frontmatter. Every HTML page advertises it via<link rel="alternate" type="text/markdown">and aLink:header. - llms.txt and llms-full.txt - 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.
- Public read-only MCP server - a stateless Model Context Protocol (JSON-RPC 2.0, Streamable HTTP) endpoint at
/wp-json/42a/v1/mcp, discoverable at/.well-known/mcp.json,/.well-known/mcp,/.well-known/mcp/server-card.jsonand/.well-known/mcp-server(all current draft discovery specs). Tools:get_site_info,search_content,get_page(markdown),list_recent_posts,list_categories, plussearch_productsandget_productwhen WooCommerce is active. - Local GEO vitals - 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.
- Full GEO vitals report (optional, free account) - connect a free 42A account for the full ~30-check AI SEO / GEO report with per-check scores and fixes, refreshed by 42A's crawlers.
wordpress-mcp expose authenticated admin automation (create posts, manage settings). 42A AEL is the opposite: a zero-config, anonymous, read-only public-content MCP server - the same data any visitor sees, packaged for agents - bundled with the whole agent layer (markdown, llms.txt, vitals). The two can coexist; they use different routes.
Privacy first
The plugin makes zero external requests until you explicitly click "Connect to 42A". Agent-traffic counters are stored locally only. Telemetry reporting to 42A is opt-in and default off.
常见问题:
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.
更新日志:
- The admin interface is now translatable and ships with Spanish (es_ES), French (fr_FR) and Brazilian Portuguese (pt_BR) translations in addition to English. The plugin automatically uses your WordPress site language; you can override any string with your own translation in wp-content/languages/plugins.
- New Contact tab: reach 42A support directly from wp-admin. Includes a one-click email link plus a quick composer that opens your mail app pre-filled (with your site URL and plugin/WordPress version) so you never have to leave the dashboard to ask for help.
- Security: the "Connect to 42A" return flow is now gated by a single-use state token minted when you start the flow, protecting against cross-site request forgery.
- Lengthened the plugin's internal name prefixes (
ael42a_/AEL42A) to comply with WordPress.org naming guidelines. If your site was connected, reconnect it from the Account tab after updating.
- Corrected the Contributors list to the plugin owner's WordPress.org username. No functional changes.
- The plugin now detects content your site already provides before generating its own. If an llms.txt, llms-full.txt or MCP discovery document already exists (a real file on the server or one served by another plugin), 42A AI Visibility respects it and does not override it. Detection runs on activation, daily and whenever you re-run the Agent Layer checks; the checks report which files are respected. Developers can force generation per artifact via the
ael42a_respect_existingfilter.
- Plugin renamed to "42A AI Visibility - Agentic Enablement Layer (AEL)" with a refreshed description and tags. No functional changes.
- Expanded FAQ covering AI Visibility, GEO, MCP, supported AI search engines and theme compatibility.
- Plugin slug renamed from
42a-aeltoael-42a(folder, main file, text domain and internal prefixes) to comply with WordPress.org naming rules - prefixes may not start with a digit. Functionality is unchanged. - If you are upgrading from 1.0.5 or earlier: deactivate and delete the old "42A AEL" plugin, install this version fresh, then reconnect your 42A account from the Account tab (settings and tokens do not carry over across the slug change).
- New Account tab: all connection management in one place - connect / manual pairing, organization, brand, who connected the site and when, domain-verification status, refresh and disconnect.
- The plugin now detects when a site is disconnected from the 42A platform and clears its local connection automatically (on the next data fetch and via a daily sync).
- New AI Visibility tab: a read-only snapshot of your 42A brand dashboard - visibility score, total mentions, sentiment, share of voice, mention coverage, trend charts and your analysis projects.
- The Agent Layer tab now shows your live AI-visibility metrics in the sidebar once connected.
- The connect teaser now previews the same dashboard stats.
- The 42A logo is now the wp-admin menu icon, and plugin copy uses plain typography throughout.
- API error notices now include the HTTP status code, so failures are diagnosable at a glance.
- Redesigned wp-admin UI in the 42A brand: light design-system theme with the 42A logo, lime accents and brand colors (all assets bundled locally).
- Fix "Missing Bearer token" errors on hosts that strip the Authorization header from outgoing requests - the site token is now also sent as an X-42a-Site-Token header.
- Connected sites are now always tracked under your organization's main brand (no brand picker in the connect flow).
- Organization name and domain-verification status now display correctly on the GEO Vitals tab.
- New GEO insights preview in wp-admin showing what connecting a free 42A account unlocks.
- MCP discovery now served at every emerging well-known path -
/.well-known/mcp.json,/.well-known/mcp(SEP-1960 manifest),/.well-known/mcp/server-card.json(SEP-1649 server card) and/.well-known/mcp-server(IETF draft) - so MCP clients implementing any of the draft discovery specs can find the server.
- Initial release: markdown layer (?format=markdown, .md, Accept negotiation), llms.txt + llms-full.txt, stateless read-only MCP server + /.well-known/mcp.json discovery, local GEO vitals with robots.txt AI-bot audit, agent-traffic counters, optional 42A connect flow with domain verification, opt-in telemetry.