Key Takeaways
- A Google Merchant Center disapproval is rarely a one-product problem — the same feed mistake usually repeats across a whole category.
- Most disapprovals come from the data describing a product, not the product itself: GTINs, images, price/availability mismatches, and missing attributes.
- Fix the root cause at the feed level, not product by product, so the same disapproval doesn't spread or come back.
- A pattern of unresolved violations can escalate from individual disapprovals to a full account suspension that pauses every campaign.
- Checking your catalog against Google's validation rules before you upload turns a disapproval notice into a pre-flight checklist.
Why One Disapproval Costs You More Than One Sale
The moment Google Merchant Center disapproves a product, that item drops out of Shopping ads, free listings, and Performance Max. No impressions, no clicks, no revenue from that SKU until you fix it. For one product on a 5,000-SKU catalog, that might sound survivable. It usually isn’t, because Google Merchant Center disapprovals rarely show up one at a time.
A disapproval is almost never a one-product problem. It’s a feed problem wearing one product’s name. The same missing attribute or formatting mistake that flagged one item is usually repeated across a whole category, so a “12 products disapproved” notice this morning can read “340 products disapproved” by next week as Google recrawls the rest. Left alone, a pattern of violations can climb from individual product disapprovals to a full account suspension, which pauses every campaign you run at once.
So the job isn’t to clear today’s red flags. It’s to work out what triggered them and fix the root cause in the feed, so the same disapproval doesn’t quietly spread through the rest of your catalog.
The Google Merchant Center Disapprovals You’ll Actually See
Google checks every product against a long list of requirements, and most disapprovals trace back to a small set of repeat offenders. These are the ones that account for the bulk of paused products.
| Disapproval reason | What usually triggers it |
|---|---|
| Missing or invalid GTIN | No barcode/GTIN supplied, or a made-up number that fails validation |
| Image problems | Promotional text or logos overlaid on the image, a placeholder graphic, or an image below Google’s size minimum |
| Price mismatch | The price in your feed doesn’t match the price Google reads on your product page |
| Availability mismatch | Feed says “in stock” but the landing page shows sold out, or the reverse |
| Missing required attributes | A category needs color, size, age_group, or gender and the field is blank |
| Editorial / title issues | Promotional text in the title (“FREE SHIPPING!!!”), all caps, or gimmicky punctuation |
| Policy violation | The product, claim, or landing page trips a Shopping policy |
| Landing page mismatch | The destination URL is down, redirects, or shows a different product than the feed |
Look at how few of these are about the product itself. Almost all of them are about the data describing the product. That’s the good news: you can fix data without touching a single physical item.
How to Fix the Big Ones
The fixes below are ordered roughly by how often they pause campaigns. Work top to bottom and you’ll clear most of your disapprovals before you reach the bottom of the list.
Identifiers: GTIN, brand, and MPN
Missing unique product identifiers are the single most common reason apparel and branded goods get disapproved. If your product has a manufacturer barcode, supply it in the gtin field exactly as printed, with no spaces or dashes. For branded products that genuinely have no GTIN, supply brand and mpn together. Never invent a number to fill the field. Google validates GTINs against a real registry, and a fake one fails harder than a blank one.
Images
Google wants a clean product shot on a plain background. Strip any promotional overlays, watermarks, sale badges, or call-outs, since those are the most frequent image rejections. Replace placeholder or “image coming soon” graphics, and check that each image clears the minimum resolution (250 x 250 pixels for non-apparel, 500 x 500 for apparel, though bigger is always better). One compliant image clears the disapproval; several good images help you everywhere else.
Price and availability mismatches
This one frustrates merchants because the data was right when they uploaded it. Google compares your feed against the live landing page, so if your site shows a sale price your feed hasn’t caught up to, the product gets flagged. The fix is freshness: your feed and your storefront have to agree. A daily refresh used to be enough. With dynamic pricing and fast-moving stock, intraday updates are the safer standard now, and the same accuracy that clears the disapproval also stops you paying for clicks on items a shopper can’t actually buy.
Required attributes
Different categories demand different fields. Apparel needs color, size, age_group, and gender. Plenty of categories want material or pattern. When these are blank, Google either disapproves the item or quietly limits where it can show. Start with your highest-revenue SKUs, fill the required attributes for their category, then work down. A supplemental feed is the clean way to add these fields in bulk without editing your primary feed, so you fix the gap once and leave your source data untouched.
Editorial and policy
Keep titles factual: brand, product, key attributes, and none of the marketing shouting. Move “free shipping” and promotional language into the fields built for it. For policy disapprovals, read the specific reason Google gives, because these range from a fixable claim in your description to a genuinely restricted product. Don’t resubmit blindly. Repeated resubmissions of the same violation are exactly what tip an account toward suspension.
A disapproval isn’t a verdict on your product. It’s a gap in the data describing it, and gaps in data are fixable.
Stop Disapprovals From Coming Back
Clearing the current batch feels like the finish line. It’s the start. Merchants who stop living in the Merchant Center diagnostics tab tend to share a few habits.
They keep the feed fresh, because stale data is the root of most price and availability mismatches, and the closer your feed tracks your live store, the fewer surprises Google finds. They fix at the feed level rather than the product level. Correct the underlying data through a supplemental feed instead of editing items one by one, and the fix lands across every product with the same problem. And they check their own catalog before Google does, running it against the same validation rules Google enforces so a disapproval notice becomes a pre-flight checklist instead of a fire alarm.
That last habit is where tooling earns its keep. UCP Radar scans your existing Merchant Center feed against more than 50 GMC validation rules and scores every product, so you can see which items are at risk of disapproval and which field is the actual problem, before a campaign gets paused. The same enrichment that clears a disapproval also lifts the product’s UCP Score, which is what keeps you visible as AI shopping assistants start reading the same feed Google does.
Conclusion
Google Merchant Center disapprovals are rarely about the product and almost always about the data. Fix the GTIN, clean the image, get your price and stock in sync, and fill the attributes a category requires, and you clear most of what pauses Shopping campaigns. Make those fixes at the feed level rather than product by product, and they stay fixed. UCP Radar does that work in one pass, scoring your whole catalog against Google’s rules and generating a corrected supplemental feed, so the next disapproval notice is one you catch before Google ever sends it.
Frequently Asked Questions
Almost always because of the data describing the product, not the product itself. The common triggers are a missing or invalid GTIN, an image with promotional overlays or below the size minimum, a price or availability that doesn't match your landing page, a missing required attribute like color or size, or promotional text in the title. Each maps to a specific field you can fix in your feed.
Once you correct the data and Google recrawls the product, the disapproval usually clears within a few days. You can speed this up by requesting a re-review in Merchant Center after the fix is live in your feed and on your landing page. The key is that both your feed and your product page have to agree before you resubmit.
A single product disapproval won't, but a pattern of unresolved violations can. Repeatedly resubmitting products that still break the same rule is one of the fastest ways to escalate from individual disapprovals to an account-level suspension, which pauses every campaign at once. Fix the root cause before you resubmit.
A disapproval removes the product from Shopping ads and free listings until it's fixed. A warning means the product still shows but has a data issue that limits its reach or risks becoming a disapproval later. Both are worth fixing, but disapprovals cost you impressions immediately, so they come first.
No. A supplemental feed lets you add or override specific fields, such as missing attributes or corrected titles, without touching your primary feed. That's the cleaner approach because the fix applies across every product with the same problem and your original data source stays intact. Tools like UCP Radar generate this supplemental feed automatically.
