A UK shopper searches for a product and sees it listed at $49 instead of £39. An Australian sees euros. A US shopper clicks a Shopping ad priced in dollars and lands on a page in pounds. Each of these mismatches costs clicks, sales and trust, and in Merchant Center it can lead to warnings or product disapprovals. Currency discrepancies are one of the most common technical problems for international ecommerce sites, and they are almost always fixable.
This guide explains why Google shows the wrong currency, what Google's own documentation requires, and the step-by-step fix for structured data, page templates and product feeds. It draws on searches such as "google shopping wrong currency", "multi currency ecommerce SEO google" and "google product structured data pricecurrency ISO 4217". Sources are listed at the end.
Where currency appears in Google
| Surface | Where Google gets the price and currency |
|---|---|
| Product rich results in Search | Product structured data on the page (offers.price and offers.priceCurrency), checked against visible content |
| Merchant listings and free listings | Structured data and Merchant Center product data |
| Shopping ads and Performance Max | Merchant Center product data, checked against the landing page |
| Google Images and Discover product features | Structured data and Merchant Center data |
All of these need to agree with what a shopper sees on the page. When they do not, Google may show the wrong currency, drop the price, show no rich result at all, or flag products in Merchant Center.
What Google's documentation requires
- ISO 4217 codes. Google's merchant listing documentation defines priceCurrency as the currency used to describe the product price, in three-letter ISO 4217 format, and says it is required when price is specified.
- One URL per currency. The same documentation says that when products are sold in multiple currencies, you should have a distinct URL per currency, for example one URL for Canadian dollars and one for US dollars.
- Feed currency matches the page. Merchant Center Help says the price should be in the official currency of the target country, in both the product data and the website, including the landing page and checkout.
- Other currencies are allowed, but not as the default. Merchant Center allows multiple currencies on a landing page as long as the currency in your product data is the default, prominently listed currency, and at checkout the customer can easily select that currency for at least one payment method.
Why the wrong currency appears
| Cause | What happens | How to spot it |
|---|---|---|
| Geo-IP currency switching on one URL | The page changes currency based on visitor location. Google's crawler, which mostly crawls from US IP addresses, sees one currency; shoppers elsewhere see another. | URL Inspection shows a different currency from your target market |
| Hard-coded priceCurrency | The structured data template always outputs one currency, even on pages showing another. | Rich Results Test shows a currency that does not match the visible price |
| JavaScript currency switching | The server sends one currency; a script swaps it after load. Structured data and visible price disagree. | Compare page source with the rendered HTML |
| Cached pages | A CDN or page cache serves a currency version meant for another region. | Different results on repeated tests; cache headers |
| Feed and page mismatch | Merchant Center feed lists a currency or price that differs from the landing page. | Merchant Center diagnostics warnings |
| App or platform conversion settings | Ecommerce platforms or apps convert prices automatically and inconsistently across templates. | Check platform market and currency settings |
| Wrong code | Symbols or non-standard codes (such as "$" or "US$") used instead of ISO 4217 codes. | Validation warnings in testing tools |
Check your setup
Currency consistency checker
The fix, step by step
1. Decide your country and currency structure
Choose how each currency or country version will have its own URL:
| Structure | Example | Notes |
|---|---|---|
| Subdirectories | example.com/uk/, example.com/us/ | Easy to manage on one domain; common choice |
| Subdomains | uk.example.com, us.example.com | Clear separation; more setup |
| Country domains | example.co.uk, example.com.au | Strong local signal; more domains to maintain |
| URL parameters | example.com/product?currency=GBP | Works if each parameter URL is stable, crawlable and consistent, but is harder to manage and less clear for users |
Google's international guidance covers the trade-offs of each. What matters for currency is that each URL always shows the same currency to every visitor and crawler.
2. Stop forcing currency by IP address
Google's guidance on locale-adaptive pages explains that Googlebot crawls mostly from US IP addresses, so pages that change content based on visitor location may only be seen in their US version. Instead:
- Serve a fixed currency on each country or currency URL.
- Show a banner suggesting the visitor's local version rather than redirecting automatically.
- Let visitors switch with a clear country or currency selector that links to the other URL.
- Remember the visitor's choice for convenience, without changing what a URL shows to others.
3. Make structured data match the visible price
- Generate offers.price and offers.priceCurrency from the same data that renders the visible price, not from a separate hard-coded value.
- Use ISO 4217 codes (GBP, USD, EUR, CAD, AUD, INR), never symbols.
- Use a plain number for price, without currency symbols or thousands separators.
- If you use priceSpecification, remember Google's documentation: when both offers.price and offers.priceSpecification encode the active price, Google uses offers.price.
- Render structured data on the server, so crawlers do not depend on scripts that may change currency later.
Example for a UK product page
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "Linen Throw Blanket",
"sku": "LTB-001",
"image": "https://example.com/images/ltb-001.jpg",
"offers": {
"@type": "Offer",
"url": "https://example.com/uk/products/linen-throw-blanket",
"price": 39.00,
"priceCurrency": "GBP",
"availability": "https://schema.org/InStock"
}
}
The US version at example.com/us/products/linen-throw-blanket would show and mark up its own US dollar price.
4. Add hreflang between country versions
Hreflang annotations tell Google which URL is meant for which language and country, so the right version appears in each market. Each country version should list all others, including itself, and use consistent canonical tags (each country URL canonical to itself, not to a single global version).
5. Align Merchant Center feeds
- Use a separate feed or feed label for each target country, with prices in that country's currency.
- Link each product to the matching country URL.
- Make sure the landing page shows that currency by default, and checkout can complete in it.
- Consider Merchant Center's currency conversion feature if you want to reach additional countries without separate prices, understanding how converted prices are shown.
- Check that prices include or exclude tax according to each country's rules, since tax differences can also cause price mismatches.
6. Check caching
Make sure CDN and page caches store each country URL separately and never serve one country's currency on another's URL. Avoid varying cached content by IP location on the same URL.
7. Test and request recrawling
- Use URL Inspection in Search Console and view the rendered page and HTML for each country version.
- Run the Rich Results Test to confirm product structured data shows the right price and currency.
- Check Merchant Center diagnostics for currency and price mismatch issues.
- Request indexing for key URLs and resubmit feeds.
- Monitor Search Console's merchant listings and product snippets reports for errors.
Sale prices and strikethrough prices in several currencies
Sales add another layer. Each currency version needs its own sale price and, if shown, its own original price. Google's merchant listing documentation supports strikethrough prices through priceSpecification, using UnitPriceSpecification objects for the sale and the original price. Make sure:
- Sale prices start and end at the same time on the page, in structured data and in the feed for each country.
- The original price shown is genuine and consistent with local pricing rules.
- Converted sale prices are not rounded differently on the page and in the feed.
- Expired sales are removed everywhere, including cached pages.
Tax, duties and price mismatches
Some price mismatches are not currency problems at all. Countries differ on whether consumer prices must include tax: many European countries expect prices including VAT, while US prices are usually shown before sales tax. If the feed price includes tax and the page does not, or the reverse, Merchant Center may flag a mismatch. Follow each country's rules for the feed, and make sure the landing page shows the same price structure. Explain duties and import charges clearly for cross-border shoppers, because surprise charges at checkout lead to abandoned carts and complaints.
Converted prices versus local prices
| Converted prices | Local prices | |
|---|---|---|
| How it works | Base price converted at exchange rates | A set price per market |
| Pros | Easy to manage; quick to launch new markets | Clean, rounded prices; control over margins and positioning |
| Cons | Odd-looking prices; values change with exchange rates; mismatch risk if updated at different times | More work to maintain; needs regular review |
| Currency consistency risk | Higher, because page, schema and feed may update at different moments | Lower, if all outputs read from one price table |
Whichever you choose, make sure the page, structured data and feed all read from the same source at the same time. Exchange-rate updates that reach the website hours before the feed are a common cause of mismatch warnings.
Rounding and price presentation by market
Shoppers in different countries are used to different price formats, such as decimal commas, currency symbols before or after the number, and typical price endings. On the page, format prices the way local shoppers expect. In structured data, always use a plain number with a dot as the decimal separator and the ISO currency code, regardless of how the price is displayed. Keep the underlying value identical; only the display format should differ.
Monitoring currency issues over time
- Check Search Console's merchant listings and product snippets reports monthly for structured data errors.
- Watch Merchant Center diagnostics for currency, price and availability mismatches by country.
- Spot-check key products with URL Inspection after theme, app or platform updates.
- Track impressions and clicks for each country version in Search Console; sudden drops can signal a currency or hreflang problem.
- Search for your products from each target country (using a VPN or the location setting in testing tools) to see what shoppers see.
Running a quick currency audit
- List your target countries and their official currencies.
- Pick five to ten top products and collect each country URL.
- For each URL, record the visible currency, the structured data currency and price, and the feed currency and price.
- Note whether the URL changes when you visit from a different location.
- Check canonical and hreflang tags.
- Fix templates rather than individual products wherever the cause is systematic.
- Retest the same URLs after the fix, then sample more products.
Platform-specific notes
| Platform | What to check |
|---|---|
| Shopify | Markets settings, whether each market has its own subfolder or domain, automatic currency conversion, and whether the theme's structured data outputs the market currency |
| WooCommerce | Multi-currency plugins, whether currency is set by URL or by geolocation, and how SEO plugins generate product schema |
| Magento and Adobe Commerce | Store views per currency, base and display currency settings, full page cache by store view |
| Headless and custom builds | Server-side rendering of prices and schema, cache keys per locale, consistent data between front end and feeds |
Platform settings change over time, so test the output rather than relying on settings alone.
Multi-currency ecommerce SEO
Currency fixes are part of wider international SEO. To perform well in several countries:
- Give each market its own URLs, with local currency, language, shipping and returns information.
- Use hreflang and self-referencing canonicals.
- Translate and localise content properly, not only prices.
- Show local trust signals: delivery times, duties and taxes, local reviews and payment methods.
- Register each market in Merchant Center with appropriate feeds and shipping settings.
- Monitor performance by country in Search Console and analytics.
See our guide on multilingual PPC campaigns for the paid side of international ecommerce.
Common mistakes when fixing currency
- Fixing structured data only, while the page still switches currency by IP.
- Canonicalising all country versions to one URL, which hides the other currencies from Google.
- Redirecting crawlers to a default country, so other versions are never crawled.
- Using currency symbols instead of ISO codes in markup.
- Forgetting the feed, leaving Merchant Center mismatches in place.
- Forgetting checkout, where the feed currency must be available.
- Not retesting after theme or app updates, which often reintroduce hard-coded values.
Checklist
- Each currency has its own stable URL
- No forced currency switching by IP on a single URL
- Country selector links between versions
- priceCurrency uses ISO 4217 codes and matches the visible price
- Structured data rendered on the server from the same data as the page
- Hreflang and self-referencing canonicals across country versions
- Merchant Center feed per country, linked to the matching URL
- Checkout supports the feed currency
- Caches separated by country URL
- Tested with URL Inspection, Rich Results Test and Merchant Center diagnostics
Need help with Shopping campaigns across countries? See our Google Shopping ads service.
Sources
- Google Search Central: Merchant listing structured data. developers.google.com
- Google Search Central: Product snippet structured data. developers.google.com
- Google Merchant Center Help: Inconsistent currency between your product data and your website. support.google.com
- Google Merchant Center Help: Mismatched product price. support.google.com
- Google Search Central: Managing multi-regional and multilingual sites. developers.google.com
- Google Search Central: Locale-adaptive pages. developers.google.com