Cosmetic but worth having: JSON-LD is now pretty-printed and no longer escapes ampersands, slashes and accented characters. Purely an output-formatting change \u2014 the schema itself is unchanged.<\/p>","1.2.0":"
Fixes custom post types not staying selected under Settings \u2192 Content coverage (your saved selections were never lost \u2014 only mis-displayed, so nothing needs re-saving). Also important for Elementor, Divi, Bricks, Oxygen, Beaver Builder and WPBakery sites: readiness checks were reading post_content directly and scoring builder pages as empty. Expect scores to rise after updating. Also fixes post types whose slug is not plain lowercase being impossible to disable, and a settings save leaving the upgrade routine re-flushing rewrite rules on every admin page load.<\/p>","1.1.9":"
Fixes page-builder and ACF pages being scored as empty across six readiness checks \u2014 expect scores to rise on Elementor, Divi, Bricks, Oxygen, Beaver Builder and WPBakery sites. Renamed, with a new AI Readiness dashboard, an AI crawler log that records the HTTP status served to each bot, and a first-audit onboarding step. Fixes two readiness checks that were silently degraded, tightens the per-post citation-gaps permission check, caches and bounds \/llms.txt and \/llms-full.txt, and makes uninstall remove everything it should. Recommended update.<\/p>","1.1.8":"
Conflict detection now respects your SEO plugin's own schema settings, and custom post type coverage saves reliably. Recommended update.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3583610,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3583608,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3685818,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3685818,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"aeomatic\/faq":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"aeomatic\/faq","title":"AEO FAQ","category":"text","description":"Frequently asked questions block. Auto-generates FAQ schema for AI search engines.","icon":"format-chat","keywords":["faq","questions","aeo","schema"],"textdomain":"aeomatic","supports":{"align":["wide","full"],"html":false,"reusable":true},"editorScript":"file:.\/index.js","editorStyle":"file:.\/editor.css","style":"file:.\/style.css"},"aeomatic\/faq-item":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"aeomatic\/faq-item","title":"AEO FAQ item","category":"text","parent":["aeomatic\/faq"],"description":"A single FAQ question and answer.","icon":"editor-help","textdomain":"aeomatic","attributes":{"question":{"type":"string","default":""},"answer":{"type":"string","default":""}},"supports":{"html":false,"reusable":false},"editorScript":"file:.\/index.js"}},"tagged_versions":["1.0.0","1.1.0","1.1.1","1.1.2","1.1.3","1.1.4","1.1.5","1.1.6","1.1.7","1.1.8","1.1.9","1.2.0","1.2.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3615854,"resolution":"1","location":"assets","locale":"","width":1920,"height":1243},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3615854,"resolution":"2","location":"assets","locale":"","width":1920,"height":1343},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3615854,"resolution":"3","location":"assets","locale":"","width":1900,"height":1901},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3615854,"resolution":"4","location":"assets","locale":"","width":1920,"height":2893},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3615854,"resolution":"5","location":"assets","locale":"","width":1920,"height":1246}},"screenshots":{"1":"AI Readiness dashboard \u2014 overall score, three category cards labelled direct-check or heuristic, issue count and top recommendations.","2":"Visual schema editor in the block-editor sidebar \u2014 auto-populated fields, live JSON-LD preview, type confidence.","3":"Type-aware JSON-LD generation \u2014 Recipe schema with auto-extracted ingredients and instructions.","4":"AI crawler activity \u2014 which bots requested which URLs and what HTTP status was served.","5":"Setup wizard readiness step \u2014 your first audit score with the three highest-value fixes.","6":"Live verification panel showing what is actually being served, with a direct Google Rich Results Test link."}},"plugin_section":[262246],"plugin_tags":[244526,220145,232780,2516,1121],"plugin_category":[55],"plugin_contributors":[268599],"plugin_business_model":[],"class_list":["post-310812","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-aeo","plugin_tags-ai-search","plugin_tags-ai-crawler","plugin_tags-json-ld","plugin_tags-structured-data","plugin_category-seo-and-marketing","plugin_contributors-mmtushar","plugin_committers-mmtushar"],"banners":{"banner":"https:\/\/ps.w.org\/aeomatic\/assets\/banner-772x250.png?rev=3685818","banner_2x":"https:\/\/ps.w.org\/aeomatic\/assets\/banner-1544x500.png?rev=3685818","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/aeomatic\/assets\/icon-128x128.png?rev=3583610","icon_2x":"https:\/\/ps.w.org\/aeomatic\/assets\/icon-256x256.png?rev=3583608","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/aeomatic\/assets\/screenshot-1.png?rev=3615854","caption":"AI Readiness dashboard \u2014 overall score, three category cards labelled direct-check or heuristic, issue count and top recommendations."},{"src":"https:\/\/ps.w.org\/aeomatic\/assets\/screenshot-2.png?rev=3615854","caption":"Visual schema editor in the block-editor sidebar \u2014 auto-populated fields, live JSON-LD preview, type confidence."},{"src":"https:\/\/ps.w.org\/aeomatic\/assets\/screenshot-3.png?rev=3615854","caption":"Type-aware JSON-LD generation \u2014 Recipe schema with auto-extracted ingredients and instructions."},{"src":"https:\/\/ps.w.org\/aeomatic\/assets\/screenshot-4.png?rev=3615854","caption":"AI crawler activity \u2014 which bots requested which URLs and what HTTP status was served."},{"src":"https:\/\/ps.w.org\/aeomatic\/assets\/screenshot-5.png?rev=3615854","caption":"Setup wizard readiness step \u2014 your first audit score with the three highest-value fixes."}],"raw_content":"\n
Answer Engine Optimization (AEO) for WordPress.<\/strong> AI search engines cannot cite what they cannot parse. AEOmatic makes your WordPress content machine-readable \u2014 then shows you what the crawlers actually got.<\/p>\n\n It does three jobs:<\/p>\n\n Most AI SEO plugins parse AEOmatic runs one normalising extraction pass that understands Gutenberg, the Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery<\/strong>, plus ACF text, textarea, wysiwyg, repeater and flexible-content fields. Everything downstream \u2014 schema generation, the audit, readiness scoring, This work goes by several names \u2014 Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), LLM SEO, AI search optimization. Same underlying job.<\/p>\n\n 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.<\/p>\n\n 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 \u2014 with a one-click fix that adjusts AEOmatic's<\/strong> output, never theirs.<\/p>\n\n AEOmatic measures what is verifiable on your own install: whether AI crawlers can reach your pages, whether those pages carry structured data a machine can parse, and whether your content is shaped so an answer can be lifted out of it. Every check tells you whether it is a direct check or a heuristic, so you can see which is which.<\/p>\n\n The dashboard is labelled AI Readiness<\/strong> rather than AI Visibility, because that is what it measures \u2014 your site's preparation, not whether an engine has cited you.<\/p>\n\n AI readiness audit, three levels.<\/strong> 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\u2013100 content rubric of thirteen weighted checks. Every category states whether it is a direct check or a heuristic.<\/p><\/li>\n Visual schema editor for 22 types<\/strong> \u2014 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.<\/p><\/li>\n Type-specific property extraction<\/strong> \u2014 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.<\/p><\/li>\n AI crawler control<\/strong> \u2014 per-bot Allow\/Disallow toggles in AI crawler log and breakdown<\/strong> \u2014 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<\/strong>, nothing leaves your server.<\/p><\/li>\n Page-builder support<\/strong> \u2014 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.<\/p><\/li>\n WooCommerce Product schema<\/strong> \u2014 price, availability, SKU, brand, ratings and sale dates auto-filled; variable products get AggregateOffer with a min\/max range.<\/p><\/li>\n AI Citation Gaps<\/strong> \u2014 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.<\/p><\/li>\n Entity Scanner<\/strong> \u2014 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.<\/p><\/li>\n FAQ block<\/strong> \u2014 a native Q&A block producing accessible Setup wizard with a real first audit<\/strong> \u2014 six skippable steps: welcome, import from your existing SEO plugin, organisation details, AI crawler access, your first readiness audit<\/strong>, 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.<\/p><\/li>\n SEO plugin conflict detection<\/strong> \u2014 detects Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework, and checks whether each is currently emitting<\/em> overlapping schema. One click disables only the overlapping types in AEOmatic<\/strong>; your other plugin's configuration is never modified.<\/p><\/li>\n AI HTTP discovery headers<\/strong> \u2014 optional Live verification panel<\/strong> \u2014 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.<\/p><\/li>\n VideoObject, Speakable, WebSite + SearchAction schema<\/strong>, an author-profile panel, a wp-admin dashboard widget, and a bulk re-audit action on post list screens.<\/p><\/li>\n<\/ul>\n\n Controlling a crawler's access controls whether it can read you. It does not control whether an engine cites you.<\/p>\n\n 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.<\/p>\n\n AEOmatic does not collect, store, or transmit any personal data to external servers.<\/p>\n\n Schema, 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<\/strong>, 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.<\/p>\n\n AEOmatic makes no external API calls on the front end and ships with no third-party analytics or telemetry.<\/p>\n\n\n Requirements:<\/strong> WordPress 6.4+, PHP 8.0+, and pretty permalinks (any structure other than \"Plain\").<\/p>\n\n You do not<\/strong> normally need to re-save permalinks after installing or updating \u2014 the plugin flushes rewrite rules on activation and again automatically when it detects a version change. If No plugin can promise that, and AEOmatic does not. What it does is fix the technical and content signals you control: crawler access, parseable structured data, an llms.txt index, and content shaped so an answer can be extracted. Whether an AI engine then cites you depends on that engine's own ranking and retrieval, which nobody outside those companies controls. Any plugin promising guaranteed AI citations is guessing.<\/p><\/dd>\n AI readiness is how well-prepared your site is \u2014 measurable from your own database and settings, which is what AEOmatic scores. AI visibility is whether AI systems actually surface or cite you \u2014 measurable only by querying those engines from outside your site, which AEOmatic does not do. The dashboard is labelled \"AI Readiness\" for that reason.<\/p><\/dd>\n No. It tells you a crawler requested a URL and what status you served. Whether that page was retained, used, or quoted in an AI answer is not visible in crawler traffic, and no AI vendor exposes it there. Treat crawler visits as access evidence, not citation evidence.<\/p><\/dd>\n It is designed to run beside them. AEOmatic writes only its own settings and its own post meta and never modifies another plugin's configuration. Because several SEO plugins also emit Article, Organization and Breadcrumb schema, AEOmatic detects that overlap and offers a one-click fix that disables only the overlapping types in AEOmatic<\/em>. The detector checks whether the other plugin's schema module is actually switched on, so it does not nag you about a conflict that is not happening. Until you resolve a real overlap, both plugins emit their types and the site readiness score reports it as a failing technical check.<\/p><\/dd>\n Yes \u2014 organisation name, logo and social profiles from Yoast SEO, Rank Math, SEOPress, All in One SEO or The SEO Framework. Import is per-plugin, opt-in, one-directional, and never overwrites a value you have already set in AEOmatic.<\/p><\/dd>\n A single URL returning the extracted body text of your published content, so an AI crawler can ingest the site in one request instead of following dozens of links. It is capped at 200 items per post type by default and says so in its own output when it truncates; raise or remove the cap with the Check that Settings \u2192 Permalinks<\/strong> is not set to \"Plain\" \u2014 the endpoints need a rewrite rule, which plain permalinks do not support. Then click Save Changes<\/strong> on that screen once. Also confirm llms.txt is enabled under AEOmatic \u2192 Settings<\/strong>.<\/p><\/dd>\n Content extraction does. AEOmatic reads content from Gutenberg, Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery, plus ACF fields, so schema and scoring reflect what your pages actually render. It does not add builder-native widgets.<\/p><\/dd>\n Schema is generated server-side and cached in post meta. Twenty-two page-level types (Article, BlogPosting, NewsArticle, TechArticle, Recipe, HowTo, FAQPage, QAPage, Review, Product, Service, LocalBusiness, Event, JobPosting, Course, Book, Movie, WebPage, AboutPage, ContactPage, CollectionPage, ProfilePage) plus Organization, Author\/Person, Breadcrumb, WebSite with SearchAction, VideoObject and Speakable.<\/p><\/dd>\n Yes. Product schema with price, availability, SKU, brand and ratings; variable products get AggregateOffer with a min\/max price range.<\/p><\/dd>\n Open AEOmatic \u2192 What did we do?<\/strong> for the live verification panel. It fetches your own URLs and shows what is being served, with a direct link to Google's Rich Results Test for your latest post.<\/p><\/dd>\n No. No external API calls on the front end, no telemetry, no analytics, no account. The only server-side HTTP requests are the verification panel fetching your own site, for administrators only.<\/p><\/dd>\n It is a rubric, and it is honest about which parts are heuristic. The Technical and AI crawler access categories are direct checks \u2014 a setting is either on or off. Content readiness is explicitly labelled a heuristic: it uses pattern matching to estimate how answer-shaped your content is. Category scores are combined with an unweighted mean, because no public evidence supports specific relative weights and inventing some would be false precision.<\/p><\/dd>\n Deleting the plugin removes every option, transient, scheduled task and post-meta key it created. Deactivating alone leaves your settings intact so reactivating does not lose your configuration.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
llms.txt<\/code> index at your site root, a \/llms-full.txt<\/code> full-text endpoint, and per-bot crawl directives in robots.txt<\/code>.<\/li>\nIt reads your page builder, not just Gutenberg<\/h4>\n\n
post_content<\/code> 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.<\/p>\n\nllms.txt<\/code> \u2014 reads that single extraction, so a page assembled in a builder is scored on what it actually renders.<\/p>\n\nBuilt to sit beside your SEO plugin, not replace it<\/h4>\n\n
Scores you can check yourself<\/h4>\n\n
Everything included, no account and no API key<\/h4>\n\n
\n
\/llms.txt<\/code> generator<\/strong> \u2014 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.<\/p><\/li>\n\/llms-full.txt<\/code> endpoint<\/strong> \u2014 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.<\/p><\/li>\nrobots.txt<\/code> 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.<\/p><\/li>\n<details><\/code>\/<summary><\/code> markup plus FAQPage JSON-LD. [aeo_faq]<\/code> \/ [aeo_qa]<\/code> shortcodes for the Classic Editor.<\/p><\/li>\nX-AI-Crawl<\/code>, X-AI-Citeable<\/code>, X-Content-License<\/code>, X-AI-Content-Type<\/code>, X-AI-Speakable<\/code> headers plus a Link: rel=\"ai-context\"<\/code> pointer to your llms.txt. These are proposed conventions, not a ratified standard, and no AI vendor has committed to reading them \u2014 so they ship as a setting you can switch off.<\/p><\/li>\nAI crawlers recognised<\/h4>\n\n
\n
Runs entirely on your own server<\/h4>\n\n
Who it is for<\/h4>\n\n
\n
Privacy Policy<\/h3>\n\n
llms.txt<\/code>, \/llms-full.txt<\/code> 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.<\/p>\n\n\n
aeomatic<\/code> folder to \/wp-content\/plugins\/<\/code>, or use Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/li>\n\/llms.txt<\/code> and \/llms-full.txt<\/code> endpoints and flushes rewrite rules for you.<\/li>\n\/llms.txt<\/code> returns a 404, confirm Settings \u2192 Permalinks<\/strong> is not set to \"Plain\", then click Save Changes<\/strong> there once.<\/p>\n\n\n\n
Will this get me cited by ChatGPT or ranked in AI search?<\/h3><\/dt>\n
What is the difference between AI readiness and AI visibility?<\/h3><\/dt>\n
Does the crawler log tell me if a page was cited?<\/h3><\/dt>\n
Does this conflict with Yoast SEO or Rank Math?<\/h3><\/dt>\n
Can I import my existing SEO plugin's settings?<\/h3><\/dt>\n
What is \/llms-full.txt?<\/h3><\/dt>\n
aeomatic_llms_full_max_items<\/code> filter.<\/p><\/dd>\nMy llms.txt or \/llms-full.txt shows a 404. How do I fix it?<\/h3><\/dt>\n
Does the plugin work with Elementor, Divi, or other page builders?<\/h3><\/dt>\n
Will this slow down my site?<\/h3><\/dt>\n
\/llms.txt<\/code> and \/llms-full.txt<\/code> are cached for an hour and flushed when content changes. The crawler log writes only when a recognised AI bot requests a page, and defers its single database write to the end of that request. There are no external requests and no third-party assets on public pages. Admin CSS and JS load only on AEOmatic screens.<\/p><\/dd>\nWhat schema types does it support?<\/h3><\/dt>\n
Does it work with WooCommerce?<\/h3><\/dt>\n
How do I know the schema is actually working?<\/h3><\/dt>\n
Does the plugin send my data anywhere?<\/h3><\/dt>\n
Is the audit score reliable?<\/h3><\/dt>\n
What happens when I uninstall AEOmatic?<\/h3><\/dt>\n
1.2.1<\/h4>\n\n
\n
&<\/code> written as &<\/code>, every <<\/code> as <<\/code>, every \/<\/code> as \/<\/code>, and every accented or non-Latin character as an escape sequence. It was valid and search engines accepted it, but it looked broken in page source and in validators \u2014 and on non-English sites a headline became nothing but escape codes. Output is now pretty-printed with slashes and Unicode intact. Nothing about which schema is generated has changed, only how it is written.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n
\n
1.1.9<\/h4>\n\n
\n
1.1.8<\/h4>\n\n
\n
rich-snippet<\/code> is present in the