Google AI shopping readiness

Prepare your product facts for Google AI Mode and Gemini.

Google discovery readiness starts with consistent product pages, Merchant Center data, prices, stock, variants, and policies. Site Scanner checks the public foundation and keeps gated UCP checkout work as a later, evidence-backed path.

Scan my store for Google AI See sample report

Separate product discovery readiness from gated checkout access.

Our proprietary rules-based scanner verifies public pages, visible product facts, information behind the page, and policies. Merchant Center account state and UCP transaction behavior require separate authorized reviews.

Public product pages, stable links, and whether search tools can reach them.
Visible titles, descriptions, price, stock, identifiers, images, and variants.
Product and offer information behind the page compared with visible facts.
Shipping, returns, privacy, terms, support, and seller identity.

Public layerPages and built-in product information

Private layerMerchant Center and UCP reviewed later

Public scanProduct facts, access, and policies

Next routeSite, catalog, or UCP readiness

The scan cannot confirm Merchant Center approval, Google selection, UCP access, placement, checkout activation, or sales.

What Site Scanner checks

Find the public product and policy gaps to address first.

A strong Merchant Center account cannot compensate for conflicting landing-page facts, and clean page information does not replace a complete product file. The first scan keeps those layers distinct.

Page access and stable links

Product pages should be reachable, internally connected, and tied to stable preferred addresses that shopping systems can revisit.

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.

Recommended Google-side route

The evidence separates basic site cleanup from product-file work and a later UCP Readiness Audit when foundations are viable.

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.

Merchant Center is the data hub

Approved product data, identifiers, variants, imagery, price, availability, policies, and optional conversational attributes support discovery readiness.

UCP checkout remains gated

Current guidance requires a Merchant Center account in good standing, approved free-listing products, Google selection, onboarding, and technical implementation.

Regional 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.

Official guidance checked July 18, 2026.

Google UCP implementation overview Google merchant preparation guide Merchant Center UCP onboarding Google AI shopping updates

Recommended next-step routing

Choose one Google-side next step from the evidence.

The page avoids treating every Gemini or Google AI search as a protocol implementation request.

Public pages or policies disagree

Use Site Scanner and AI Search Remediation when access, product-page facts, page information, or trust is the blocker.

Run the Google AI scan

Merchant Center data is weak

Use Catalog Scanner for missing identifiers, variants, images, price, availability, attributes, and Google-format output problems.

Check a product file

Foundations support deeper review

Use UCP Readiness Audit for Merchant Center, policy, regional, payment, and checkout pathway fit before implementation is scoped.

Review UCP readiness

Sample full report

See how confirmed store problems are prioritized.

Open the current sample to see each problem found, why it is a problem, how to fix it, and how to verify the fix.

Illustrative full scan

Rules-based scores

Affected pages

Fix verification

A tested score that keeps verified checks separate from checks the scanner could not complete.
Confirmed problems tied to affected page addresses, followed by the merchant consequence.
Practical fix steps and a clear rerun or validation check for every issue group.
One recommended next step, work to defer, and clear limits on what the report proves.

See sample Site Scanner report Review full-report details

Sample data is illustrative. A paid report uses a fresh scan for your chosen store.

Preview image of a sample Site Scanner full report PDF cover and summary.

Free Site Scanner preview

Check the public store before deeper Google-side work.

Enter the store URL, email, and commerce platform. The preview checks a focused public sample and emails the verified findings and one recommended next step.

You provideStore URL, email, and merchant context

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

Preview setup

Tell us which store to scan.

Keep this tab open to see the results appear here automatically, or close it after submitting and wait for the email. We send the preview summary to the email address you enter.

Free previewUp to 100 pages

Work emailWebsite URLCommerce platformChoose the system that runs your storefront and product catalog.

Refine the recommended next step.

These visible starting assumptions keep the preview quick. Change any detail you know; choosing an unsure option is fine.

Checkout or payment providerChoose this if you do not know who handles checkout or payments.Where do you sell?Your markets are mixed, different from these choices, or not confirmed.Catalog size estimateA growing catalog with up to 250 products.Primary goalStart broad and let the scan show which area needs attention first.

This preview scans up to 100 pages. Full reports use an in-depth website scan of up to 1,500 pages.

If the scanner cannot read your site

Some firewall, bot protection, or rate-limit settings can block automated checks. If that happens, try these steps and run it again.

If your firewall supports user-agent rules, temporarily allow AI-Commerce-Readiness-Audit/0.1 during the scan.
If safe, reduce bot challenges only for Site Scanner requests, then restore the rule after the scan.

When this check fits

Use the public scan before choosing deeper platform work.

This page is a good fit 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.

If Google-side pathway work remains viable after the scan, readiness and implementation stay separate. Any transaction testing uses a safe environment and an approval checkpoint.

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.