Google Merchant Center disapproved products: 7 Causes and fixes

If your products are disapproved in Google Merchant Center, they won't show in Shopping ads or free listings.

That means no impressions, no clicks, and no sales until you address the issue.

The fix depends on why your products were disapproved. This guide walks you through the most common causes of Google Merchant Center disapproved products, how to resolve them, and how to stop them from happening again.

Key takeaways

• Disapprovals happen at the item level or the account level. The fixes are different
• Most issues come from price mismatches, missing identifiers, image problems, or policy violations
• Fixing a disapproval means correcting the feed and, in some cases, the landing page too
• Prevention is mostly about keeping your feed data fresh, validated, and complete before it reaches Google

What disapproved means in Google Merchant Center

A disapproved product is one that Google has reviewed and decided can't be shown. It's removed from Google Shopping ads and free listings until the issue is resolved and Google reapproves it.

Item-level disapprovals vs. account-level enforcement

Item-level Merchant Center disapprovals happen when a specific product has a data issue, and only that product is affected. For example, the wrong price or missing the global trade item number (GTIN). All you need to do is fix the data, request a review, and you're back to selling.

Account-level enforcement is a different situation. If Google detects repeated policy violations or a pattern of misleading data, it can suspend your entire Merchant Center account. This affects every product you sell and takes significantly longer to resolve.

Warnings, preemptive item disapproval (PID), and suspensions: what's the difference?

Most account-level enforcements start with a warning consisting of an email and a Diagnostics flag, giving you time to fix the issue before anything goes dark. Your ads keep running while the clock is ticking.

If the problem is a price or availability mismatch, Google may issue a preemptive item disapproval (PID) instead. That means only the affected products get pulled, not your whole account. Everything else stays live.

Suspension is the last step. It kicks in if you don't fix things in time, or if the violation is serious enough to skip the warning entirely — things like selling prohibited products, hiding fees, or running a misleading return policy. At that point, your full catalog stops showing, and you'll need to go through a formal appeal to get reinstated.

How to find your disapproved products in the Merchant Center

To find your Google Merchant Center errors, follow these steps:

• Go to Google Merchant Center and open the Products tab
• Filter by Status: Disapproved to see all affected items
• Click into a product to see the specific disapproval reason and a link to the relevant

• For bulk issues, export the product report or use the Diagnostics tab for an overview by issue type

Once you know what you're dealing with, fixing it is usually straightforward. Here are the seven most common reasons products get disapproved and how to solve each.

7 Common reasons for disapproval and how to fix them

The majority of Google Merchant Center errors trace back to the same handful of issues. These include feed data that doesn't match your online store, missing product attributes, images that fall short of Google's requirements, or content that runs into policy restrictions. Once you know which issue you're dealing with, the path forward is usually clear.

1. Price or availability mismatch (feed vs. landing page)

This is one of the most common disapproval reasons. If the price in your feed doesn't match what's shown on the product page, Google will flag it as a preemptive item disapproval.

Things worth knowing:

• Out-of-stock products still need to show a price on the landing page
• If you sell in bulk quantities or with a minimum order, the feed price should reflect the total cost of the minimum purchasable amount, and that same figure should be visible on the page

Fix: Update your product feed to reflect the current price on the landing page. If you run frequent promotions, make sure your feed refreshes often enough to stay in sync.

Product feed tools like Channable let you automate feed updates so the price in your feed always matches your webshop.

💡 Read this guide to learn more about what it takes to create good-quality Google Shopping feeds.

2. Structured data conflicts (feed vs. schema.org markup)

If your product pages use schema.org markup, Google cross-checks it against your feed. Conflicting price, availability, or other attributes between the two will get a product flagged.

This one catches a lot of eCommerce teams off guard because the schema markup is often auto-generated by a CMS plugin that nobody watches closely.

Fix: Check your landing pages for structured data and make sure it matches your product feed. If your CMS generates schema automatically, confirm it's pulling live product data rather than cached or default values.

