Every few years Google changes a rule in Merchant Center quietly enough that most merchants find out when their products disappear. This is one of those.
From 31 January 2027, product images in Merchant Center must be at least 500 x 500 px. Products below that are disapproved and stop showing in Shopping ads and free listings. Merchant Center has been warning about it since July. If nobody in your organisation has opened the Needs attention tab since then, the warnings are sitting there waiting.
What is the new rule?
The minimum image size moves from 100 x 100 px (250 x 250 px for apparel) to 500 x 500 px for every category and every listing format. It applies to the main image and to additional images. Google separately recommends 1500 x 1500 px or larger for performance, and that is the number to aim for if you are replacing images anyway.
Why does this break products that work today?
Because the rule changes and the products do not. A product approved with a 350 px image in December is disapproved in February with the same feed, the same URL and the same file. There is no warning email on the day. The product simply stops being eligible.
That makes this different from most feed errors. Normally something breaks because something changed. Here, everything that is currently compliant with the old rule and below the new one will fail on a fixed date.
How do you find the affected products?
Log in to Merchant Center. Go to Products, then Needs attention, then View history. Look for the orange warning ”Image too small for upcoming enforcement” and click View fix, then Download impacted products. You get a CSV of every product at risk.
Sort it by supplier, brand or category. Undersized images almost never scatter randomly across a catalogue. They come from one import, one supplier feed or one era of product photography, and the fix is usually one conversation rather than 600.
Is it the images or the feed?
Usually the feed. This is the part worth reading twice.
Magento and WooCommerce both generate resized image caches for the storefront. Feed extensions and third-party feed tools frequently pick up those cached URLs instead of the original media file, because that is the URL the product page renders. The result is a store with 2000 px originals sending 300 px thumbnails to Google.
If that is your situation, the fix is a feed configuration change, not a photo shoot. It takes an afternoon and resolves most of the list at once. The remaining products, the ones where the original really is too small, are a much shorter list and can be handled with upscaling or new material.
What does a fix look like on Magento or WooCommerce?
On Magento, check which image role and cache path your feed extension uses and point it at the original media path. Confirm the image_link URLs in the generated feed resolve to full-size files. On WooCommerce, the equivalent is checking whether the feed plugin uses the full size registered image or a resized intermediate, and whether any image optimisation plugin is serving a downscaled variant to the feed URL.
In both cases, verify by opening ten image_link URLs from the live feed and reading the dimensions. If they are all above 500 px, the feed is fine and the remaining work is on individual products.
When should this be done?
Before the end of the year. Google needs to recrawl the images and re-approve the products, and a feed change in December competes with the busiest weeks of the year. October and November are the right months.
We are offering this as a fixed-scope job for our hosting and maintenance clients: export and analysis of the affected products, feed configuration fix, verification in Merchant Center, and a short action list for products that need new images. If you run Shopping ads on a Magento or WooCommerce store, get in touch and we will tell you within a day whether your feed is the problem.