# UCP Readiness Checklist for Magento 2: 10 Steps to AI Agent Commerce > Is your Magento 2 store ready for Google's Universal Commerce Protocol? 10 steps from AEO foundations to a verified UCP profile - with free MIT modules. Source: https://angeo.dev/ucp-readiness-checklist-magento/ Updated: 2026-10-09 *UCP is an actively evolving protocol - capabilities, naming, and merchant onboarding processes may change. This checklist reflects UCP version 2026-08-25, checked September 2026. We update this guide when the spec changes.* [image: UCP Readiness Checklist for Magento 2 - 10 steps from default installation to AI agent commerce readiness] 10 steps from default Magento 2 installation to UCP-ready AI agent commerce ### TL;DR - 2 minute version - UCP readiness is **not just installing a module** - it requires AEO foundations first (robots.txt, llms.txt, schema, feed) - Steps 1-4 are **AEO foundations** that also benefit Google Search, ChatGPT, and Perplexity visibility - Steps 5-8 are **UCP-specific**: module installation, key generation, profile enablement, verification - Steps 9-10 are **optimisation**: FAQ schema and a full AEO audit - Estimated total time: **4-6 hours** (excluding OpenAI's ACP feed approval timeline) - UCP discovery ≠ UCP recommendation. Completing this checklist makes your store *findable* - not automatically *recommended* In this guide - 10 min read 1. Foundation: Steps 1-4 (AEO prerequisites) 2. UCP implementation: Steps 5-8 3. What you have after Step 8 4. Optimisation: Steps 9-10 5. The complete picture 6. What comes next 7. FAQ Universal Cart has begun rolling out in the US as of May 19, 2026. Canada and Australia are next, per Google's announcements. The UK is expected to follow. If your Magento store has not implemented UCP, it cannot be discovered by AI agents using the UCP protocol - which Google is deploying across Search AI Mode, Gemini, and YouTube Shopping. This does not mean your store is invisible to all AI systems - Google Merchant Center feeds, direct crawling, and schema still matter - but UCP is an additional discovery layer that is growing in importance. This checklist covers the ten steps between a default Magento installation and a UCP-compliant store. Some take five minutes. Some take a few hours. All steps can be implemented on your existing Magento installation. *This guide is part of the [Merchant-Controlled AEO](https://angeo.dev/merchant-controlled-aeo/) architecture. For a plain-English explanation of what UCP is and why it matters, see [What Is UCP? A Store Owner's Guide](https://angeo.dev/what-is-ucp-for-store-owners/).* ## Before UCP: the foundation (Steps 1-4) UCP is the roof. These four steps are the foundation. Without them, UCP has nothing to build on - a UCP profile without indexed content and structured product data is a door with nothing behind it. These steps also improve your visibility in Google Search, ChatGPT, Perplexity, and Claude - they are valuable regardless of whether you implement UCP. ### Step 1 - Unblock AI crawlers in robots.txt **Time:** 5 minutes **Why it matters:** AI agents and crawlers need permission to access your store. Magento's default `robots.txt` blocks most of them. Open `yourstore.com/robots.txt` and verify that these bots are explicitly allowed: # Required for AI commerce visibility User-agent: OAI-SearchBot Allow: / Disallow: /checkout/ Disallow: /customer/ User-agent: Googlebot Allow: / Disallow: /checkout/ Disallow: /customer/ `OAI-SearchBot` is ChatGPT's search crawler. Google's AI Mode and Gemini shopping use the normal `Googlebot` index and Merchant Center; `Google-Extended` is only a token for Gemini training and grounding. Each named group must repeat your `Disallow` lines, because it replaces the `User-agent: *` group for that bot (RFC 9309). If any of these appear under a `Disallow: /` directive, fix it before proceeding. Everything else in this checklist is irrelevant if crawlers cannot reach your store. **Detailed guide:** [How to fix robots.txt for ChatGPT and Gemini ->](https://angeo.dev/magento-2-robots-txt-chatgpt-gemini-ai-bots/) ### Step 2 - Generate llms.txt **Time:** 10 minutes (automated) **Why it matters:** `llms.txt` tells AI systems what your store sells, in plain language. Without it, AI agents construct an approximate - and often inaccurate - model of your business. composer require angeo/module-llms-txt bin/magento module:enable Angeo_LlmsTxt bin/magento setup:upgrade The module generates both `llms.txt` and `llms.jsonl` from your live catalog automatically. Cron-scheduled to update when products change. Verify: visit `yourstore.com/llms.txt` - you should see a structured summary of your store, categories, and key products. **Detailed guide:** [How to generate llms.txt for Magento 2 ->](https://angeo.dev/how-to-generate-llms-txt-for-magento-2-in-5-minutes/) ### Step 3 - Implement Product JSON-LD schema **Time:** 1-2 hours **Why it matters:** AI agents - and UCP specifically - rely on structured product data. JSON-LD is the format both Google and OpenAI prefer. Magento's default uses microdata, which is less reliable for AI parsing. Critical fields to include: | Field | Why it matters | | `name` | Product name - used as the primary identifier | | `description` | Product description - AI agents read this to form recommendations | | `offers.price` | Current price - required for shopping comparisons | | `offers.priceCurrency` | Currency code - ambiguous pricing breaks AI agent trust | | `offers.availability` | **Most common failure.** ChatGPT Shopping and UCP both skip products without confirmed availability | | `sku` | Product identifier - used for cross-platform matching | | `aggregateRating` | Review score - affects recommendation confidence (if you have reviews) | **The single most common failure:** `offers.availability` missing. This one field determines whether AI agents consider your product purchasable. Without it, your products may be skipped entirely - regardless of how complete the rest of your schema is. **Detailed guide:** [Product JSON-LD schema for AI Search ->](https://angeo.dev/magento-2-product-schema-json-ld-ai-search/) ### Step 4 - Submit product feed for ChatGPT Shopping **Time:** 30 minutes + 1-4 weeks approval **Why it matters:** ACP and UCP serve different platforms but share the same foundation. A submitted product feed makes your products available for ChatGPT Shopping consideration. The product data you prepare - prices, availability, descriptions - is the same data UCP needs. composer require angeo/module-openai-product-feed bin/magento module:enable Angeo_OpenaiProductFeed bin/magento setup:upgrade Submit your feed through `chatgpt.com/merchants`. Approval typically takes one to four weeks. Note: OpenAI has not published a stable, widely-documented merchant onboarding standard as of May 2026 - treat the submission process as evolving. **Detailed guide:** [Magento 2 ChatGPT Shopping Registration ->](https://angeo.dev/magento-2-chatgpt-shopping-registration/) ## UCP implementation (Steps 5-8) With the foundation in place, your store is ready for UCP. These steps add the protocol-specific discovery layer. ### Step 5 - Install the UCP profile module **Time:** 10 minutes **Why it matters:** This is the discovery layer - the file at `/.well-known/ucp` that tells AI agents your store exists and what capabilities it supports. # Profile + catalog endpoints. Magento 2.4.x (catalog: 2.4.6+), PHP 8.2+, OpenSSL composer require angeo/module-ucp angeo/module-ucp-catalog bin/magento module:enable Angeo_Ucp bin/magento setup:upgrade bin/magento setup:di:compile bin/magento cache:flush ### Step 6 - Generate ECDSA signing keys **Time:** 5 minutes **Why it matters:** UCP requires cryptographic signing keys for secure communication between your store and AI agents. The module generates ECDSA P-256 keys - the same standard used by Apple Pay and Google Pay. bin/magento angeo:ucp:keys:generate Since spec 2026-08-25 the public keys are published in the profile's top-level `keys[]` array, an RFC 7517 JWK Set. Where the private key is stored depends on the module version: follow the [module README](https://github.com/angeo-dev/module-ucp). It never belongs in the profile itself. ### Step 7 - Enable the UCP profile **Time:** 2 minutes **Why it matters:** The module installs disabled by default. You need to explicitly opt in. Navigate to: **Stores -> Configuration -> Angeo -> UCP -> General -> Advertise UCP Profile: Yes** Advertise only the capabilities you actually serve. With `angeo/module-ucp-catalog` installed, `catalog.search` and `catalog.lookup` answer. Do not advertise cart or checkout until an endpoint exists: an agent will call what the profile declares. ### Step 8 - Verify the profile **Time:** 2 minutes **Why it matters:** A malformed profile is worse than no profile - it signals to AI agents that your store is unreliable. # Fetch and validate your UCP profile curl -s https://yourstore.com/.well-known/ucp | python3 -m json.tool You should see a valid JSON response with `version: "2026-08-25"`, your signing keys, and the `dev.ucp.shopping` service binding. Run the built-in validator: bin/magento angeo:ucp:validate --json Green pass means your profile is spec-compliant. Non-zero exit means something needs fixing - the output tells you what. **External validation:** You can also use [ucpchecker.com](https://ucpchecker.com) to validate your profile against the official conformance test suite. ## What you have after Step 8 **At this point, your store has a spec-compliant UCP profile at `/.well-known/ucp`.** AI agents that support UCP discovery can find your store and read its capabilities. This does not mean AI agents will immediately recommend your products. UCP discovery is one layer in a stack that also includes catalog quality, pricing, schema completeness, entity authority, and feed registration. Steps 9 and 10 address the most impactful remaining signals. Think of Steps 1-8 as infrastructure. What you build on that infrastructure - product quality, content quality, brand authority - determines the commercial outcome. ## Optimisation and monitoring (Steps 9-10) ### Step 9 - Answer real buyer questions on key pages **Time:** 1-2 hours **Why it matters:** Clear answers to real buyer questions - shipping, returns, sizes, compatibility - give assistants something concrete to quote. FAQPage markup is optional: it helps parsers, but Google has shown no FAQ rich results since May 2026. Add short Q&A sections to: - Your top 10 category pages (by revenue) - Your top 20 product pages (by revenue) - Your homepage Each FAQ section should contain 3-5 questions with direct, factual answers. Use the questions your customers actually ask - shipping times, return policies, size guides, compatibility, care instructions. ### Step 10 - Run a full AEO audit **Time:** 30 seconds **Why it matters:** Steps 1-9 cover the individual components. The CLI audit scores your store across 20 AEO signals and shows where gaps remain. # CLI audit - shows scored results for all 20 signals bin/magento angeo:aeo:audit Or use the web-based audit - no installation required: ### See exactly where the gaps are The free scan checks 14 signals - robots.txt, llms.txt, schema, feeds, UCP profile, and more. A few seconds. [Run free AEO audit ->](https://angeo.dev/ai-magento-audit/) Target: 85%+ AEO score with UCP profile active. ## The complete picture | Step | Time | Impact | Also benefits | | 1. robots.txt | 5 min | Prerequisite - without this, nothing works | ChatGPT, Perplexity, Claude | | 2. llms.txt | 10 min | AI agents understand your store correctly | All AI platforms | | 3. JSON-LD schema | 1-2 hrs | Products are parseable and purchasable | Google Search, ChatGPT Shopping | | 4. ACP feed | 30 min + wait | ChatGPT Shopping visibility | ChatGPT | | 5. UCP module | 10 min | Google AI discovery layer | UCP-specific | | 6. Signing keys | 5 min | Secure agent communication | UCP-specific | | 7. Enable profile | 2 min | Go live on UCP | UCP-specific | | 8. Verify | 2 min | Confirm spec compliance | UCP-specific | | 9. FAQ schema | 1-2 hrs | Higher citation rate in AI answers | All AI platforms, Google Search | | 10. Full audit | 30 sec | Identify remaining gaps | Everything | **Total estimated time:** 4-6 hours for a complete implementation, including ACP registration (excluding OpenAI's approval timeline of 1-4 weeks). **Note the "Also benefits" column.** Steps 1-4 improve your visibility across all AI platforms - not just UCP. Even if you decide to defer UCP implementation, completing Steps 1-4 makes your store more visible to ChatGPT, Perplexity, Gemini, and Claude. ## What comes next `angeo/module-ucp` 2.x publishes the profile (spec 2026-08-25) and `angeo/module-ucp-catalog` serves catalog search and lookup. Cart and checkout endpoints come later, as the specification settles. ### Planned roadmap (subject to UCP spec evolution) The UCP specification is under active development. This roadmap reflects current planning as of May 2026 and may change as the protocol matures. | Target version | Planned capability | Status | | 0.2.x | Catalog search endpoint - AI agents can search your products | In development | | 0.3.x | UCP-Agent header parsing and capability negotiation | Planned | | 0.4.x | HTTP Message Signatures (RFC 9421) | Planned | | 0.5.x | Cart capability | Planned | | 1.0.0 | Full shopping vertical - catalog, cart, checkout, order | Dependent on spec stability | Release dates are not committed. Each version will be tested against the current UCP conformance suite before release. Each release will be announced on the [angeo.dev blog](https://angeo.dev/blog/) and on [Packagist](https://packagist.org/packages/angeo/module-ucp). The module is MIT-licensed - no licensing fees, no SaaS subscriptions, no external data transmission. **Need checkout endpoints now?** The `gtstudio/module-ucp` module includes checkout session endpoints, quote management, and UcpSession persistence in its current release. If you need functional checkout capability today rather than profile-only discovery, it may be the better fit. See its [Packagist page](https://packagist.org/packages/gtstudio/module-ucp) for details. Both modules implement the same UCP specification - the difference is scope and release strategy. Related guides [What Is UCP? - Plain English guide ->](https://angeo.dev/what-is-ucp-for-store-owners/) [ACP vs UCP for Magento 2 ->](https://angeo.dev/acp-vs-ucp-for-magento-2/) [Magento 2 AEO Guide 2026 ->](https://angeo.dev/magento-2-aeo-guide/) [Merchant-Controlled AEO - full architecture ->](https://angeo.dev/merchant-controlled-aeo/) [Track AI Search traffic in GA4 ->](https://angeo.dev/track-ai-search-traffic-magento-2/) [Free AEO audit - check your score ->](https://angeo.dev/ai-magento-audit/) ## Frequently asked questions FAQ schema Can I implement UCP without fixing robots.txt and schema first? Technically yes - the UCP module installs independently. Practically, a UCP profile without indexed content and structured product data is a door with nothing behind it. AI agents discover your profile, find no usable catalog data, and move on. Complete Steps 1-4 first. Do I need a developer for this? Steps 1-2 and 5-8 require SSH access to your Magento server and comfort with `composer` and `bin/magento` commands. If you have a development team or agency, this is routine Magento module management. Steps 3 and 9 require template modifications or a schema module. Step 10 (the audit) can be run by anyone via the web-based tool. Is UCP live in the EU? Not yet, per Google's public announcements. Google has announced rollout to Canada, Australia, and the UK, with more markets to follow. Implementing now means you are ready the day your market goes live - ahead of competitors who will start from scratch. What if I already have the other Angeo modules installed? The UCP module works alongside the existing Angeo module suite - `module-aeo-audit`, `module-llms-txt`, `module-openai-product-feed`, `module-rich-data`, and `module-robots-txt-aeo`. No conflicts. They share configuration conventions but operate independently. Should I enable capabilities in production right now? Only the ones you serve. With angeo/module-ucp-catalog, catalog search and lookup are implemented; cart and checkout are not yet, so do not advertise them. Does UCP guarantee my products will be recommended by AI agents? No. UCP makes your store discoverable - a prerequisite, not a guarantee. Whether an AI agent recommends your products depends on catalog quality, pricing, review signals, entity authority, schema completeness, and fulfilment reliability. Completing this checklist makes you findable. Building a strong catalog, competitive pricing, and good product data makes you recommendable. ## More on this topic - [UCP (Universal Commerce Protocol) - Definition](https://angeo.dev/ucp-definition/) - [Best Magento 2 UCP Modules Compared (2026)](https://angeo.dev/magento-ucp-modules-compared/) - [UCP Merchant Profile for Magento 2](https://angeo.dev/modules/ucp/) - [UCP Catalog Service for Magento 2](https://angeo.dev/modules/ucp-catalog/) - [/.well-known/ucp - The UCP Business Profile](https://angeo.dev/well-known-ucp-definition/) - [UCP Authority Binding - Definition and Algorithm](https://angeo.dev/ucp-authority-binding/)