Open source · MIT · Magento 2.4.x
Thirteen modules that make a Magento 2 store readable, quotable and purchasable by AI.
Every AEO signal an AI engine checks has one module behind it. Install the whole stack or just the piece you are missing. No licence key, no admin account, no telemetry — and around 2,600 installs across the suite so far, all countable on Packagist.
You almost certainly do not want all thirteen. Install the audit first — it names the signals you actually fail, and most stores fail two or three.
Measure first
Before changing anything, find out what AI engines currently see. Both are read-only.
angeo/module-aeo-audit
A read-only CLI audit that scores 15 AI-visibility signals for every store view and prints the exact command to fix each failure.
- Fifteen signals, one command
- Severity, not just pass or fail
- Real field performance
angeo/module-aeo-brand-visibility
Measures whether ChatGPT, Claude, Perplexity, Gemini and Groq actually mention your brand when someone asks a buying question — and how they describe you when they do.
- Recall and citation rate
- Competitors in the same run
- Three-valued tone analysis
Access and structure
A crawler has to be allowed in, then given something it can parse. Everything downstream depends on these three.
angeo/module-robots-txt-aeo
Manages AI crawler directives in robots.txt from the Magento admin — OAI-SearchBot, GPTBot, ChatGPT-User, PerplexityBot, Perplexity-User, Google-Extended, ClaudeBot, anthropic-ai, Claude-User, Applebot, cohere-ai, Amazonbot and Meta-ExternalAgent — without destroying the rules you already have.
- Lossless round-trip parsing
- A current bot catalogue
- Usage terms, not just access
angeo/module-llms-txt
Generates spec-compliant llms.txt, llms-full.txt and streaming JSONL so an AI reads a structured summary of your catalogue in one request instead of crawling thousands of rendered pages and guessing.
- Three formats, one pipeline
- Safe on large catalogues
- Markdown page mirrors
angeo/module-rich-data
Magento’s default theme emits partial microdata.
- Availability as a full URI
- Return and shipping details
- Product identifiers
Product data and feeds
ChatGPT Shopping does not read your storefront. It reads a registered feed built to the Agentic Commerce Protocol.
angeo/module-openai-product-feed
Builds the Agentic Commerce Protocol product feed that ChatGPT Shopping reads, on a schedule you control.
- Every product type
- Built for real catalogues
- Refresh cadence that passes review
angeo/module-openai-product-feed-api
A REST layer over your product data — endpoints for feeds, products and promotions — for integrations that need to pull rather than wait for a scheduled file.
- Six endpoints, pull instead of push
- Authenticated end to end
- Promotions mapped to spec
angeo/module-ai-description-updater
Generates product descriptions in bulk with OpenAI, Claude or Gemini, with a review step before anything reaches the storefront.
- Three providers, chosen per task
- Bulk and scheduled
- Dry run before anything ships
Live agent access
A static file is a snapshot. MCP is a live connection — an agent asks your store a question and gets current data back.
angeo/module-mcp-server
A Model Context Protocol server that gives AI agents live, structured, rate-limited access to your catalogue — product search, product cards, categories and store info.
- Structured access instead of scraping
- Read-only until you decide otherwise
- Rate limited at the server
angeo/module-mcp-checkout
Adds guest cart and checkout tools to the MCP server, so an agent can go from discovery to a placed order in one conversation: create_cart, add_to_cart, get_cart, get_shipping_methods, set_shipping_information, place_order.
- Six tools, one complete flow
- Guardrails on the server, not in the prompt
- Guest checkout by design
Agentic transaction
Being recommended is half of it. These let an agent verify who you are and complete a purchase without a browser.
angeo/module-ucp
Publishes a Universal Commerce Protocol profile at /.well-known/ucp with ECDSA P-256 signing keys, so an AI agent can verify who the merchant is before acting on their behalf.
- A signed, verifiable manifest
- Key rotation without downtime
- Validated against the spec
angeo/module-openai-instant-checkout
Implements Agentic Commerce Protocol Instant Checkout, so a purchase initiated inside an AI assistant can complete against your Magento store through a dedicated Agentic Checkout API rather than browser automation.
- A checkout built for agents
- Follows the protocol, not a workaround
- Uses your existing Magento rules
angeo/module-ucp-catalog
Implements the catalog.search and catalog.lookup services for Magento 2 — the REST endpoints your UCP profile advertises.
- Makes the profile honest
- catalog.search and catalog.lookup
- Spec 2026-04-08
Questions merchants ask before installing
Are the angeo Magento 2 modules really free?
Yes. All thirteen are MIT-licensed and published on Packagist and GitHub. There is no paid tier, licence key or usage limit. Angeo earns from audits, implementation and ongoing monitoring.
Which module should I install first?
angeo/module-aeo-audit. It is read-only and reports which AEO signals pass and which fail, so you install only the modules that close a real gap. Most stores fail two or three signals, not thirteen.
Do I need all thirteen?
Almost certainly not. The first five cover the signals that decide whether AI engines can read your store at all. The MCP and UCP modules matter when you want agents to query and transact, which is a later stage for most merchants.
Do they work on Adobe Commerce Cloud?
Yes, on Magento Open Source and Adobe Commerce 2.4.x with PHP 8.2 or later. On Cloud, purge the Fastly cache after changing robots.txt, or AI crawlers keep reading the cached version.
Will they slow down the storefront?
Generation runs on cron and CLI rather than page render, with batched cursor-based queries so large catalogues do not exhaust memory or lock tables. The MCP server is rate limited server-side.
Does installing these guarantee ChatGPT will recommend my store?
No, and anyone promising that is selling something. The modules fix the signals a merchant controls: crawler access, structured data, a conforming feed, a verifiable profile, live agent access. Whether an engine then recommends you also depends on price, reviews and third-party coverage no module can produce.
Not sure which signals you are failing?
Run the free web scanner for a score in about 30 seconds, or install the CLI audit and get the same check across every store view with the exact fix command for each failure.