Magento AEO

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.

⚠ Default Magento 2 install

  • AEO score: ~25%
  • ✗ AI crawlers blocked by default
  • ✗ No llms.txt
  • ✗ Product schema incomplete
  • ✗ No AI product feed

✓ With Angeo AEO suite

  • AEO score: 80–91%
  • ✓ All 10 AI bots allowed
  • ✓ llms.txt auto-generated
  • ✓ offers.availability live
  • ✓ ACP feed validated

Based on sampled store audits · 90 minutes from install to 80%+ score

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

🏗 Magento agencies

Deployable AEO stack for every client project

🏪 Adobe Commerce merchants

Enterprise stores needing AI shopping surface eligibility

⚡ Hyva stores

Theme-independent — works with any Magento frontend

📊 Technical SEO teams

Auditable signals with CLI output and 0–100 scoring

🔬 AI commerce experimentation

Early movers building agentic commerce infrastructure

The modules — one per signal

Module Signal fixed
angeo/module-aeo-audit CLI audit — all 9 signals, score, fix commands
angeo/module-llms-txt llms.txt + llms.jsonl — AI catalog map per store view
angeo/module-openai-product-feed ACP product feed — AI commerce platforms, 15-min refresh
angeo/module-rich-data Product schema — offers.availability, aggregateRating, FAQPage
angeo/module-openai-product-feed-api ACP REST API — 6 endpoints for live AI agent queries
angeo/module-robots-txt-aeo robots.txt — Allow rules for all 10 AI bots, append-only

View all packages on Packagist →

Default Magento 2 vs with the Angeo suite

Signal Default With suite
AI crawler access (OAI-SearchBot, PerplexityBot, ClaudeBot) ✗ Blocked ✓ All 10 bots
llms.txt catalog map ✗ Missing ✓ Auto-generated
Product schema — offers.availability ⚠ Missing ✓ Live stock status
ACP product feed ✗ Not available ✓ .jsonl.gz validated
FAQPage schema ✗ Missing ✓ Auto-detected
Server-rendered product description ⚠ Hidden in JS tab ✓ Layout override
AEO score ~25% 80–91%

How the AEO stack works

Magento 2 store
       ↓
9 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.

🔓 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

View all articles →

Frequently asked questions

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 — 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 blocks 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 the single most impactful AEO fix 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 catalog 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 must apply at chatgpt.com/merchants, generate a spec-compliant ACP product feed in .jsonl.gz format, 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 →

Is this compatible with Hyva Theme?

Yes. All modules operate at the Magento core level — compatible with Luma, Hyva, and any custom frontend. Hyva 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.

Check your store’s AEO score

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

One command checks all 9 signals and outputs the exact Composer commands to fix each failure.

Request a free manual audit → View all modules on Packagist

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