Why Google shows the wrong price (and how to fix it)

Short answer: Google usually shows the wrong price when your product feed, the price visible on the landing page, and the structured data on that page don’t match. For countries where VAT or GST must be included in the displayed price, any mismatch between tax-inclusive values in your feed and on your page can trigger inaccuracies or disapprovals (https://support.google.com/merchants/answer/10897069?hl=en-GB). A common culprit is a stale sale price left in your structured data that no longer matches the page (https://zatomarketing.com/blog/why-is-my-sale-price-wrong-in-google-merchant-center).

How price mismatches happen

Google evaluates the price you provide in Merchant Center product data against the price on your website; for most countries outside the US and Canada, both must be a total tax-inclusive amount (https://support.google.com/merchants/answer/10897069?hl=en-GB). Even when your page visually shows the correct price, outdated structured data (for example, an old price or sale price in JSON-LD) can be crawled and used, leading to a mismatch in Merchant Center diagnostics or listings (https://zatomarketing.com/blog/why-is-my-sale-price-wrong-in-google-merchant-center).

Fix wrong prices fast: the essentials

Start with a single SKU and compare the three sources of truth: feed, on-page price, and structured data. For VAT/GST countries, confirm that the price you submit and display is tax-inclusive and consistent across both locations (https://support.google.com/merchants/answer/10897069?hl=en-GB). Then scan your JSON-LD or microdata for stale price or salePrice values and update them to match the page (https://zatomarketing.com/blog/why-is-my-sale-price-wrong-in-google-merchant-center).

If you use automated discounts, make sure discounted prices persist for the required minimum time on the product page and through checkout as described in Google’s guidance; otherwise you may see inconsistency notices in Merchant Center (https://support.google.com/merchants/answer/16798068?hl=en).

Common pitfalls to audit

VAT/GST inclusion mismatch

For products targeting all countries except the US and Canada, submit and display the total price inclusive of VAT/GST, and ensure the landing page price matches your feed. Don’t rely on a separate tax attribute for these countries (https://support.google.com/merchants/answer/10897069?hl=en-GB).

Stale sale price in structured data

If your PDP shows a current sale but your structured data still contains the previous price, crawlers can pick up the old value. Update or remove the stale salePrice so markup and the visible price align (https://zatomarketing.com/blog/why-is-my-sale-price-wrong-in-google-merchant-center).

Currency and variant confusion

Ensure priceCurrency in markup matches the currency shown to users, and avoid listing multiple conflicting prices on the same page. For product families, model and link to variant-specific pages where possible so the displayed price unambiguously reflects the advertised SKU (read how to model variants).

Verify your fix and timing expectations

Validate your structured data after edits to confirm the price and priceCurrency are correct and parsable (how to validate schema markup). After you update product data, resubmit and request a review; Google notes that most crawls complete within 24 to 48 hours (https://support.google.com/merchants/answer/10897069?hl=en-GB). If problems persist, collect the affected examples and Merchant Center notifications before contacting support.