| 开发者 | mmtushar |
|---|---|
| 更新时间 | 2026年8月12日 11:38 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0.2 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
llms.txt, no /llms-full.txt, and no AI HTTP headers. ChatGPT and Perplexity skip you and cite your competitors.
AEOmatic fixes that. It runs alongside Yoast, Rank Math, AIOSEO, SEOPress, or The SEO Framework. Auto-imports their settings. Adds the AI visibility layer none of them cover. Never overwrites your titles, meta descriptions, canonicals, or sitemaps.
What you get — all free, no account, no data sent to external servers
/llms.txt generator — serves a spec-compliant /llms.txt at your site root. Curated ## Key pages section plus a full list of every published page and post./llms-full.txt endpoint — a single URL that returns the full markdown body of every published page and post. AI crawlers can ingest your whole site in one HTTP GET instead of following dozens of links from your llms.txt index.robots.txt for 18 AI crawlers by default (20 recognised in the visit log): GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended, meta-externalagent, Meta-ExternalFetcher, DeepSeekBot, Cohere-AI, DuckAssistBot. Tracks Anthropic's three current user agents (ClaudeBot, Claude-User, Claude-SearchBot) per Anthropic's published crawler documentation.X-AI-Crawl, X-AI-Citeable, X-Content-License, X-AI-Content-Type, X-AI-Speakable. Plus a Link header pointing to your llms.txt.aeomatic_ai_readiness_analyzers filter. Fully offline.aeomatic_entity_detectors filter. Fully offline.<details>/<summary> HTML and automatic FAQPage JSON-LD. No configuration needed.llms.txt, /llms-full.txt, AI HTTP headers, and audit all generate server-side and cache in post meta. Zero external API calls on the front-end. No content sent to vendor clouds./llms-full.txt alongside the rest of the toolkit. A single URL that returns the full markdown body of every published page and post — packaged with schema, crawler control, audit, and HTTP headers in one plugin.aeomatic folder to /wp-content/plugins/, or install through Plugins → Add New → Upload Plugin, or install directly from Plugins → Add New searching for "AEOmatic"./llms.txt and /llms-full.txt endpoints work.AEO means structuring your content so AI answer engines (ChatGPT, Perplexity, Claude, Google AI Overviews, Gemini) can find it, understand it, and cite it. Also called GEO (Generative Engine Optimization), AIO (AI Optimization), LLM SEO, AI SEO, or ChatGPT SEO. Same shift, different acronyms — from optimising for search result links to optimising for AI-generated answers.
AEOmatic ships a broad free toolkit — 22 schema types, 8 page-builder integrations, 16 AI crawler controls, 5 AI HTTP headers, content audit, and /llms-full.txt — all generated on your own server with no external API calls on the front-end. Some paid alternatives offer Citation Trackers that poll ChatGPT, Perplexity, Claude, and Gemini to verify whether they cited you; AEOmatic does not have that feature today. Pick the plugin that matches the outcome you need most.
It can, if both plugins output the same schema types. AEOmatic detects active SEO plugins and shows a warning notice. The "Fix it for me" button disables only the overlapping schema types in AEOmatic — your Yoast or Rank Math settings are not changed. AEOmatic's AEO-specific features (llms.txt, /llms-full.txt, AI crawler control, AEO audit, AI HTTP headers, visual schema editor) sit alongside classic SEO plugins without conflict.
Go to Settings → Permalinks and click Save Changes. This flushes WordPress rewrite rules and registers the virtual endpoints. If the 404 persists, check that your hosting is not serving a physical robots.txt, llms.txt, or llms-full.txt file from your server root — a physical file will override WordPress's virtual endpoint.
A virtual URL AEOmatic serves at /llms-full.txt that returns the full markdown body of every published page and post in a single HTTP response. AI crawlers can ingest your whole site in one fetch instead of following 50 links. AEOmatic shipped /llms-full.txt in version 1.1.0 (June 2026) as part of the free tier, packaged alongside schema, crawler control, audit, and AI HTTP headers.
Yes. AEOmatic has a content extractor for every major page builder: Gutenberg, Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen, and WPBakery. It reads each builder's native data format to extract text content. ACF text, textarea, wysiwyg, and repeater fields are also scanned automatically.
No. Schema is generated once per post and cached in post meta with a content fingerprint. The cache is invalidated automatically when you save the post, change meta, switch categories, or edit a field override. There are no external API calls on the front-end. The audit engine and verification tool only run in the WordPress admin.
22 types: Article, BlogPosting, NewsArticle, TechArticle, Recipe, HowTo, FAQPage, QAPage, Review, Product, Service, LocalBusiness, Event, JobPosting, Course, Book, WebPage, AboutPage, ContactPage, CollectionPage, ProfilePage, and Movie. The type is auto-detected from your content. You can override it per-post from the editor sidebar.
Yes. WooCommerce products automatically receive Product schema with price, availability, SKU, brand (from product attributes), aggregate rating, and review count. Variable products get AggregateOffer schema with min/max price range. All fields are editable in the visual editor.
Go to AEOmatic → What did we do?. The verification panel makes live HTTP requests to your site and shows status for llms.txt, /llms-full.txt, robots.txt AI directives, JSON-LD blocks on your latest post, content coverage, and AEO scores. Click "Validate with Google" to open Google's Rich Results Test pre-loaded with your post URL.
No. AEOmatic makes zero external API calls on the front-end. Schema is generated server-side and cached. The verification panel only makes HTTP requests to your own site to confirm the public output. No content, no analytics, no telemetry is sent off-site.
Yes. AEOmatic produces standards-compliant schema, llms.txt, robots.txt directives, and HTTP headers. Nothing cloaked, no doorway pages, no manipulation. Just the structured signals AI engines and Google's guidelines explicitly recommend.
Yes, that's the whole point. AEOmatic generates the structured signals (schema, llms.txt, /llms-full.txt, AI HTTP headers, answer-shaped content scoring) that AI engines use to identify and cite trustworthy sources. We can't guarantee placement (no plugin can), but we give you every signal those engines look for.
A local, rules-based analyser that runs 16 checks on every post and page and flags the specific reasons a page is unlikely to be cited by AI engines — orphan pages, missing opening answers, FAQ content without FAQPage schema, low-confidence schema types, missing meta descriptions, missing from llms.txt, and more. Each gap comes with a one-line fix hint and — for structurally fixable gaps — a one-click quick-fix button. Available in the block editor sidebar per-post and as a site-wide AEOmatic → Citation Gaps table sorted worst-first. No external API calls; no keys, no account. Deeper LLM-powered gap analysis is planned for the Pro tier separately.
Deactivating the plugin stops the AI crawler visit log, unregisters the /llms.txt and /llms-full.txt endpoints, and removes the injected schema, HTTP headers, and robots.txt AI directives. Your posts, pages, WooCommerce products, and any content you authored remain untouched. Uninstalling (deleting via Plugins → Delete) additionally removes AEOmatic's own options and per-post schema cache. It does not remove your Yoast, Rank Math, AIOSEO, or SEOPress settings — those were never modified.
AEOMATIC_Post_Types in-memory map is populated on init (before the admin_init save handler runs) and was not being invalidated after a save, so the settings view re-rendered from a stale map and boxes appeared unchecked even though the DB was correct. AEOMATIC_Settings::save() now flushes the Post_Types cache immediately after update_option().AEOMATIC_Content_Extractor::extract_text() method and silently falling back to wp_strip_all_tags( $post->post_content ) — so every text signal (keyword patterns, founding-date, NAP pattern) and every heading-based signal missed ACF fields, Elementor, Divi, Beaver, Bricks, Oxygen, and WPBakery content entirely. The collector now calls the real AEOMATIC_Content_Extractor::extract() API which merges all supported sources. ACF wysiwyg headings are now detected too.organization settings section, so organization_setting('name') and organization_setting('logo') always returned empty strings — the Organization detector permanently reported "Organisation name is not set" and "Organisation logo not configured" even when both were filled in. It now reads from the correct schema.org_name / schema.org_logo / schema.org_sameas keys.wp:aeomatic/faq block markers; it now also credits FAQs surfaced by the content extractor (ACF FAQ repeaters, Elementor / Divi / WPBakery accordions, shortcode Q&As, universal HTML detection).aeomatic_schema_overrides filter. Signals themselves are unchanged; only the recommendation strings adapt.question and another whose name contains answer qualifies, so common variants like faq_question / faq_answer / question_text / answer_text all work.GET /aeomatic/v1/entity-scan/{id}. Fingerprint-cached in post meta. Filter hook aeomatic_entity_detectors for custom detectors. Ships one reusable signal-collector service consumed by all six detectors — no code duplication with existing extraction.?post={id}. "Recompute (skip cache)" button forces a fresh analysis.GET /aeomatic/v1/ai-readiness/{id}?force=false — returns { overall_score, categories[], fingerprint, cached }. Same auth model as /audit/{id} (edit_post capability check)._aeomatic_ai_readiness (payload) + _aeomatic_ai_readiness_fingerprint (invalidation key) + _aeomatic_ai_readiness_score (overall score, exposed via REST). Cache auto-invalidates on save_post.aeomatic_ai_readiness_analyzers so third-party code can add or replace categories without patching core.AEOMATIC_Content_Extractor, AEOMATIC_Schema_Analyzer, AEOMATIC_Schema_Generator, AEOMATIC_LLMs_Txt, AEOMATIC_Post_Types, and AEOMATIC_Settings.DuckAssistBot (DuckDuckGo AI) and Meta-ExternalFetcher (Meta's per-user fetcher, distinct from the training UA meta-externalagent). Both added to detection and to the default allow-list. Total recognised: 20 AI user agents.AEOMATIC_Audit::site_summary() and AEOMATIC_Citation_Gaps::site_summary() as reusable public entry points so the dashboard widget, bulk-action notice, and REST endpoints all share one code path./llms.txt.aeomatic_citation_gap_results so power users can register their own rules.Claude-User (Anthropic's user-triggered live-fetch UA, equivalent to ChatGPT-User) to the default allow-list and audit detection. Removed deprecated Claude-Web and anthropic-ai from the default allow-list for new installs; they remain recognised by the visit log for backward compatibility. Source: Anthropic crawler documentation.## Pages section in llms.txt — lists every published page (parent and child), ordered by menu_order then title./llms-full.txt virtual endpoint — emits the full markdown body of every included page and post, designed for direct LLM ingestion. Advertised from llms.txt via a Full content: line.llms_full_serves records hits to the new endpoint./llms-full.txt rewrite rule.