3. Missing or invalid product identifiers

Google uses GTINs, MPNs, and brand names to match your products to search queries. Missing or incorrect identifiers reduce visibility and, in many categories, cause outright disapproval.

A few common mistakes:

• Submitting an incorrect GTIN (which will get the product disapproved)
• Leaving the brand field blank instead of omitting it properly
• Filling in placeholder values like "N/A" or "Does not exist" for the brand

If your product genuinely has no GTIN — custom items, bundles, or vintage goods — the right move is to set identifier_exists to no and still provide whatever identifiers you do have.

Fix: Submit only GTINs you're certain are correct. When in doubt, leave the field out rather than guessing. For bundles, use the main product's identifiers. For products without a brand, leave the field empty — don't fill it with a placeholder.

4. Image issues

Google's image requirements are stricter than most people expect, and enforcement is getting tighter. As of January 2027, the minimum image size will increase to 500 x 500 pixels across all product categories.

Common reasons for disapproval: images that are too small, have watermarks or overlaid promotional text, placeholder images, generic product shots that don't accurately show what's being sold, and broken image URLs that return a 404.

Fix: Audit your image URLs for broken links and check all images meet the size requirements. Remove any watermarks or text overlays. Make sure Googlebot and Googlebot-image aren't blocked in your robots.txt from crawling your product pages and images — that's a surprisingly common cause of image load failures.

5. Missing apparel attributes (gender, size, color, age group)

For clothing and accessories, Google requires gender, size, color, and age group on top of the standard attributes. Missing any of these will result in the products being disapproved. This applies to both Shopping ads and free listings.

A few specifics:

• Color values must be text-based (not hex codes or numbers)
• If a product comes in multiple colors, list the primary one first
• Size should include all relevant dimensions in a single value — for example, "16/34 Tall" for a dress shirt
• For variants, each combination of size, color, and gender should be a separate item sharing the same item_group_id

Fix: With Channable, you can add the required attributes for all applicable products. If your source data is missing values, use the Mapping step to link existing fields and Rules to enrich or fill gaps before the feed goes out.

6. Policy violations and restricted product categories

Some product categories have eligibility requirements (alcohol, healthcare products, certain supplements), and others are outright prohibited. But Merchant Center disapprovals in this category aren't always about what you're selling. They can also come from how you're presenting the products. Promotional text in the title or description, all-caps formatting, or misleading product information can all trigger a policy flag.

Fix: Review Google's Shopping policies for your specific category and region. If you're selling restricted products, confirm you meet the eligibility criteria before submitting.

On the feed side, keep titles and descriptions factual and clean — no promotional language, no gimmicky formatting, and no information that isn't directly about the product.

7. Requesting a product review after fixing issues

Fixing the underlying issue doesn't automatically get your product back. Google doesn't recheck products on its own after you update your feed — you need to request a review.

Fix: In the Merchant Center, go to your affected product, confirm the issue is resolved, and request review. Item-level reviews typically take 1–3 business days.

Account-level suspensions take longer and require a formal appeal through the Merchant Center. Don't submit multiple appeals for the same issue — it doesn't speed things up and can actually slow your process down.

💡 If you're a Channable user connecting to Google Merchant Center for the first time, read this guide on the 10 most common Google Shopping errors and how to fix them.

How Channable helps you stay on top of disapprovals

Having read about all these potential issues, you may be feeling a little overwhelmed. Most Google Merchant Center disapproved products are avoidable with the right setup.

With Channable, the Rules step lets you clean and optimize your Google Shopping feed data before it goes live. Fill missing attributes, normalize values, fix formatting issues — all automatically, so your feed stays compliant without manual work every time something changes.

The Quality step catches what rules don't, such as empty fields, invalid identifiers, and non-unique IDs. It shows you exactly how many products are affected before that information reaches Google.

Give Channable a try for free