4 min read
Fix library - item disapproved
Price mismatch: the rule Google actually enforces
The price in your feed must match the price on your landing page and at checkout, in the same currency, shown prominently. That is the rule in Google's current documentation. Here is what the docs say, what they do not say, and how to fix a mismatch.
Last verified: 2026-08-10
The problem
Items come back from Diagnostics disapproved with a price-related issue, or a shopper lands on your product page and the price is different from the ad. Either way Google now has two prices for the same product, and a price mismatch is one of the classic triggers for a misrepresentation-style review of the whole account, not just the item.
Why it happens
The feed price, the landing page price, and the checkout price are three places the same number can drift apart. The usual causes: a price change in Shopify that never regenerated the feed, a sale price running on the site but not in the feed, a currency or VAT mismatch between the site and the feed, geo-pricing that shows a different price to Google's crawler than to shoppers, or a checkout that adds fees the product page does not show.
Google's price documentation is explicit about what it checks: the amount and currency in the product data must match the landing page and the checkout pages, the price must be shown prominently and not hidden behind a "See price in cart" step, and the price must not change based on the user's location (IP detection is against the guidelines).
Google Merchant Center Help, "Price [price]": https://support.google.com/merchants/answer/6324371
Direct quotes: "Submit an amount and currency that match the price on your landing page and the checkout pages." And: "Don't change the price of your product on your landing page based on a user's location. IP detection is against our guidelines and may interfere with the crawler behavior."
Some older guides and forum posts describe a "45 day" price consistency rule for Google Merchant Center. We checked Google's current Merchant Center help on 2026-08-10 and no such rule appears in the live documentation. What is in the documentation is the landing page and checkout consistency requirement above, plus the requirement to keep prices up to date. Trust the live policy page over the forum post.
How to fix it, step by step
- List the mismatching items. Open Diagnostics and pull the items with price issues. If the issue code does not name the items, spot check a sample: five to ten products across categories, comparing feed price to the live product page.
- Decide which side is the source of truth. For almost every store it is the site: the price shoppers actually pay. If the site price is right, the feed is what needs regenerating.
- Fix the store side first. Update the prices in Shopify (or your backend), and make sure sale prices are entered as sale prices, not as overwritten regular prices. Check the currency matches your target country, and that VAT handling is consistent: the feed price must equal what the shopper sees.
- Regenerate the feed and verify the file. Open the raw feed and grep a few known SKUs: the price column should now match the site. A feed that still shows old prices after regeneration usually means a caching layer, a stuck app job, or a mapping that pulls from the wrong field.
- Check the checkout too. Google's docs require the checkout price to match as well, so test the end to end: if the checkout adds fees that were not on the product page, that is part of the mismatch. Fees you charge at checkout must be included in the total the shopper sees.
- Remove geo-pricing and "see price in cart" patterns. A price that changes by location, or one that only appears after cart, is explicitly against the guidelines and is a fast way to turn an item issue into an account issue.
- Consider automatic item updates for price. Google's docs describe enabling automatic item updates, which reads Schema.org microdata from your landing page to keep prices fresh between feed submissions. It is an assist, not a replacement: you still need to resubmit the product data regularly.
- Verify and, if needed, request a review. Once the feed and site agree, wait for reprocessing, confirm the disapproved count drops, then use the review request path if items are still flagged.
When to get help
Price mismatches are simple when they are one stale regeneration. They compound when the mismatch is part of a wider drift: prices that have not synced in weeks, a feed app that maps prices from the wrong field, or a misrepresentation review already opened on the account. That is the £99 rescue plus feed fix territory: the underlying cause found and fixed, then verified against the live feed.
Is a price mismatch part of a bigger problem?
Take the free 5 question audit for a straight verdict on your account, or run the free feed health check to see the other errors sitting next to it.
Take the free audit →Can I show a different price to Google's crawler than to shoppers?
No. Location-based price changes are explicitly against the guidelines, and any scheme that serves one price to Google and another to shoppers is a misrepresentation pattern, which is account-level risk, not item-level.
Does a sale price need to be in the feed?
Yes, if the sale price is what the shopper pays. Google's docs cover the sale price attribute for telling shoppers about promotions; the key is that whatever the shopper pays must match what is in the feed and on the page.