| 开发者 | aaronkaltman |
|---|---|
| 更新时间 | 2026年8月16日 00:58 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/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.
4. IndexNow auto-ping. When you publish or update a post, the plugin instantly notifies the IndexNow API so Microsoft Bing — and the engines that read its index, including ChatGPT and Copilot retrieval — re-crawl the URL in minutes instead of waiting days to discover it on their own. 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 fans out to Bing, Yandex, Seznam, and Naver.
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 the six documented fan-out types — implicit, comparative, entity-expanded, related and personalized. 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.
https://example.com/llms.txt.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.
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.
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.
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.
GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Bytespider, CCBot, cohere-ai, Diffbot, FacebookBot, Meta-ExternalAgent, Meta-ExternalFetcher, Bingbot, YouBot, Amazonbot, DuckAssistBot, PetalBot, TimpiBot, MistralAI-User, AI2Bot, iaskspider, AwarioRssBot, AwarioSmartBot, plus a few others. The list is curated to AI engines; we deliberately exclude Googlebot because that's already covered by Google Search Console.
No. Crawler detection is a single substring scan of the User-Agent on template_redirect, and the write to wp_options is bounded to 500 entries (oldest entries are pruned). 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.
Locally, on your own site — no telemetry, and no data leaves your site unless you opt in to pairing with AuditAE. AI crawler hits live in one small custom table, {prefix}auditae_crawler_hits (pruned to 90 days, 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.
No. If Yoast or Rank Math is active and emitting their own JSON-LD, AuditAE detects their @id values and links to them instead of duplicating Organization/WebSite nodes. You can layer AuditAE's per-post schema on top of any SEO plugin.
Pairing is free. AuditAE itself is pay-per-use ($0.05 per AI-engine prompt check, $0.05 per WordPress mutation action) with $5 free credit at signup, no subscription. Sign up at https://auditae.app.
Settings → AuditAE → Connect to AuditAE tab → Disconnect. The bearer token is wiped instantly.
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 stops emitting Organization and Article schema (so you never get duplicate JSON-LD), 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.
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. Microsoft Bing uses it, and because ChatGPT and Copilot retrieval lean on the Bing index, 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.
?p= shortlinks, and any path already covered by one of your redirects are all resolved before a link is called dead.