Google Merchant Center product disapproval warning for frequently changing prices

Google May Disapprove Products That Change Price or Stock Too Often

If you run flash sales or your inventory turns over quickly, Google just raised the stakes on keeping your product data honest. A quiet update to the Merchant Center help documentation says that products with frequent price or availability changes, for example more than once per day, may now be disapproved instead of updated when Google detects a mismatch.

For Shopify stores and any ecommerce merchant running intraday price changes, this is not a theoretical risk. A disapproved product does not rank a little lower on Google Shopping. It vanishes from the surface entirely, free listings included, until the mismatch is resolved.

Here is what the updated guidance actually says, in three parts:

  1. Automatic updates have a frequency limit. Google’s automations may not work for products with frequent price or availability value changes, giving more than once per day as the example threshold.
  2. A detected mismatch can mean disapproval, not a correction. If Google’s crawl finds the feed disagreeing with the landing page, the product may be disapproved instead of updated.
  3. Too many mismatches can shut off updates. Google may also stop applying updates to a product if the total number of detected mismatches becomes too large.

This hits some stores much harder than others:

  • Stores running flash sales where prices change during the day while the feed still shows the old figure.
  • Stores with fast-moving inventory where availability flips between in stock and out of stock repeatedly.
  • Stores using dynamic pricing or discount apps that display different prices to different visitors, because Google’s crawler may see a price your feed never sent.
  • Any merchant still uploading feeds manually while the website changes underneath them.

Failon’s POV: Feed hygiene is the unglamorous backbone of ecommerce SEO, and most merchants I look at have it backwards. They obsess over on-page tweaks while the product feed quietly rots, and then they wonder why Shopping visibility collapsed. Google is telling you plainly now that the feed is a promise, not plumbing. If the price on your page and the price in your feed disagree more than once a day, Google would rather remove the product than show a shopper the wrong number. I would rather have fewer, accurate products in the feed than a full catalogue that keeps tripping mismatch flags.

Here is what I would do about it this week:

  1. Open Merchant Center diagnostics and work the list top down. Price mismatches, availability mismatches, and landing page errors account for the bulk of disapprovals, so start there.
  2. Match your feed schedule to your pricing reality. If you run intraday promotions, either refresh the feed on the same cadence or hold prices steady through the day. Changing prices at noon on a feed that uploads at midnight is asking for a mismatch.
  3. Keep sale prices, sale dates, and availability identical everywhere. The feed, the landing page, and your structured data should all tell the same story at the same time.
  4. Turn on automatic item updates. Letting Google pull current price and availability directly from your site removes one layer where the two can drift apart.
  5. Audit discount and dynamic pricing apps for crawler-visible differences. Load your product pages the way Googlebot sees them and confirm the price matches what your feed declares.

None of this is complicated, which is exactly why it gets ignored. The stores that treat the feed as part of their SEO foundation will barely notice this change. The stores that treat it as an afterthought are about to find out what disapproval looks like at scale.

Failon Oben

Failon Oben

Organic Growth Strategist (SEO/GEO/AEO)

Search, Answer, and Generative Engine Optimization Specialist helping brands in ecommerce, B2B, SaaS, local, and international markets earn more organic traffic, more rankings, and more sales, and get cited by AI search.

Connect with me on LinkedIn
error: Content is protected !!