UCP is a Google-initiated open standard, co-developed with Shopify, Etsy, Wayfair, Target, and Walmart (20+ endorsers), plus payment partners (Stripe, Visa, Mastercard, Adyen, Amex). Its purpose: let AI agents discover, negotiate, and transact with merchants without one-off integrations. It is interoperable with A2A (Agent2Agent), AP2 (Agent Payments Protocol), and MCP.
For commerce sites, UCP sits next to Google Merchant Center feeds and Google Business Profile as the third leg of agent-era discovery. Google confirms a first reference implementation for conversational buying in AI Mode in Search; broader Universal Cart rollout details are reported from Google I/O 2026 keynote coverage; not confirmed on a Google-owned source.
Primary sources (canonical, stable): - Google merchant developer guide: https://developers.google.com/merchant/ucp (and /merchant/ucp/guides/ucp-profile) - Spec / overview: https://ucp.dev. ucp.dev lists 2026-04-08 as the latest release in its date-based versioning scheme (YYYY-MM-DD); revalidate before using it as a hard validator.
| What it is | What it isn't |
|---|---|
| A capability-declaration + negotiation protocol | A new payment processor |
| Transport-agnostic (REST, MCP, A2A) | A replacement for Merchant Center feeds |
| Compatible with AP2 (Agent Payments Protocol) for cryptographic user-consent proof on autonomous purchases | A way to skip being merchant of record |
| Google reference implementation for conversational buying in AI Mode in Search | A "ranking factor" because Google has not framed it that way |
Merchants stay Merchant of Record under UCP — they keep customer relationships and post-purchase ownership.
Publish a profile at /.well-known/ucp describing capabilities and versions.
The general shape (consult the live spec for exact field names):
{
"version": "2026-04-08",
"capabilities": [
{
"id": "dev.ucp.shopping.checkout",
"version": "2026-04-08",
"endpoint": "https://api.example.com/ucp/checkout"
},
{
"id": "dev.ucp.shopping.fulfillment",
"version": "2026-04-08",
"endpoint": "https://api.example.com/ucp/fulfillment"
},
{
"id": "dev.ucp.shopping.discount",
"version": "2026-04-08",
"endpoint": "https://api.example.com/ucp/discount"
}
],
"merchant": {
"name": "Example Co.",
"id": "merchant-center-id-here"
}
}
UCP uses date-based versioning (YYYY-MM-DD), current release 2026-04-08
— a literal "1.0" does not match any real UCP release and will fail the spec's
version negotiation. Platforms (AI Mode in Search, Gemini, and eventually
others) auto-discover the profile and negotiate.
Merchants join a waitlist and must be Google-approved before going live.
| Capability ID (shape) | Purpose |
|---|---|
dev.ucp.shopping.checkout |
Initiate checkout, return totals + payment intent |
dev.ucp.shopping.fulfillment |
Quote shipping options and delivery windows |
dev.ucp.shopping.discount |
Apply promo codes / loyalty discounts at quote time |
dev.ucp.shopping.cart |
Add / remove / update items in agent-managed carts |
Exact identifiers are governed by the live spec. The namespace pattern is
dev.ucp.<domain>.<verb>; version values are date-based.
/seo ecommerce <url> should report:
/.well-known/ucp resolve to a valid JSON document?version a valid date-based
(YYYY-MM-DD) UCP release? ucp.dev lists 2026-04-08 as latest; revalidate
before flagging a version as invalid. Flag a literal "1.0" or unrecognized
version as invalid.The audit should not score the absence of UCP as a critical failure — frame it as an opportunity, especially for merchants already on Google Merchant Center. (UCP itself is live; what's "early" is broad merchant adoption.)
| Existing surface | Relationship to UCP |
|---|---|
| Google Merchant Center feed | Required upstream — UCP capabilities reference Merchant Center products by ID |
| Google Business Profile | Independent — UCP is product / order; GBP is store / location |
Product schema (hasMerchantReturnPolicy, shippingDetails) |
Complementary — UCP exposes the same data at the API layer; schema exposes it at the page layer |
| AP2 (Agent Payments Protocol) | Pair. UCP handles discovery + checkout structure; AP2 handles cryptographic proof of user consent. Treat FIDO governance, v0.2, and Mastercard Verifiable Intent details as secondary-source context, not canonical audit guidance until primary sources verify them. |
A merchant that already has clean Merchant Center feeds, complete Product schema, and a checkout API can declare a UCP profile in a sprint.
/.well-known/ucp readiness for AI Mode in Search.2026-06-21. Re-check when: