Last updated: May 26, 2026
Merchant-Controlled AEO
The architectural alternative to platform-mediated AI commerce.
In 2026, AI engines became the discovery layer for commerce. ChatGPT Shopping, Microsoft Copilot, Google AI Mode, Gemini, and Perplexity now sit between catalogs and customers. Two architectures compete for that layer:
- Platform-mediated AI distribution — the platform (Shopify, via Agentic Storefronts) handles AI channel relationships on the merchant’s behalf. Fast. Opaque.
- Merchant-Controlled AEO — the merchant owns and audits every signal between the catalog and the AI layer. Slower to set up. Inspectable. Portable.
This page is the pillar reference for Merchant-Controlled AEO: definition, six pillars, implementation path, AI engine coverage, and where it fits.
Definition
Merchant-Controlled AEO (MC-AEO) is the architectural approach to AI commerce visibility where the merchant — not the platform — owns every signal between their catalog and AI platforms: robots.txt AI bot policy, llms.txt catalog map, Product JSON-LD schema, Agentic Commerce Protocol (ACP) feed generation, Model Context Protocol (MCP) server endpoints, and AI order attribution.
It is the alternative to platform-mediated AI distribution. Adobe Commerce / Magento 2 supports Merchant-Controlled AEO natively. Shopify is architected around platform-mediated AI distribution.
The core principle
Every AI commerce platform — OpenAI, Google, Microsoft, Perplexity, Anthropic — needs structured signals from merchants to surface products, cite stores, and execute agentic transactions. There are two ways to deliver those signals:
- Through a platform aggregator. The merchant publishes their catalog into a commerce platform (Shopify). The platform negotiates AI channel relationships, manages feed syndication, and exposes a single switch to the merchant: “on” or “off.”
- Directly, from the merchant’s own infrastructure. The merchant generates the feed, exposes the MCP endpoint, configures the bot policy, persists the attribution data, and applies to AI platforms in their own name.
Merchant-Controlled AEO is the second path. It does not mean rejecting AI platforms — it means owning the interface to them.
The six pillars
Merchant-Controlled AEO is not a single feature. It is six signals, each configured and auditable independently:
Pillar 1 — robots.txt AI bot access
AI engines crawl through dedicated user-agents: OAI-SearchBot, GPTBot, ChatGPT-User (OpenAI), PerplexityBot (Perplexity), Google-Extended (Google AI Mode, Gemini), ClaudeBot and Claude-Web (Anthropic), Bingbot (Microsoft Copilot), CCBot (Common Crawl), Applebot-Extended (Apple Intelligence).
A default Adobe Commerce robots.txt blocks most of these via wildcard rules. Merchant-Controlled AEO requires explicit allow directives per bot, with per-store-view variants for multi-locale stores. Module: angeo/module-robots-txt-aeo.
Pillar 2 — llms.txt catalog map
The emerging llms.txt convention provides AI systems with a machine-readable map of a site’s most important content. For commerce, this means category structure, product collections, and key resource pages — in a format optimized for LLM ingestion.
Magento has no native llms.txt support. Merchant-Controlled AEO requires generating it per store view, regenerating on catalog changes, and exposing it at the root domain. Module: angeo/module-llms-txt.
Pillar 3 — Product JSON-LD schema
AI engines parse Product JSON-LD to extract availability, pricing, ratings, brand, and identifiers. For ChatGPT Shopping ACP conformance, offers.availability is mandatory. For editorial citation, aggregateRating, brand, sku, gtin13, and priceValidUntil materially affect surfacing quality.
Magento’s default Luma theme emits a partial Product schema. Merchant-Controlled AEO completes it. Module: angeo/module-rich-data.
Pillar 4 — Agentic Commerce Protocol (ACP) feed
The Agentic Commerce Protocol is the spec OpenAI uses to ingest merchant catalogs into ChatGPT Shopping. It defines required product fields, refresh cadence, image formats, and conformance rules.
Shopify generates and syndicates this feed centrally for Agentic Storefronts merchants. Merchant-Controlled AEO requires generating an ACP-spec feed locally, applying at chatgpt.com/merchants, passing conformance review, and maintaining a 15-minute refresh interval. Module: angeo/module-openai-product-feed.
Pillar 5 — Model Context Protocol (MCP) server endpoint
MCP is the emerging standard for AI agents to access live data from external systems — live inventory, real-time pricing, variant availability, customer-specific catalogs. In a Merchant-Controlled AEO stack, the MCP server runs on the merchant’s infrastructure and exposes commerce data directly to AI agents under bearer-token authentication.
Production MCP adoption in commerce is still early, but the infrastructure is foundational for agentic checkout. Module: angeo/module-openai-product-feed-api.
Pillar 6 — AI order attribution
Without AI attribution, AI-driven revenue appears as direct or dark traffic in GA4. Merchant-Controlled AEO requires capturing AI referrers (chatgpt.com, perplexity.ai, copilot.microsoft.com, gemini.google.com) at session start and persisting them to sales_order.ai_referrer through checkout.
This is the difference between knowing “AI drove 12% of orders last quarter” and not knowing.
Implementation path: from 25% to 90%+ AEO score
A default Adobe Commerce 2.4.x install scores approximately 25% on a 9-signal AEO audit. The implementation path to 90%+ is sequential and takes approximately 90 minutes of focused work, plus elapsed time for OpenAI conformance review.
| Step | Pillar | Effort | AEO score impact |
|---|---|---|---|
| 1 | Unblock AI bots in robots.txt | ~10 min | +15 points |
| 2 | Generate llms.txt | ~15 min | +10 points |
| 3 | Complete Product JSON-LD | ~20 min | +15 points |
| 4 | Generate ACP feed + apply | ~25 min config + review queue | +15 points |
| 5 | Expose MCP endpoint | ~10 min | +10 points |
| 6 | AI order attribution | ~10 min | +5 points (operational, not retrieval) |
Verifiable at any step with one command:
bin/magento angeo:aeo:audit
✓ PASS robots.txt All 10 AI bots permitted
✓ PASS llms.txt Generated — 12,400 products mapped
✓ PASS Product JSON-LD offers.availability present
✓ PASS ACP product feed Spec-compliant — 15min refresh
✓ PASS MCP server endpoint /mcp/v1 active
✓ PASS AI order attribution sales_order.ai_referrer column active
AEO Score: 91% — ExcellentAI engine coverage
A fully configured Merchant-Controlled AEO stack reaches the same AI commerce channels as a platform-mediated approach:
| AI engine | Primary signal | Secondary signal |
|---|---|---|
| ChatGPT Shopping | ACP feed (applied via chatgpt.com/merchants) | OAI-SearchBot crawl + Product JSON-LD |
| ChatGPT (editorial citation) | OAI-SearchBot crawl + llms.txt | Server-rendered content + FAQPage schema |
| Perplexity | PerplexityBot crawl + llms.txt | Product JSON-LD |
| Google AI Mode | Google Merchant Center feed | Google-Extended crawl + Product JSON-LD |
| Gemini app | Google Merchant Center feed | Google-Extended crawl |
| Microsoft Copilot | Bingbot crawl + Product JSON-LD | Custom ACP feed configuration |
| Claude (Anthropic) | ClaudeBot / Claude-Web crawl | llms.txt + server-rendered content |
| Apple Intelligence | Applebot-Extended crawl | Product JSON-LD |
Coverage is achievable without a platform intermediary. The trade-off is operational: the merchant maintains the signals; the merchant audits them; the merchant migrates them if they change platforms.
Merchant-Controlled AEO vs platform-mediated AI distribution
| Dimension | Platform-mediated (Shopify) | Merchant-Controlled AEO (Adobe Commerce) |
|---|---|---|
| Setup effort | Near-zero for eligible merchants | ~90 min + conformance review queue |
| Default AI visibility | Yes, via Agentic Storefronts | No, requires explicit configuration |
| Feed transparency | Low — platform-managed | High — generated locally, fully auditable |
| Per-signal control | Limited — single on/off switch | Full — each pillar configurable independently |
| Multi-store-view granularity | Limited without Shopify Plus | Native per-store-view |
| B2B catalog depth | Constrained to standard fields | Full attribute system + price books |
| Data ownership | Transits through platform | Direct from merchant infrastructure |
| Auditability | Black-box debugging | CLI audit, one command |
| Portability across platforms | Low — coupled to Shopify ecosystem | High — signals are standards-based |
| Fee structure exposure | Subject to platform pricing changes | No platform mediation fees on AI traffic |
Who needs Merchant-Controlled AEO
This architecture is not the right choice for every merchant. Honest segmentation:
Strong fit
- Mid-market and enterprise Adobe Commerce merchants with technical teams or implementation partners
- Multi-store, multi-language, multi-currency operators — EU, UK, APAC primary markets where Shopify AI features are US-weighted
- B2B manufacturers and distributors — complex pricing rules, customer-specific catalogs, configurable products, ERP integration
- Regulated industries — medical, industrial, financial — where catalog data should not transit through third-party distribution layers without auditability
- Merchants with strategic catalog data who want to know exactly what AI platforms receive about their products
- Anyone running independent commerce infrastructure — Adobe Commerce, Magento Open Source, Mage-OS — where platform mediation is structurally unavailable
Weak fit
- Single-store DTC brands under 10k SKUs targeting US consumers — Shopify Agentic Storefronts is the faster, lower-effort path
- Merchants without technical capacity or implementation partner — Merchant-Controlled AEO requires module installation, configuration, and ongoing maintenance
- Stores where AI traffic is not yet economically significant — defer until the channel is worth instrumenting
The right question is not “Shopify or Magento?” — it is “do the constraints of platform-mediated distribution match my business, or do I need to own the infrastructure?”
The strategic case
Platform-mediated AI distribution is convenient now because AI commerce is consolidated around a small number of platforms with active partnership agreements. That consolidation is unlikely to last. As MCP, ACP, and successor protocols stabilize, AI engines will multiply — vertical-specific agents, regional engines, enterprise-internal AI, marketplace AI layers. Each will need feed access, bot crawl access, and structured data.
A merchant on Shopify reaches the platforms Shopify has agreements with. A merchant running Merchant-Controlled AEO reaches any AI engine that speaks the open standards — present and future. The signals are not Shopify-specific or Magento-specific. They are protocol-specific: robots.txt is a 30-year-old standard, JSON-LD is W3C, ACP is OpenAI’s open spec, MCP is Anthropic’s open spec, llms.txt is an emerging community convention.
Owning the infrastructure between your catalog and the AI layer is increasingly the more defensible long-term position — not because platform mediation is bad, but because the AI layer itself is fragmenting faster than any single platform aggregator can keep up with.
Implementation reference
The angeo open-source module suite implements all six pillars of Merchant-Controlled AEO for Adobe Commerce / Magento 2:
| Pillar | Module | License |
|---|---|---|
| robots.txt AI bot access | angeo/module-robots-txt-aeo | OSL-3.0 (free) |
| llms.txt | angeo/module-llms-txt | OSL-3.0 (free) |
| Product JSON-LD schema | angeo/module-rich-data | OSL-3.0 (free) |
| ACP product feed | angeo/module-openai-product-feed | OSL-3.0 (free) |
| MCP server endpoint | angeo/module-openai-product-feed-api | OSL-3.0 (free) |
| 9-signal AEO audit CLI | angeo/module-aeo-audit | OSL-3.0 (free) |
Run the audit on your store before installing anything — it reports the current AEO score and shows which pillars are already in place.
Related reading
- Shopify vs Magento for AI Commerce in 2026 — full platform comparison with retrieval tests
- Magento 2 AEO Guide — step-by-step technical implementation
- Magento 2 ChatGPT Shopping Registration — applying for ACP feed eligibility
- Magento 2 robots.txt for AI Bots — unblocking OAI-SearchBot, Google-Extended, PerplexityBot
- Why Magento product descriptions are invisible to ChatGPT — JavaScript rendering and AI extraction
- Free AEO audit for your store
Merchant-Controlled AEO is the position angeo.dev builds for: open-source modules, auditable signals, no platform mediation between your catalog and the AI layer. Start with the free audit — it shows you where your store sits today.