Skip to main content

Geo-redirects and currency: what Google Shopping expects

A product link from a Shopping listing has to open the same product, price and currency for every visitor, wherever they are. Redirecting by location breaks that, so give each market a stable URL instead. Your listings do not care where the shopper is standing.

Major4 min read

By How the guides are reviewed

You run this check yourself

Our scanner can’t see inside your Google accounts, so this one’s on you. Work through the checklist below without running a scan.

Why this matters

Google's landing page requirements leave little room here: “Show a product on your landing page that is essentially identical to the product in your product data, regardless of the user’s device, user agent (including bots), browser, location, cookies, your ad targeting choices, or any other consideration.” Their worked example is a US furniture store: “If your landing page is visited from Germany, the page must show the same couch, including all key elements of the product.” A redirect that sends German visitors to a euro store with a different price does the opposite.

Google's “Submit stable landing pages” page gives the fix. Stores can use stable URLs per country or language, such as a /fr/ path, or pass the country and language in a URL parameter so a visitor from a Shopping ad gets the version the product data describes. Its testing advice is plain: “Visit your website using the submitted URLs to ensure the landing page content meets the Shopping ads requirements. Consider using a VPN to test the experience from different locations.”

Prices that really differ by region have their own route. The “Price [price]” page says: “If the price of your product changes based on the user's regional location you need to join and use the regional pricing program where available.” Google's “About regional availability and pricing” page describes that add-on. Without it, the page shows one price for the whole country. Currency menus that ask rather than redirect are covered in currency switchers.

This one is largely a manual check: the free scan opens your store from one place, so it cannot see what a visitor in another country is sent. What it does flag is a currency switcher or automatic converter on the page. Test the rest yourself with a VPN, and see the full set of currency checks on the misrepresentation checker.

Typical evidence

Test the route a visitor actually receives

An auto-localise rule can send visitors to a different currency page. Test the public route from each target market, then compare the displayed price with the relevant submitted data yourself.

alternate locale request
store.com/p/merino-crew302 →store.com/us/p/merino-crew
FlagThe request reached a localised page with a different public price.
Public page showed
$39.99
localised page · USD
Feed declared
£29.99
submitted entry · GBP

Investigator’s note

The public price changes by location. Check the redirect rule, market-specific price and submitted feed entry together; StoreVerifier does not retrieve the feed.

StoreVerifier compliance desk

The public signals this check looks for:

  1. Visitors from outside your home country are redirected to a different domain or subfolder …

    Visitors from outside your home country are redirected to a different domain or subfolder with other prices.

  2. The same product URL shows a different price or currency depending on where it is opened

    The same product URL shows a different price or currency depending on where it is opened.

  3. A redirect based on browser language sends a product link to the home page of a translated…

    A redirect based on browser language sends a product link to the home page of a translated site.

  4. Only some countries are redirected, so testing from home never shows the problem

    Only some countries are redirected, so testing from home never shows the problem.

  5. A regional price appears on the page without regional availability and pricing set up in M…

    A regional price appears on the page without regional availability and pricing set up in Merchant Center.

What it looks like once it is right

The store gives Switzerland its own /ch/ pages and a CHF data source, removes the automatic redirect, and shows a “Shop in CHF” banner instead. Every product link opens the page its data describes.

Common mistakes

Common mistake

A German store submits EUR prices. Visitors from Switzerland are redirected to a CHF store with higher prices, so a Swiss shopper clicking a listing never sees the price in the product data.

Self-check steps

Test from the countries you serve

Use a VPN or market preview to load your own product pages from each country you target, record the public price, and compare it with the appropriate submitted data. Do not assume this reproduces a Google fetch; it is a shopper-facing check.

Test from
Price shown
Feed has
Match
United Kingdom
£29.99
£29.99 GBP
Germany · VPN
€34.99
no EUR entry
United States · VPN
$39.99
no USD entry
Example · document the intended canonical route
# Keep the canonical destination explicit for public requests.
# Match Google's PUBLISHED Googlebot + Googlebot-Shopping IP
# ranges (developers.google.com/.../googlebot.json) — not the
# user-agent string, which anyone can spoof.
if ($remote_addr in $googlebot_ranges) { set $skip_currency_redirect 1; }
Use market-specific public pages and submitted data that agree. Test each shopper-facing route; do not claim a redirect configuration guarantees another system’s destination.

Questions merchants ask

Can I redirect visitors to a country store based on their location?

Not on the product pages your listings open. Google's landing page requirements ask for a product that is essentially identical for every visitor, regardless of location. Give each country its own stable URL, link that country’s product data to it, and let visitors switch store themselves.

How do I test what shoppers abroad see?

Google's stable landing pages page suggests visiting your submitted URLs and using a VPN to test the experience from different locations. Open a sample of product links from each target country and set product, price and currency beside your product data.

What if my prices differ by region?

Use regional availability and pricing where it is available. Google's “Price [price]” page says that if the price changes based on the user’s regional location, you need to join and use the regional pricing program; the page itself should not switch prices by location.

Remediation

Risk signal

Geo-redirects feel helpful and quietly turn one link into several offers. Stable URLs per market, no automatic jumps on product pages, and a VPN test after every localisation change keep one link meaning one price.
PriorityAddress and document this finding as part of the store’s remediation work.
EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

  1. How StoreVerifier checks public store evidenceOverview
  2. Tax at checkout: what shoppers must see before they payCheckout & Payment
  3. Shipping cost at checkout vs Merchant Center settingsCheckout & Payment

Sources

  1. About landing page requirementsGoogle Merchant Center Help — support.google.com
  2. Submit stable landing pages (the same page for every location)Google Merchant Center Help — support.google.com
  3. About regional availability and pricingGoogle Merchant Center Help — support.google.com

Last reviewed 25 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.