Skip to main content

Currency switchers and Merchant Center: what to check

A currency switcher is fine when the page opens in the currency you submit and nothing converts prices by location. The shopper chooses; checkout agrees.

Major4 min read

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

A switcher is not banned. The trouble is the default. Google's checkout requirements say: “Unless you have currency conversion enabled in your product source, your product pages must show the currency for the country you sell products in.” And: “All pages from the product page to the checkout page must consistently show the same currency.” So the page a listing opens has to show the currency you submitted, and checkout has to charge it.

Where switchers go wrong is automatic conversion. The “Price [price]” page says “Don’t change the price of your product on your landing page based on a user’s location”, adds that “IP detection is against our guidelines”, and rules out products priced from “prices based on a live currency exchange”. A switcher that converts by IP address on first load shows each visitor a different page from the one your product data describes, and a live exchange rate moves the number every day.

A second currency on the page is fine if it is plainly secondary. Google's landing page requirements say that where a page shows several prices, “such as other variants, original currency, or promotional prices, the additional prices should be clearly differentiable from the advertised base price.” Selling abroad in one currency is what Google's own currency conversion is for, covered in currency in Merchant Center. If your store redirects visitors by country, read geo-redirects first.

Manual check first: StoreVerifier does not see your Merchant Center account or what your payment provider charges, so a test order in each currency is yours to run. The free scan flags a currency switcher or automatic converter on the page, and reports structured data whose currency conflicts with the page as a failure. Currency checks sit beside the pricing checks on the misrepresentation checker.

Typical evidence

One product, three different prices

A display-only switcher changes the label and nothing else. So the shopper sees euros, the feed submits pounds, and the card gets charged pounds — three numbers for one product, and the only one the shopper actually read is the one nobody honoured.

Product · MERINO-CREW-01
Merino Crew — one item, one true price
Shopper sees
€34.99
switcher display · EUR
Feed submits
£29.99
price attribute · GBP
Card charged
£29.99
checkout · GBP
Three numbersThe page promised euros; the bank took pounds. Display, feed and charge all have to agree — here only two do, and not the two the shopper actually read.

The public signals this check looks for:

  1. The site opens in euros for a visitor in France and in pounds for a visitor in the UK, whi…

    The site opens in euros for a visitor in France and in pounds for a visitor in the UK, while your product data says GBP.

  2. The switcher converts prices with a live exchange rate, so the figure changes from one day…

    The switcher converts prices with a live exchange rate, so the figure changes from one day to the next.

  3. The page shows a converted price, but checkout charges the store’s base currency at a diff…

    The page shows a converted price, but checkout charges the store’s base currency at a different amount.

  4. A “Switch to EUR?” pop-up covers the price when the page first loads

    A “Switch to EUR?” pop-up covers the price when the page first loads.

  5. The chosen currency is lost between the product page and the cart

    The chosen currency is lost between the product page and the cart.

What it looks like once it is right

The same store opens every page in GBP, keeps the switcher as an opt-in menu with converted prices marked “approx.”, and charges GBP with the amount shown before payment. Google’s currency conversion handles its listings abroad.

Common mistakes

Common mistake

A UK store submits prices in GBP. Its switcher reads the visitor’s IP address and opens the page in USD at today’s exchange rate for anyone outside the UK, then checkout charges GBP.

Self-check steps

Sync it, and the three numbers become one

The switcher isn’t the enemy — an unsynced switcher is. Turn on the Merchant Center integration so picking a currency updates the feed and the charge as well as the label, and the page, feed and till finally tell the same story.

Currency switcher → Merchant Center syncON
Stage
Currency
Price
Shopper sees
EUR
€34.99
Feed submits
EUR
€34.99
Card charged
EUR
€34.99
ReconciledOne currency, one number, from the page the shopper reads to the line on their statement.

Questions merchants ask

Can I use a currency switcher with Google Shopping?

Yes, if the page opens in the currency of your product data and nothing converts prices by the visitor’s location. Google's “Price [price]” page says not to change the price on your landing page based on a user’s location, and its checkout requirements ask for the same currency from product page to checkout.

Can I show converted prices next to my main price?

Yes, as long as they are clearly secondary. Google's landing page requirements say that where a page has several prices, such as an original currency, the additional prices should be clearly differentiable from the advertised base price.

Do I need a switcher to sell abroad?

No. Google's currency conversion is automatically enabled in Merchant Center accounts and shows a converted price in your listings, while your site keeps charging in its own currency. See currency in Merchant Center.

Remediation

Risk signal

A switcher helps shoppers when they choose it and hurts listings when it chooses for them. Open in the currency you submit, let people switch, and make checkout charge what the page said. Then test it with a real card, because the statement is where the truth turns up.
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

Sources

  1. Checkout requirements and best practicesGoogle Merchant Center Help — support.google.com
  2. Price [price] — submitting accurate product pricesGoogle Merchant Center Help — support.google.com
  3. About landing page requirementsGoogle Merchant Center Help — support.google.com

Last reviewed 23 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.