AuditAE – MCP Server & AI SEO

Description

Connect Claude and ChatGPT to WordPress over MCP (Model Context Protocol). Pair this plugin with an AuditAE account, add the hosted AuditAE MCP server (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: MCP reads are free; edits are 5¢ each (25¢ for a designed page), and new accounts get $5 of credit with 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, including Elementor 4’s atomic Heading, Paragraph and Button widgets, 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, for how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini and Google AI Overviews, computed from local signals: citation bots blocked in robots.txt, FAQ and Article schema coverage, Organization schema, AI-bot 404s, freshness and llms.txt. Every failing check says what to fix and what it’s worth, and a 7-day delta shows the score climb. A companion per-post checklist in the editor sidebar grades the post you’re writing on an answer-first opening, question-shaped headings, FAQ and structured data, depth and freshness.

1. AI Crawler Tracker. Identifies hits from ~30 AI crawlers — GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Perplexity-User, Bytespider, CCBot, Meta-ExternalAgent, Bingbot and more. See the AI bot hits that reached WordPress over the last 30 days (pages served from a page cache never reach the plugin, so treat it as a minimum; see the FAQ), a by-bot breakdown with last-seen times, daily activity, top crawled paths, CSV export and a Dashboard widget. A built-in robots.txt audit flags any tracked AI bot your robots.txt blocks. It answers what 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. Schema.org JSON-LD without touching your theme. Free, with no account: a site-wide Organization block you fill in once on the Schema tab; per-post Article, Blog post, HowTo or Product schema from the Schema box in the editor (blank fields fall back to the post’s title, excerpt and author, dates, URL and image are filled in on save, and a preview shows the exact JSON-LD); and per-post FAQPage schema from the FAQ box. On a paired site, AEBOT does the same in bulk and adds BreadcrumbList. Designed to coexist with Yoast, Rank Math, All in One SEO and SEOPress: AuditAE defers the types your SEO plugin already emits (Organization, Article), leaves Product to WooCommerce on product pages, and never outputs duplicate structured data. If your SEO plugin emits no Organization at all, AuditAE fills the gap with the one you saved; if your theme or another plugin already outputs one, AuditAE holds yours back.

4. IndexNow auto-ping. When you publish or update a post, the plugin notifies the IndexNow API so Microsoft Bing, Yandex, Seznam.cz, Naver, Yep and Amazon learn the URL changed instead of waiting to discover it (Google does not use IndexNow; Bing’s index also grounds AI answers such as Copilot’s). Changed URLs are queued and sent in batches a couple of minutes later, so a bulk edit or an import costs a few requests, not one per post. The site key is generated and served automatically, password-protected and noindex posts (Yoast, Rank Math, SEOPress, AIOSEO) are skipped, submissions pause on staging sites and while search engines are discouraged, and “Submit all published URLs” seeds the index in one shot.

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 in your existing posts, Elementor pages and page settings, block widgets, theme header images, and the social-share images set in Yoast, Rank Math or SEOPress, so your live images, srcset and share cards never break. Free, no account, gated by your normal WordPress permissions.

6. Query Fan-Out coverage. AI engines split the reader’s question 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. A panel under the editor models the fan-out for the post you’re writing (from your focus keyword, categories, titles and Organization schema; nothing leaves your site), splits your draft at its headings and shows which sub-queries each passage answers. Missing ones sort to the top, so “add more depth” becomes “you never say what this costs”. It scores five of the six documented fan-out types (implicit, comparative, entity-expanded, related, personalized); reformulation can’t be scored honestly (see the FAQ). Free, offline, no account.

7. Broken internal links + orphaned content. The Links tab lists links in your content that point at pages of your own that no longer resolve, a dead end for a crawler. Rank Math charges for a broken link checker in PRO; Yoast removed theirs. This one runs on your own site with no external requests and is deliberately conservative: archives, custom post types, files, paginated URLs, ?p= shortlinks and redirected paths are resolved before anything is called dead. Links to drafts, private or trashed posts are listed separately. Orphaned content is the other end of the problem: every published post and page nothing else links to. Pick one and AuditAE shows which of your pages already mention it in ordinary prose and links the phrase in one click, changing nothing else. The link graph rebuilds in the background after your edits, so the tab opens without waiting and says when a rebuild is still running. Both are Premium features in the big SEO plugins; here they’re free.

8. Redirects (AI-bot 404 → 301). When an AI crawler asks for a page that no longer exists, the Redirects tab lists that dead URL so you can 301 it to the page that replaced it, so the bot lands somewhere useful and the old URL’s link credit isn’t lost. Suggestions come straight from the AI crawler log, and scanner probes (.env, .git, wp-config backups) are left out. You can also add your own 301 or 302 rules, or start one from a dead path on the Links tab. A rule only fires on a URL that returns 404, so it can never hijack a page that still exists, and each rule counts its hits. Free, no account.

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 the post already gets FAQPage schema from somewhere else (a Yoast, Rank Math, All in One SEO or SEOPress FAQ block, an Elementor Accordion or Toggle with its FAQ Schema switch on, or Rank Math’s Schema Builder), AuditAE stands down so the page never carries two FAQPage nodes, and the AI Readiness Score counts the post as covered.

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 lets its assistant (AEBOT) also draft and update posts, edit Yoast/Rank Math meta, manage the schema graph, curate /llms.txt, and rename and describe your images in bulk. On sites running the companion AuditAE AI Autopilot theme it can also edit page copy, brand colors and structured records, and your wp-admin dashboard shows live AI-citation, Analytics and Search Console figures. Pairing is optional; everything above stays free. $5 free credit at signup, no subscription.

External Services

This plugin connects to two external services: IndexNow, and AuditAE when you pair the site. It also downloads images from URLs AuditAE supplies, as described below.

IndexNow (https://api.indexnow.org) — On by default; toggle off any time.
When the IndexNow feature is enabled, the plugin notifies the IndexNow API after you publish or update a public post or page (changed URLs are queued and sent together a couple of minutes later) and when you click “Submit all published URLs”. Nothing is sent from staging or development sites, or while Settings → Reading discourages search engines. Each request sends only: the URL(s) that changed, your site’s hostname, and a randomly generated site-ownership key (served as a verification file at your site root). No post content, personal data, analytics, or telemetry is transmitted. IndexNow is an open protocol operated by the participating search engines (Microsoft Bing, Yandex, Seznam.cz, Naver, Yep and Amazon); one submission notifies all of them. You can turn auto-ping off under Settings → AuditAE → AI Crawlers.

• IndexNow documentation: https://www.indexnow.org/documentation
• Bing terms of use: https://www.bing.com/webmaster/help/indexnow-faq

AuditAE (https://auditae.app) — Optional, opt-in only.
The free features (AI Readiness Score, crawler tracker, llms.txt, schema graph and the per-post Schema box, FAQ schema, internal links, broken link checker, redirects, image renames, Query Fan-Out coverage, IndexNow) do not call AuditAE. The broken link checker and Query Fan-Out coverage make no network requests of any kind — both resolve entirely against your own database. The plugin only contacts AuditAE after you pair the site from the “Connect to AuditAE” tab — in three ways. The first two are authenticated over HTTPS with the per-site bearer token you can revoke from the admin at any time:

1. Inbound (AuditAE → your site). The AuditAE service sends authenticated REST API requests to this site to read posts, write drafts, manage schema, or update SEO metadata — only for the capabilities you grant. With the read permission it can also fetch the site’s status (site name and address; the WordPress, PHP and AuditAE plugin versions; the active theme’s name and version; the list of active plugins; and the permissions you granted) and the plugin’s own logs: the log of AuditAE actions on this site (including the previous state kept so recent changes can be undone) and the AI crawler log (bot name, path, response status and time; no visitor IP addresses).
2. Outbound (your site → AuditAE). On a paired site, the AuditAE widget on the wp-admin Dashboard (and the companion AuditAE AI Autopilot theme’s dashboard, if you use it) requests a small scorecard from https://auditae.app/api/wp/summary to show your AI-citation rate, Google Analytics, and Search Console figures in one place. The request runs in the background (WP-Cron) when the widget or the plugin’s settings page is opened and the local copy is more than ~15 minutes old, so wp-admin never waits on it. Each request transmits only your site URL and the bearer token; the response is your own data, and the last copy is kept locally to display. If AuditAE answers that the pairing is no longer valid, the plugin shows a re-pair prompt instead. No post content, analytics, or telemetry is sent.
3. Image imports. When a paired AuditAE account adds an image to your Media Library (for example, one you uploaded in AuditAE), your site downloads it from the source URL AuditAE provides, using WordPress’s HTTP API (wp_safe_remote_get()), which stops downloading once the file passes the size limit. That request sends nothing but the HTTP request itself; the file is type-checked before it is saved.

Links to auditae.app — Only when you click them.
A few links in the plugin’s own screens open auditae.app in your browser: the free AI citation check (Score tab and Dashboard widget) and Help & docs, which appear whether or not the site is paired; on the Connect tab, AuditAE sign-up and sign-in links that open AuditAE’s connect page with your site’s address filled in, and on a paired site the MCP setup link; and on a paired site the fix buttons that open AEBOT. Nothing is sent when the page loads; a link sends only what is in its URL, and only when you click it. The citation-check link carries your site name and domain to fill in the form, and the check runs only when you press its button on auditae.app. The AEBOT buttons carry the request and your site’s address; AuditAE opens the chat on this site with that request typed in. Nothing is sent to AEBOT or charged until you press Send, and AEBOT’s replies use your AuditAE credit.

• Terms of service: https://auditae.app/terms
• Privacy policy: https://auditae.app/privacy

The admin UI uses the Newsreader typeface, which is bundled locally in assets/fonts/ under the SIL Open Font License 1.1. No font requests are made to Google or any third party.