Title: AuditAE – MCP Server & AI SEO
Author: aaronkaltman
Published: <strong>2026-06-24</strong>
Last modified: 2026-10-07

---

Szukaj wtyczek

![](https://ps.w.org/auditae-ai-search-toolkit/assets/banner-772x250.png?rev=3710381)

![](https://ps.w.org/auditae-ai-search-toolkit/assets/icon-256x256.png?rev=3584668)

# AuditAE – MCP Server & AI SEO

 Autor: [aaronkaltman](https://profiles.wordpress.org/aaronkaltman/)

[Pobierz](https://downloads.wordpress.org/plugin/auditae-ai-search-toolkit.0.34.0.zip)

 * [Szczegóły](https://pl.wordpress.org/plugins/auditae-ai-search-toolkit/#description)
 * [Recenzje](https://pl.wordpress.org/plugins/auditae-ai-search-toolkit/#reviews)
 *  [Instalacja](https://pl.wordpress.org/plugins/auditae-ai-search-toolkit/#installation)
 * [Rozwój](https://pl.wordpress.org/plugins/auditae-ai-search-toolkit/#developers)

 [Wsparcie](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/)

## Opis

**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](https://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](https://www.indexnow.org) 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.

## Zrzuty ekranu

[⌊MCP in action — ask Claude, ChatGPT, Cursor or any MCP client for a change in 
plain English, and it reads and edits your WordPress site through the AuditAE MCP
server. Here it edits text inside an Elementor widget in place and publishes FAQPage
schema from the page's own accordion. Every write is limited to the capabilities
you granted and logged in wp-admin.⌉⌊MCP in action — ask Claude, ChatGPT, Cursor
or any MCP client for a change in plain English, and it reads and edits your WordPress
site through the AuditAE MCP server. Here it edits text inside an Elementor widget
in place and publishes FAQPage schema from the page's own accordion. Every write
is limited to the capabilities you granted and logged in wp-admin.⌉[

MCP in action — ask Claude, ChatGPT, Cursor or any MCP client for a change in plain
English, and it reads and edits your WordPress site through the AuditAE MCP server.
Here it edits text inside an Elementor widget in place and publishes FAQPage schema
from the page’s own accordion. Every write is limited to the capabilities you granted
and logged in wp-admin.

[⌊Elementor pages are scored like any other page — the per-post AI Readiness checklist
and Query Fan-Out coverage read Elementor's own widget data (headings, text, accordions,
icon lists, and Elementor Pro widgets), so you see which buyer questions the page
answers and which it misses.⌉⌊Elementor pages are scored like any other page — the
per-post AI Readiness checklist and Query Fan-Out coverage read Elementor's own 
widget data (headings, text, accordions, icon lists, and Elementor Pro widgets),
so you see which buyer questions the page answers and which it misses.⌉[

Elementor pages are scored like any other page — the per-post AI Readiness checklist
and Query Fan-Out coverage read Elementor’s own widget data (headings, text, accordions,
icon lists, and Elementor Pro widgets), so you see which buyer questions the page
answers and which it misses.

[⌊The block editor — the AI Readiness checklist sits in the editor sidebar and grades
the post you're writing: answer-first opening, question-shaped headings, FAQ and
structured data, depth, and freshness. Synced patterns and FAQ blocks (Yoast, Rank
Math) count toward the score.⌉⌊The block editor — the AI Readiness checklist sits
in the editor sidebar and grades the post you're writing: answer-first opening, 
question-shaped headings, FAQ and structured data, depth, and freshness. Synced 
patterns and FAQ blocks (Yoast, Rank Math) count toward the score.⌉[

The block editor — the AI Readiness checklist sits in the editor sidebar and grades
the post you’re writing: answer-first opening, question-shaped headings, FAQ and
structured data, depth, and freshness. Synced patterns and FAQ blocks (Yoast, Rank
Math) count toward the score.

[⌊The AI Readiness Score — one 0–100 score with a letter grade and a 7-day trend
for how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, 
and AI Overviews. Every check that isn't passing shows the points it's worth and
links straight to the fix, and most of those fixes are free and need no account.⌉⌊
The AI Readiness Score — one 0–100 score with a letter grade and a 7-day trend for
how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, and 
AI Overviews. Every check that isn't passing shows the points it's worth and links
straight to the fix, and most of those fixes are free and need no account.⌉[

The AI Readiness Score — one 0–100 score with a letter grade and a 7-day trend for
how ready your site is to be read and cited by ChatGPT, Perplexity, Gemini, and 
AI Overviews. Every check that isn’t passing shows the points it’s worth and links
straight to the fix, and most of those fixes are free and need no account.

[⌊The Links tab — every published page nothing else links to, and for any one of
them, the existing pages that already say its name in plain prose. One click wraps
that phrase in a link and changes nothing else. Free; the big SEO plugins charge
for both halves.⌉⌊The Links tab — every published page nothing else links to, and
for any one of them, the existing pages that already say its name in plain prose.
One click wraps that phrase in a link and changes nothing else. Free; the big SEO
plugins charge for both halves.⌉[

The Links tab — every published page nothing else links to, and for any one of them,
the existing pages that already say its name in plain prose. One click wraps that
phrase in a link and changes nothing else. Free; the big SEO plugins charge for 
both halves.

[⌊The AI crawlers tab — which AI bots are reading your site (hits, distinct bots,
and time since last hit), with new-bot celebrations the first week a crawler discovers
you, plus a robots.txt audit that flags when you're blocking citation engines like
GPTBot, ClaudeBot, or PerplexityBot.⌉⌊The AI crawlers tab — which AI bots are reading
your site (hits, distinct bots, and time since last hit), with new-bot celebrations
the first week a crawler discovers you, plus a robots.txt audit that flags when 
you're blocking citation engines like GPTBot, ClaudeBot, or PerplexityBot.⌉[

The AI crawlers tab — which AI bots are reading your site (hits, distinct bots, 
and time since last hit), with new-bot celebrations the first week a crawler discovers
you, plus a robots.txt audit that flags when you’re blocking citation engines like
GPTBot, ClaudeBot, or PerplexityBot.

[⌊The llms.txt tab — a live /llms.txt manifest at your site root, with per-section
control over what AI tools see.⌉⌊The llms.txt tab — a live /llms.txt manifest at
your site root, with per-section control over what AI tools see.⌉[

The llms.txt tab — a live `/llms.txt` manifest at your site root, with per-section
control over what AI tools see.

[⌊The Schema tab — emit a clean, schema.org-valid site-wide Organization JSON-LD
block, working alongside Yoast and Rank Math. Per-post FAQ schema comes from the
editor; on a paired site, AEBOT can add per-post Article and Product schema.⌉⌊The
Schema tab — emit a clean, schema.org-valid site-wide Organization JSON-LD block,
working alongside Yoast and Rank Math. Per-post FAQ schema comes from the editor;
on a paired site, AEBOT can add per-post Article and Product schema.⌉[

The Schema tab — emit a clean, schema.org-valid site-wide Organization JSON-LD block,
working alongside Yoast and Rank Math. Per-post FAQ schema comes from the editor;
on a paired site, AEBOT can add per-post Article and Product schema.

[⌊The FAQ schema editor — add question-and-answer pairs to any post or page and 
AuditAE publishes them as schema.org FAQPage structured data, so AI engines can 
read your questions and answers as data. Free, no account, and your post content
is never modified.⌉⌊The FAQ schema editor — add question-and-answer pairs to any
post or page and AuditAE publishes them as schema.org FAQPage structured data, so
AI engines can read your questions and answers as data. Free, no account, and your
post content is never modified.⌉[

The FAQ schema editor — add question-and-answer pairs to any post or page and AuditAE
publishes them as schema.org FAQPage structured data, so AI engines can read your
questions and answers as data. Free, no account, and your post content is never 
modified.

[⌊The Redirects tab — turn the 404s that AI bots hit into one-click 301s so you 
keep the link credit; suggestions are drawn straight from your AI crawler log.⌉⌊
The Redirects tab — turn the 404s that AI bots hit into one-click 301s so you keep
the link credit; suggestions are drawn straight from your AI crawler log.⌉[

The Redirects tab — turn the 404s that AI bots hit into one-click 301s so you keep
the link credit; suggestions are drawn straight from your AI crawler log.

[⌊The Connect tab — pair with a free AuditAE account so the AEBOT assistant, or 
Claude, ChatGPT and Cursor over MCP, can draft posts, edit SEO metadata and manage
schema on your site. Choose what it may do; every write is logged and the token 
is revocable at any time.⌉⌊The Connect tab — pair with a free AuditAE account so
the AEBOT assistant, or Claude, ChatGPT and Cursor over MCP, can draft posts, edit
SEO metadata and manage schema on your site. Choose what it may do; every write 
is logged and the token is revocable at any time.⌉[

The Connect tab — pair with a free AuditAE account so the AEBOT assistant, or Claude,
ChatGPT and Cursor over MCP, can draft posts, edit SEO metadata and manage schema
on your site. Choose what it may do; every write is logged and the token is revocable
at any time.

## Instalacja

 1. Install and activate the plugin.
 2. 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.
 3. 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.
 4. Visit the **llms.txt** tab to review or edit the manifest served at `https://example.
    com/llms.txt`.
 5. (Optional) Visit the **Connect to AuditAE** tab to pair with an AuditAE account
    if you want the citation-audit and AEBOT writing features. Pairing needs a free
    AuditAE account; the tab links to sign-up with your site’s address filled in, then
    you generate a pairing code and paste it into AuditAE.
 6. (Optional) Connect Claude, ChatGPT or Cursor over MCP. Once the site is paired,
    the Connect tab shows the AuditAE MCP server address, `https://auditae.app/api/
    mcp`. In Claude or ChatGPT, add it as a custom connector and sign in with your 
    AuditAE account. In Claude Code, Cursor and other clients that take a config file,
    use an API key from your AuditAE dashboard (the Connect tab links to the setup 
    steps). Then ask your assistant to list your WordPress sites to check the connection.

## Najczęściej zadawane pytania

### Do I need an AuditAE account to use the plugin?

No. The AI Readiness Score, the AI Crawler Tracker and robots.txt audit, the llms.
txt generator, Organization schema, the per-post Schema box (Article, Blog post,
HowTo, Product) and FAQ schema box, the broken link checker, orphaned content and
internal link suggestions, Redirects, image file renames, IndexNow and Query Fan-
Out coverage are all free and standalone. They work the moment the plugin is activated,
and pairing doesn’t take any of them away. The Connect to AuditAE tab is optional
and only relevant if you want the paid citation audits, AEBOT, or MCP access for
Claude, ChatGPT and Cursor.

### 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.

### Why does the crawler log show fewer hits than my server logs?

Because the plugin only sees requests that reach WordPress. A page cache (WP Rocket,
LiteSpeed Cache, W3 Total Cache, WP Super Cache, your host’s cache, or a CDN such
as Cloudflare) answers many requests before WordPress loads, and those hits are 
never logged. Treat the counts as a minimum: if a bot shows up at all, it is reading
your site. For fuller counts, add the AI bots’ user agents to your cache’s list 
of user agents it never caches (WP Rocket: „Never Cache User Agent(s)”; LiteSpeed
Cache: „Do Not Cache User Agents”; W3 Total Cache and WP Super Cache: „Rejected 
User Agents”): `GPTBot`, `OAI-SearchBot`, `ChatGPT-User`, `ClaudeBot`, `Claude-User`,`
Claude-SearchBot`, `PerplexityBot` and `Perplexity-User`. A CDN needs the same exception
as a cache-bypass rule on its side. Those bots’ requests then run through WordPress,
which costs a little more server time.

### 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 by a daily background clean-up, never inside a visitor’s
request. A 404 that matches none of your redirects is answered without loading the
redirect list. 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`.
IndexNow pings are batched and sent from one background event. 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) and `auditae_redirect_sources` (an index of their source paths),`
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
and its queue of changed URLs waiting to be sent — plus per-post meta `_auditae_schema_graph`
and `_auditae_faq_schema`. Uninstalling removes all of it.

### 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 cost 5¢ each (25¢ for a designed page),
and reads are free. Replies from AEBOT, the AuditAE assistant, are billed per reply
on the AI tokens they use, and each reply shows its exact charge. 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, Rank Math or other SEO plugins?

No — it’s designed to run alongside Yoast SEO, Rank Math, All in One SEO, SEOPress
and The SEO Framework. AuditAE is an AI-search toolkit, not an SEO plugin: it never
outputs title tags, meta descriptions, canonical URLs, Open Graph tags or sitemaps
of its own, so it won’t trigger a „you have two SEO plugins active” warning. It 
changes values your SEO plugin stores only when asked: AEBOT can edit a post’s SEO
title and description with your permission, and renaming an image updates the social-
image URLs your SEO plugin saved, so share cards don’t break. Where the two genuinely
overlap — structured data and IndexNow — AuditAE detects your SEO plugin and steps
aside:

 * Schema: it leaves the node types your SEO plugin owns (Organization, WebSite,
   Article, BreadcrumbList…) to that plugin and adds only the types it doesn’t cover,
   such as HowTo or Product, so you never get duplicate JSON-LD. 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.
 * FAQ schema: it skips posts that already carry an SEO plugin’s FAQ block, or Rank
   Math Schema Builder FAQ schema.
 * IndexNow: it turns its 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, and a note on the plugin’s own settings
page says exactly what’s been deferred.

### How do I connect Claude, ChatGPT or Cursor to my WordPress site?

Pair the site on the Connect to AuditAE tab (a free AuditAE account is needed), 
then add the AuditAE MCP server, `https://auditae.app/api/mcp`, to your AI client.
In Claude or ChatGPT, add it as a custom connector and sign in with your AuditAE
account; that one connection covers every paired site in your workspace. In Claude
Code, Cursor, Windsurf and other clients that take a config file, connect with an
API key from your AuditAE dashboard; team workspaces connect with an API key too.
The assistant can then read, draft, edit and publish posts, edit SEO titles and 
descriptions, and manage schema and llms.txt, limited to the permissions you granted
on the Connect tab. MCP reads are free; edits are 5¢ each (25¢ for a designed page).
Every change is listed on the Activity tab, and Disconnect revokes access at once.

### 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. It pauses on its own on staging and development sites and 
while Settings  Reading  „Discourage search engines from indexing this site” is 
ticked. 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.

## Recenzje

Wtyczka nie ma jeszcze żadnej recenzji.

## Kontrybutorzy i deweloperzy

„AuditAE – MCP Server & AI SEO” jest oprogramowaniem open source. Poniższe osoby
miały wkład w rozwój wtyczki.

Zaangażowani

 *   [ aaronkaltman ](https://profiles.wordpress.org/aaronkaltman/)

[Przetłumacz wtyczkę “AuditAE – MCP Server & AI SEO” na swój język.](https://translate.wordpress.org/projects/wp-plugins/auditae-ai-search-toolkit)

### Interesuje cię rozwój wtyczki?

[Przeglądaj kod](https://plugins.trac.wordpress.org/browser/auditae-ai-search-toolkit/),
sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/auditae-ai-search-toolkit/)
lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/auditae-ai-search-toolkit/)
przez [RSS](https://plugins.trac.wordpress.org/log/auditae-ai-search-toolkit/?limit=100&mode=stop_on_copy&format=rss).

## Rejestr zmian

Recent releases are below. WordPress.org truncates this section at 5,000
 characters,
so older entries are kept in the plugin’s development history rather than here, 
where they would push the current release out of view.

#### 0.34.0

 * New: a free Schema box in the post editor adds Article, Blog post, How-to or 
   Product schema to a post, with a JSON-LD preview. No account needed.
 * Elementor 4: AuditAE can read and edit the text of atomic Heading, Paragraph 
   and Button widgets.
 * Renaming an image also updates Elementor page settings, block widgets, header
   images and the social images Yoast, Rank Math and SEOPress store.
 * Coexistence: no duplicate FAQ schema next to Elementor’s FAQ Schema switch or
   Rank Math’s Schema Builder, Product schema is left to WooCommerce on product 
   pages, and an Organization your theme or another plugin already prints is respected.
 * Faster: IndexNow URLs are queued and sent in batches (a post unpublished or set
   to noindex before its turn is skipped), the crawler log prunes once a day, and
   page views and 404s skip database reads for Organization schema and redirects.
 * The Links tab and the Dashboard widget no longer make the page wait: the link
   graph rebuilds and the scorecard refreshes in the background.
 * Connect tab: a free sign-up link with your site address filled in, a warning 
   to paste the pairing code only at auditae.app, and how to use the site from Claude
   or ChatGPT over MCP. A pairing AuditAE no longer accepts asks you to re-pair.
 * Accessibility: higher-contrast colours, visible keyboard focus and screen-reader
   text on badges, new-tab links and repeated links.
 * A one-time review request on the AI crawlers tab after the first AI crawler visit.
 * Redirects tab: the Suggested redirects table fits its card, so the destination
   field and Save button are always visible.

#### 0.33.1

 * Security: AuditAE text edits no longer strip embeds (iframes, embed scripts, 
   forms) from the rest of a post, and may not change or add markup WordPress’s 
   content filter would remove. Storing an AuditAE theme page template now needs
   the publish or write SEO permission.
 * AI Readiness Score: WordPress’s default robots.txt no longer costs 8 points. 
   Rules that only cover wp-admin, search, feeds or cart pages don’t count as limits,
   and only AI citation bots count.
 * robots.txt fix: the one-click Allow group names only the citation bots that are
   blocked and keeps your own rules for them. Subfolder installs and physical robots.
   txt files get a copy-paste snippet.
 * IndexNow pauses on staging and development sites and while search engines are
   discouraged, and skips password-protected and noindexed posts (Yoast, Rank Math,
   SEOPress, AIOSEO). „Submit all” covers every public post type.
 * The Score and Crawlers tabs wait at most about 5 seconds on the site’s self-checks;
   hosts that can’t reach themselves are checked in the background.
 * Scanner probes (.env, .git, wp-config backups) no longer appear as AI-bot 404s
   to redirect.
 * Yoast site-name and company settings are saved where Yoast reads them, and page
   caches are cleared after schema and SEO changes.
 * Elementor 4 atomic widgets keep their text when AuditAE edits other widgets on
   the page. Image imports stop at the size limit.
 * Clearer copy: 5¢ per edit, nothing is sent to AEBOT until you press Send, and
   the HTTPS error says what to change.

#### 0.33.0

 * New name on WordPress.org, AuditAE – MCP Server & AI SEO. The plugin, its settings
   and your connection are unchanged.
 * Organization schema on Rank Math sites that haven’t finished Rank Math’s setup,
   and a more accurate crawler log and IndexNow wording.

#### 0.32.0

 * Score fix buttons match the permissions you’ve granted AuditAE („Show me the 
   exact edits” when AEBOT can’t apply them) and open AEBOT on this site.
 * A link to a free AI citation check on the Score tab and the Dashboard widget,
   plus Help & docs links.

#### 0.31.0

 * Connection: sites running a JWT authentication plugin no longer reject AuditAE’s
   requests.
 * Crawlers: AI bots reading your /llms.txt and IndexNow key file now appear in 
   the crawler log.
 * Query Fan-Out: how-to post titles are no longer used as comparison topics.

#### 0.30.0

 * 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.

## Meta

 *  Wersja **0.34.0**
 *  Ostatnia aktualizacja **2 dni temu**
 *  Włączone instalacje **10+**
 *  Wersja WordPressa ** 6.0 lub nowszej **
 *  Testowano do **7.1.3**
 *  Wersja PHP ** 7.4 lub nowszej **
 *  Język
 * [English (US)](https://wordpress.org/plugins/auditae-ai-search-toolkit/)
 * Tagi
 * [ai seo](https://pl.wordpress.org/plugins/tags/ai-seo/)[ai visibility](https://pl.wordpress.org/plugins/tags/ai-visibility/)
   [llms.txt](https://pl.wordpress.org/plugins/tags/llms-txt/)[mcp](https://pl.wordpress.org/plugins/tags/mcp/)
   [wordpress mcp](https://pl.wordpress.org/plugins/tags/wordpress-mcp/)
 *  [Widok zaawansowany](https://pl.wordpress.org/plugins/auditae-ai-search-toolkit/advanced/)

## Oceny

Nie przesłano jeszcze żadnych recenzji.

[Twoja opinia](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/reviews/#new-post)

[Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/reviews/)

## Zaangażowani

 *   [ aaronkaltman ](https://profiles.wordpress.org/aaronkaltman/)

## Wsparcie

Masz coś do dodania? Potrzebujesz pomocy?

 [Zobacz forum wsparcia](https://wordpress.org/support/plugin/auditae-ai-search-toolkit/)