What Google’s UCP Tells Us About Agent-Ready Websites

Google’s Universal Commerce Protocol is the primary manufacturing blueprint for what each web site (ecommerce or not) will ultimately want to reveal to AI brokers: discoverable actions, predictable outcomes, persistent periods, and express agent insurance policies.

UCP was launched as infrastructure for Google Service provider Heart retailers. However the extra necessary story is the structure beneath it. UCP is the primary actual implementation of what I’ve been speaking about within the Interplay pillar of machine-first architecture. If you wish to perceive what agent-ready web sites appear like in apply, it’s essential have a look at UCP’s developer documentation. The structure is the lesson, and it goes far past Google Procuring.

What Google Really Constructed

UCP is an open customary Google unveiled in January 2026 on the Nationwide Retail Federation convention alongside Shopify, Etsy, Wayfair, Goal, and Walmart, as a typical language between AI surfaces (Gemini, Google AI Mode) and service provider backends. Based on Google’s “Under the Hood” post on UCP, the protocol has 4 transferring elements price listening to.

A discovery endpoint at /.well-known/ucp. Brokers question the /.well-known/ucp URL to be taught what a service provider’s web site can do, which merchandise it sells, which actions it exposes, and which transports it helps. This manifest is the handshake between an AI agent and a service provider’s backend. With out that manifest, an agent has no data of what it must parse or name. At greatest, it is going to attempt to guess.

Three REST endpoints for checkout. UCP reduces your entire transaction to a few calls: Create a session, replace a session, full a session. That’s it. No cart web page, no tackle kind, no affirmation display. The checkout state lives in session responses, not in rendered HTML. Human layer of your web site will get fully ignored. An interface will exist, however it is not going to be the one you designed.

Transport flexibility. UCP helps REST, Model Context Protocol (MCP) bindings, and A2A (Agent-to-Agent), so brokers constructed on totally different stacks can speak to the identical service provider backend with out customized adapters. An agent operating inside Gemini and an agent operating on a customized MCP shopper can each hit the identical UCP endpoints. This was a really good transfer.

An open specification at ucp.dev. UCP is revealed as an open spec any web site, AI platform, or merchant platform can implement. Google doesn’t personal the protocol or its governance. The openness issues as a result of the structure turns into moveable to any web site outdoors Google Service provider Heart, even when Google’s onboarding path doesn’t.

Google is constructing UCP for its personal Procuring ecosystem first. UCP’s design is the true lesson for everybody else, and that design is a textbook implementation of the Interplay pillar of machine-first structure. Procuring carts are deserted by roughly 70% of people (per Baymard Institute’s long-running checkout analysis). You may anticipate the agent abandonment rate on web sites with no Interplay layer to be nearer to 100%.

For UCP’s place within the broader agentic commerce panorama, alongside OpenAI and Stripe’s ACP, Shared Fee Tokens, and the platforms already promoting by means of AI brokers, see Selling to AI: The Complete Guide to Agentic Commerce. For the particular capabilities Google shipped in March 2026 (Cart, Catalog, and Identification Linking), see Google’s UCP Update: Carts, Catalogs, and Loyalty in AI Shopping.

UCP Is The Interplay Pillar In Manufacturing

The Interplay pillar of machine-first architecture describes what an internet site should expose so an AI agent can accomplish a objective on it. 5 properties: discoverable actions, predictable outcomes, workflow continuity, error restoration, and agent insurance policies. UCP maps to every one virtually completely.

Discoverable actions. The Interplay pillar says brokers want a machine-readable index of what they’re allowed to do on a web page earlier than they attempt to do it. UCP’s /.well-known/ucp functionality manifest is strictly the machine-readable motion index the Interplay pillar requires, shipped as a manufacturing endpoint. An agent fetches the manifest, reads the record of obtainable operations, and plans its subsequent step. No trial and error, no DOM scraping.

