Magento AEO: Why AI Visibility Needs Explicit Setup

Why Magento requires explicit AEO configuration: platforms like Shopify have platform-level AI commerce infrastructure — merchants get default syndication through partnership agreements. Magento merchants own their stack, which means full control and full responsibility. Every AI visibility signal must be configured deliberately.

Based on sampled store audits · most stores significantly improve within about 90 minutes · check which column you are in

---

Install in one command

composer require \
  angeo/module-aeo-audit \
  angeo/module-robots-txt-aeo \
  angeo/module-llms-txt \
  angeo/module-rich-data \
  angeo/module-openai-product-feed

bin/magento setup:upgrade && bin/magento cache:flush
bin/magento angeo:aeo:audit

Or request a free manual audit →

---

Built for

---

The modules — one per signal

View all packages on Packagist →

---

Default Magento 2 vs the Angeo suite

---

How the AEO stack works

Magento 2 store
       ↓
AEO signals configured
(robots.txt · llms.txt · schema · ACP feed · rendering)
       ↓
AI crawlers gain access
(OAI-SearchBot · PerplexityBot · Google-Extended · ClaudeBot)
       ↓
Content extraction + retrieval
       ↓
AI commerce platforms
(ChatGPT Shopping · Perplexity answers · Gemini AI Mode)
       ↓
AI recommendation → high-intent shopper

Default Magento 2 fails at the first step — AI crawlers are blocked before extraction begins.

---

Two scores, because they measure different things

AI Discovery asks whether AI systems can find, fetch and read the store: crawler access, llms.txt, sitemap, Product schema, Open Graph, canonical tags. This is the half that pays off today — ChatGPT, Perplexity and Gemini are already citing merchants that get it right.

Agentic Readiness asks whether an agent can transact: a UCP profile at /.well-known/ucp, a reachable MCP endpoint, the well-known discovery matrix. Adoption here is early, and that is exactly why it is scored separately — merged into one number, a near-universal zero would drown out the discovery work that is already worth doing.

The scan reports both. So does angeo/module-aeo-audit, on the same weights, so an external scan and an in-store audit can be compared directly. ACP vs UCP — which to implement first →

---

Why open-source?

AEO is infrastructure — it should not be locked behind a paywall. Every Magento merchant should be able to allow AI crawlers, generate llms.txt, and add proper Product schema without a subscription. The modules are MIT licensed and free on Packagist.

Implementation help, custom AEO configuration, and enterprise consulting are available as paid services. Free audit →

---

Featured guides

• Complete Magento 2 AEO Guide — all signals, CLI commands, theory, benchmarks
• What scanning live Magento stores actually found — measured results across a sample
• The product description that AI can’t read — JavaScript rendering gap and fix
• Shopify vs Magento for AI commerce 2026 — AEO capabilities compared
• ACP vs UCP for Magento 2 — which agentic protocol to implement first

View all articles →

---

Frequently asked questions

How do I check my Magento store’s AEO score?

Two ways. The free scan reads your store the way an AI crawler does and needs no installation — it returns an AI Discovery score and an Agentic Readiness score in a few seconds. For a full audit, angeo/module-aeo-audit runs inside Magento and measures 16 signals, including ones no external tool can see — such as whether Product schema is rendered server-side or assembled by JavaScript after the crawler has left. Both use the same weights, so the two scores are directly comparable.

What is AEO for Magento 2?

AEO (AI Engine Optimization) is the practice of configuring a Magento 2 store so AI assistants — ChatGPT, Gemini, Perplexity, Claude — can discover, read, and recommend it. Key signals: allowing AI crawlers in robots.txt, generating llms.txt, adding offers.availability to Product schema, and submitting an ACP product feed. Default Magento 2 installations typically fail most of these checks. Complete guide →

Does ChatGPT crawl Magento stores?

ChatGPT uses OAI-SearchBot to crawl the web for live query answers. By default, Magento 2’s robots.txt can block OAI-SearchBot via wildcard rules — making the store invisible in ChatGPT search results. Adding an explicit Allow: / rule for OAI-SearchBot before any wildcard Disallow is one of the most impactful AEO fixes for most stores. robots.txt fix guide →

What is llms.txt and does Magento support it?

llms.txt is a plain-text file at yourstore.com/llms.txt — a structured catalogue map for AI systems, similar to sitemap.xml but for AI assistants. Default Magento 2 does not generate it. The free angeo/module-llms-txt generates spec-compliant llms.txt and llms.jsonl per store view with cron-based auto-regeneration. Generation guide →

Does Magento 2 support ChatGPT Shopping?

Yes, but it requires manual configuration. Magento merchants apply at chatgpt.com/merchants, generate a spec-compliant ACP product feed, and pass OpenAI’s conformance checks — including offers.availability in Product schema, which default Magento omits. The free angeo/module-openai-product-feed handles feed generation. Registration guide →

What is the difference between AI Discovery and Agentic Readiness?

AI Discovery measures whether AI systems can find, fetch and read a store: robots.txt access, llms.txt, sitemap, Product schema, Open Graph, canonical tags. Agentic Readiness measures whether a shopping agent can transact with it: a UCP profile at /.well-known/ucp, a reachable MCP endpoint, and the well-known discovery matrix. They are scored separately because agentic adoption is early — a store can be perfectly discoverable and still have no agentic surface at all, and merging the two would hide that.

Is this compatible with Hyvä Theme?

Yes. All modules operate at the Magento core level — compatible with Luma, Hyvä, and any custom frontend. Hyvä stores have one additional consideration: product descriptions rendered via Alpine.js x-show may have reduced AI extraction reliability. Rendering guide →

Is Adobe Commerce supported?

Yes. All modules support Magento 2.4.x on both Open Source and Adobe Commerce. Adobe Commerce Cloud requires a Fastly cache purge after any robots.txt change.

---

Audit it from inside

The free scan sees what a crawler sees. The module sees everything — including signals no external tool can reach, like whether your product schema is rendered server-side or assembled by JavaScript after the crawler has left.

composer require angeo/module-aeo-audit
bin/magento setup:upgrade
bin/magento angeo:aeo:audit

Same weights as the scan above, so the two scores are directly comparable. The CLI prints the exact Composer command to fix each failing signal.

---

Part of the AI Commerce Optimization service suite · Open-source modules on Packagist