From 31 January 2027 Google Merchant Center requires product images of at least
500 × 500 pixels, for the main image (image_link) and for the additional images
(additional_image_link).
Merchant Center already shows the warning “Image too small for upcoming enforcement” on offers
whose images are smaller. Google may reject such an image or replace it with an enlarged copy.
A shop that has been adding products for years can have hundreds of such images and no way to see
them: WordPress shows every picture as a neat thumbnail. This plugin measures every image that goes
to Google and tells you which products need attention, and how much work each one is.
What it checks
The size is read from the image file itself, the full-size file that feeds send to Google.
A verdict for every product
Images under 100 × 100 px are marked separately: Google Merchant Center rejects those already today
(clothing: under 250 × 250 px).
Larger originals already on the server
Very often a small product image is a thumbnail — a file whose name ends in -300x300 — that was
uploaded or imported as an image of its own, while the full picture is still there. The plugin
looks for:
Where you see the result
wp merchlint-product-image-size-checker scan, with --export=file.csv for the fullIt never changes your products or images. It does not enlarge images and does not add frames:
an enlarged small picture gets bigger, not sharper. Every finding shows the size that was read, so
you can check the claim before you act on it.
The check runs in a single request, so on a very large catalogue it can run into your host’s time
limit — the screen says so when that becomes likely, and the WP-CLI command has no such limit.
This plugin comes from the author of Merchlint, a free
audit of the whole WooCommerce catalogue: products that sold in the past year and can no longer be
bought, products with no price or no photo, duplicate SKUs, sale prices that should have ended and
images with no alt text, each with the money at stake. This plugin carries its own copy of the
scanning engine with its own class names, so both can run side by side.