Google Merchant Center requires 500 x 500 px from January 2027
Google is raising the floor for product images in Merchant Center. From 31 January 2027, every main image and every additional image has to be at least 500 x 500 px. Anything smaller gets the product disapproved, which means it stops appearing in Shopping ads and free listings.
The date sounds far away. It is not. Merchant Center has been warning about affected images for months, and the fix usually involves three parties: whoever owns the images, whoever owns the feed, and whoever owns the platform. Getting all three moving takes longer than most merchants expect.
What exactly is Google changing?
Until now the minimum was 100 x 100 px for most categories and 250 x 250 px for apparel. From 31 January 2027 the minimum is 500 x 500 px for all categories and all listing formats, and it applies to both the image_link and additional_image_link attributes.
Treat 500 px as the line where products get rejected, not as a target. If you are going to touch your images anyway, aim well above it — we work to 1500 x 1500 px.
Will Google not fix it for me?
Partly, and it is worth knowing. Google says it will begin optimising some images smaller than 500 x 500, and that those optimised images will meet the requirement and keep the product approved without any action from you.
“Some” is doing a lot of work in that sentence. There is no list of which images qualify and no way to opt in. Treat it as a safety net, not as a plan.
Why will approved products suddenly get rejected?
This is the part that catches people out. A product that is approved today with a 300 x 300 px image will be disapproved in February with the same URL, the same file and the same product data. Nothing in your feed has to change for it to break. The only thing that changes is the rule.
You can see who is affected right now. In Merchant Center, open Needs attention and look for the warning “Image too small for upcoming enforcement”. From there you can download the impacted products as a CSV. That list is your scope.
Where does the problem usually sit?
In our experience it is rarely the original photography. Most stores have perfectly good 1500 or 2000 px product images in their media library. The problem is what the feed sends.
Product feeds are often built on cached, resized versions of images because that is what the storefront renders. A thumbnail URL ends up in the image_link column, Google fetches a 240 px file, and the product gets flagged even though the original is fine. The fix is in the feed configuration, not in the photo studio.
The second common cause is supplier data. Small images tend to cluster around one supplier, one brand or one import job. Sort the CSV by that dimension before you plan anything, because it turns a list of 800 products into three conversations.
How does HDL Commerce handle this?
HDL Commerce has a built-in PIM, so product images live on the product itself, and the web formats the storefront uses are generated from them rather than replacing them.
The Google feed is built with the same field selector as export, which means what the feed sends is a setting you can open and read, not something buried in a template. Completeness rules per channel decide which products reach a feed at all; a product that fails them stays as a draft in that channel with the gap visible in the list.
For merchants already on HDL Commerce, the practical work is to compare the affected-product export with what the PIM holds, and find the products where the original itself is too small. Those need new image material. For the rest, the question is which image the feed sends, and that is something we check with you in the feed configuration.
What should you do before the end of the year?
Three things, in this order:
- Export the impacted products from Merchant Center and group them by supplier or brand.
- Check what your feed actually sends by opening a handful of
image_linkURLs and reading their dimensions. - Fix the feed first, because it usually resolves most of the list, then handle the remaining products with new image material.
We recommend being finished before the Christmas freeze. Google’s crawl and re-approval take time, and January is not the month to discover a feed problem.
If you want us to look at your feed, get in touch. It is a small, fixed-scope job and we would rather do it in October than in February.
Forty-five minutes with someone who knows the platform, not a sales deck. The migration assessment is free.