
You open Merchant Center and see “Promotional overlay on image”, “Image too small” or “Unable to show image” next to a row of products. Those items have dropped out of Shopping ads and free listings, often right before a payday or 11.11 campaign.
A Merchant Center image rejected message is an item-level problem, not an account ban. This guide explains each message, ranks the usual causes, walks through the fix with menu paths from Google’s help centre, and gives honest timelines. If you are still setting up, start with our guide to setting up Google Merchant Center in Malaysia. If your worry is photos ranking in Google Images rather than feed approval, see our guide to images not ranking on Google.
Google’s own short video below sums up the image rules Merchant Center checks against.
Source video: Watch on YouTube (Google Ads)
Quick Answer: Google rejects a product image when it breaks the image_link rules. That means text, logos or badges added on top of the photo; a file Google cannot download; an image below the size minimum; or a placeholder instead of the real product. The exact message in Needs attention tells you which rule failed, and each one needs a different fix.
Google’s image link [image_link] specification is the rulebook. It bans promotional overlays, watermarks, added logos, barcodes, borders, placeholders and generic graphics on the main image. Here is how the common messages map to causes and first fixes:
| Message you see | What it means | First fix |
|---|---|---|
| Promotional overlay on image [image_link] | Text, badge, logo or watermark added to the photo | Automatic image improvements, or a clean photo |
| Image too small [image_link] | Below the pixel minimum, often a thumbnail | Send the original high-resolution file |
| Unable to show image | Google could not fetch the file | Check robots.txt, firewall and that the URL loads publicly |
| Processing failed [image_link] | URL leads to a web page, redirect or broken file | Link straight to the image file on a new URL |
| Unsupported image type | File extension does not match the real format | Save as JPEG or WebP with the matching extension |
| Placeholder or generic image | Store logo, icon or “coming soon” graphic | Photograph the actual item |
Source: ZenWeb summary of Google Merchant Center Help pages on image_link, image too small, unable to show image and image processing, checked October 2026.
Read the issue column first. An overlay is fixed in the photo; a fetch problem is fixed on your server. For price, availability or landing-page errors, see our guide to products disapproved in Merchant Center .
Hundreds of products stuck on image issues?
We audit the feed and the photos together, so Shopping campaigns keep running while images are replaced. See how ZenWeb manages Google Shopping and Merchant Center →
Quick Answer: In Malaysian shops, promotional overlays cause the most rejections, usually marketplace-style stickers like “Free Shipping”, “COD” or a price tag. Next come images Google cannot reach because a firewall or robots.txt blocks it, then thumbnails sent instead of full-size photos. Placeholders, collages and wrong file types make up the rest.
Here is how the causes ranked across Merchant Center feeds we have reviewed:
| Root cause | Share of rejected images |
|---|---|
| Promotional overlay (badge, price, logo, watermark) | 38% |
| Image URL blocked or unreachable | 21% |
| Thumbnail sent, image too small | 16% |
| Placeholder or store logo instead of product | 12% |
| Collage, border or extra products in frame | 8% |
| Wrong file type or mismatched extension | 5% |
Source: From ZenWeb client tracking across Malaysian SME Merchant Center feeds, 2024–2026. Illustrative of typical patterns, not a Google statistic.
What each cause looks like in practice:
Quick Answer: Google wants a clear photo of the product you sell, with nothing added on top. Use JPEG or WebP, keep files under 16MB and 64 megapixels, and aim for about 1500 x 1500 pixels. Google has announced a 500 x 500 pixel minimum for all products from 31 January 2027, so treat 500 pixels as your floor now.
The “Image too small” help page lists today’s minimums as 100 x 100 pixels, or 250 x 250 pixels for apparel. Images under 500 x 500 already show an “Image too small for upcoming enforcement” warning. Here is how common Malaysian shop habits compare with the rules:
| Habit | Allowed on main image? | Do this instead |
|---|---|---|
| “Free Shipping”, “COD” or “Ready Stock” sticker | No | Set shipping in Merchant Center |
| Price tag or “-50%” badge | No | Use the price and sale_price attributes |
| Shop logo watermark against copying | No | Keep a clean master file for the feed |
| WhatsApp number or QR code on photo | No | Put contact details on the landing page |
| All colours in one collage | Risky | One photo per variant; extras in additional_image_link |
| Clean photo on plain background, 1500 px | Yes | The safest main image |
Source: ZenWeb practice guide based on Google Merchant Center Help (image_link and Image too small), checked October 2026.
Move the message out of the photo. “Free shipping” belongs in your Merchant Center shipping settings, where Google can show it properly. If large photos slow your own site, compress them as our guide to heavy images slowing your site explains. Just keep the feed version at full size.
Quick Answer: Go to Products under Products & store, open Needs attention, filter by the image issue and download the affected list. Fix each image at the source: a clean photo for overlays, the full-size file for small images, or server access for fetch errors. Give every replaced image a new file name and URL, then re-upload the feed.
These steps follow Google’s help pages on “Unable to show image” and image processing delays, checked in October 2026:
Editing inside Merchant Center suits a handful of items (open the product, select Edit product, change the main image URL and save). If your feed comes from WooCommerce, Shopify or a spreadsheet, the next sync can overwrite that edit, so fix the shop platform too. The same workflow clears the missing GTIN error in Merchant Center.
Quick Answer: Yes, for promotional overlay rejections it is the fastest first step. When switched on, Merchant Center tries to remove text, watermarks, overlays and logos and swap in the cleaned image. It is off by default, it cannot fix every photo, and it does nothing for blocked, small or placeholder images.
Google’s page on automatic image improvements gives the current path: Products & store, then Products, then the Automations tab, then the image improvements setting, View details, and switch it on. Weigh it up like this:
| Works well for | Does not help with |
|---|---|
| Small corner badges and stickers | Heavy text over the product itself |
| Light shop-logo watermarks | Dense, repeated watermarks and collages |
| Buying time on a large catalogue | Blocked URLs, small files and placeholders |
Check the result, then fix the source anyway. Improved images show as “Improved image quality [image_link]” in Needs attention. The cleaned copy only lives in Google, so the same overlay can still trip a Facebook catalogue that is not syncing or a WhatsApp catalogue waiting for approval.
Sale season coming and products still disapproved?
Our Google Ads team can prioritise your best sellers, fix their images first and keep Shopping spend on approved items. Get a Merchant Center health check from ZenWeb →
Quick Answer: With a new image URL, Google typically recrawls the image within three days, and Needs attention updates within 24 to 72 hours of the data change. Large batches can take up to 30 days. If you replace the photo but keep the same URL, Google’s help pages say detection can take weeks.
Here are the timelines Google states across its help pages:
| Stage | Typical | Upper limit |
|---|---|---|
| Needs attention refreshes after a data fix | 1–3 days | 3 days |
| Recrawl after a review request | 1–2 days | 7 days (account level) |
| New image URL crawled | 3 days | 30 days |
| Old image still showing | Varies | 30 days |
| Same URL, replaced photo | Weeks | 6 weeks |
Source: ZenWeb summary of Google Merchant Center Help pages (Image too small; Image processing delays; Unable to show image; Issues in Merchant Center), checked October 2026. Google’s pages quote three to six weeks for same-URL changes; the longer figure is shown.
Request a review only when you believe Google is wrong. A genuine fix clears on recrawl; Google’s Issues in Merchant Center page covers reviews. Nobody, including ZenWeb, can promise approval or a date. Once approved, check that products actually serve with our guides to Google Shopping ads not showing and free listings not showing on Google.
Quick Answer: Never show Google one image and shoppers another, never use a photo of a different or better product, and never open a new Merchant Center account to escape disapprovals. These shortcuts can turn a fixable item problem into a misrepresentation suspension, which is far harder to reverse.
The shortcuts we see most, and why they backfire:
Account-level trouble is a different problem. If repeated issues have led to a suspension, read our guide to a Merchant Center suspension for misrepresentation. The same clean-creative rule applies elsewhere, as our guide to a TikTok ad rejected shows.
Quick Answer: Keep two versions of every product photo: a clean master for Google and a marketing version for marketplaces and social posts. Map your feed to the clean, full-size file, keep image folders open to Googlebot-Image, and check Needs attention weekly, especially after adding products for a campaign.
Build these habits into how your team lists products:
Clean images get you shown; clear titles get you clicked. Once images pass, our guide to Google Shopping feed optimisation covers titles.
Quick Answer: Get help when a Merchant Center image rejected warning returns after every sync, when you cannot find what blocks Googlebot-Image, or when hundreds of products need new photos before a sale. We cannot override Google, but we can fix the feed and images at the source.
Escalate when any of these apply:
ZenWeb is a Google Partner agency that has worked with 500+ Malaysian businesses. Our Google Ads management service covers Merchant Center health, product images and Shopping campaigns as one job.
A Merchant Center image rejected message almost always traces back to the photo, the file or the server. Read the exact issue, fix the image at the source, give it a new URL and re-upload. Keep a clean master photo for every product and allow a few days before checking again. For more practical guides, visit the ZenWeb home page.
Your website allows sale badges, logos and stickers, but Google’s main product image rules do not. Google may also be unable to fetch the file if a firewall, plugin or robots.txt blocks Googlebot-Image, even though the image loads for you.
No. Shipping offers, prices and discounts on the image count as promotional overlays. Set shipping in Merchant Center and send discounts through the sale price attribute, so Google can show them properly.
Aim for about 1500 x 1500 pixels. Google has announced a 500 x 500 pixel minimum for all products from 31 January 2027, and files must stay under 16MB and 64 megapixels.
No. It only tries to remove text, watermarks, overlays and logos. It cannot fix blocked URLs, small files or placeholders, and some heavily edited photos cannot be cleaned without losing quality.
Usually not. A corrected image on a new URL clears once Google recrawls it, typically within about three days. Request a review only if you believe Google rejected a compliant image by mistake.
Cite this page: ZenWeb (2026). Product Images Rejected in Merchant Center? How to Fix Them. https://zenweb.my/blog/merchant-center-image-rejected/
You may quote our data with this credit and a link. See our Terms of Use.
Product images keeping your Shopping ads offline?
Send us your Needs attention export. We will find what is blocking each image, fix the feed at the source and get your products back in front of shoppers.
Get A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.