Google Merchant Center disapproved products: causes and fixes
UPDATED 6 MIN READBY THE SCENOX COMMERCE TEAM
SHORT ANSWER
Merchant Center disapproves products mainly for price or availability that differs from the landing page, missing identifiers such as GTIN, image problems like promotional overlays, missing shipping data, landing page errors and policy violations. Open Products, then Needs attention, fix the cause in the feed or site, and request a re-review. Rechecks typically take 24 to 48 hours.
ON THIS PAGE
A disapproved product is not shown in Shopping ads or free listings, so every one is lost visibility. The good news is that a handful of causes account for most disapprovals, and nearly all of them are fixed in the feed or on the product page. This guide lists the common ones, how to find them in Merchant Center, the fix for each, and how to stop them returning.
Find the problem first
In Merchant Center, go to Products under Products and store, then open the Needs attention tab. Per Google's help documentation, you can filter by impact, label, status, title or issue type, and download a CSV of everything affected. Open a single product and check its Needs attention section for the exact issues. Account-level problems appear in a banner at the top, and under the same tab through "View setup and policy issues".
Work from the issue that affects the most products. One fix at feed level, such as a missing shipping setting, can clear hundreds of items at once. Fixing products one by one while a systemic cause remains is the slowest route.
Issue, cause and fix
| Issue | Typical cause | Fix |
|---|---|---|
| Price mismatch (feed vs landing page) | Feed is stale, sale price live on site only, currency or tax shown differently, price changed by script | Sync the feed daily or more often; match the displayed price; use a sale price attribute with dates |
| Availability mismatch | Item sells out on site but feed says in stock | Update inventory automatically; send availability from the live platform |
| Missing GTIN or identifiers | Branded product without GTIN, wrong barcode, no brand or MPN | Add the manufacturer GTIN, brand and MPN; set identifier_exists to no only if none exists |
| Invalid GTIN | Typos, wrong length, internal codes | Check the barcode against the packaging or supplier data; remove made-up values |
| Image issues | Promotional overlay, watermark, placeholder, too small | Replace with a clean product image that meets size rules |
| Missing or invalid shipping | No shipping settings at account level, or the item has none for a target country | Configure shipping in Merchant Center for each target country |
| Landing page errors | Broken link, 404, redirect loop, blocked crawling, page requires login | Fix the URL; check robots.txt and bot protection allow Google's crawler |
| Misrepresentation | Missing contact details, unclear returns policy, unclear business info | Add clear business, returns and contact information on the site |
| Policy violations | Restricted or prohibited product, misleading claims | Remove or edit the product; read the specific policy cited |
The fixes in more detail
Price and availability mismatches
This is the most common one. Google compares the feed value with what its crawler finds on the page. A feed that updates once a day will mismatch whenever you run a flash sale or an item sells out in between. The fix is structural: schedule the feed to update more often than your prices change, or use an API or app that pushes updates when inventory or price changes.
Check what a crawler sees, not what you see. If your theme adds a market-specific price with JavaScript, or shows tax-inclusive prices to a visitor in one country and tax-exclusive to another, Google may read a different number from your feed.
Missing GTIN and identifiers
If a product has a manufacturer barcode, the feed should include it, along with brand and MPN. Do not invent a GTIN to clear the warning: wrong values create worse disapprovals than missing ones. For handmade, custom or own-brand products, set identifier_exists to no and keep the brand field filled in.
Image issues
The image requirements on Google's help page rule out promotional text, prices, logos, watermarks and borders on the main image, and also placeholder images such as "coming soon" graphics or one stand-in photo reused across different products. Replace the image with a clean shot of the product itself. Our product image requirements guide has the sizes and formats.
Shipping
If shipping is not configured for a target country, products there are disapproved. Set shipping at account level in Merchant Center for each country you sell to, and check that rates, delivery times and any free-shipping thresholds match the website.
Landing page errors
Open the product link from the feed in a private window. A 404, a login wall, a redirect chain or a page that serves an error to bots will each fail the check. If you use a bot-protection service, make sure Google's crawlers are allowed. After a migration or URL change, the feed link often still points at the old URL, which is why feeds should be rebuilt after any store migration.
Misrepresentation and policy
These are the serious ones. They are about trust in the business, not a single field. Check your site shows who you are, how to contact you, your returns and refund terms, and your payment and shipping information, and that product claims are accurate. Read the exact policy named in the issue and fix that, rather than guessing.
How long re-review takes
After your fixes are live, Google says that a small edit to the item or selecting Appeal starts a fresh crawl, and that this typically finishes within 24 to 48 hours. Some violations need extra verification or limit how many reviews you can request, so build in slack. Do not request repeated reviews without fixing the cause first.
Prevent disapprovals with a clean feed
Most disapprovals are preventable at the source. The checks we run before a feed goes live:
- Every product has a unique title, a working HTTPS link and a main image without text or watermarks.
- Price and availability in the feed are generated from the live store, not typed into a spreadsheet.
- GTIN, brand and MPN are populated where they exist, and verified.
- Shipping and returns are configured per country.
- Titles and descriptions are accurate to the product, with no promotional wording.
- The feed is re-tested after any theme, URL or app change.
A rules-based feed tool or a managed feed can enforce most of this automatically, but the underlying product data still has to be clean. That is a catalog problem as much as a feed problem.
When to do it yourself and when to hand it off
For a store with a few dozen products and one disapproval type, fixing it yourself is fine: follow the table, correct the data, request a review. Merchant Center's diagnostics are clear enough for that.
It makes sense to hand it off when thousands of items are disapproved for mixed reasons, your source data is messy, you sell across several countries, or you want ongoing monitoring. Our feed management service handles setup and clean-up: the AI engine does the volume, a person reviews every output, and you approve before anything goes live. We work through a staff or collaborator account you can remove, not your passwords. Feed and marketplace setup starts from ₹7,999 / $299 / £239 / A$449 per channel, with a fixed quote after we inspect your files, and turnaround starts from 48 hours for eligible projects; turnaround depends on scope, catalog complexity and the quality of the data and access we receive. You can request the free 10-product sample if the project is a fit.