Predictable outcomes. The Interplay pillar says each motion ought to return machine-readable state (computed totals, allotted stock, success flags), not a 200 OK with an HTML receipt. UCP session responses carry structured information at each step: pricing breakdowns, low cost allocations, and express session state. An agent studying a UCP response is aware of precisely what simply occurred and what it owes subsequent.

Workflow continuity. The Interplay pillar says brokers want steady session references that survive throughout multi-step workflows, so they don’t lose context mid-task. UCP periods have persistent IDs, and PUT updates carry that ID ahead. An agent can add a line merchandise, apply a reduction, alter transport, and full the order throughout a number of calls with out re-creating state.

Error restoration. The Interplay pillar says failures ought to return structured alternate options, not useless ends. When a UCP low cost code fails, the session response explains why and surfaces alternate options the agent can attempt. A human may click on “attempt once more.” An agent wants a payload that tells it what to do subsequent.

Agent insurance policies. The Interplay pillar says web sites ought to declare what brokers are allowed to do, what requires human affirmation, and what’s off-limits solely. UCP’s functionality declarations are that coverage layer: A service provider alerts which actions brokers can invoke, underneath what circumstances, and the place human approval is required. Request signatures and tokenized funds implement the coverage on the protocol degree.

Google’s /.well-known/ucp endpoint is the Interplay pillar’s “discoverability of actions” being shipped as manufacturing infrastructure. Brokers question it to be taught what an internet site can do earlier than they try and do it. UCP requires three REST endpoints for checkout: session creation, updates, and completion. That’s the whole Interplay pillar lowered to a few API calls.

The Hole UCP Exposes For Everybody Else

UCP is Google’s reply to the agent-traffic hole inside its Procuring ecosystem. Each non-UCP web site nonetheless has the hole, although not each retailer agrees on the place the hole really lives.

Breanna Fowler, Dell’s Head of International Shopper Income Applications, advised Digital Commerce 360 in an April 2026 interview that she has not but seen “something behaviorally constant” within the agent visitors reaching Dell.com. Her focus is search and discoverability, not agent-specific infrastructure: “If I can’t discover your merchandise simply and effortlessly, no quantity of content material and configurator capabilities, no person actually offers a crap about that stuff.”

Fowler is correct that nothing issues if brokers can not discover the product. However for an AI agent, “discovering” a product doesn’t imply typing right into a search field. Discovering means querying a functionality manifest, studying a structured product catalog, and invoking a discoverable motion. In a human-first web site, findability is a UI drawback. In an agent-ready web site, findability is a protocol drawback. UCP exists as a result of Google determined that treating findability and checkout as protocol issues, not UI issues, is the one means agent conversions ever scale.

A Gemini agent purchasing by means of a UCP-enabled service provider doesn’t parse a product grid, doesn’t guess at kind fields, and doesn’t hope nothing re-renders underneath it. The agent queries /.well-known/ucp, reads the potential manifest, and advances the session by means of UCP’s three checkout endpoints. The remainder of the online (each SaaS dashboard, each B2B quote circulation, each reserving system, each subscription portal) has no equal protocol coming to rescue it.

Baymard Institute’s aggregated checkout analysis places the human cart abandonment price at 70.22% throughout 50 research. The agent abandonment price on web sites with out an Interplay layer is nearer to 100% as a result of people hesitate at checkout, whereas brokers can not even discover checkout.

What Each Web site Can Study From UCP’s Structure

You don’t want to implement UCP. You’re most likely not even a commerce enterprise. UCP’s structure nonetheless generalizes into 5 rules any agent-ready web site ought to implement: a functionality manifest, structured actions, machine-readable state, persistent periods, and an express agent coverage.

1. Publish a functionality manifest. Brokers must know what your web site can do earlier than they begin. That manifest is perhaps a /.well-known/ endpoint, an llms.txt file, a WebSite schema node with potentialAction entries, or an MCP server itemizing out there instruments. The format issues lower than the existence. If there may be nothing for an agent to question, the agent has to guess, and guessing is how conversions die.

