Currency mismatch: Merchant Center data vs your product page

The currency in your product data must be the currency your product page shows most prominently and the one your checkout charges. When they differ, fix the setting that sends the wrong code instead of stacking another converter on top. It is usually one setting, which is the good news.

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 “How to fix: Mismatched product price” page covers the currency as well as the amount: “If your landing page displays prices in multiple currencies, make sure the price and currency in your product data source matches the price and currency prominently displayed on your landing page.” The “Price [price]” page adds the checkout: “Show the price in the currency of your target country prominently on your landing page and checkout pages.”

Most mismatches come from settings, not intent. A store currency changed on the platform while the feed app still sends the old code; a data source set up for one country and later pointed at another; a multi-currency app that makes the storefront’s default something other than the submitted currency. Google's “Supported languages and currencies” page lists the currency each target country supports, noting that “other currencies may be supported using currency conversion”.

Currency conversion is the proper way to list in a country whose currency your site does not use, and it comes with a condition from Google's “About currency conversion” page: “Make sure to clearly indicate the price in the original currency throughout your landing pages and website.” The same page explains why: your site keeps charging in its own currency, so “the final purchase price for the user depends on the exchange rates used by the user's credit card or other payment service provider.” The wider setup is in currency in Merchant Center, and switcher apps in currency switchers.

Manual check: StoreVerifier does not see your product data, so the currency code in each data source is yours to confirm. The free scan reports structured data whose currency conflicts with the page or checkout as a failure, and flags product structured data that names no currency. Every currency check is listed on the misrepresentation checker.

Typical evidence

GBP in the feed, EUR on the page

Keep submitted product data and the public page consistent for the market you serve. Compare them manually in the relevant locale; StoreVerifier does not access feed data or reproduce another system's fetch.

Product feed · submitted entry

<item>
  <g:id>MERINO-CREW-01</g:id>
  <g:price>29.99 GBP</g:price>   <!-- declared charge currency -->
</item>

Product page · served to EU shoppers

€34.99

currency converter active · the price attribute’s GBP never reaches the shopper

VerdictIn this example, the feed says pounds and the page says euros. Treat that as a public mismatch to investigate; do not assume its scope from one item.

The public signals this check looks for:

The data source sends USD while the product page shows GBP prices with a small USD option
The data source sends USD while the product page shows GBP prices with a small USD option.
A price with no currency symbol or code, such as “49…
A price with no currency symbol or code, such as “49.00”, on a store that sells in several currencies.
The platform’s store currency changed, but the feed app kept the old currency code
The platform’s store currency changed, but the feed app kept the old currency code.
The Product structured data says EUR while the visible price is in GBP
The Product structured data says EUR while the visible price is in GBP.
One data source targets two countries with different currencies, set up without currency c…
One data source targets two countries with different currencies, set up without currency conversion in mind.

What it looks like once it is right

The store switches the feed app back to EUR, sets its structured data’s priceCurrency to EUR, and lets Google’s currency conversion show pound estimates to UK shoppers while the site keeps charging in euros.

Common mistakes

Common mistake

A Dutch store sells in EUR, but its feed app was set up during a UK push and still sends GBP. Listings show pounds, the page shows euros, and checkout charges euros.

Self-check steps

In Merchant Center, note the currency and target countries of each data source.
Open sample product links in a private window and note the currency the page shows first, the currency in its structured data and the currency charged at checkout.
Make one currency the default, most prominent price for each data source, and keep it all the way to payment.
Fix the source of a wrong code: the platform’s currency setting, the feed app’s currency option or the data source’s settings, not a one-off edit.
Show a currency symbol or code with every price, so nobody has to guess.
Set priceCurrency in the Product structured data to the currency the page shows.
For countries whose currency your site does not use, rely on currency conversion and keep the original currency clearly shown.

One feed per currency, each charging what it declares

The structural fix isn’t a display layer — it’s a feed per market whose declared currency is the genuine charge currency. Stretch one feed across currencies it never charges and you’re back to the mismatch you started with.

Target market

Feed currency

Charge currency

Match

United Kingdom

GBP

GBP

Eurozone

EUR

EUR

United States

USD

USD

One feed for everyone

GBP

EUR / USD

The ruleA converted price shown for comfort needs a matching charge currency behind it. Compare the submitted feed entry yourself; display conversion is not the same thing as charge currency.

Questions merchants ask

Why does Merchant Center show a currency mismatch?

Because the currency in your product data differs from the one your product page shows prominently or your checkout charges. Google's price mismatch page asks that the price and currency in your product data match those prominently displayed on your landing page, even when the page offers several currencies.

My site shows several currencies. Which one should the product data use?

The one the page shows by default and prominently, which is also the one checkout charges. Other currencies can sit beside it as a clearly secondary choice. See currency switchers for how to set that up.

Can I list products in a country whose currency my site does not use?

Yes, with currency conversion. Google's currency conversion page says it converts the price in your product data for the target country and shows both prices in the listing, while your site keeps charging in its own currency, which you must show clearly throughout your pages.

Remediation

Risk signal

A currency mismatch is usually one setting repeated across the whole catalogue, so one fix clears it. Find the setting that sends the wrong code, change it once, and test a product page and a checkout the same day.

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.