Is Your Magento Store Visible to ChatGPT & Gemini?
Enter your store URL. The scan fetches your store exactly as an AI crawler does and reports what it found — every signal, the evidence, and the command that fixes it.
Scan your store
Two scores come back. AI Discovery — can AI systems find and read the store. Agentic Readiness — can a shopping agent actually transact with it.
What the scan reads
Fourteen signals, fetched from outside with no access to your admin. Each one is weighted by how much it affects whether an AI assistant can use your store — the widths in the result bar are those weights.
Full weights and reasoning in the Magento 2 AEO Guide 2026 →
Outside and inside see different things
Both use the same weights, so a signal never means two things. What differs is reach — and where they disagree, the disagreement is itself the finding.
The scan, from outside
- What an AI crawler actually receives
- Catches a feed that returns 401 to anonymous callers — installed from inside, unreachable from outside
- Catches schema that only appears after JavaScript runs
- Works on any store, including a competitor’s
The module, from inside
- All 16 signals, including the four no external tool can reach
- File freshness — a sitemap whose newest entry is 264 days old
- Core Web Vitals from CrUX field data
- Score Trend over time, and a CI gate on regressions
Run the full audit from the CLI
One command, 16 signals, the same scoring as the scan above — so the two numbers are directly comparable rather than two opinions.
What a low score actually costs
A default Magento install usually fails at the first step: robots.txt blocks the AI crawlers through a wildcard rule, so nothing downstream matters — the store is never read, never extracted, never cited. Scanning live stores at scale →
Critical signals: robots.txt AI bot access, llms.txt content map, Product JSON-LD, ACP product feed.
Supporting signals: merchant return and shipping policies, UCP profile, MCP endpoint, llms.jsonl, Organization and FAQPage schema, JSON-LD quality, sitemap, Open Graph, canonical and hreflang, Core Web Vitals.
Each failing signal in the report carries the exact command that fixes it. Most stores clear the critical ones in under 90 minutes.
Fix what the scan found
Open-source Magento 2 modules, one per signal. Composer install, MIT licensed, no SaaS. Ten of the thirteen are listed here — the rest are on the modules index.
All 13 modules, with docs for each → · Compatibility matrix · Packagist
Want it done for you?
The modules are free and the scan is free. If you would rather not spend the afternoon on it, send the report link from your scan and I will quote the work — or say what I would do differently, at no charge.
Frequently asked questions
Why is my Magento store not visible in ChatGPT?
The most common reasons: robots.txt blocks OAI-SearchBot and GPTBot via a wildcard Disallow rule, there is no llms.txt file, Product JSON-LD is missing offers.availability, or no ACP product feed has been submitted. The scan on this page tells you which of these applies to your store in a few seconds.
What is AEO and how is it different from SEO?
SEO gets your store ranked in Google’s link list. AEO (AI Engine Optimization) gets your store cited in AI-generated answers — ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews. The signals differ: robots.txt AI bot access, structured data, llms.txt, and ACP product feeds. A store with strong SEO often scores low on AEO by default.
What is the difference between AI Discovery and Agentic Readiness?
AI Discovery measures whether AI systems can find, fetch and read the store: crawler access, llms.txt, sitemap, Product schema, Open Graph, canonical tags. Agentic Readiness measures whether a shopping agent can transact with it: a UCP profile, a reachable MCP endpoint, and the well-known discovery matrix. They are scored separately because agentic adoption is early, and merging them would bury the discovery work that already pays off.
Do I need to install anything to run the scan?
No. The scan reads your store from outside, exactly as an AI crawler does — no module, no admin access, no signup. Install angeo/module-aeo-audit only if you want the in-store audit, which reaches four signals an external scan cannot see.
Why does the module give a different score from the scan?
Both use the same weights, so individual signals always agree. The totals can differ because the module measures 16 signals and the external scan measures 14 of them — it cannot see file freshness, Core Web Vitals field data, or whether schema is server-rendered or added by JavaScript. Where the scan and the module disagree about one signal, the scan is usually right about what an agent experiences: a feed behind an auth wall, for instance, looks installed from inside and unreachable from outside.
How long does it take to fix AEO issues in Magento 2?
Most critical fixes take under 90 minutes: robots.txt, llms.txt generation, Product schema, and ChatGPT Shopping registration. Every failing signal in the report shows the exact command to fix it.
Is the audit module free?
Yes. angeo/module-aeo-audit is free and MIT licensed, as are all the fix modules. No signup, no SaaS — it runs entirely on your own server.
Does this work with Adobe Commerce and Hyvä?
Yes. All Angeo modules support Magento Open Source 2.4+ and Adobe Commerce, and are theme-independent, including Hyvä. PHP 8.2+ required. On Adobe Commerce Cloud, robots.txt changes need a Fastly cache purge to take effect. The compatibility matrix lists the declared version constraint for every module.