2. Expose actions as structured information. Schema.org has supported Actions for over a decade, together with BuyAction, OrderAction, ReserveAction, SubscribeAction, and SearchAction. Nearly no web sites use them. UCP’s POST /periods endpoint is successfully a BuyAction goal given a steady API contract, which is what schema.org Actions have wanted for a decade to really work. Any web site can do the identical by itself actions: declare the motion sort, title the endpoint, doc the payload. The how AI agents see your website put up lined the Construction pillar facet of this query. Schema.org Actions are the Interplay pillar facet.

3. Return machine-readable state at each step. Each response to an agent ought to carry structured state the agent can parse: what occurred, what modified, what’s subsequent. HTML affirmation pages will not be machine state. A redirect to /thank-you will not be machine state. JSON with named fields and express flags is machine state. Returning JSON state as an alternative of HTML affirmation pages is the only largest architectural shift from human-first design to agent-ready design.

4. Design for periods, not pageviews. Brokers don’t restart once they get distracted. They arrive again to a workflow in progress and anticipate the state to nonetheless be there. Periods with steady IDs, safe-to-retry updates, and sleek resume paths will not be optionally available for brokers; they’re the bottom layer. Pageview analytics educated a era of product groups to suppose in discrete hits. Brokers suppose in transactions.

5. Declare your agent coverage explicitly. An agent coverage defines three issues: what brokers can do with out asking a human, what requires human affirmation, and what’s off-limits solely. UCP solutions these questions by means of functionality declarations. Your web site can reply them by means of an AGENTS.md file, a /.well-known/ coverage endpoint, or structured annotations. Decide one. Publish it. Guessing a coverage is how brokers find yourself taking actions their customers didn’t intend.

None of those rules require Google’s participation. None require UCP’s adoption. They require a choice to deal with an internet site as an API floor for brokers along with a display for people.

Quotation Will get You Into The Reply. Actions Get You Into The Income

Many of the AXO dialog right this moment remains to be concerning the Content material pillar: learn how to get cited in ChatGPT solutions, learn how to rank in Google AI Overviews, learn how to develop into the supply AI surfaces quote. That work issues. Quotation drives consciousness, and consciousness is the highest of the funnel. The SEO to AAIO and Answer Engine Optimization articles lined learn how to win it.

UCP demonstrates the Interplay pillar, which is the opposite half of the agent-ready web site stack that AEO and GEO don’t cowl. The Interplay pillar is about being transacted by means of by an AI agent, not quoted in its reply. The distinction between a cited web site and a transactable web site is the Interplay pillar. Quotation will get you into the AI’s reply. Discoverable actions get you into the AI’s income.

On the Cheeky Pint podcast, Sundar Pichai described a future the place an AI person has “many threads operating” on the identical time, analysis, comparability, reserving, buy, all executing in parallel on behalf of a single human. In that mannequin, the web site that lets the agent resolve its thread quickest wins the thread. Decision means finishing an motion, not loading a web page. Dell has the visitors and loses the thread. A UCP-enabled service provider resolves the identical thread in three API calls.

UCP is the primary manufacturing artifact that will get the Interplay pillar proper. UCP is not going to be the final. Each web site that wishes to take part in agent-mediated income will ultimately must ship its own version of the same architecture, by means of an open protocol, a schema.org functionality layer, a WebMCP endpoint, or a customized MCP server. The spec can differ even when the rules can not.

UCP is the working reference implementation of the Interplay pillar, constructed by Google and operating in manufacturing inside Google Procuring right this moment. Each different web site nonetheless owes its personal reply. Dell’s Breanna Fowler mentioned discoverability is what issues. For an agent, discoverability is a protocol.

Extra Sources:

This put up was initially revealed on No Hacks.

Featured Picture: Natalya Kosarevich/Shutterstock