Start in Diagnostics, not in the feed editor
Merchant Center tells you what it thinks is wrong. Open the product or the Diagnostics view and write down the issue name, the number of affected items, and an example ID. Fix the cause, then let the feed refresh. Requesting a review before the data has changed just sends the same problem back in.
If the issue is an account-level misrepresentation suspension, stop here and use the misrepresentation guide. The steps below will not lift a store-trust suspension by themselves. If Shopping ads have zero impressions and products are approved, the campaign settings may be the problem instead — that is a different checklist.
Unique product identifiers: GTIN, brand and MPN
Google’s help article on unique product identifiers, and the GTIN attribute article, are the rules. The practical version is this:
- If the product has a real GTIN (the barcode issued for that item, including that size and colour), submit that exact number. Do not guess. Do not reuse a sibling product’s code. Do not use an internal SKU.
- If the product has a GTIN but you cannot find it, leave the attribute blank rather than inventing a value. Google notes that products which have an assigned GTIN but are submitted without one may have limited visibility. That is still better than a wrong GTIN, which can be disapproved.
- If the product has no GTIN — common with custom, handmade, or some private-label goods — do not submit a fake one. Do not put store-specific SKUs in the GTIN, brand or MPN fields.
- If you are the manufacturer and there is no official brand, Google’s identifier guidance says to use your store name as the brand, plus an MPN that uniquely identifies the product in your catalogue.
- Submit brand and MPN when they apply. They help Google understand the item, and in some cases they are expected alongside, or instead of, a GTIN.
- Each variant that has its own GTIN needs its own value. Two colours are not the same product for identifier purposes.
Google has a dedicated article for “Incorrect GTIN”: the number is a valid-looking GTIN, but it does not belong to this product. This often happens when a barcode is copied from a similar listing or from the wrong variant. Confirm the number on the manufacturer’s packaging or documentation, then update the feed. Do not “make up a close one”.
| Situation | What to submit | What not to submit |
|---|---|---|
| You have the manufacturer’s barcode for this exact variant | That GTIN, plus brand when you have it | A neighbour listing’s GTIN, or a number you generated |
| The product has a GTIN, but you cannot find it yet | Leave GTIN blank until you have the real one | A placeholder, SKU, or “best guess” |
| No GTIN exists (custom or some private label) | No GTIN. Brand + unique MPN when that guidance applies | A fabricated barcode “so it will approve” |
| You manufacture it and have no official brand | Store name as brand, plus a unique MPN you control | Someone else’s brand name |
Image problems that get products disapproved
The image_link attribute article is the specification for the main product image. Google also publishes a data-quality article that walks through common image violations such as generic placeholders, promotional overlays and images that are too small. Follow the requirement shown in your Diagnostics issue, and use the official attribute page as the current standard for what you submit.
- Use a real product photo of the item being sold. Logos, “no image available” placeholders and random lifestyle shots that barely include the product are the kind of generic images Google says will stay disapproved until you replace them.
- Keep the main image unobstructed. Promotional text, watermarks, sale badges and extra logos on the image are a common reason for disapproval. If you need a badge, put it on the landing page, not on the feed image.
- Meet the size and file rules. The current image_link help page asks for a main image of at least 500 × 500 pixels, recommends around 1,500 × 1,500 pixels where possible, and sets upper limits (including a 16 MB file size and a 64 megapixel cap). Do not upscale a tiny thumbnail and hope it passes.
- Make the URL crawlable. The image must be a single
httporhttpsURL, in a supported format, that Googlebot and Googlebot-Image can fetch. If your robots.txt blocks those user agents from the image path, the product can fail even when the photo looks fine to you. - Show the same variant the rest of the item data describes. A red product with a blue image is a mismatch, and mismatches are how you wander from “image issue” into broader trust problems.
Other data problems, and how to request a review
Price and availability must match the landing page. That mismatch is one of the issues Google lists in its data-quality disapproval article, and it is also a theme in misrepresentation reviews. If Diagnostics mentions price, tax, shipping or availability, fix the page and the feed together, then refresh.
After you change the data, give Merchant Center time to recrawl. When the new values are visible and the issue no longer applies, request a review from the place Merchant Center offers for that issue. Do not send a review that says “please approve” while the GTIN is still invented or the image still has a “50% OFF” banner on it.
Work in batches: identifiers first for the products that should already have GTINs, images second, then remaining attribute mismatches. A clean set of fifty products is more useful than a catalogue of two thousand still carrying placeholder photos.
FAQ
What if my product has no GTIN?
Do not invent one. Google’s identifier help says that if a product has no assigned GTIN, you should not submit a made-up value, and you should not put an internal SKU in the GTIN field. If you manufacture the item and have no official brand, the same help page describes using your store name as the brand and a unique MPN you control.
I submitted a GTIN and the product is still disapproved. Why?
A value that looks like a GTIN can still be the wrong GTIN, the wrong length, in a restricted prefix range, or reused from another product. Google has a specific 'Incorrect GTIN' help article for the case where the number is valid but belongs to something else. Check the manufacturer’s barcode, and do not copy a number from a similar listing.
Is this the same as a misrepresentation suspension?
No. A product disapproval is usually about that item’s data — identifiers, images, prices and so on. A misrepresentation suspension is a broader account or store-trust problem. Fix both if you have both, but do not treat this checklist as a substitute for the misrepresentation guide.
Google Merchant Center Setup 2026
The course covers business identity, website trust, shipping, feeds, approvals and launch readiness, which is the right place to go when you are setting the account up so these disapprovals happen less often. If the issue is already a store-level trust problem, use GMC Trust & Feed Operations as well as the misrepresentation guide.
[ Open the course ]