Why Is Google Shopping Showing the Wrong Currency? Causes, Diagnostics & Fixes

Google Shopping usually shows the wrong currency because the currency submitted to Google Merchant Center doesn’t match what Google finds on your landing page. In most cases, the problem comes from multi-currency store setups, geolocation-based currency switching, incorrect target-country feeds, or product schema that reports a different currency than the one submitted in your feed.

Unlike regular search results, Google Shopping validates pricing across multiple sources before approving a product. If Google sees USD in your feed but GBP on your product page or if your website automatically changes currency based on location, your products can trigger price mismatch and currency mismatch errors.

This guide explains exactly why Google Shopping is showing the wrong currency, how to identify the source of the mismatch, and how to fix it before it affects your Shopping campaigns.

What Does “Google Shopping Showing the Wrong Currency” Actually Mean?

A currency issue occurs when Google receives one currency from your product data but detects another during its validation process.

Common examples include:

• Your product feed submits USD, but the landing page displays GBP.
• Google Shopping shows EUR while the checkout switches to USD.
• A product feed targets the United Kingdom, but prices are submitted in USD.
• Google may crawl a version of the page that displays a different currency than the one submitted in your product feed.
• Structured data reports one currency while the visible product price shows another.

Google doesn’t evaluate pricing from a single source. It compares multiple pricing signals before approving products.

How Google Verifies Product Currency

When a product is submitted to Google Shopping, Google cross-checks pricing information across several locations.

Product Feed

The feed is Google’s primary pricing source.

Example:

• 49.99 USD
• 39.99 GBP
• 69.99 AUD

The submitted currency becomes Google’s expected currency for that product.

Landing Page

Google crawls the product page and compares the visible price against the feed.

If the feed contains USD but the page displays GBP, Google may flag the product.

Structured Data

Google also checks Product schema.

A common issue occurs when:

“price”: “49.99”,

“priceCurrency”: “USD”

exists in schema while the visible page displays GBP.

Checkout

Google may verify the final checkout experience.

If the advertised price is GBP but the cart converts to USD during checkout, that inconsistency can trigger account warnings.

The 7 Most Common Reasons Google Shopping Shows the Wrong Currency

1. Feed Currency and Landing Page Currency Don’t Match

This is the most frequent cause of Merchant Center currency issues.

Example:

Source	Currency
Product Feed	USD
Product Page	GBP

Google expects both sources to display identical currency values.

Even if the numerical price is correct, a currency mismatch alone can trigger product disapprovals.

2. Your Feed Targets the Wrong Country

Many merchants submit a feed with one currency while targeting a market that expects another.

Examples:

Target Country	Submitted Currency
United Kingdom	USD
Australia	EUR
Canada	GBP

Google may still process the feed, but inconsistencies often create approval issues and lower trust signals.

3. Currency Switchers Are Modifying Product Pages

WooCommerce merchants frequently install:

• Multi-currency plugins
• Currency switchers
• Geolocation pricing tools

The feed may remain in USD while visitors see GBP, EUR, or CAD.

This creates a situation where Merchant Center stores one value while Google discovers another during page crawls.

4. Googlebot Sees a Different Currency Than Users

Many stores display currency based on IP addresses.

For example:

• US visitors see USD.
• UK visitors see GBP.
• European visitors see EUR.

The problem occurs when Googlebot receives a different version of the page than the one used to generate the feed.

This is one of the most overlooked causes of recurring currency mismatch errors.

5. Product Schema Uses the Wrong Currency

Merchants often update front-end pricing but forget schema markup.

Example:

Visible page:

• £39.99

Schema:

“priceCurrency”:”USD”

Google may trust the structured data and report a mismatch even though the front-end display appears correct.

6. Checkout Currency Changes After Add-to-Cart

Some payment systems automatically convert currency during checkout.

Example:

• Product page: GBP
• Cart: GBP
• Checkout: USD

This creates a broken pricing experience and can lead to Merchant Center warnings.

7. Automatic Currency Conversion Creates Price Differences

Currency conversion tools rarely produce exact values.

A product submitted as:

• $100 USD

might display as:

• £74.11 GBP
• £74.09 GBP
• £74.15 GBP

depending on exchange rates, caching, and rounding rules.

Over time these small differences can become large enough for Google to flag pricing discrepancies.

