Rabbot
Blog

Most Google Shopping disapprovals are mechanical. One of them can reopen on its own.

August 23, 2026

  • google-shopping
  • product-feed
  • disapprovals
  • shopify

You open Google Merchant Center this morning, the dashboard behind your Google Shopping listings, click into Diagnostics, the tab that lists every problem by product, and a chunk of your catalogue is sitting there with a warning icon next to it. Or you haven’t opened it yet, because you already have a feeling about what’s inside. Either way, the word next to your products is disapproved, and it reads like an accusation. It usually isn’t one.

The short version: almost every Google Shopping disapproval comes down to one of four mechanical reasons. Your feed, the file that tells Google and Meta what you sell and for how much, disagrees with your product page on price or stock. A product is missing the barcode number Google wants. A page trips a policy called Misrepresentation, which sounds far worse than it usually is. Or the page itself, not just the feed, breaks one of Google’s landing page rules, the requirements for the actual page a shopper reaches after clicking your ad. Three of those four are one-off fixes you make once and move on from. The fourth, the gap between what your feed says and what your store actually shows, is the one worth building a habit around, because it can reopen on its own weeks after you thought you’d closed it.

I’ve spent years on the SEO side of e-commerce, and Shopping feed reviews are some of the pickiest checks in retail. Once you see the pattern, none of it looks random. Think of it less like a courtroom and more like a trading standards officer, the local inspector who checks shops are pricing and describing things honestly, doing the rounds of a parade of shops, checking the price on the window sticker against the till, the barcode against the box, the claims on the sign against what’s actually for sale. Most shops pass without a second look. The ones that get pulled up almost always slipped on the same kind of thing, something on display stopped matching something out the back.

Start with the most common cause, because it’s also the one worth genuine attention. When the price or stock level in your feed stops matching what a shopper sees on your live product page, Google’s reviewers can pull the item pre-emptively, before the usual review even runs its course. Google’s own fix-it page for this exact error says reviewers found “price or availability mismatches between your product data and landing pages,” and that you should have had a warning email first, giving you a date to sort it before enforcement began. In practice the warning and the disapproval can feel like they land on the same morning, which is exactly the “I woke up and it was all gone” story every merchant running a live feed eventually tells.

This is the cause that keeps coming back, because your feed and your storefront are rarely edited by the same hand at the same moment. A price change in your Shopify admin should flow straight through. A stock sync from a supplier app might lag an hour, or a day, or quietly stop working after an update, and the two drift apart until Merchant Center notices for you.

The second cause is smaller, and much easier to fix. It’s the barcode. Google wants a GTIN on most products, a Global Trade Item Number, which is just the barcode number already printed on the box for anything you didn’t make yourself. Miss it, or type it wrong, and Google’s own page on product identifiers says the item may end up with limited visibility at best, disapproved outright at worst, when the category requires one and Shopify’s barcode field is empty. The one real trap is guessing. If you make the product yourself and there genuinely is no barcode, Google’s own guidance is to skip the GTIN, list your store name as the brand, and add an MPN, a manufacturer part number, that you choose yourself. What it won’t accept is a guess. Google’s own page puts it bluntly: “Don’t make up, guess, or include values from similar products.” An invented number just fails validation later anyway.

The third cause reads the scariest of the four, because of a policy called Misrepresentation. Google aims it at listings that lie, sellers posing as a different brand, stock that doesn’t exist, or attempts to grab a shopper’s card details under false pretences. Read the policy and the stated penalty is blunt. A confirmed violation gets your account suspended the moment Google finds it, no warning first.

That line is real, and it’s also mostly not about you. One Shopify seller of handmade jewellery described the flag on the Shopify community forum like this: “Google DISAPPROVED every single item in my store because they claim I am selling prescription medication when in reality I am selling handmade jewelry that I make myself!” In another thread, a reply pointed out that the same flag often traces back not to anything in your product data at all, but to a missing or out-of-date business address on file in Merchant Center, worth checking before you tear your feed apart looking for the real problem. The instant-suspension penalty is for confirmed bad actors. What most merchants are actually looking at is a trading standards officer working from a checklist and getting a detail wrong, not proof that they did something wrong.

The fourth cause is easy to forget, because it isn’t in the feed at all. It’s the page itself. Google reviews the actual page a shopper lands on too, separately from the data file. Its landing page rules ask for the basics (title, price, currency, and a working buy button, all visible on the page Google can crawl), and for out-of-stock items they get specific. The page has to say “sold out” or grey out the buy button, not leave a live “add to cart” sitting on something you can’t actually sell. Miss one of these on a page nobody’s touched in months, a theme update shifts the price display, an app injects a banner over the buy button, and the feed can be flawless while the page still fails on its own.

Here’s the part that actually calms most of this down. Google splits enforcement into layers, and a single disapproved product sits at the gentlest one. Google’s own policy overview says it enforces mainly by disapproving specific listings so they stop showing, with account-wide suspension reserved for repeat or serious violations. That makes disapproval Google’s mildest enforcement tool, well short of account suspension. A problem on one product usually stays a problem on one product. It doesn’t spread to your whole catalogue by itself. Fixing it isn’t a dead end either. Mark the issue resolved in Merchant Center and request a review. Google says that can take up to 7 business days, and once you’re approved, the product is eligible to show across Google within 24 hours.

Here’s what to keep from all this. Most disapprovals are mechanical, not personal, and Google’s own review process clears most of them within a matter of business days. The one worth a permanent spot on your worry list is the mismatch. It’s the only cause here that can come back after you’ve already fixed it once, and nothing pings you when it does.

That mismatch is the exact thing I built Rabbot to catch. It cross-checks your product feed against what your storefront actually shows (price, availability, the identifiers Shopping channels ask for), and flags the gap as disapproval risk before it’s the thing waiting for you in Diagnostics. The one-time feed cross-check is free forever, no card required. Running it every day from there, so a new gap gets caught the same day it opens, is the paid upgrade.

Sources