Fixing Product Image Links Before Google's 500 x 500 Minimum Takes Effect

From January 31, 2027, Google Merchant Center requires every product image to be at least 500 x 500 pixels, and images below that stop being approved. Meta's catalog spec already sets the same floor. Most catalogs we see are not uniformly small. They carry a minority of bad rows: a thumbnail URL pasted in by an old import, a banner-style image with a price burned in, a placeholder shared by 300 SKUs.

This guide is for feed managers and e-commerce teams who own a catalog of a few hundred to a few hundred thousand SKUs. By the end you will have a repeatable audit that sorts every image URL into pass, warn or fail, a fix path for each failure cause, and a way to confirm the fix landed in Merchant Center before the deadline.

What the image rules actually say today

Google's image_link help page is the primary source. Meta's rules live in the catalog fields reference. The table compares the parts that cause most rejections.

Two details are easy to miss. First, Google requires the file extension to match the real format, otherwise you get an "Unsupported image type" error. Second, Google asks you to keep AI-generation metadata, such as the IPTC DigitalSourceType tag, on images made with generative AI. We cover that in our AI-generated images policy guide.

A note on dates. Sources disagree on when warnings for undersized images began appearing in the Needs attention tab, and Google's own help page does not give one date. Do not rely on a warning date. Check your own account, and treat January 31, 2027 as the hard line.

A feed teardown: five rows, five different failures

The rows below are an illustrative, constructed example, not client data. The shop and URLs are invented. The failure patterns are the ones we look for first in any audit.

Row SKU-1005 matters if you sell in Turkey or the Gulf. Google requires image URLs to be ASCII and RFC 3986 compliant, so a filename exported from a CMS with Turkish or Arabic characters needs percent-encoding or, better, a clean slug at the source. Rename the file rather than relying on encoding, because some downstream channels handle encoded Unicode inconsistently.

Step 1: Export every image URL and measure it

Do not audit from the Merchant Center UI alone. It only reports what Google has already processed. Audit the feed itself so you find the problems before any channel does.

1. Export every image_link and additional_image_link value, one row per URL, with the product id.
2. Request each URL and record the HTTP status, the Content-Type header, the Content-Length and the pixel dimensions. A script using an HTTP client and an image library does this in an afternoon, even for large catalogs.
3. Compare the extension to the real content type. A .jpg URL that returns image/webp is a row-level error.
4. Count how many products share the same image URL. Any URL used by more than a handful of unrelated products is a placeholder until proven otherwise.
5. Test the URLs as Googlebot would see them. Google requires Googlebot and Googlebot-image to be allowed in robots.txt, and changes there can take 24 to 48 hours to apply.

Step 2: Score each row pass, warn or fail

A simple rubric keeps the work prioritized. Fix fails first, then warns, and treat passes as done.

The 1500 px warn line is Google's own recommendation, not a disapproval threshold. We use it to order the work, not to block publishing.

Step 3: Fix each failure at its source

Undersized images

Never upscale a 300 px file to 500 px in a script. It passes the pixel check and still looks poor, and Google also flags a "Low image quality [image_link]" issue for blurry or pixelated images. Instead, find the master file. Most shops keep a high-resolution original in the CMS or a DAM and publish a thumbnail on the product page. Point the feed at the original.

Overlays and watermarks

Google's list of prohibited overlays covers calls to action, prices, shipping or warranty claims, promotional adjectives, barcodes and QR codes, watermarks, and added logos. Keep a clean version of every hero image. If your design team produces sale badges as flattened JPEGs, make them a separate asset, and use the badge version in ads, not in image_link.

Placeholders

A placeholder is worse than a missing image because it passes through the pipeline silently. If a product has no photo, take it out of the feed until it has one. Use a rule that excludes rows whose image URL matches your placeholder filename.

Format and URL hygiene

Fix extension mismatches at the file level, not by renaming. Give each image a stable URL without timestamps or session IDs, as Google asks. Percent-encode special characters, and keep each URL under 2,000 characters.

A rules layer such as Feed Rules can hold the exclusion logic and text cleanup. Pixel dimensions, overlays and format conversion have to be fixed in the image pipeline itself.

Step 4: Replace images without breaking caching

Meta states that a replaced image needs a different URL, or the change will not be recognized. Google asks for stable URLs. These fit together once you separate two cases. Keep the URL stable while the image is unchanged. When you swap in a new image, publish it under a new filename, for example 1001_v2.jpg, instead of overwriting 1001.jpg. This is our reading of both rules, so test it on a small batch first.

Step 5: Verify in Merchant Center

1. Resubmit the corrected feed or run a fetch.
2. In Merchant Center, open Products, then the Needs attention tab, and filter by the issue title, for example "Low image quality [image_link]".
3. Download the CSV of affected products and diff it against your fail list.
4. Recheck after the next processing cycle. Google notes updates can take time to disappear from the tab.

Where this method breaks down

Pixel checks do not see content. A 2000 x 2000 image can still carry a watermark or a "Buy now" banner, so a human or an image-classification step has to review the overlays. We also cannot tell you how Google will label every undersized image after January 31, 2027. Press coverage says such products are disapproved, while Google's help page describes warnings and mentions automatic optimisation for some images without specifying which. Read your own Diagnostics tab after the date.

This guide also does not replace an image pipeline. If you need bulk resizing, background cleanup or format conversion at scale, an image CDN or a DAM, or the image tooling in a larger feed suite, is the right place to do it. We have not tested those tools here and do not claim any of them handles every rule above. Feedance's own feature set does not include a pixel-level compliance checker as far as we document, so use the script above or your own tooling for that part.

Frequently asked questions

What is the minimum image size for Google Shopping?

At least 500 x 500 pixels for all products from January 31, 2027, according to Google's image_link help page. Google recommends 1500 x 1500 pixels or larger.

What happens to images smaller than 500 x 500 pixels?

Press coverage reports the products will no longer be approved or shown in Shopping or Ads. Google's help page also describes warnings in the Needs attention tab, so check your Diagnostics view.

Is the 500 x 500 rule the same on Meta?

Meta's catalog fields reference lists 500 x 500 pixels as the minimum, with a maximum file size of 8 MB and JPEG or PNG formats. Meta's limits differ from Google's on format and file size.

Can I use a sale badge on my main product image?

Not in image_link for Google. Promotional text, prices and calls to action are prohibited overlays. Put badges on ad creative, not on the feed image.

Should I put a placeholder image on products without photos?

No. Google prohibits text placeholders and shared stand-in images reused across distinct products. Remove those products from the feed until a real photo exists.

Why does my image show "Unsupported image type"?

Usually because the file extension does not match the real format, for example a WebP file named .jpg. Convert or rename the file so the extension matches.

Do I have to keep AI metadata on generated images?

Google states images created with generative AI must contain metadata indicating that. Do not strip the IPTC DigitalSourceType tag when you resize or compress.

Does the Needs attention warning mean my products are already disapproved?

Not for "Low image quality [image_link]". Google says the product keeps showing in ads and free listings while the issue is open, though better images may improve performance.

Check your feed before the deadline

Start by running your catalog through our free product feed audit tool. It scores data completeness, data quality and technical health. It is not a pixel-level image check, so use the measurement in Step 1 for dimensions.