Page access and stable links
Product pages should be reachable, internally connected, and tied to stable preferred addresses that shopping systems can revisit.
Product-data guidance · Google shopping
A Merchant Center patch can leave the storefront problem untouched.
When the public source stays wrong, the next update can restore the conflict. Our free check documents the storefront mismatch. We can open a private diagnostic comparison after a fit review when the evidence supports it.
Public pages only. Our public check cannot confirm private settings, eligibility, activation, placement, approval, or sales.
Across your store and sales channelsWhat happens when your product details stop matching?
A different price can disrupt a purchase, incorrect stock can hide an available product, and a mismatched code or size can give shoppers the wrong information.
Auto-playingFictional sample
Inconsistent priceA shopper can reach your store expecting a lower price.
The mismatchShopify and the online store show $48, while the selected feed shows $42.
Why it mattersThe surprise may interrupt the purchase and weaken trust in the offer.
North HarborOutdoor Supply Co.Product and optionTrail PackForest green, 20 L
- North HarborShopify catalog$48.00Source price
- North HarborOnline store$48.00Matches
- MarketLaneSelected feed$42.00$6 lower
What we would verify: We would verify the market, currency, promotion, and selected option before recommending a correction.
You provideWork email, store URL, and commerce platform
The scanner checksA focused sample of public pages
You receiveEvidence-backed findings, limits, and one recommended next step
Site changesNone. The scan is read-only
Check the layer your business controls
Check which public product and policy gaps need attention.
Merchant Center, landing pages, and the product file each contribute different evidence. The scan compares the public layer and shows which one contains the confirmed gap.
Product and offer consistency
We compare visible title, price, currency, stock, identifiers, images, and variants with the information built into the page.
Merchant policy context
Shipping, returns, support, privacy, terms, seller identity, and regional context need to be clear before deeper Google-side work.
Current Google pathway
Discovery improvements can start before UCP checkout access.
Google currently keeps Merchant Center product data at the center of AI shopping while UCP checkout follows a selection, onboarding, and technical implementation path.
01Merchant Center is the data hub
Approved product data, identifiers, variants, imagery, price, availability, policies, and optional conversational attributes support discovery readiness.
02UCP checkout remains gated
Current guidance requires a Merchant Center account in good standing, approved free-listing products, Google selection, onboarding, and technical implementation.
03Regional rollout and checkout access differ
Onboarding is rolling out in the United States, Canada, and Australia, while current checkout availability remains limited to select U.S. merchants.
Use this guidance when
- You are exploring Google AI Mode or Gemini and need to confirm the public-store foundation.
- You suspect Merchant Center, product-page, or checkout facts disagree and want to check the public layer first.
- You need to decide between site cleanup, product-file cleanup, and a later UCP Readiness Audit.
What this Google AI scan cannot prove
Site Scanner cannot inspect private Merchant Center diagnostics, approve products or free listings, confirm Google selection, test Google Pay or UCP APIs, activate checkout, guarantee placement, or predict sales.
Primary sources
Official guidance checked July 18, 2026.
Catch the mismatch before another channel update repeats it.
Your result documents what the page shows and whether the available evidence supports a platform-specific review.
Run the free product check