Google Merchant Center disapproves a product when its feed data breaks a policy or misses a required attribute — an invalid or missing GTIN, no brand, promotional wording in the title, a price or stock mismatch, a bad image, or prohibited content. Most are feed-data problems you fix in Renable with a rule, a mapping, or a join, then publish.
How to work through a disapproval#
Google shows each disapproval with a reason attached to the product — the exact attribute or policy that failed. [VERIFY: the Merchant Center menu path where per-product disapproval reasons and diagnostics appear, and the exact wording of the reason labels.] Read that reason, match it to one of the causes below, and apply the Renable fix — then Publish so the change reaches your feed.
One thing to keep in mind throughout: Renable fixes your feed data; it doesn't clear the disapproval itself. Google re-reviews on its own schedule once it picks up your updated feed. So every fix below ends the same way — publish, let the next import run, and give the ad network time to re-review.
The product has a missing or invalid GTIN#
A GTIN is the barcode (EAN, UPC, or ISBN) that Google uses to match your product to its own catalog. Google flags a product when the GTIN is missing, or when it's present but invalid — most often because its check digit doesn't add up. [VERIFY: Google's exact reason labels for missing vs. invalid GTIN, and whether each is a disapproval or a warning.]
The Renable fix depends on which of the two it is:
- Invalid GTIN. Renable's own check catches only one kind of bad barcode: a value whose check digit doesn't add up. Such a value imports but is dropped before the feed reaches any ad network — so it arrives at Google as missing, not invalid, and you fix it exactly like a missing GTIN (below). A Google invalid-GTIN disapproval is a different thing: it's Google checking the barcode against its own product registry, and it fires on a number that's well-formed — its check digit is fine, so Renable passed it through untouched — but doesn't match the product Google has on record for it. Verify the barcode against the physical product or the manufacturer's GS1 record rather than assuming a typo, because a structurally valid number won't be a check-digit slip. See Feed runs, warnings, and tracing a value for how Renable's check-digit handling works.
- Missing GTIN. Map the identifier field if your feed has the value under a different column, or set it with a rule. If your main feed simply doesn't carry barcodes but a supplier feed does, pull them in with a lookup — see Joining another feed. The full walkthrough is in Add missing product identifiers.
The product is missing a required attribute#
Google rejects a product that's missing an attribute it requires. Every product needs the core set — an ID, title, description, link, price, availability, and image — and some categories require more: apparel, for example, typically needs color, size, age group, and gender, and most new products need a brand. [VERIFY: Google Merchant Center's current list of universally required attributes, the category-specific apparel requirements, and exactly when brand is required vs. recommended.]
Renable proactively flags only the gaps it treats as required — its seven required fields are ID, title, description, URL, main image, price, and availability. On the Mapping tab, the "{N} required missing" chip and per-row "N empty" warnings surface any of those seven that lack a value. Brand and the category-specific attributes (color, size, age group, gender) are recommended, not required in Renable, so they never appear in that chip or those warnings — you fill them with a mapping or a Set field rule and check how many products actually got a value with the Fill column. For the required-vs-recommended distinction, see Add missing product identifiers. To fix a gap either way:
- The value exists under another column — map that column onto the catalog field. See Mapping your feed to catalog fields.
- Your feed doesn't carry the value — write it with a Set field rule (for example, set a brand across a whole product line). See Fixing your feed data with rules.
- The attribute varies per variant (size, color) and your feed packs several variants into one row — Split into variants so each size or color becomes its own product with its own attributes. See Splitting variants into products.
If a field is mapped but comes back empty for only some products, that's a coverage gap rather than a missing mapping — see A field is empty or wrong.
The title contains promotional wording#
Google treats the product title as descriptive data, not ad copy, and disapproves titles that carry promotional wording — SALE, free shipping, superlatives, all-caps hype. [VERIFY: Google Merchant Center's title/promotional-text policy name and the exact wording it disapproves.] This is a whole job of its own: strip the wording across your entire catalog with a single Set field rule that rewrites the title, so new products stay clean on every import. The full walkthrough, including the value steps to use, is in Remove prohibited wording from product titles.
The price or availability doesn't match your store#
Google crawls your product's landing page and disapproves the product when the price or availability in your feed doesn't match what it finds on the page. [VERIFY: Google's exact reason labels for a price mismatch and an availability mismatch, and its tolerance for currency, tax, and rounding differences.]
This is almost always a mapping problem, not a policy one:
- Price mismatch — check that the Price field maps to the column holding the price your store actually charges, in the right currency and with tax handled the way your landing page shows it. A stale or wrong column reads as a mismatch even when your store is correct.
- Availability mismatch — a wrong or missing availability value reads as out-of-stock or in-stock incorrectly. Confirm the Availability field maps to your real stock column. If your main feed's stock is unreliable, pull live availability from a stock or supplier feed with a lookup — see Joining another feed.
For a deeper look at diagnosing wrong prices or stock, see Prices or stock look wrong.
The image is rejected#
Google disapproves a product whose image breaks its image policy — a promotional overlay (text, badges, or watermarks on the picture), a generic or placeholder image, an image that's too small, or a broken image link. [VERIFY: Google's exact image-policy reason labels and its minimum image dimensions.]
The Renable fix depends on the specific complaint:
- Broken or wrong image link — on the Mapping tab, confirm the Main image field maps to the column holding a real, reachable product photo, not a placeholder or a thumbnail. See Mapping your feed to catalog fields.
- Promotional overlay or watermark (text, a badge, or a logo burned onto the picture) — Renable can't strip an overlay off an existing photo, so the honest fix is a clean image. Point the Main image field at a clean product shot if your feed carries one under another column (see Mapping your feed to catalog fields), or generate a fresh lifestyle image to use instead (see Improve your product images).
- Low-quality or generic image — improve the underlying image with background removal or generated lifestyle imagery. See Improve your product images for what Renable can do with your product photos.
The product violates a content policy#
Some disapprovals aren't about a data field at all — Google restricts or prohibits certain products outright (for example counterfeit, dangerous, adult, or healthcare categories, and products it judges to misrepresent themselves). [VERIFY: Google Merchant Center's current prohibited and restricted content policy categories and their exact names.]
There are two paths, depending on the cause:
- The product genuinely can't be advertised — keep it out of your feed with an Exclude product rule, so it never reaches any channel or ad. See Fixing your feed data with rules.
- It's a data-quality or misrepresentation flag — correct the offending field (a misleading title, a wrong category, a missing attribute) using a mapping or a rule, then republish.
Account-level or policy-review issues are resolved in Merchant Center itself, not in your feed — Renable can only fix what lives in the product data.
FAQ#
Where do I see why a product was disapproved?
In Google Merchant Center, each disapproved product carries a reason naming the attribute or policy that failed. [VERIFY: the exact Merchant Center screen — products or diagnostics — where per-product reasons are listed.] Read that reason and match it to a cause above; the label tells you which field to fix.
I fixed the feed but the product is still disapproved — what now?
Publish the catalog so the fix goes live, then wait for the next import and channel regeneration. Google re-reviews feed changes on its own schedule after it picks up the updated feed, so a disapproval can linger briefly after you've corrected the data. Also confirm you fixed the field the channel actually exports.
Does Renable clear the disapproval for me?
No. Renable corrects your feed data; Google is the one that re-reviews and clears the disapproval once it reads your updated feed. Renable's job is to make sure the feed it receives is clean.
One product is disapproved but the rest of the category is fine — why?
That points at product-specific data — a bad barcode, a missing attribute, a wrong price on that one product. Trace the product to see exactly how each field resolved, or ask Aimée to diagnose it end to end.
Or ask Aimée#
Rather than working through the causes by hand, ask Aimée about a specific disapproved product. She can diagnose one product end to end — its import state, how each field resolved, and which rule or mapping decided each value — and surface the data-quality problems on it (a missing brand, an invalid barcode, an empty required field) so you can match them against the reason Google gave. She can then build the fix for you — a rule to set a missing brand, a mapping to correct a price, a lookup to pull in GTINs from a supplier feed — and publish once you approve. She can also search your catalog to find products missing a brand so you can fix them as a group, and wait for the next import to finish and report the results.
Related articles#
- Add missing product identifiers — GTIN, brand, and MPN.
- Remove prohibited wording from product titles — strip SALE, free shipping, and hype.
- Fixing your feed data with rules — conditions, actions, and value steps.
- A field is empty or wrong — when a mapped field comes back empty.
- Prices or stock look wrong — diagnosing price and availability problems.