How to fix disapproved products in Merchant Center
A practical workflow for clearing product disapprovals in Google Merchant Center, reading Diagnostics properly, fixing the five most common causes, and requesting re-review.
Disapproved products aren't showing on Google at all, so this is always the first thing to fix. The workflow: read the exact reason in Diagnostics, fix the underlying data (not the symptom), resubmit, and wait for re-crawl. Most disapprovals come down to five causes, price/availability mismatch, identifier problems, image issues, missing shipping info, or policy trips.
Before anything: read the actual reason
Every disapproval in Diagnostics carries a specific reason string and, usually, an affected-attribute hint. Merchants lose weeks treating "product disapproved" as one problem: it's dozens of distinct problems with distinct fixes. The reason string is the diagnosis; start there.
The five causes behind most disapprovals
1. Price or availability mismatch
Google crawled your landing page and the price or stock state didn't match the feed. Root causes: slow feed refresh vs fast site changes, currency/tax display differences, or sale prices applied on-site but not in the feed. Fix by tightening feed refresh frequency and making sure price / sale_price mirror exactly what the crawler sees on the page. This one also drives account-level suspension if left to fester.
2. Identifier problems
Invalid GTINs (failed check digit), reused GTINs across variants, mismatched brand/GTIN pairs. See the identifier guide: and validate at the feed layer so bad numbers never reach Google.
3. Image issues
Placeholder images, promotional text overlaid on images, images that 404 or time out on crawl, or generic images shared across distinct products. The fix is a compliant primary image per product; watch for image CDNs that block Google's crawler.
4. Missing or contradictory shipping / tax
Products in a country with no shipping configuration, or feed-level shipping overrides contradicting account settings. Configure shipping at account level in Merchant Center unless per-product rates genuinely differ.
5. Policy trips
Restricted-category terms in titles/descriptions, misrepresentation flags, unsupported claims. These need a copy fix and then an explicit Request review.
Deep dive Working the queue at catalog scale
At catalog scale, disapprovals are a pipeline problem, not an incident. The durable setup:
- Fix upstream of Merchant Center. Whatever generates your feed should validate identifiers, image URLs and required attributes before submission. A feed layer that catches a bad GTIN pre-submit costs you nothing; the same GTIN caught by Google costs a disapproval, a crawl cycle, and sometimes a warning that suppresses siblings.
- Watch trends, not counts. A stable 2% disapproval rate is business as usual; a step change after a data import is an event worth tracing to its commit. /tools change monitoring exists for exactly this: score movement plus a change log pinpointing what changed and when.
- Pre-empt where possible. Disapproval prediction in /tools flags products matching known disapproval patterns before Google acts, so the fix lands before impressions are lost. See Feed Health Score explained.
- Respect the re-review budget. Policy re-reviews that fail add escalating cooldowns. Verify the fix is live (crawl the landing page yourself) before clicking Request review.
Step by step
- Open Diagnostics and filter to item-level issues. In Merchant Center go to Products → Diagnostics → Item issues. Ignore the account-level tab for now unless the whole account is suspended.
- Group by issue, not by product. Sort the issue list by affected-item count. Fixing one root cause usually clears hundreds of products; fixing product-by-product wastes the day.
- Identify whether the fix belongs in the data or on the site. Data issues (identifiers, missing attributes) are fixed in your feed. Site issues (price mismatch, availability mismatch, checkout problems) are fixed on your store, the feed just has to agree with the landing page.
- Fix the underlying data and resync your feed. Make the fix at the source (or in your enrichment layer), then push an updated feed. Don't hand-edit individual products in Merchant Center, the next feed fetch overwrites manual edits.
- Wait for re-crawl, or request a re-review for policy issues. Data fixes clear automatically on the next fetch and crawl (up to 72 hours). Policy disapprovals show a "Request review" button once fixed, use it, but only after the fix is genuinely live, as failed reviews add cooldown time.
Frequently asked questions
How long until a fixed product shows again?
Data fixes typically clear within 24–72 hours of the next feed fetch. Policy re-reviews take up to 7 days. Nothing you can click makes the crawl instant.
What's "preemptive item disapproval"?
Google disapproving items for a predicted policy problem (usually price or availability accuracy) before a shopper ever saw the mismatch, commonly triggered when your feed updates much less often than your site changes prices or stock.
Should I just delete disapproved products from the feed?
Only if you genuinely don't want to advertise them. Deleting hides the symptom and shrinks your coverage; the disapproval reason usually points at a fixable data problem affecting other products too.