AuditAE – MCP Server & AI SEO
| 开发者 | aaronkaltman |
|---|---|
| 更新时间 | 2026年10月3日 02:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
https://auditae.app/api/mcp) to Claude, ChatGPT, Cursor or any other MCP client, and ask for changes in plain English. The agent gets 26 WordPress tools: list, read, draft, update and publish posts and pages, edit Yoast / Rank Math titles and descriptions, lay out pages in Gutenberg blocks, manage schema and FAQ schema, and curate /llms.txt. You choose what it may do: read, create drafts, publish, or write SEO settings. Every change is logged with its previous state, and one click on the Connect tab disconnects it. MCP is part of the optional AuditAE service ($5 free credit, no subscription).
Free AI search readiness, no account. The plugin is also a free AI SEO / AEO (Answer Engine Optimization) toolkit that makes your site easier for ChatGPT, Perplexity, Gemini and Google AI Overviews to read, trust and cite. It works the moment you activate, with no signup and no account, whether or not you ever use MCP.
Built for Elementor. Elementor pages are read from Elementor's own widget data, not the leftover copy in the post body, so the per-post checklist, Query Fan-Out coverage, the link checker and llms.txt all see what your visitors see. AI agents edit Elementor text in place, one-click internal links land inside your Elementor text widgets, and renaming an image updates it in Elementor image widgets too. On the block editor, synced patterns are read as part of every page that uses them, and AI edits keep FAQ and other blocks valid in the editor.
AI Readiness Score. One 0–100 number, with a letter grade, that summarizes how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, and Google AI Overviews — computed entirely from local signals (are citation bots blocked in robots.txt, FAQ and Article schema coverage, Organization schema, unresolved AI-bot 404s, content freshness, llms.txt). Every check that isn't passing shows exactly what to fix and how many points it's worth, and the score tracks a 7-day delta so you can see it climb as you ship fixes. Surfaced on its own tab and on the wp-admin Dashboard widget. A companion per-post AI Readiness checklist appears right in the editor sidebar — grading the post you're writing on an answer-first opening, question-shaped headings, FAQ + structured data, depth, and freshness, so you fix it before you publish.
1. AI Crawler Tracker. Identifies hits from ~30 AI search-engine crawlers — GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Perplexity-User, Bytespider, CCBot, Meta-ExternalAgent, Bingbot, and more. Get a real-time count of AI bot hits over the last 30 days, a by-bot breakdown with time-since-last-hit per bot, a per-day activity table, top crawled paths, one-click CSV export, and an at-a-glance wp-admin Dashboard widget. A built-in robots.txt audit flags any tracked AI bot your robots.txt is blocking — the silent killer of AI visibility. Answers the question Google Search Console can't: "Are AI engines actually reading my site?"
2. llms.txt Generator. Serves a live /llms.txt file at the root of your site, conforming to the llmstxt.org spec — a markdown manifest that helps LLM-powered tools find the right pages on your site. Builds defaults automatically from your public post types, with per-section customization, optional links list, and a one-click "Reset to defaults" if you want to start fresh.
3. Schema Graph. Per-post and site-wide schema.org JSON-LD injection. Add structured data for Organization, Article, Product, HowTo, FAQPage, BreadcrumbList — all linked together by @id so AI engines can resolve "this org wrote this article" without guessing. Designed to coexist with Yoast and Rank Math: when one of them is active, AuditAE defers the schema types they already emit (Organization, Article) and only adds the types they don't, so your pages never carry duplicate structured data. If your SEO plugin emits no Organization at all, AuditAE fills the gap with the one you saved.
4. IndexNow auto-ping. When you publish or update a post, the plugin notifies the IndexNow API so Microsoft Bing and the other participating engines learn the URL changed instead of waiting to discover it on their own. When each engine re-crawls is up to that engine. Bing's index also grounds AI answers such as Copilot's. A site ownership key is generated and served automatically (no manual setup), per-post noindex flags from Yoast/Rank Math are respected, and a "Submit all published URLs" button seeds the index in one shot for sites that installed the plugin after publishing. One submission is shared with every participating engine: Microsoft Bing, Yandex, Seznam.cz, Naver, Yep and Amazon. Google does not use IndexNow.
5. Image filename rename. A "Rename file" action in the Media library turns a generic IMG_4821.jpg into a descriptive, keyword-bearing red-running-shoes.jpg — the filename is one of the few image-SEO signals AI engines and image search actually read. It renames the original and every generated thumbnail size in one move, then rewrites the old URL to the new one inside your existing posts so your live images and srcset never break. Free, no account, gated by your normal WordPress permissions.
6. Query Fan-Out coverage. AI engines don't search for the phrase your reader typed. They split it into 8–12 parallel sub-queries, retrieve one passage per sub-query, and assemble the answer from those passages — so citations are won passage by passage, not page by page. A panel under the editor models the fan-out for the post you're writing (from your own focus keyword, categories, post titles and Organization schema — nothing leaves your site), splits your draft at its headings, and shows which sub-queries each passage actually answers. Missing ones sort to the top with the sub-query spelled out, so a vague "add more depth" becomes a specific "you never say what this costs". Sub-queries are grouped by five of the six documented fan-out types — implicit, comparative, entity-expanded, related and personalized. The sixth, reformulation, is left out because it can't be scored honestly (see the FAQ). Free, offline, and no account.
7. Broken internal links + orphaned content. The Links tab answers both halves of the same question. Broken internal links are links in your content pointing at pages of your own that no longer resolve — a dead end for a crawler, and crawl budget spent going nowhere. Rank Math charges for a broken link checker in PRO; Yoast removed theirs. This one runs entirely on your own site with no external requests, and is deliberately conservative: archives, custom post types, uploaded files, paginated URLs, ?p= shortlinks and paths already covered by one of your redirects are all resolved before anything is called dead, because a checker that flags a working link is worse than one that misses a broken one. Links pointing at drafts, private or trashed posts are listed separately — they work while you're logged in, which is exactly why they survive so long. Orphaned content is the same problem from the other end: the tab lists every published post and page that nothing else on your site links to. A page with no incoming internal links is hard for a crawler to reach and gives an AI engine no signal that it matters. Pick one and AuditAE shows which of your existing pages already say its name in ordinary prose, and offers to link the phrase for you in one click — wrapping exactly one occurrence and changing nothing else in the post. Suggestions are verified before they're offered, so the button never fails on you. Both of these are Premium features in the big SEO plugins; here they're free.
Plus FAQ schema injection. Add question-and-answer pairs to any post or page from the FAQ schema box in the editor — free, no account — and AuditAE publishes them as a schema.org FAQPage <script type="application/ld+json"> block on the post view. The pairs live in post_meta; your post content is not modified, and removing them is one click. If a Yoast or Rank Math FAQ block already covers the post, AuditAE stands down so the page never carries two FAQPage nodes.
No external service is required for any of the above. All data is stored locally — crawler hits in one small dedicated table (90-day retention, dropped on uninstall), everything else in wp_options. No telemetry.
Optional — pair with AuditAE (auditae.app). AuditAE is a separate paid service that measures whether AI engines cite your brand for the prompts your buyers ask. Pairing this plugin with an AuditAE account lets the AuditAE assistant (AEBOT) also draft posts, update existing posts, edit Yoast/Rank Math meta, manage the schema graph, curate /llms.txt, and edit your images end to end — rename files in bulk across the posts that matter, and write every image field (alt text, title, caption, description) — for you. On sites running the companion AuditAE AI Autopilot theme, AEBOT can additionally edit page copy, brand colors, and structured records (services, locations, FAQs, testimonials, team) in place, and your wp-admin dashboard shows live AI-citation, Analytics, and Search Console figures pulled from your AuditAE account. Pairing is fully optional; everything above remains free regardless. $5 free credit at signup, no subscription.
安装:
- Install and activate the plugin.
- Go to Settings → AuditAE. You'll land on the AI Readiness Score tab — a 0–100 grade, with a letter grade and 7-day trend, of how ready your site is to be read and cited by AI engines, with a one-click fix on every check that isn't passing yet.
- Open the AI crawlers tab to see which AI bots are reading your site (hits populate automatically as they crawl) and whether your robots.txt is blocking any citation engines like GPTBot, ClaudeBot, or PerplexityBot.
- Visit the llms.txt tab to review or edit the manifest served at
https://example.com/llms.txt. - (Optional) Visit the Connect to AuditAE tab to pair with an AuditAE account if you want the citation-audit and AEBOT writing features.
屏幕截图:
常见问题:
Do I need an AuditAE account to use the plugin?
No. The Crawler Tracker, llms.txt generator, schema graph, FAQ schema, internal linking, and Query Fan-Out coverage are all fully free and standalone. They work the moment the plugin is activated. The Connect to AuditAE tab is optional and only relevant if you want the paid citation-audit + AEBOT writing features.
Why does the broken link checker miss some dead links?
By design. It only reports links it can prove are dead, because the fix a user applies to a false positive is deleting a link that was working. Anything it can't positively classify is left out of the report rather than guessed at. It also checks internal links only — external link checking needs real HTTP requests to other people's servers, which is a separate feature with its own throttling and failure modes.
Are the fan-out sub-queries the real ones Google ran?
No, and the panel says so. Query fan-out is probabilistic and Google doesn't publish the sub-queries it generates, so nobody can show you the exact set — every tool in this space either models them or asks an LLM to guess. AuditAE models them from your own site: your focus keyword, your categories, your post titles, and your Organization schema. The wording won't match Google's, but the themes do, and that's what decides whether a passage of yours can be retrieved. Nothing is sent off your server to produce them.
Why do reformulations like "what is X" never appear in the list?
Because they can't be scored honestly. A reformulation restates your seed topic in different words, so there's no distinguishing term to look for — any on-topic post covers it by construction. Including such a row would mean either always passing it (meaningless) or reporting a post that opens with a textbook definition as missing its own definition (wrong). The gaps that matter live in the other five fan-out types, so those are what the panel shows.
Which AI bots does the Crawler Tracker identify?
GPTBot, OAI-SearchBot, OAI-AdsBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User, Bytespider, CCBot, cohere-ai, Diffbot, FacebookBot, Meta-ExternalAgent, Meta-ExternalFetcher, Bingbot, YouBot, Amazonbot, DuckAssistBot, PetalBot, TimpiBot, MistralAI-User, AI2Bot, iaskspider, AwarioRssBot and AwarioSmartBot. The list is curated to AI engines; we deliberately exclude Googlebot because that's already covered by Google Search Console. Google-Extended and Applebot-Extended aren't on it because they aren't crawlers: they're robots.txt tokens that Googlebot and Applebot read to decide whether your content may be used for AI, so no request ever carries them. The robots.txt audit still checks both.
Will the plugin slow down my site?
No. Crawler detection is a single substring scan of the User-Agent on template_redirect; only a matching AI bot adds one row to a small indexed table, which is kept to 90 days and capped at 200,000 rows (oldest pruned first). The /llms.txt response is cached in a transient and regenerated only when you save changes. Schema injection runs once per page render in wp_head. On any reasonable host, the per-request cost is well under a millisecond.
Where is data stored?
Locally, on your own site — no telemetry. Apart from IndexNow pings (changed URLs only; on by default, see External Services), nothing leaves your site unless you pair it with AuditAE. AI crawler hits live in one small custom table, {prefix}auditae_crawler_hits (pruned to 90 days and 200,000 rows, dropped on uninstall); everything else is in wp_options: auditae_crawler_rollup (per-bot first-seen + lifetime totals), auditae_redirects (redirect rules), auditae_audit_log (action log for the optional Connect tab), auditae_llms_txt_config (llms.txt manifest), auditae_organization_schema (site-wide schema), auditae_score_history / auditae_score_best (AI Readiness Score trend), auditae_score_email (the optional digest opt-in), auditae_link_index (the internal link graph), and IndexNow settings — plus per-post meta _auditae_schema_graph and _auditae_faq_schema. Uninstalling removes all of it.
Does the schema graph conflict with Yoast or Rank Math?
No. When an SEO plugin is active, AuditAE leaves the node types it owns (Organization, WebSite, Article, BreadcrumbList…) to that plugin and emits only the types it doesn't cover, such as HowTo or Product. The one exception: if your SEO plugin demonstrably emits no Organization or Person node and you've saved one in AuditAE, AuditAE emits yours so the site isn't left without a publisher entity.
What does the AuditAE connection cost?
Pairing is free. AuditAE itself is pay-per-use: AI-engine checks cost 5¢–12¢ each depending on the engine, WordPress edits 1¢–25¢, and reads are free. New accounts get $5 of credit and there is no subscription. Sign up at https://auditae.app.
How do I revoke the AuditAE connection?
Settings → AuditAE → Connect to AuditAE tab → Disconnect. The bearer token is wiped instantly.
Does AuditAE conflict with Yoast SEO or Rank Math?
No — it's designed to run alongside them. AuditAE is an AI-search toolkit, not an SEO plugin: it never changes your title tags, meta descriptions, canonical URLs, Open Graph tags, or sitemaps, so it won't trigger a "you have two SEO plugins active" warning. Where the two genuinely overlap — structured data and IndexNow — AuditAE detects your SEO plugin and steps aside: it leaves Organization and Article schema to that plugin (so you never get duplicate JSON-LD; AuditAE only fills in Organization when your SEO plugin emits none), skips FAQ schema on posts that already use a Yoast/Rank Math FAQ block, and turns its IndexNow auto-ping off if Rank Math (or a standalone IndexNow plugin) is already submitting. You keep AuditAE's AI-specific features — crawler tracking, AI Readiness Score, llms.txt — on top of your existing SEO setup. The settings page shows a notice describing exactly what's been deferred.
What is IndexNow and do I need to set it up?
IndexNow is an open protocol that lets your site tell search engines "this URL just changed" instead of waiting for them to re-crawl on their own. The participating engines are Microsoft Bing, Yandex, Seznam.cz, Naver, Yep and Amazon, and one submission reaches all of them. Bing's index also feeds AI answers such as Copilot's, so faster indexing means faster eligibility to be cited. There's nothing to set up — the plugin generates and serves the required ownership key automatically, and starts pinging on your next publish. To turn it off, go to Settings → AuditAE → AI Crawlers and uncheck auto-ping. Google does not use IndexNow (it has no public submission API), so this complements rather than replaces normal Google crawling.
更新日志:
- New name on WordPress.org, AuditAE – MCP Server & AI SEO, and a description that leads with connecting Claude and ChatGPT to WordPress over MCP. The plugin, its settings and your connection are unchanged.
- Organization schema: Rank Math outputs nothing until its account step is done (connect a free account, or skip it). Until AuditAE had checked your homepage, it assumed such a site already had Rank Math's Organization and held back the one you saved. It now emits yours, and the AI Readiness Score agrees.
- Crawler log: adds OpenAI's OAI-AdsBot. Google-Extended and Applebot-Extended are no longer counted as crawlers, because they are robots.txt tokens that no request carries; the robots.txt audit still checks them.
- IndexNow wording lists every participating engine (Bing, Yandex, Seznam.cz, Naver, Yep, Amazon) and no longer promises how fast engines re-crawl. The Query Fan-Out description now says it scores five of the six fan-out types.
- AI Readiness Score: on a connected site, fix buttons now match the permissions you've granted AuditAE. When AEBOT isn't allowed to make a change, the button says "Show me the exact edits" and a second link takes you to the permission that would let it apply them.
- Fix buttons open AEBOT on this site in your AuditAE workspace.
- New: a link to a free AI citation check (ChatGPT, Perplexity, Gemini, AI Overviews) on the Score tab and the Dashboard widget. No account needed; it opens auditae.app with your site name and domain filled in.
- Help & docs links on Settings → AuditAE and the Plugins screen. Clearer permission descriptions.
- Connection: sites running a JWT authentication plugin (for example "JWT Authentication for WP REST API" or "JWT Auth") no longer reject AuditAE's requests with "Wrong number of segments". Only AuditAE's own routes are affected, only when the request carries your valid AuditAE token, and nobody is logged in by it. Other REST routes keep the JWT plugin's rules.
- Crawlers: AI bots reading your /llms.txt and your IndexNow key file now appear in the crawler log (those files are served before the log ran). The llms.txt tab shows how many times AI crawlers read your file in the last 30 days.
- Query Fan-Out: how-to post titles such as "Make pour-over coffee" are no longer used as comparison topics, so you won't see sub-queries like "X vs make pour-over coffee".
- A link to leave a WordPress.org review now appears when you reach a new personal-best grade or add a suggested internal link, and as a footer line on Settings → AuditAE. It never appears as an admin notice and stops once you have followed it.
- Security: Elementor find-and-replace edits may no longer add anything WordPress's content filter would strip.
- Crawler log capped at 200,000 rows; bots WordPress redirects are logged with their 301.
- Fixes to redirects, image renames, the internal-link graph and the AI Readiness Score's Organization check.