About this plugin
AI search engines cannot cite what they cannot parse. AEOmatic makes your WordPress content machine-readable — then shows you what the crawlers actually got. It does three jobs: Publishes the signals AI systems read. JSON-LD structured data across 22 schema types, an llms.txt index at your site root, a /llms-full.txt full-text endpoint, and per-bot crawl directives in robots.txt . Scores how extractable your content is. A site-wide AI readiness score across three categories, plus per-post audits that name the specific thing to fix rather than handing you a number. Reports what actually happened. A server-side log of every recognised AI crawler request — which bot, which URL, and the HTTP status your site returned. If you are quietly serving 404s to GPTBot, this is where you find out. It reads your page builder, not just Gutenberg Most AI SEO plugins parse post_content and stop. If your pages are built in Elementor or Divi, or your copy lives in ACF fields, that means your schema and your scores are computed against an almost-empty string. AEOmatic runs one normalising extraction pass that understands Gutenberg, the Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery , plus ACF text, textarea, wysiwyg, repeater and flexible-content fields. Everything downstream — schema generation, the audit, readiness scoring, llms.txt — reads that single extraction, so a page assembled in a builder is scored on what it actually renders. This work goes by several names — Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), LLM SEO, AI search optimization. Same underlying job. Built to sit beside your SEO plugin, not replace it AEOmatic writes only its own settings and its own post meta. It never touches your titles, meta descriptions, canonicals or XML sitemaps, and it never modifies another plugin’s configuration. It detects Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework, can import your organisation details from whichever you run, and flags the case where two plugins would emit the same JSON-LD type on one page — with a one-click fix that adjusts AEOmatic’s output, never theirs. What AEOmatic measures, and what it refuses to guess at AEOmatic scores readiness — everything about your site that a machine can check locally: can AI crawlers reach your pages, do those pages carry structured data something can parse, is your content shaped so an answer can be lifted out of it. Measurable from your own install, so AEOmatic measures it. It does not score visibility — whether ChatGPT, Gemini, Claude or Perplexity actually surface or cite you, for which prompts, trending over time. Answering that means querying those engines on a schedule from outside your site. That is a hosted service, not a plugin feature, and a local imitation of it would just be a number with nothing behind it. So the dashboard is labelled AI Readiness , not AI Visibility. A well-prepared site still is not guaranteed to be cited — no plugin can promise that, and every check in the audit tells you whether it is a direct check or a heuristic so you can see which is which. One distinction the crawler log makes easy to get wrong: a crawl is not a citation. The log proves a bot fetched a URL. Whether that page ended up in an answer is not visible in crawler traffic, and no AI vendor exposes it there. Everything included, no account and no API key AI readiness audit, three levels. Site-wide across three categories (Technical readiness, Content readiness, AI crawler access), per post across five categories (Content, Trust, Authority, Entities, Technical), and a per-post 0–100 content rubric of thirteen weighted checks. Every category states whether it is a direct check or a heuristic. Visual schema editor for 22 types — Article, BlogPosting, NewsArticle, TechArticle, Recipe, HowTo, FAQPage, QAPage, Review, Product, Service, LocalBusiness, Event, JobPosting, Course, Book, WebPage, AboutPage, ContactPage, CollectionPage, ProfilePage, Movie. The type is auto-detected from your content and every field is editable in the block-editor sidebar with a live JSON-LD preview. Type-specific property extraction — Recipe posts get ingredients and instructions, JobPosting posts get salary ranges, Event posts get dates and venue, LocalBusiness gets address and opening hours. Not generic Article schema on everything. /llms.txt generator — a spec-compliant Markdown index at your site root: site summary, curated key pages from your nav menu, then every published item grouped by post type. /llms-full.txt endpoint — the extracted body text of your published content at one URL, so an AI crawler can ingest the site in a single request. Bounded and cached so it cannot become a load problem. AI crawler control — per-bot Allow/Disallow toggles in robots.txt for 18 AI crawlers: 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. Twenty user agents recognised in the visit log. AI crawler log and breakdown — which AI bots requested which URLs, what HTTP status you served them, and when. A 404 or 403 being served to OAI-SearchBot is the kind of thing you want to know. Records bot name, URL, user agent and status only: no IP addresses, no cookies, no visitor data , nothing leaves your server. Page-builder support — content is read from Gutenberg, Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery, plus ACF text, textarea, wysiwyg, repeater and flexible-content fields. Scoring reflects what your pages actually render. WooCommerce Product schema — price, availability, SKU, brand, ratings and sale dates auto-filled; variable products get AggregateOffer with a min/max range. AI Citation Gaps — sixteen local rules-based checks that name why a page is unlikely to be quoted: orphan pages, no opening answer, thin body, no FAQ block, no question heading, schema type mismatch, missing author signal, missing from llms.txt, low outbound links, low alt coverage, no citation hook, no related links, sibling-topic gaps by category, FAQ or HowTo content without matching schema, missing meta description. Two ship a one-click fix. Entity Scanner — scans content, schema, headings and metadata for Organization, Person, Service, Product, LocalBusiness and FAQ entities, returning a coverage score with per-entity confidence, detected signals, missing signals and recommendations. FAQ block — a native Q&A block producing accessible <details> / <summary> markup plus FAQPage JSON-LD. [aeo_faq] / [aeo_qa] shortcodes for the Classic Editor. Setup wizard with a real first audit — six skippable steps: welcome, import from your existing SEO plugin, organisation details, AI crawler access, your first readiness audit , verify. The audit step shows your score and the three highest-value fixes with direct links, so you finish onboarding knowing what to do next. SEO plugin conflict detection — detects Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework, and checks whether each is currently emitting overlapping schema. One click disables only the overlapping types in AEOmatic ; your other plugin’s configuration is never modified. AI HTTP discovery headers — optional X-AI-Crawl , X-AI-Citeable , X-Content-License , X-AI-Content-Type , X-AI-Speakable headers plus a Link: rel="ai-context" pointer to your llms.txt. These are proposed conventions, not a ratified standard, and no AI vendor has committed to reading them — so they ship as a setting you can switch off. Live verification panel — makes HTTP requests to your own site and shows what is actually being served: llms.txt with size and line count, robots.txt with AI bot count, schema blocks on your latest post with a direct Google Rich Results Test link. VideoObject, Speakable, WebSite + SearchAction schema , an author-profile panel, a wp-admin dashboard widget, and a bulk re-audit action on post list screens. AI crawlers recognised ChatGPT / ChatGPT Search (OpenAI) — GPTBot, OAI-SearchBot, ChatGPT-User Claude / Claude Search (Anthropic) — ClaudeBot, Claude-User, Claude-SearchBot Perplexity — PerplexityBot, Perplexity-User Google AI Overviews / Gemini — Google-Extended controls Gemini training; AI Overviews retrieval uses Googlebot Microsoft Copilot — no dedicated AI user agent; retrieves from the Bing index via Bingbot Meta AI — meta-externalagent, Meta-ExternalFetcher DeepSeek — DeepSeekBot Apple Intelligence — Applebot-Extended Cohere — Cohere-AI DuckDuckGo AI answers — DuckAssistBot Common Crawl — CCBot Controlling a crawler’s access controls whether it can read you. It does not control whether an engine cites you. Runs entirely on your own server Schema and metadata generate server-side and cache in post meta. There are no external API calls on the front end, no account, no API key, no credit limits, and no content sent to a vendor cloud. The verification panel only ever requests URLs on your own site, and only for logged-in administrators. No third-party analytics, no telemetry. Who it is for Publishers and media who want to be quoted by AI as a source Businesses and SaaS companies who want their entity data to be unambiguous to AI systems Local businesses who want correct LocalBusiness signals E-commerce stores on WooCommerce SEO professionals and content teams who need an AI layer on top of their existing stack Agencies running a repeatable audit across client sites WordPress developers — 11 filters, a documented REST namespace, and analyzer interfaces to extend What is not in this plugin Stated plainly so you can decide before installing. None of the following exists here: Citation tracking — whether an AI engine quoted you Prompt tracking — which questions surface your site Historical AI visibility trends Competitor monitoring or citation comparison AI referral analytics (traffic arriving from AI answers) Multi-site management, client dashboards, or white-label reports These all need infrastructure outside WordPress — something querying AI engines on a schedule and storing results over time. They are on the roadmap as hosted functionality, not faked locally. Privacy Policy AEOmatic does not collect, store, or transmit any personal data to external servers. Schema, llms.txt , /llms-full.txt and the AI discovery headers are generated server-side on your own site. The verification panel makes HTTP requests only to your own site, only for logged-in administrators, to confirm public output. The AI crawler visit log records, in your own database only: the matched bot name, the requested URL, the user-agent string (truncated to 255 characters), the HTTP status your site returned, and a timestamp. It records no IP addresses, no cookies, no referrers and no human-visitor data , and only logs requests whose user agent matches a known AI crawler. Retention is configurable from 7 to 365 days (default 90) with a 500-entry ceiling and a daily purge. Nothing in the log ever leaves your site. AEOmatic makes no external API calls on the front end and ships with no third-party analytics or telemetry.