Currency in Merchant Center: product data, page and checkout

Submit prices in the currency your product pages and checkout charge, and keep that one currency from product page to payment. Google converts it for shoppers in other countries; your site does not have to, and it should not switch prices by the visitor’s location. The usual culprit is a currency app.

Critical4 min read

By Edvinas Ivanauskas 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 “Price [price]” page asks you to “Submit an amount and currency that match the price on your landing page and the checkout pages”, and to “Show the price in the currency of your target country prominently on your landing page and checkout pages.” The checkout requirements add: “All pages from the product page to the checkout page must consistently show the same currency.”

Selling abroad does not need a second currency on the site. Google's “About currency conversion” page says: “Currency conversion is automatically enabled in all Merchant Center accounts.” It converts the price in your product data for shoppers in another target country and shows both prices in the listing, and it tells you to “clearly indicate the price in the original currency throughout your landing pages and website.” One rule comes with it: “you must follow the price and tax requirements of the country that the currency in your product data is local to.”

What goes wrong is usually a currency app. The “Price [price]” page says: “Don’t change the price of your product on your landing page based on a user’s location.” A switcher that converts prices automatically by location shows each visitor a different page from the one your product data describes, and a checkout that charges in another currency again leaves the shopper guessing what they will pay.

The free scan flags a currency switcher or automatic converter, and structured data whose currency disagrees with the page. Compare the currency you submit in Merchant Center yourself. Switchers and automatic converters have their own guide: currency switchers. See every pricing check on the misrepresentation checker.

Typical evidence

Three surfaces, one should agree — none do

The GMC account is configured in USD (set at account creation for a US launch that never happened). The feed submits GBP prices. The checkout charges GBP. A three-way currency disagreement.

currency configuration audit

GMC account

29.99USD (configured)

Feed price attr

29.99GBP (submitted)

Checkout

29.99GBP (charged)

All three disagree. Account must be reconfigured for GBP — this is a structural fix, not a feed update.

Currency misconfiguration affects every product simultaneously. Change the GMC account currency to match checkout and feed, or create a separate account per currency market.

The public signals this check looks for:

Your product data sends prices in GBP while a currency app shows visitors from other count…
Your product data sends prices in GBP while a currency app shows visitors from other countries a converted price in their own currency.
The product page shows euros and the checkout charges in pounds
The product page shows euros and the checkout charges in pounds.
You added a target country and made a separate currency version of the site by IP address,…
You added a target country and made a separate currency version of the site by IP address, instead of using Google's currency conversion.
The product page's structured data declares one currency and the visible price shows anoth…
The product page's structured data declares one currency and the visible price shows another.
The price on the page shows a number with no currency symbol or code at all
The price on the page shows a number with no currency symbol or code at all.

What it looks like once it is right

The same store shows £29.99 everywhere, with a note that prices are in pounds sterling, and lets Google's currency conversion show French shoppers an estimate in euros in the listing. Checkout charges £29.99.

Common mistakes

Common mistake

A UK store submits prices in GBP. Its currency app shows a French visitor €34.50, the checkout charges £29.99, and the product markup says EUR. Three answers to one question.

Self-check steps

For each target country, write down the currency your product data submits, the currency the product page shows, and the currency the checkout charges. All three must agree, unless you rely on Google's currency conversion, in which case the page and checkout show your original currency.
Open a product page from a private window and, if you can, from another country or a VPN. If the price or currency changes by location, turn off automatic conversion in your currency app.
If you keep a currency selector, make it the shopper's choice rather than automatic, and make sure checkout charges in the currency the shopper chose and saw.
Show the currency clearly beside every price, with the symbol or ISO code, on product pages, in the cart and at checkout.
Check the product page's structured data: priceCurrency should be the same currency the page shows. Google's Rich Results Test shows what the markup declares.
For countries whose currency you do not show, rely on currency conversion and follow the price and tax rules of the country your currency belongs to.
Re-check one product per market after installing or updating any currency, translation or market app.

One account per currency, not one account for everything

For multi-market operations, the correct structure is a separate GMC account (or sub-account) per currency market. Each account is configured in its own currency, each with its own currency-priced feed.

UK market

Account currency: GBP

Feed price currency: GBP

US market

Account currency: USD

Feed price currency: USD

DE market

Account currency: EUR

Feed price currency: EUR

Note: use a Multi-Client Account (MCA) to manage all three under one login. Each sub-account is independent — its own currency configuration and its own feed.

Once separated by currency account, a feed price error in one market does not affect the others. This also makes Diagnostics per-market cleaner.

Questions merchants ask

Do I need a separate currency on my site for each country I target?

No. Google's currency conversion is automatically enabled in all Merchant Center accounts. It converts the price in your product data for shoppers in another target country and shows both prices in the listing. Your pages keep showing your original currency, and you follow the price and tax rules of that currency's country.

Can I use a currency switcher app with Google Shopping?

A switcher the shopper chooses is workable if checkout charges in the chosen currency. Automatic conversion by location runs into Google's rule on the Price [price] page: don't change the price of your product on your landing page based on a user's location. StoreVerifier's free scan reports a switcher or auto-converter it finds.

What if my checkout charges in a different currency from the product page?

Fix it. Google's checkout requirements say all pages from the product page to the checkout page must consistently show the same currency. Make the checkout charge the currency the product page shows, or show the product page in the currency checkout will charge.

Remediation

Risk signal

A currency that changes between listing, page and checkout makes the price unclear, and the rule behind it is written plainly in Google's price and checkout pages. Keep one currency per market all the way to payment, and let Google do the converting; it is less work for you anyway.

PriorityTreat this and any other highest-severity findings as first-priority work, then document each fix.

EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

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.