Protocols and platform status change. Verify current spec versions before implementation. Reflects ACP, UCP, and AP2 as of June 2026.

TL;DR. Default Magento has none of the signals AI agents need to discover, understand, or transact with your store. This page maps every signal, every protocol, every open-source module, and every implementation step — in priority order.

The AEO foundation (robots.txt + llms.txt + schema) takes 90 minutes. ACP conformance review adds 1–4 weeks. UCP manifest adds 30–60 minutes once foundations are in place. Multi-protocol payment readiness (AP2, Visa TAP, Mastercard Agent Pay) is handled by your payment processor.

What is agentic commerce — and what does it mean for Magento?

Agentic commerce is when an AI assistant (ChatGPT, Gemini, Copilot, Perplexity) finds a product and completes the purchase for a user — without the user ever visiting your storefront. The shopper says “order trail shoes under €120 that arrive by Friday” and the agent handles discovery, comparison, and checkout.

For Magento merchants this creates both an opportunity and an infrastructure gap. Platforms like Shopify handle the AI channel relationship centrally — their merchants get default syndication with no individual setup. Magento merchants own their stack, which means full control and full responsibility. Every AI visibility signal must be configured deliberately.

The good news: once configured, a Merchant-Controlled AEO stack reaches the same AI commerce channels as platform-mediated approaches — with full auditability, no platform dependency, and no revenue share to a commerce aggregator.

→ See: Shopify vs Magento for AI Commerce 2026: Platform-Mediated vs Merchant-Controlled AEO

The agentic commerce protocol landscape in 2026

Five protocol families now shape agentic commerce. Magento merchants do not integrate all of them directly — the cards below map what each requires at the merchant level.

Merchant decision rule: Implement ACP first (broadest reach, clearest conformance path). Prepare UCP manifest second (Google ecosystem checkout). AP2 / Visa TAP / Mastercard Agent Pay resolve through your payment processor automatically.

→ ACP vs UCP for Magento 2: Which Protocol Should You Implement First?

Implementation path: 25% → 90%+ AEO score

A default Magento 2.4.x install scores approximately 25% on the angeo AEO audit. The steps below are sequential — each builds on the previous. Active configuration time: ~90 minutes. Total elapsed including OpenAI review: 1–4 weeks.

1. 1

   Unblock AI crawlers in robots.txt

   Default Magento blocks most AI bots via wildcard rules. In 2026 more than ten named AI crawlers and fetchers matter, from OpenAI, Anthropic, Perplexity, Apple and others. None are explicitly allowed out of the box.

   Module: angeo/module-robots-txt-aeo — explicit rules for the AI search, user-triggered and training crawlers, append-only, per-store-view support.

   ⏱ ~10 min +15 pts Full guide →
2. 2

   Generate llms.txt catalog map

   llms.txt tells AI systems what your store is, what categories exist, and what products you sell — in a format optimized for LLM ingestion. Magento has no native support.

   Module: angeo/module-llms-txt — auto-generates llms.txt and llms.jsonl per store view, regenerates on catalog changes.

   ⏱ ~15 min +10 pts Full guide →
3. 3

   Complete Product JSON-LD schema

   The single most common failure: offers.availability missing — ChatGPT Shopping skips those products entirely. Magento’s default Luma outputs partial microdata. Hyvä emits Product microdata but no JSON-LD and no brand, GTIN, shipping or return fields.

   Module: angeo/module-rich-data — server-rendered JSON-LD with offers.availability, aggregateRating, brand, sku, gtin13, priceValidUntil. Works with all frontends including Hyvä.

   ⏱ ~20 min +15 pts Full guide →
4. 4

   Generate ACP product feed and apply for ChatGPT Shopping

   The ACP product feed is what OpenAI uses to ingest your catalog into ChatGPT Shopping — required fields, image formats, refresh cadence, and conformance rules. Shopify generates this centrally; Magento merchants generate it independently.

   Module: angeo/module-openai-product-feed — spec-compliant feed on a schedule you control (full snapshot at least daily). Apply at chatgpt.com/merchants.

   ⏱ ~25 min + 1–4 weeks review +15 pts Full guide →
5. 5

   Configure UCP manifest for Google AI Mode

   UCP exposes a /.well-known/ucp profile that AI agents use to discover your store’s capabilities, then uses Magento’s GraphQL API for browsing and REST API for cart operations. Steps 1–4 are prerequisites.

   angeo/module-ucp publishes the profile (spec 2026-08-25) and angeo/module-ucp-catalog serves catalog search and lookup. See the 10-step checklist.

   ⏱ ~30–60 min +10 pts 10-step UCP checklist →
6. 6

   Add AI order attribution

   Without attribution, AI-driven revenue appears as direct or dark traffic in GA4. AI referrers (chatgpt.com, perplexity.ai, copilot.microsoft.com, gemini.google.com) must be captured at session start and persisted through checkout to sales_order.ai_referrer.

   This is the difference between knowing “AI drove 12% of orders last quarter” and not knowing.

   ⏱ ~10 min Operational signal

Install all modules in one command

All modules are MIT-licensed and free on Packagist. Implementation help and enterprise configuration are available as paid services.

Open-source module reference

AI engine coverage by signal

A fully configured Angeo AEO stack reaches every major AI commerce channel. The table maps which signals each platform uses as primary and secondary inputs.

Agentic commerce timeline — what changed and when

Complete guide library

Foundation — AEO basics

Protocols — ACP and UCP

AI content and product visibility

Frequently asked questions