Price Mismatch Errors: Causes and Fixes
Why Google disapproves products for price mismatch and the three places prices must stay in sync.
What Is a Price Mismatch?
Google crawls your product landing pages and compares the price it finds there against the price in your product feed. If they differ by more than a small rounding tolerance, the product is disapproved.
This is one of the most common disapproval reasons for e-commerce sites that run sales or use dynamic pricing.
The Three Places Prices Must Match
- Your product feed — the price attribute
- Your product landing page — the visible price the user sees
- Your Product schema markup — if you have JSON-LD structured data
All three must match within normal currency rounding (typically +-0.01).
Common Causes
Sale ended but feed still has sale price — When a sale expires on the website, the feed still shows the discounted price until it re-fetches. Fix: use the sale_price and sale_price_effective_date attributes so prices expire automatically.
Currency or tax differences — GMC checks the price in the country/currency of your target market. If your site shows prices excluding tax but your feed includes tax (or vice versa), this can trigger mismatches in some markets.
Dynamic pricing tools — Repricing software that changes website prices in real time may update faster than your feed refreshes. Increase your feed fetch frequency to match.
JavaScript-rendered prices — Google's crawler sees prices rendered client-side. If your price is loaded via JS after the initial page load, the crawler may see a different value than the final rendered price.
Fix Process
- Identify which products have the mismatch (Products > Diagnostics in GMC)
- Check the live product page price vs the feed price
- Update whichever is wrong — usually the feed
- Re-fetch your feed and request a re-review in GMC