How to Find the Exact Cause in Merchant Center

Instead of guessing, start with Merchant Center Diagnostics.

Step 1: Open Diagnostics

Go to:

Products → Diagnostics

Look for:

• Price mismatch
• Currency mismatch
• Incorrect price
• Landing page issues

Step 2: Open an Affected Product

Review:

• Submitted price
• Submitted currency
• Landing page URL

Step 3: Compare What Google Sees

Check:

• Visible product price
• Structured data
• Cart currency
• Checkout currency

The mismatch usually appears within minutes once all four areas are reviewed together.

How to Fix Google Shopping Showing the Wrong Currency

Fix 1: Make Feed and Landing Page Match

Your feed and landing page should always use the same currency.

Bad:

• Feed = USD
• Landing Page = GBP

Good:

• Feed = GBP
• Landing Page = GBP

Fix 2: Create Country-Specific Feeds

If you sell internationally, create separate feeds for each market.

Country	Currency
United States	USD
United Kingdom	GBP
Australia	AUD
Canada	CAD

This approach is significantly more reliable than relying on automatic currency conversion.

Fix 3: Audit Multi-Currency Plugins

If you’re using WooCommerce currency plugins:

Verify that:

• Feed currency
• Product page currency
• Schema currency
• Checkout currency

all remain identical for the targeted country.

Fix 4: Verify Product Schema

Review your structured data and confirm:

“price”:”49.99″,

“priceCurrency”:”GBP”

matches the actual product page.

Fix 5: Prevent Googlebot From Seeing a Different Currency

Avoid forcing currency changes based solely on IP detection.

Whenever possible:

• Use dedicated regional URLs.
• Use country-specific feeds.
• Keep pricing stable for crawlers.

Fix 6: Refresh Feed Data

After making corrections:

1. Regenerate your feed.
2. Upload the updated feed.
3. Request a new fetch if needed.
4. Monitor Diagnostics over the next 24–48 hours.

How to Change Currency in Google Shopping

Many merchants search for “how to change Google Shopping currency,” but there is no currency setting inside Google Shopping itself.

Google Shopping uses the currency submitted through your product feed.

To change currency:

1. Update your store pricing currency.
2. Regenerate your product feed.
3. Ensure landing pages display the same currency.
4. Update schema markup if necessary.
5. Resubmit products to the Merchant Center.

Once Google processes the updated feed, Shopping listings will reflect the new currency.

WooCommerce-Specific Currency Problems

WooCommerce stores experience currency mismatches more often than most platforms because merchants commonly combine:

• Product feed plugins
• Multi-currency plugins
• Geolocation tools
• Dynamic pricing plugins

A typical scenario looks like this:

• Feed submitted in USD
• UK visitor sees GBP
• Schema still contains USD
• Checkout converts again

From Google’s perspective, there are four different pricing signals for the same product.

The solution is not adding more conversion rules. The solution is ensuring that every pricing source reports the same currency for the targeted market.

Example: Google Shopping Shows USD Instead of GBP

Suppose you sell in the United Kingdom.

Current setup:

Component	Currency
Feed	USD
Product Page	GBP
Schema	USD
Checkout	GBP

Google receives conflicting information.

Correct setup:

Component	Currency
Feed	GBP
Product Page	GBP
Schema	GBP
Checkout	GBP

Once all four components align, the mismatch warning typically disappears after Google recrawls the affected pages.

Best Practices to Prevent Currency Mismatches

• Use separate feeds for separate countries.
• Match feed currency with landing page currency.
• Match schema currency with visible pricing.
• Review Merchant Center Diagnostics weekly.
• Test product pages using incognito mode.
• Avoid excessive IP-based currency switching.
• Keep checkout currency identical to advertised pricing.
• Revalidate feeds after installing new currency plugins.

Frequently Asked Questions

Final Thoughts

When Google Shopping shows the wrong currency, the issue is rarely Google itself. The problem usually originates from conflicting pricing signals across your feed, landing page, schema markup, checkout flow, or country-targeting configuration.

The fastest way to resolve the issue is to identify every place where pricing appears and ensure the same currency is used consistently. When feed data, landing pages, structured data, and checkout all align, Google can validate products correctly, eliminate mismatch warnings, and display accurate pricing across Shopping listings.