Product images in Merchant Center: what the feed needs
The [image_link] in your feed should point to a stable, full-size image of that exact product and variant, with no text, logo or border added. Feed image trouble usually starts with a template picking the wrong file, so fix that setting before you touch single products.
You run this check yourself
Our scanner can’t see inside your Google accounts, so this one’s on you. Work through the checklist below without running a scan.
What does Google Merchant Center require from product image links?
Each [image_link] has to point at a stable, full-size image of that exact product and variant, in a supported format. Google’s [image_link] page accepts JPEG, WebP, PNG, GIF, BMP and TIFF, and warns that a wrong file extension, like .jpg on a PNG, can cause “Unsupported image type” errors. The same page says no promotional elements or content covering the product, no scaled-up images or thumbnails, and a unique image showing the distinguishing details of each variant. When you replace an image, Google says it is best to submit a new, unique URL, because new content at the same URL can take up to six weeks to be picked up. Extra images under the minimum size don’t get the product disapproved; they just aren’t shown. Most of this starts with one bad template setting, not a hundred bad photos. So start with the image issues in Merchant Center’s Needs attention tab, and fix the feed template or app setting that picks the image size before touching single products.
Why this matters
The URL comes first. Google's [image_link] minimum requirements start with “Use a URL that points to an image in a supported file format.” The supported formats are JPEG, WebP, PNG, GIF, BMP and TIFF, and “Using incorrect file extensions (for example .jpg for a .png file) can lead to 'Unsupported image type' errors.” The best practices add “Use a stable URL: The URL that you include shouldn’t change unless your image moves or is replaced.”
Changing an image has its own etiquette. The same page says “it is best to submit a new, unique URL for the new image”, and warns that “If you update the image content but keep the same URL, it can take significantly longer (up to 6 weeks)”. The reverse trap is a platform move: the media library moves, the feed keeps the old links, and every image quietly breaks.
Then the image itself. “Don't use an image that contains promotional elements or content that covers the product.” “Don't scale up an image or submit a thumbnail.” For variants, “Submit a unique image that represents the distinguishing details of each variant.” Extra photos have a softer rule on size: “If you include images that are under the minimum size requirements, your product won’t be disapproved, but your images won’t be shown.”
Opening the image links you submit is a manual feed audit. StoreVerifier cannot read the submitted feed. The free scan flags a main product image served from a known stock-photo site; it does not flag an image for its size, so check that in the feed audit too. Overlays in detail: watermarks and promo overlays; size and content: product image size and quality.
Typical evidence
Four checks for an image before submission
Open the image URL yourself and check its status, dimensions, public accessibility and overlays before submitting it. StoreVerifier does not retrieve image_link values from a feed, and it does not flag an image for its size.
The public signals this check looks for:
A platform move changed the image paths and the feed still points at the old ones, which n…
A platform move changed the image paths and the feed still points at the old ones, which now return an error.
The feed sends a thumbnail, with “_small”, “200x200” or similar in the file name, instead …
The feed sends a thumbnail, with “_small”, “200x200” or similar in the file name, instead of the full-size file.
Image URLs carrying a timestamp or version number that changes on every export
Image URLs carrying a timestamp or version number that changes on every export.
A file named
A file named .jpg that is really a PNG or WebP.
Every variant row sends the same image, whatever the colour
Every variant row sends the same image, whatever the colour.
The main image carries a sale flash or watermark that a theme or app baked into the file
The main image carries a sale flash or watermark that a theme or app baked into the file.
What it looks like once it is right
The channel app is set to send the original image. Each variant row links to a full-size photo of that colour under a new URL, and the “SALE” message lives in the page design instead of the file.
Common mistakes
Common mistake
Self-check steps
Test every feed image URL before it reaches GMC
Open each image URL in an incognito window. Check that it loads, is full-size rather than a thumbnail, and meets the 800×800px minimum. This gives you a repeatable image check before upload.
Questions merchants ask
Why can't Merchant Center use my product image?
The usual reasons are a link that does not open an image, a file format that does not match its extension, an image below the size requirement, or promotional elements on the image. Google's [image_link] page lists the URL and image requirements, and the Needs attention tab names the issue for each product.
Should I change the image URL when I replace a product image?
Yes. Google's [image_link] best practices say it is best to submit a new, unique URL for a new image; keeping the same URL can take up to six weeks to be picked up.
What happens to additional images that are too small?
Google's [additional_image_link] page says the product is not disapproved, but images under the minimum size requirements are not shown. Send full-size files for the extra slots too.
Remediation
Risk signal
Similar cases
Sources
Last reviewed 29 Sep 2026.
That is one issue. The library documents 134.
The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.