Google Merchant Center disapproves products that break its rules, pulling them from your Shopping ads. The recovery panel inside All products collects every rejected product, explains the real reason for each rejection in plain language rather than Google's error code, and lets you fix and resubmit — turning a confusing error list into a simple to-do list.
Google Merchant Center disapprovals arrive as a list of codes against product IDs. The code rarely says what to change, the affected products are pulled from Shopping with no announcement, and the total only ever goes up until someone sits down with it.
Most merchants discover the problem as a drop in traffic rather than as a notification.
How it works
Every rejection in one queue
Disapprovals are pulled in and grouped by reason, so you see "94 products rejected for missing GTIN" rather than 94 separate errors.
The reason, in plain language
Each rejection is translated from Google’s code into what actually went wrong and which field to change, with severity attached so you know whether it is blocking the product or merely limiting it.
Fix from the same screen
The fix ladder starts with the cheapest option that works: a value FeedGraph already detected, then a pick from the values Google accepts for that field, then a single AI suggestion, then a bulk fix across the whole group.
Resubmit and watch it clear
Fixed products go back out on the next push, and the queue shrinks as Google re-approves them. Validation history tracks whether rejections are trending down over time.
What you get
- ✓Every disapproved product in one place, grouped by cause
- ✓Google’s error codes translated into the field to change
- ✓A cheapest-first fix ladder rather than an AI button on everything
- ✓The recovery queue inside All products, next to the catalogue it is about
- ✓Validation history, so you can see rejections falling rather than guess
- —It cannot overrule Google. FeedGraph fixes the product data and resubmits; whether the product is re-approved is Google’s decision, and some rejections are about your store or policy rather than your feed.
- —It needs a Merchant Center connection to read disapprovals. Without one there is nothing to recover.
- —Account-level suspensions are out of scope. This works on product-level disapprovals.
Questions
Does it fix rejections automatically?
No, and deliberately not. It groups them, explains them, and offers the cheapest fix that will work — but a person decides. Resubmitting products to Google is a platform write, so it also passes through the approval gate.
Why are my products disapproved when the data looks fine?
The most common causes are a missing identifier such as GTIN or MPN, a landing page that does not match the product, a price or availability mismatch between the feed and the page, or an image that breaks Google’s rules. The recovery queue names which of these applies per product rather than leaving you to guess.
See Google rejection recovery in use
More in Catalog quality
All features →All products
One searchable list of every product you sell — with tabs for what needs fixing, what you deleted, and what changed.
View feature →Needs fixing
A focused repair queue inside All products: every product with something missing or wrong, grouped by issue, fixable in bulk.
View feature →Quality rules
The built-in rulebook that checks every product against Google, Meta and ChatGPT Ads requirements before anything is exported.
View feature →Ready to try it?
FeedGraph is in early access. Apply to join and we'll onboard you personally — no credit card required.
Join early access