Product Image SEO and Merchant Center: What Google Actually Checks

A product listing with perfect on-page SEO can still get rejected from Google Shopping over something as simple as image dimensions or a watermark. Merchant Center’s image requirements are stricter and more specific than most WooCommerce store owners realize, and there’s a real deadline coming that’s worth planning around now rather than scrambling for later.

The current requirements, exactly as Google states them

Google’s official Merchant Center image specification sets a minimum of 100×100 pixels for most products, and a stricter 250×250 pixel minimum for apparel images specifically. The recommended size — what you should actually aim for, not just the bare minimum to be accepted — is 800×800 pixels or larger. Accepted formats are JPEG, PNG, WebP, GIF, and BMP/TIFF.

The rules that cause the most rejections aren’t about size at all — they’re about what’s in the image. Google explicitly disallows watermarks, promotional badges or text overlaid on the image, and logos placed over the product itself. A neutral background is recommended, and images that are primarily illustrations, placeholder graphics, or “coming soon” stand-ins for a real product photo get flagged. If you’ve ever had a Merchant Center listing rejected and couldn’t figure out why, a promotional “20% off” badge baked into the image itself is a very common, very avoidable cause.

A real deadline worth planning around

Google’s own Merchant Center documentation confirms that starting January 31, 2027, the minimum image size requirement increases to 500×500 pixels across all product categories — not just apparel. That’s a meaningful jump from the current 100×100 baseline, and while I couldn’t pin down the exact date Google first announced this change while researching, the effective date itself is stated directly on Google’s current spec page. If any of your product images are sitting near the current minimum rather than the recommended 800×800px, this is a good reason to fix that proactively rather than waiting until the requirement actually changes and listings start getting rejected.

The gap between “meets the current minimum” and “meets the recommended size” is exactly the gap that a future requirement change is likely to close. Building to the recommendation now avoids a scramble later.

Where WooCommerce stores typically fall short

In my experience looking at store setups, the recurring problems aren’t about knowing the rules — they’re about product photography workflows that predate anyone checking Merchant Center’s specific requirements:

Product photos shot for the website, not for feeds. A lot of WooCommerce product images are sized and cropped for how they look on the product page, without anyone checking whether the same file also satisfies Merchant Center’s minimums.
Marketing overlays baked directly into the image file — sale badges, “bestseller” ribbons, or brand logos stamped onto the photo rather than added as separate on-page elements. These look fine on your site and get your listing rejected in the feed.
Inconsistent backgrounds across a catalog — some products shot on white, others on a lifestyle background, without a consistent standard. This isn’t a hard rejection reason on its own, but it does affect how your listings look next to competitors’ in an actual Shopping results grid.
Feed image mismatches — the image URL in your product feed pointing to a different (often lower-resolution, or outdated) version of the image than what’s actually live on the product page. Google checks for this kind of mismatch, and it can trigger a manual review.

What to actually check in a WooCommerce catalog

Audit your primary product images against the 800×800px recommendation, not just the current 100×100/250×250 minimums — treat the minimum as a floor you never want to be near, not a target.
Search your product catalog for any images with baked-in text or badges and move that messaging to on-page elements (a genuine WooCommerce sale badge overlay, rendered by the theme, rather than part of the photo file) instead.
Confirm your product feed’s image URLs match what’s actually live on the product page — a feed pointing to a stale cached image is a surprisingly common, easy-to-miss cause of listing issues.
Standardize background treatment across at least your primary product image, even if secondary gallery images vary.

A note on how Merchant Center actually surfaces rejections

One detail that trips up a lot of store owners: Merchant Center’s disapproval notices don’t always arrive the moment an issue exists — they surface during scheduled feed processing, which means a batch of newly added products with an image problem can sit unflagged for longer than expected before the rejection actually shows up in your account. That lag makes it easy to assume a new product line is fine simply because nothing’s been flagged yet, when the real answer is that Google just hasn’t finished processing it. Checking the Diagnostics tab in Merchant Center directly after any bulk product upload, rather than waiting for a notification, closes that gap.

Lifestyle images and the secondary-gallery gray area

Google’s neutral-background recommendation applies most strictly to the primary product image feeding your Shopping listing, not necessarily to every image in a product’s full gallery — lifestyle shots showing a product in actual use are common and generally accepted as supplementary gallery images, even though they wouldn’t satisfy the primary-image guidance on their own. Confusing the two is a common source of unnecessary anxiety: you don’t need every single product photo shot on a plain background, you specifically need the one designated as your primary feed image to meet that standard, with more creative latitude available for the supporting images around it.

Why this is worth doing now rather than later

Merchant Center rejections tend to surface at the worst possible time — during a sale push, or right when a new product line launches — because nobody audited the image requirements until something actually got flagged. Given that Google has already published a concrete future increase in minimum image size, treating your current product photography as a one-time setup task rather than something to revisit is a bet that’s getting riskier, not safer, the longer it goes unchecked.