Google's Universal Commerce Protocol (UCP) is designed to let shoppers discover, compare and buy products inside Google experiences such as Search, AI Mode and Gemini, without opening a storefront.
It's a meaningful shift. But most of the conversations around it focus on the checkout moment, which is the last step of the journey.
The part that matters today is the first step: whether Google can understand your products well enough to recommend them at all. That depends on data you already control. Your catalog, your Google feed, your shipping rules and your Merchant Center account.
This guide walks you through what to configure, why it matters, and how it works natively in VTEX.
Why readiness beats waiting
Google's shopping experiences don't browse your website. They read structured product data, compare it across merchants and show what looks most complete, accurate and trustworthy.
That creates a simple rule: a product Google can't understand is a product Google won't recommend. No integration fixes a catalog with generic titles, missing GTINs or a shipping cost that doesn't match reality.
The good news is that the same work that prepares you for UCP already improves your results on Google Shopping, AI Mode and Gemini, sending qualified audiences to your ecommerce website. Nothing on this list is speculative. It pays off now and keeps paying later.
The four pillars of readiness
1. Catalog: make your products easy to understand
Your catalog is the source of everything Google knows about your products. If it's ambiguous, every other layer inherits the ambiguity.
Things to check:
- Specific titles. "Running shoes" says nothing. "Women's lightweight trail running shoes, size 38, blue" says everything Google needs to match a search.
- Brand, category and a valid GTIN/EAN. The GTIN is how Google recognizes your product as the same item sold elsewhere, and how it decides you're a credible seller of it.
- Explicit variants. Size, color and material must be structured attributes, not buried in a description.
- At least three images per SKU. Multiple angles help Google and shoppers confirm what they're looking at.
In VTEX, this lives in the Catalog module: product and SKU specifications, brand and category trees, and image management are all native. No middleware required.
2. Google feed and Merchant Center: supply, not marketing
It's tempting to treat the Google feed as a marketing export. It isn't. It's a product supply layer, and it needs the same rigor as inventory data.
Things to check:
- Connect the native Google integration in VTEX. The Marketplaces › Google integration sends your catalog to the Merchant Center and keeps it synchronized.
- Fill required and recommended attributes. Required attributes get you listed. Recommended attributes get you chosen. Use Google's Product Data Specification as the reference.
- Align price and availability. What the feed says must match what the store shows. Mismatches are the fastest path to disapproval.
- Test your product pages with Google's Rich Results Test. Structured data on the product page reinforces what the feed declares.
3. Shipping and regional accuracy: what Google shows is what you deliver
Shipping is where most readiness efforts quietly fail. A product can be perfectly described and still be flagged if there is no shipping info or if the delivery promise Google shows differs from what the customer receives.
Things to check:
- Enable shipping information in the Marketplaces › Google integration in VTEX, so cost and delivery time are sent along with the product.
- Make cost and delivery time correct by region. Google compares them against the actual checkout.
- Make your storefront understand the regionId from Google and regionalize the navigation to that region. When a shopper clicks through from a regional offer, the store must load the same region: same price, same stock, same shipping. Google passes the regionId; your front end has to honor it.
4. Merchant Center health: trust is earned weekly
Readiness isn't a one-time setup. Merchant Center continuously evaluates your account, and its signals influence how your products are shown.
Things to check:
- No critical account alerts. Resolve them before anything else. They can suppress your entire catalog.
- Disapprovals reviewed weekly. Each disapproved item is a product Google won't recommend.
- Zero price or shipping mismatches. These are the most common, most avoidable trust failures.
Make it a recurring routine, not a project.
From readiness to UCP
Here's how the shift looks when the groundwork is done:
- Generic listings become products Google can understand and compare
- The feed stops being an export and becomes a supply layer
- A single national offer becomes the right offer for every region
- A one-time setup becomes a continuously healthy account
Merchants who complete this checklist aren't just waiting for UCP. They're already winning on the surfaces that exist today. When UCP arrives in their market, the hard part is done.
You already have everything you need in VTEX
Everything in this checklist is native to the VTEX platform, including Catalog, the Google integration in Marketplaces, regionalization, and feed synchronization.
Talk to your Commerce Engineer to kick off your implementation