# Agentic Commerce Optimization: The Complete Guide > Agentic commerce optimization is the discipline of making a catalog legible and preferable to AI buying agents: the answer-engine-era successor to SEO. - Being eligible is not the same as being chosen: emitting the right feed and schema gets you into the running, but a separate set of signals decides which store an agent actually picks. - We argue the selection layer is an open space: the checkout and payment protocols, and the readiness checkers, all explicitly disclaim ranking (evidenced below). - Five levers move agent selection: product feed completeness, product schema, product titles, crawler access, and endorsement signals. - Agent behaviour is model-dependent and shifts when models update, so every claim here is evidence-typed and dated. - Official documentation teaches eligibility; this handbook teaches winning. We link out for spec syntax rather than rewrite it. ## What agentic commerce optimization is (and why it isn't SEO) Agentic commerce optimization (ACO) is the practice of getting a store, product, or offer chosen by an AI shopping agent (ChatGPT, Google's AI Mode and Gemini, Perplexity, Copilot, Claude) when a shopper asks it to find or compare products. It is the same job SEO did for the era of ranked blue links, moved to an era where a single agent reads your structured data and returns one pick or a short list. That shift changes the target. SEO optimizes a page for a human who scans a results list; ACO optimizes a catalog for a machine that parses your feed, your schema, and your product pages and then decides on the shopper's behalf. The unit of victory is no longer a click on rank three: it is being the one product the agent names. Learning why an agent makes that choice, and how to influence it, is what we mean by [agent selection](/glossary/#agent-selection). The reason a handbook like this can exist is that the choosing layer has no owner. No incumbent owns the selection layer of agentic commerce: every official protocol disclaims ranking, every readiness checker states that it measures preparedness rather than selection, and the only rigorous selection research is academic and written for researchers, not merchants. Even the tools built to score your setup make that limit visible once you look at what they actually check. UCP Checker grades a store's Universal Commerce Protocol readiness across three weighted categories, discovery, conformance, and capability, combining what a store declares in its manifest with what an agent actually finds when it visits: a technical-readiness score, not a prediction of whether an agent would choose that store over a competitor. A second checker that once covered similar ground, UCP.tools, is no longer a working tool: as of this writing the domain is parked and listed for sale, so we do not cite it as a current example. That gap between preparedness and selection is exactly the ground this guide stands on: the practitioner layer of [answer engine optimization for ecommerce](/glossary/#aco-aeo). ## Why now: AI-referred retail traffic is surging The reason to work on this in 2026 rather than later is that agents are already sending buyers. Retail traffic from AI-driven sources rose 393% year over year in the first quarter of 2026, and in March 2026 that AI-referred traffic converted 42 percent better: a record, and a reversal from a year earlier. The demand is arriving faster than most catalogs are ready for it. On Adobe's AI Content Visibility Checker, retail product pages score an average of 66 out of 100 for machine readability, meaning roughly a third of a typical product page is not machine-readable to an agent at all. A rising channel meeting under-prepared catalogs is precisely the window in which optimization work pays back. These figures are cited to Adobe Digital Insights' own first-party post (Vivek Pandya, Director, Adobe Digital Insights, published 2026-04-16), which TechCrunch and e-commerce.news covered at the time attributing the same Adobe data. ## The eligibility-to-winning seam There is a cliff in the middle of agentic commerce, and most merchants don't see it. You can pass every validator, expose every endpoint, and conform to every spec, and still never be the product an agent recommends. Passing validation makes you *eligible*. Being recommended makes you *selected*. The two are governed by different things, and nobody official lives on the selected side, because the protocols deliberately stop at eligibility. They say so themselves: - OpenAI and Stripe's Agentic Commerce Protocol states that implementing it does not guarantee your products will automatically be listed; each AI platform "will manage their own process" for how businesses can participate. - Google's Agent Payments Protocol is explicitly agnostic about how agents identify or evaluate merchants beforehand. - Google describes its Universal Commerce Protocol as "open, agnostic, built together with industry leaders Shopify, Etsy, Wayfair, Target and Walmart," and states that under UCP "the retailer remains the merchant of record," owning and shaping the customer relationship rather than ceding it to the protocol. Read together, those disclaimers draw the boundary this handbook occupies. Official documentation is the authority on eligibility (the fields to emit, the endpoints to expose, the specs to conform to), and we link to it rather than rewrite it. What comes after eligibility is winning: given that you qualify, how do you become the choice? That is the layer webmaster-guidelines-era SEO writing was to a search engine's own documentation, and it is the only layer this site covers. ## The five levers of agent selection Winning is not one move; it is a small set of levers that make your catalog easier to read and harder to skip. Each has a dedicated playbook. - **Product feed completeness.** Lead your titles with what shoppers search and fill the attributes agents parse; incomplete data is, we argue, a prime reason a product gets skipped. See [Make your product feed AI-readable →](/make-product-feed-ai-readable/). - **Product schema.** Ship the JSON-LD an agent trusts when your page and your feed disagree. See [Product schema (JSON-LD) for AI shopping →](/product-schema-for-ai-shopping/). - **Product titles.** Write the words a shopper types, not a brand codename; agents appear to match queries to titles closely, though the direct evidence is for description rewrites, not titles. See [Product titles that AI agents match →](/product-titles-for-ai-agents/). - **Crawler access.** Don't block the bots that read the page data agents use beyond your feed. See [AI crawlers, robots.txt and llms.txt →](/ai-crawlers-robots-llms-txt/). - **Endorsement signals.** The credibility markers, such as genuine reviews and editorial picks, that can tip an agent's choice, and the dark patterns that backfire. How they work and what the evidence says is in [How AI shopping agents choose products →](/how-ai-agents-choose-products/). ## How selection actually works Agents do not browse the way people do. Independent research on shopping agents points to a consistent pattern: they read structured product data, score it, and concentrate demand on a few products, often ignoring the rest entirely. The signals that appear to move that score include price, availability, review depth, how completely your data is filled in, on-screen position, and endorsement markers. [How AI shopping agents choose products →](/how-ai-agents-choose-products/) breaks each one down with the sourced figures and caveats, and is the deepest place to understand the mechanism before you touch the levers. ## Which agents you're optimizing for You are not optimizing for one agent; you are optimizing one catalog for several. The same structured signals surface you across ChatGPT, Google's AI Mode and Gemini, and Perplexity, but each engine appears to weight them differently and reaches your store over a different rail, so ties break per engine. The practical consequence is that most of the work is shared and a thinner layer is engine-specific. Per-engine playbooks live in the [AI shopping platforms hub →](/platforms/). ## The protocol layer, in one minute Underneath all of this sit two kinds of protocol: checkout rails that let an agent complete a purchase, and payment rails that authorize it. OpenAI and Stripe's Agentic Commerce Protocol already powers ChatGPT's Instant Checkout. Google's Universal Commerce Protocol is the analogous open standard on its side. Which rail reaches which engine (and which one you should implement) is the whole subject of [UCP vs ACP: which gets you selected →](/ucp-vs-acp/). The payment protocols beneath them (AP2, Visa's Trusted Agent Protocol, and Mastercard Agent Pay) decide whether an agent can actually pay you; we cover those in [Agentic payment protocols, explained →](/agentic-payment-protocols/). None of these rails choose *which* merchant wins. That is the point of the seam above, and the reason the rest of this handbook exists. ## How we prove our claims The space around agent selection is full of confident guesses, so the thing that makes this handbook worth trusting is that every factual claim is labeled with where it came from. We use four evidence types you will see attached to claims throughout: **spec-fact** (stated in an official specification, linked to the primary source), **reported** (a finding from a named third party, with a date, because model behaviour has a shelf life), **hypothesis** (our own inference, phrased as such and never dressed up as data), and **measured** (a result from our own experiments, which we publish only when real data backs it). We have not published a measured claim yet: our experiments ship with the methodology complete and results held in a "data collection in progress" state until the numbers are real, and we never invent a figure to fill the gap. You can see how we design those tests in the [Research Lab →](/research/) and the [methodology for testing agent selection →](/research/methodology/), and every term used here is defined and typed in the [glossary](/glossary/).