WHAT GOOGLE'S UCP TELLS US ABOUT AGENT-READY WEBSITES

Google's Universal Commerce Protocol is the first production blueprint for what every website (e-commerce or not) will eventually need to expose to AI agents: discoverable actions, predictable outcomes, persistent sessions, and explicit agent policies.

UCP was released as infrastructure for Google Merchant Center retailers. But the more important story is the architecture underneath it. UCP is the first real implementation of what I've been talking about in the Interaction pillar of machine-first architecture. If you want to understand what agent-ready websites look like in practice, you need to look at UCP's developer documentation. The architecture is the lesson, and it goes far beyond Google Shopping.

Contents

• What Google Actually Built
• UCP Is the Interaction Pillar in Production
• The Gap UCP Exposes for Everyone Else
• What Every Website Can Learn from UCP's Architecture
• Citation Gets You Into the Answer. Actions Get You Into the Revenue.

What Google Actually Built

UCP is an open standard Google unveiled in January 2026 at the National Retail Federation conference alongside Shopify, Etsy, Wayfair, Target, and Walmart, as a common language between AI surfaces (Gemini, Google AI Mode) and merchant backends. According to Google's "Under the Hood" post on UCP, the protocol has four moving parts worth paying attention to.

A discovery endpoint at /.well-known/ucp. Agents query the /.well-known/ucp URL to learn what a merchant's website can do, which products it sells, which actions it exposes, and which transports it supports. This manifest is the handshake between an AI agent and a merchant's backend. Without that manifest, an agent has no knowledge of what it needs to parse or call. At best, it will try to guess.

Three REST endpoints for checkout. UCP reduces the entire transaction to three calls: create a session, update a session, complete a session. That is it. No cart page, no address form, no confirmation screen. The checkout state lives in session responses, not in rendered HTML. Human layer of your website gets completely ignored. An interface will exist, but it will not be the one you designed.

Transport flexibility. UCP supports REST, MCP (Model Context Protocol) bindings, and A2A (Agent-to-Agent), so agents built on different stacks can talk to the same merchant backend without custom adapters. An agent running inside Gemini and an agent running on a custom MCP client can both hit the same UCP endpoints. This was a very smart move.

An open specification at ucp.dev. UCP is published as an open spec any website, AI platform, or merchant platform can implement. Google does not own the protocol or its governance. The openness matters because the architecture becomes portable to any website outside Google Merchant Center, even if Google's onboarding path does not.

Google is building UCP for its own Shopping ecosystem first. UCP's design is the real lesson for everyone else, and that design is a textbook implementation of the Interaction pillar of machine-first architecture. Shopping carts are abandoned by roughly 70% of humans (per Baymard Institute's long-running checkout research). You can expect the agent abandonment rate on websites with no Interaction layer to be closer to 100%.

For UCP's place in the broader agentic commerce landscape, alongside OpenAI and Stripe's ACP, Shared Payment Tokens, and the platforms already selling through AI agents, see Selling to AI: The Complete Guide to Agentic Commerce. For the specific capabilities Google shipped in March 2026 (Cart, Catalog, and Identity Linking), see Google's UCP Update: Carts, Catalogs, and Loyalty in AI Shopping.

UCP Is the Interaction Pillar in Production

The Interaction pillar of machine-first architecture describes what a website must expose so an AI agent can accomplish a goal on it. Five properties: discoverable actions, predictable outcomes, workflow continuity, error recovery, and agent policies. UCP maps to each one almost perfectly.

Discoverable actions. The Interaction pillar says agents need a machine-readable index of what they are allowed to do on a page before they try to do it. UCP's /.well-known/ucp capability manifest is exactly the machine-readable action index the Interaction pillar calls for, shipped as a production endpoint. An agent fetches the manifest, reads the list of available operations, and plans its next step. No trial and error, no DOM scraping.

Predictable outcomes. The Interaction pillar says every action should return machine-readable state (computed totals, allocated inventory, success flags), not a 200 OK with an HTML receipt. UCP session responses carry structured data at every step: pricing breakdowns, discount allocations, and explicit session state. An agent reading a UCP response knows exactly what just happened and what it owes next.

Workflow continuity. The Interaction pillar says agents need stable session references that survive across multi-step workflows, so they do not lose context mid-task. UCP sessions have persistent IDs, and PUT updates carry that ID forward. An agent can add a line item, apply a discount, adjust shipping, and complete the order across multiple calls without re-creating state.

Error recovery. The Interaction pillar says failures should return structured alternatives, not dead ends. When a UCP discount code fails, the session response explains why and surfaces alternatives the agent can try. A human might click "try again." An agent needs a payload that tells it what to do next.

Agent policies. The Interaction pillar says websites should declare what agents are allowed to do, what requires human confirmation, and what is off-limits entirely. UCP's capability declarations are that policy layer: a merchant signals which actions agents can invoke, under what conditions, and where human approval is required. Request signatures and tokenized payments enforce the policy at the protocol level.

Google's /.well-known/ucp endpoint is the Interaction pillar's "discoverability of actions" being shipped as production infrastructure. Agents query it to learn what a website can do before they attempt to do it. UCP requires three REST endpoints for checkout: session creation, updates, and completion. That is the entire Interaction pillar reduced to three API calls.

The Gap UCP Exposes for Everyone Else

UCP is Google's answer to the agent-traffic gap inside its Shopping ecosystem. Every non-UCP website still has the gap, though not every retailer agrees on where the gap actually lives.

