What Google UCP Setup Requirements Apply to Merchant Center Sellers?

What is the full checklist?

Google recommends adding the new attributes through a supplemental feed, so a formatting mistake does not disrupt your main product data and ads. Existing use of the plain native_commerce attribute remains supported as an alias.

Which products are excluded?

Google's guide lists categories that must not be marked eligible:

• Subscriptions and installments, meaning recurring billing or merchant-mandated payment plans.
• Personalized goods, such as engravings or monograms.
• Used, refurbished and final-sale items, where returns are not offered.
• Pre-orders with future release dates.
• Bundled services that need extra contracts, such as warranties, installation or setup.
• Items needing special shipping, such as freight or premium delivery.
• Gifting that needs split invoices or hidden prices.
• Products activated in store.
• Age-restricted items, such as alcohol and tobacco, and anything prohibited under Google Shopping policies.
• Services, rentals, virtual items such as in-game currency, and goods that need software installed before purchase.

Leave checkout eligibility empty or false for these products; they still appear as ordinary listings.

What does the technical integration involve?

Beyond Merchant Center, a seller implements UCP on its own systems: a business profile that tells agents what the store supports, and checkout endpoints Google can call. The protocol lets merchants choose capabilities and communicate through APIs, MCP or A2A, and supports tokenised payments through existing payment integrations. In the UCP integration hub in Merchant Center, selected merchants can choose capabilities such as cart transfer to their own site, native checkout on Google and identity linking, and test their UCP profile, cart transfer and checkout APIs in a sandbox. Merchant Center flags feed, returns or account settings that need fixing.

Platform merchants rarely build this themselves. Shopify stores support UCP natively, and Google says merchants on other platforms should ask their provider about its plans, as covered in ACP vs UCP and which platforms support them.

Does implementing UCP help AI agents complete purchases and increase agentic traffic?

It helps with completing purchases on Google's AI surfaces. With checkout enabled, a shopper can buy from an eligible listing in AI Mode or Gemini with Google Pay, using payment and shipping details saved in Google Wallet, while you remain merchant of record. Google says this may reduce steps and cart abandonment. The same foundation powers cart transfer from Google's Universal Cart to your site, as covered in what Google Universal Cart is.

Whether it increases traffic is a different question. Google has not said that UCP eligibility improves how often products are recommended, and it has published no traffic figures. Platform claims exist, such as Shopify's statement that new buyers order through AI channels at nearly twice the rate of other channels, but they are vendor figures. In practice, a Buy button on Google may mean more orders with fewer site visits, so judge it by orders and revenue, not sessions.

How should ecommerce SEO strategies adapt to Google UCP?

• Treat the feed as a ranking asset. Titles, attributes, GTINs, prices, stock, shipping and returns in Merchant Center shape what Google's AI surfaces show. How weak feeds affect Google's Business Agent is covered in how Business Agent uses Merchant Center data.
• Keep product pages strong. Discovery still draws on web content, reviews and comparisons, and shoppers who want detail still click through.
• Make policies explicit. Returns and support details are now checkout requirements, and AI answers quote them.
• Change the success measures. Add Google channel orders and Merchant Center's AI performance insights to your reports alongside organic sessions.
• Plan for exclusions. Products that cannot use checkout, such as pre-orders or subscriptions, need landing pages that convert on your own site.

If a Merchant API migration has already disrupted your product data, fix that first, as covered in what to fix first after a Merchant API migration.

What JSON-LD attributes and ratings does a UCP-compliant product schema need?

None specifically. UCP eligibility is set through Merchant Center feed attributes and your checkout integration, not through on-page structured data, and Google's UCP requirements say nothing about ratings. There is no “UCP schema” to add to product pages.

Product structured data still matters for the rest of Google Search. Google's merchant listing documentation asks for basics such as the product name, an image and an offer with price and currency, and recommends properties such as availability, brand, GTIN, shipping details, return policy and, where you collect them, aggregate ratings and reviews. Keep that markup consistent with your feed: the same price, availability and return terms, since conflicting data is a common reason listings are held back.

We have not implemented UCP checkout for a store. This page is based on Google's UCP developer guide, Merchant Center help pages on UCP, the native commerce attribute and the UCP integration hub, and Google's announcements.

What might this look like in practice?

Consider an illustrative kitchenware retailer, Oxlisk, on a custom platform. Its team created a supplemental feed setting checkout eligibility to true for 1,800 standard products and false for pre-orders and gift sets, added Proposition 65 notices for two cookware lines sold in California, and mapped feed IDs to its checkout system with merchant_item_id. It set return cost, window and policy link at each sub-account and added a support email. After being selected, the developers validated the UCP profile and checkout in the integration hub sandbox, and the team began tracking orders placed through AI Mode separately.

What do people ask about UCP setup?

Is UCP checkout open to every Merchant Center seller?

Not yet. It is available to selected merchants who apply through Google's interest form.

Do I need a Google Pay button on my website?

No. You need a Google Pay & Wallet Console account, but not the button on your own checkout.

Which countries does UCP checkout cover?

Google's help covers products eligible in the United States, Canada and Australia, and says the Merchant Center onboarding rolls out in the US first.

Do I need special JSON-LD for UCP?

No. Eligibility comes from feed attributes and the checkout integration, not on-page markup.