AEOmatic – AEO for AI Search: llms.txt, Schema & AI Crawler Check

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.

Mostly not, and be careful with anyone who says otherwise. Google says AI Overviews and AI Mode use the same crawling and indexing as normal search, with no special AI markup required. What is different is practical: CDNs and firewalls often block AI crawlers while letting Googlebot through, most AI crawlers do not run JavaScript, and AI answers are lifted from pages that state the answer plainly. AEOmatic focuses on those differences.

It is not a ranking factor. Google does not use it, and public crawl data shows AI crawlers rarely request it so far. Some AI tools can use it when they are pointed at a site. AEOmatic generates and updates it automatically, so it costs you nothing to have, and you can switch it off under AEOmatic → Settings.

They handle classic SEO, and AEOmatic does not replace them. It adds checks they are not built around: whether AI crawlers really get through your CDN or firewall, what a crawler that does not run JavaScript reads, which AI bots visit and what status they get, and how easily an answer can be quoted from each post.

Yes. Everything described on this page is in this plugin, with no account, no API key and no usage limits.

AI readiness is how well-prepared your site is — measurable from your own database and settings, which is what AEOmatic scores. AI visibility is whether AI systems actually surface or cite you — measurable only by querying those engines from outside your site, which AEOmatic does not do. The dashboard is labelled "AI Readiness" for that reason.

The check sends requests from your own server using each crawler's name. Some firewalls also verify a crawler's IP address, so they block this test while letting the real crawler in. When the AI crawler log shows successful real visits from that crawler, the check says so and marks it for review instead of blocked.

No. Every request goes to your own site. The test requests are tagged so the AI crawler log does not record them as real visits.

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.

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

Yes — 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.

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 aeomatic_llms_full_max_items filter.

Check that Settings → Permalinks is not set to "Plain" — the endpoints need a rewrite rule, which plain permalinks do not support. Then click Save Changes on that screen once. Also confirm llms.txt is enabled under AEOmatic → Settings.

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.

Schema is generated server-side and cached in post meta. /llms.txt and /llms-full.txt 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.

Twenty-one page-level types (Article, BlogPosting, NewsArticle, TechArticle, Recipe, Review, Product, SoftwareApplication, Service, LocalBusiness, Event, JobPosting, Course, Dataset, Book, Movie, WebPage, AboutPage, ContactPage, CollectionPage, ProfilePage) plus Organization, WebSite, WebPage, Author/Person, Breadcrumb, VideoObject and Speakable. FAQPage and HowTo JSON-LD and the sitelinks search box are not emitted: Google no longer shows them. The FAQ block keeps FAQPage microdata on its visible questions and answers.

Yes. Product schema with price, availability, SKU, brand and ratings; variable products get AggregateOffer with a min/max price range.

Open AEOmatic → What did we do? 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.

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.

It is a rubric, and it is honest about which parts are heuristic. The Technical and AI crawler access categories are direct checks — 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.

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.