Breanna Fowler, Dell's Head of Global Consumer Revenue Programs, told Digital Commerce 360 in an April 2026 interview that she has not yet noticed "anything behaviorally consistent" in the agent traffic reaching Dell.com. Her focus is search and discoverability, not agent-specific infrastructure: "If I can't find your products easily and effortlessly, no amount of content and configurator capabilities, nobody really gives a crap about that stuff."

Fowler is right that nothing matters if agents cannot find the product. But for an AI agent, "finding" a product does not mean typing into a search box. Finding means querying a capability manifest, reading a structured product catalog, and invoking a discoverable action. In a human-first website, findability is a UI problem. In an agent-ready website, findability is a protocol problem. UCP exists because Google decided that treating findability and checkout as protocol problems, not UI problems, is the only way agent conversions ever scale.

A Gemini agent shopping through a UCP-enabled merchant does not parse a product grid, does not guess at form fields, and does not hope nothing re-renders under it. The agent queries /.well-known/ucp, reads the capability manifest, and advances the session through UCP's three checkout endpoints. The rest of the web (every SaaS dashboard, every B2B quote flow, every booking system, every subscription portal) has no equivalent protocol coming to rescue it.

Baymard Institute's aggregated checkout research puts the human cart abandonment rate at 70.22% across 50 studies. The agent abandonment rate on websites without an Interaction layer is closer to 100% because humans hesitate at checkout while agents cannot even find checkout.

What Every Website Can Learn from UCP's Architecture

You do not need to implement UCP. You are probably not even a commerce business. UCP's architecture still generalizes into five principles any agent-ready website should implement: a capability manifest, structured actions, machine-readable state, persistent sessions, and an explicit agent policy.

1. Publish a capability manifest. Agents need to know what your website can do before they start. That manifest might be a /.well-known/ endpoint, an llms.txt file, a WebSite schema node with potentialAction entries, or an MCP server listing available tools. The format matters less than the existence. If there is nothing for an agent to query, the agent has to guess, and guessing is how conversions die.

2. Expose actions as structured data. Schema.org has supported Actions for over a decade, including BuyAction, OrderAction, ReserveAction, SubscribeAction, and SearchAction. Almost no websites use them. UCP's POST /sessions endpoint is effectively a BuyAction target given a stable API contract, which is what schema.org Actions have needed for a decade to actually work. Any website can do the same on its own actions: declare the action type, name the endpoint, document the payload. The how AI agents see your website post covered the Structure pillar side of this question. Schema.org Actions are the Interaction pillar side.

3. Return machine-readable state at every step. Every response to an agent should carry structured state the agent can parse: what happened, what changed, what is next. HTML confirmation pages are not machine state. A redirect to /thank-you is not machine state. JSON with named fields and explicit flags is machine state. Returning JSON state instead of HTML confirmation pages is the single biggest architectural shift from human-first design to agent-ready design.

4. Design for sessions, not pageviews. Agents do not restart when they get distracted. They come back to a workflow in progress and expect the state to still be there. Sessions with stable IDs, safe-to-retry updates, and graceful resume paths are not optional for agents, they are the base layer. Pageview analytics trained a generation of product teams to think in discrete hits. Agents think in transactions.

5. Declare your agent policy explicitly. An agent policy defines three things: what agents can do without asking a human, what requires human confirmation, and what is off-limits entirely. UCP answers these questions through capability declarations. Your website can answer them through an AGENTS.md file, a /.well-known/ policy endpoint, or structured annotations. Pick one. Publish it. Guessing a policy is how agents end up taking actions their users did not intend.

None of these principles require Google's participation. None require UCP's adoption. They require a decision to treat a website as an API surface for agents in addition to a screen for humans.

Citation Gets You Into the Answer. Actions Get You Into the Revenue.

Most of the AXO conversation today is still about the Content pillar: how to get cited in ChatGPT answers, how to rank in Google AI Overviews, how to become the source AI surfaces quote. That work matters. Citation drives awareness, and awareness is the top of the funnel. The SEO to AAIO and Answer Engine Optimization articles covered how to win it.

UCP demonstrates the Interaction pillar, which is the other half of the agent-ready website stack that AEO and GEO do not cover. The Interaction pillar is about being transacted through by an AI agent, not quoted in its answer. The difference between a cited website and a transactable website is the Interaction pillar. Citation gets you into the AI's answer. Discoverable actions get you into the AI's revenue.

On the Cheeky Pint podcast, Sundar Pichai described a future where an AI user has "many threads running" at the same time, research, comparison, booking, purchase, all executing in parallel on behalf of a single human. In that model, the website that lets the agent resolve its thread fastest wins the thread. Resolution means completing an action, not loading a page. Dell has the traffic and loses the thread. A UCP-enabled merchant resolves the same thread in three API calls.

UCP is the first production artifact that gets the Interaction pillar right. UCP will not be the last. Every website that wants to participate in agent-mediated revenue will eventually need to ship its own version of the same architecture, through an open protocol, a schema.org capability layer, a WebMCP endpoint, or a custom MCP server. The spec can vary even if the principles cannot.

UCP is the working reference implementation of the Interaction pillar, built by Google and running in production inside Google Shopping today. Every other website still owes its own answer. Dell's Breanna Fowler said discoverability is what matters. For an agent, discoverability is a protocol.