Roughly 1 in 4 Shopping disapprovals in Google Merchant Center in 2026 are 'Mismatched value (price)' or 'Mismatched value (availability)' errors — and almost none of them mean your data is wrong, only that your feed and your live page disagreed at the moment Google looked. Merchant Center treats the feed as a claim and the landing page as the proof, so the fix is never to guess at a new price; it is to make the feed value, the visible price, and the structured data say the same thing.
This guide works backward from the crawl through five causes — a stale feed, currency, tax and shipping, dynamic pricing, and broken structured data — so you spend your time on the real gap, not the symptom. To check your account against the most common feed and conversion leaks automatically, run our free 5-axis Google Ads audit.
Updated 2026-05-19 with current Merchant Center Diagnostics, automatic item updates, and structured-data crawl behavior observed across US, UK and European accounts.
- The page is the proof — Google crawls the landing page and trusts it over the feed when the 2 disagree. 2. Most mismatches are timing — a stale feed lags a live sale or stock change. 3. Tax and shipping belong outside price [price] — set tax in settings, ship in the shipping attribute. 4. Structured data must match too — wrong schema.org markup disapproves a correct feed. 5. Automatic item updates plus frequent refresh keep the feed, page and crawl in sync.
What does 'Mismatched value (price)' actually mean?
The error is the first thing to read carefully because the exact wording tells you which attribute to fix. Merchant Center raises 'Mismatched value (price)', 'Mismatched value (availability)', or 'Incorrect price' when the value you submit in the feed does not match what Google found on the live product page.
Mismatched value (price) — The price [price] attribute in your feed differs from the price Google crawled on the landing page or in its structured data. When the gap is larger than a small tolerance, the item is disapproved and stops serving in Shopping.
Mismatched value (availability) — The availability [availability] attribute says the product is in stock, but the crawled page says sold out or out of stock, or the reverse. Google disapproves so a shopper never clicks an ad for an item they cannot buy.
Incorrect price — A broader flag that the price shown to shoppers cannot be trusted, often because the feed, the page, and the structured data give three different numbers. The cure for all three is the same: make every source agree. See our guide to Shopping products not showing for the wider disapproval picture.
Why does Google crawl your landing page and microdata?
It feels redundant to submit a feed and then have Google read your page anyway, but the crawl exists to protect shoppers. The feed is what you claim; the page is what a buyer actually sees, and Google reconciles the two before it lets an item serve.
The crawl — On a regular schedule Google fetches each product landing page and reads three things: the visible price, the structured data, and the microdata. It then compares those to the price [price] and availability [availability] attributes in your feed.
Structured data and microdata — Most stores expose price and availability in schema.org Product markup. Google reads price, priceCurrency, and availability from that markup. If your page renders one price to shoppers but carries an old number in the structured data, Google sees a conflict even when the visible price is correct.
The page wins — When the feed and the crawl disagree, Google trusts the page, because that is what the shopper experiences. This is why fixing only the feed is not enough; the page, its structured data, and the feed must all agree. For the bigger compliance picture, read our Merchant Center suspension recovery guide.
What are the most common causes of a price mismatch?
Price mismatches almost always come from one of a handful of repeatable causes. Identify which one applies and the fix becomes obvious.
Stale feed versus live site — The single most common cause. A sale goes live on the site at midnight while the feed still carries yesterday's price until the next scheduled fetch. Both values were correct; they just updated at different moments.
Currency — If the feed submits a price in one currency while the page renders another, or a multi-currency site shows the shopper a localized figure that the feed does not match, Google reads a mismatch. The price [price] currency must match the country and the page.
Tax, VAT and shipping included differently — A frequent and subtle cause. The price [price] attribute must follow the regional tax rule and must never bundle shipping. If the page shows a tax-inclusive total while the feed submits the pre-tax figure, or shipping is folded into one but not the other, the numbers diverge.
Dynamic pricing — Stores that reprice hourly with an algorithm will always outrun a once-a-day feed. Without near real-time updates the feed is stale by definition. Our Shopping setup and optimization guide covers feed architecture for fast-moving catalogs.
How do availability mismatches and out-of-stock lag happen?
Availability mismatches follow the same logic as price, but the value is in stock, out of stock, preorder or backorder rather than a number. The danger is sending shoppers to a product they cannot buy.
Out-of-stock not updated — The most common availability leak. An item sells out on the site, but the feed still submits in stock until the next refresh, so Google crawls a sold-out page and disapproves. The reverse also happens after a restock.
The availability attribute — The availability [availability] attribute must reflect the live stock state Google will find on the page. If your storefront marks an item out of stock in its structured data, the feed must say the same, or the crawl wins and the item is disapproved.
Variant and inventory drift — Multi-variant products are a classic trap: the parent shows in stock while a specific size or color is sold out, and the feed does not break it out. Sync availability at the variant level, not just the product level.
Treat availability as a real-time signal, not a weekly one. The cure is the same family of fixes as price: more frequent refresh, automatic item updates, and structured data that matches the feed.
How do automatic item updates and the price and availability attributes work?
Google gives you two tools that, used together, keep small drift from becoming a disapproval: the attributes themselves and automatic item updates.
price [price] and availability [availability] — These are the two attributes Google compares against the crawl. The price [price] attribute carries the base price under the correct tax rule with shipping excluded; the availability [availability] attribute carries in stock, out of stock, preorder or backorder. Get these two right at the source and most disapprovals never appear.
Automatic item updates — When the crawled price or availability differs from the feed, Google can update the item to match the page rather than disapprove it. This is a safety net for the timing gap: a sale on the page is honored even before your feed catches up. Enable it in Merchant Center settings.
Not a substitute for an accurate feed — Automatic item updates only correct small differences and only work well when your structured data is correct, because that is what Google reads. Turn it on, but still fix the feed-refresh frequency and the markup. The Q4 Shopping feed optimization guide shows how to harden the feed before a high-traffic season.
The price and availability mismatch diagnostic table
Work this table top to bottom — it is ordered by how fast each cause is to confirm and how often it is the real reason an item was disapproved for a price or availability mismatch.
Correcting only the price [price] value in the feed clears the error for a day, then the disapproval returns on the next crawl because the landing page and its structured data still carry the old number. Google trusts the page, not the feed. Align all 3 sources — feed, visible price, and structured data — and close the timing gap with frequent refresh and automatic item updates, or you will keep fixing the same item every week.
How to validate the fix and prevent re-disapproval
You will usually find more than one drifting item. The mistake is fixing them in a random order, or changing the price again mid-review so you cannot tell what worked. Rank by impact times ease and ship in sequence.
Validate in Diagnostics — After you align the three sources, open the Diagnostics page in Merchant Center and request a re-fetch or re-upload the feed. Re-approval usually follows the next crawl, often within a few hours to about 3 days. Do not change the price again while the item is under review.
Prevent the timing gap — Enable automatic item updates and increase feed-refresh frequency to match how often your prices and stock change. A store with flash sales should push changes through the Content API in near real time, not wait for a once-a-day scheduled fetch.
Keep structured data honest — Use the Rich Results Test to confirm the schema.org Product price and availability on every template match both the visible price and the feed. Wrong markup is the hidden cause that makes a correct feed keep getting disapproved.
Measure one change at a time. Re-check Diagnostics after each fix, not after all of them, so you know which lever cleared the disapproval. Size the cost of disapproved inventory before you scale with our wasted ad spend calculator, and to surface every feed and conversion leak automatically, run the SteerAds free 5-axis audit.
Sources
Official sources consulted for this guide:
-
support.google.com — price and availability requirements
-
support.google.com — product data specification
-
support.google.com — automatic item updates
-
support.google.com — about Merchant Center
FAQ
What does the 'Mismatched value (price)' error mean in Merchant Center?
It means the price [price] attribute in your feed does not match the price Google crawled on the product landing page or in its structured data. Google compares the two on a regular basis, and when the gap exceeds a small tolerance the item is disapproved. Roughly 1 in 3 price disapprovals trace to a feed that updated slower than the live site after a sale or price change. The fix is to align the feed value, the page price, and the structured-data price, then refresh the feed more often so the three stay in sync. Until all three agree, the product will not serve in Shopping.
Why does Google crawl my landing page if I already submit a feed?
Google crawls the landing page to verify that the price and availability you submit in the feed are the ones a shopper actually sees. The feed is your claim; the crawl is the check. Google reads the visible price, the structured data (schema.org Product markup), and microdata, then compares them to the price [price] and availability [availability] attributes. If they disagree, Google trusts the page over the feed and disapproves the item to protect shoppers from a bait-and-switch experience. This is why correct, current structured data on the page matters as much as a clean feed.
How do I fix a price mismatch caused by tax or shipping?
Make sure the feed price and the landing-page price use the same rules. The price [price] attribute must be the price before tax for most regions, or tax-inclusive where local law requires it, and it must never bundle shipping. If your page shows a tax-inclusive price but your feed submits the pre-tax figure, Google sees a mismatch. Set tax in the Merchant Center tax settings rather than inside the price, keep shipping in the shipping attribute, and confirm the structured-data price on the page reflects the same base price as the feed. Consistency across all three is what clears the error.
What is 'automatic item updates' and should I enable it?
Automatic item updates let Google correct small price and availability differences using what it crawls on your landing page, so a stale feed does not get the item disapproved while you fix the source. When the crawled price or availability differs from the feed, Google updates the item to match the page. It is a safety net, not a substitute for an accurate feed: enable it to reduce disapprovals, but still fix the feed-refresh frequency and structured data. Turn it on in Merchant Center settings, confirm your structured data is correct first, then keep your primary feed accurate.
How often should I refresh my Merchant Center feed?
Refresh as often as your prices and stock change. A store with static prices can use a daily scheduled fetch, but a store that runs flash sales or dynamic pricing should use the Content API or a supplemental feed to push changes in near real time. Most price and availability mismatches come from a feed that updates once a day while the live site changes hourly. Pair frequent refresh with automatic item updates and accurate structured data so the feed, the page, and the crawl never drift far enough apart to trigger a disapproval.
Is a price mismatch always my fault?
No. The most common cause is a timing gap rather than a wrong value — your feed and your site are both correct, but they updated at different moments. A sale goes live on the site at midnight while the feed still carries yesterday's price until the next scheduled fetch. Caching can also serve Google an old page even after you update. The point is not blame but synchronization: align the feed value, the visible page price, and the structured data, then close the timing gap with more frequent refresh and automatic item updates so the three never disagree.
How long does it take for a fixed item to be approved again?
After you correct the feed and the page, re-approval usually follows the next crawl and feed processing, often within a few hours to about three days. You can speed it up by requesting a re-fetch of the affected items or re-uploading the feed, then checking the Diagnostics page in Merchant Center. Do not change the price again mid-review, because each change restarts the comparison. Confirm the feed value, the visible price, and the structured-data price all agree before you resubmit, then monitor Diagnostics for a few days to be sure the disapproval does not return.