Price mismatch in Merchant Center, explained
A price mismatch means the price in your product feed differs from the price Google found on your landing page. Google treats this seriously because the shopper clicked an ad or listing expecting one price and found another. Products get disapproved, and repeated mismatches can contribute to account-level problems.
How Google checks
Google compares the price and currency in your feed with what it reads on the product page, both from the visible page and from structured data. It may also add items to the cart in some cases. If any of those disagree, you can get a mismatch warning. Google can also update prices automatically from your page when you turn on automatic item updates, which can hide the problem rather than fix its cause.
The usual causes
Sale prices
The page shows a sale price, the feed shows the regular price, or the sale ended on the site but the feed still has the sale price. Use the feed's sale price field with start and end dates, so the feed changes at the same moment the site does.
Feed timing
Your feed updates once a day but you changed prices at noon. Google may crawl the page between the two. Schedule feed fetches more often, or push updates through your feed app when prices change.
Currency and location
A currency switcher shows a converted price to visitors from other countries. If Google crawls from a location that triggers conversion, the page price will not match your feed. Make sure the default currency matches the feed's target country, or set up separate feeds per country.
Variants
The feed lists one price for a product with variants that cost different amounts. Each variant should be its own item in the feed with its own price and a URL that opens that variant.
Tax and shipping
In the United States, prices in the feed normally exclude tax, while in many other countries they include it. Make sure your feed follows the convention for the country you target, and that your page does too.
Structured data drift
The visible price is right but the JSON-LD in the page code is stale or comes from a second plugin. Google reads both.
Membership or app-based pricing
Wholesale apps, member discounts or bundle apps can change the price a logged-out visitor sees. Check the page in a private browser window.
How to find the source
- Open the disapproved item in Merchant Center and note the feed price and the crawled page price.
- Open the landing page in a private window.
- View the page source and search for "price" in the JSON-LD block.
- Compare all three values and note which one is different.
- Trace that value back to the app, theme or setting that controls it.
Stopping it from coming back
Price changes are part of running a store, so the fix is a habit, not a one-off. After any sale, theme update or new app install, spot-check a few products. Better still, compare the feed and the site automatically.
Merchant Clock's feed check reads your XML or CSV feed and compares each item's price and availability with the matching product page we crawled. Starter runs it weekly. Pro and Agency run it daily. A new mismatch lowers the score, and the drop sends you an alert with the fix.
Questions
Will automatic item updates fix this for me?
It can keep Google's copy closer to your page, but it treats the symptom. If the underlying cause stays, the next feed upload brings the mismatch back.
How many mismatches cause a suspension?
Google does not publish a number. A few disapproved items is a product-level problem. Widespread mismatches can be seen as misleading and escalate.