How to fix every Google Merchant Center disapproval

A disapproved product in Google Merchant Center is worse than a bad ad. A bad ad spends money badly; a disapproved product can’t run at all, and if enough of your catalog is flagged, Google can suspend the whole account. Yet most disapprovals come from a handful of boring, fixable data problems, not policy violations.

Here’s the practical fix-list, ordered by how often they actually bite, with the real cause behind each one.

1. Missing or invalid GTIN

What you see: "Missing value [gtin]" or "Invalid value [gtin]."

GTINs (the barcode number behind most branded products) are how Google matches your item to the real-world product. Missing them is the single most common disapproval, and it also quietly suppresses the products that do run, because Google trusts them less.

Fix: Add the correct GTIN for every branded product. For genuinely GTIN-less items (handmade, custom, your own brand), set identifier_exists to false so Google stops expecting one. Don’t invent GTINs; a wrong one is worse than none.

2. Price mismatch

What you see: "Mismatched value (price)" or "Price and availability do not match."

Google crawls your landing page and compares it to your feed. If the feed says €119.99 and the page (after a coupon, currency, or tax difference) shows something else, the product is disapproved for the mismatch.

Fix: Make the feed price exactly match the price a shopper sees on the page, including currency and tax treatment. If you run sales, use the sale_price field properly rather than overwriting price, and make sure sale_price is genuinely lower than price, or Google ignores the sale annotation entirely.

3. Image problems

What you see: "Image too small," "Promotional overlay on image," "Generic image."

Google wants a clean product image. Watermarks, "SALE" badges, text overlays, or placeholder/no-image items all get flagged, and imageless products drag down the whole feed.

Fix: Use a real, high-resolution product image with no promotional overlay. Hold back products with no image until you have one, rather than shipping a placeholder that gets the item (and your feed) penalized.

4. Missing required attributes

What you see: "Missing value [brand]", "[color]", "[size]", "[age_group]", "[gender]."

Apparel and variant products need a specific set of attributes. Miss one and the variant is disapproved, even if everything else is perfect.

Fix: Fill the required attribute set for your category, consistently across every variant, not just the parent product. Color, size, age group, and gender are the usual culprits for clothing.

5. Incorrect or missing product category

What you see: Poor performance more than a hard disapproval, plus occasional policy flags.

Google has its own product taxonomy. If a product isn’t mapped to the right node, it shows for the wrong queries (wasting budget) or gets caught by category-specific policy rules.

Fix: Map each product to the correct google_product_category node. This is tedious by hand across a big catalog, which is exactly where automation earns its keep.

6. Policy disapprovals

What you see: "Misrepresentation," "Prohibited content," "Editorial issues" (e.g., ALL-CAPS titles, gimmicky punctuation).

Some of these are genuine policy matters. But a surprising number are editorial: shouting titles, excessive symbols, or claims the landing page doesn’t back up.

Fix: Use Title Case, drop the "!!!" and "★★★", and make sure every claim in the title and description is supported on the page. For genuine policy categories, read the specific policy; there’s no data shortcut.

The pattern behind all of these

Notice the theme: almost every disapproval is a data quality problem, not an advertising problem. Wrong, missing, or inconsistent product data. Which means the durable fix isn’t fixing them one by one after Google flags them, it’s keeping the feed clean before it’s submitted, and re-checking on every sync as your catalog changes.

That’s the difference between firefighting disapprovals every week and never seeing them.

Where to find the actual reason

Merchant Center tells you why, but not on the screen most people look at. The dashboard shows a count; the reason lives in the diagnostics.

Open Products, then All products, and filter to disapproved items. Each row carries its own issue. The more useful view is Diagnostics, which groups every disapproval by reason and gives you a count per reason. That grouping is the thing worth reading, because it turns “four hundred products are disapproved” into “one required attribute is missing across four hundred products”, which is a single fix rather than four hundred.

Two habits are worth building. Read the affected-item count next to each reason rather than the total, because one reason usually dominates. And check the date the issue first appeared: a reason that started on a specific day almost always traces to a feed change or a platform update on that day, which is faster to find than debugging the data.

What to fix first when everything is disapproved

The instinct is to start with the largest number. That is usually wrong, because the largest group is often the cheapest products.

Order the work by revenue at risk instead. A hundred disapproved accessories and ten disapproved bestsellers are not the same problem, and the ten will pay back the afternoon faster. Merchant Center will not rank the reasons this way for you; you have to join the disapproval list to your own sales data.

After that, prefer reasons that are systematic over reasons that are per-product. A missing required attribute across a whole category is one mapping change in the feed. A hundred individually wrong prices is a hundred conversations with whoever owns the pricing. Same count, very different afternoon.

This ordering is exactly what feed management is for: grading the catalog, grouping the findings by cause, and ranking them by what they actually cost you rather than by how many rows they touch. If you want to see where your own catalog stands before changing anything, the free feed analysis is read only and takes about two minutes.

Worth knowing separately: the same missing attributes that get a product disapproved here are what stop an assistant recommending it, and that surface gives you no diagnostics report at all. The feed behind agentic commerce raises the bar on exactly these fields.

How Verintra handles this for you

We built Verintra to catch exactly these issues before Google does. It runs your feed against 30+ health rules, turns the results into a prioritized, plain-language action list (critical first), and uses AI to fix titles, fill missing attributes, and map products to the right Google category. It then submits the clean feed straight to Merchant Center and re-checks on every sync, so a fix stays fixed.

The scan is free, and it gives you the same prioritized disapproval-and-warning list this post describes, on your real catalog.

Scan your feed free at verintra.com. See every issue holding your products back, ranked by impact, in about two minutes.