Google's Image Warning Changed. Which Photos Should You Fix First?

Google now says a product flagged for low image quality will continue to show in ads and free listings. That changes how a lean ecommerce team should triage a Merchant Center warning. It does not mean that every image issue is harmless, that poor photography performs as well as clear photography, or that the separate minimum-size requirement has gone away.

The Merchant Center help page for low image quality now explicitly says the affected product will continue to show. Search Engine Roundtable documented the wording change in October, comparing the current page with an archived version that warned the product might be prevented from showing. This is a documentation change about one issue, not a promise about impressions, clicks or sales.

Which image warning should your team fix first?

Fix image issues that actually block serving before improving a low-quality image that remains eligible. In Merchant Center, separate products with a disapproval or a size problem from products carrying only the low-image-quality issue. Then rank the remaining quality work by product importance and customer experience. The same photograph can be eligible to show and still be a poor way to sell an item.

That distinction matters when a small catalog team sees hundreds of red or yellow diagnostics and treats them all as lost distribution. The issue label alone is not the operational decision. The product's current status, the applicable destination and the affected offers are.

Low quality and too small are different issues

Google describes low image quality as blurriness, pixelation or low resolution. Its updated guidance says products with this issue continue to show in ads and free listings, while recommending a better image because image quality correlates with engagement and clicks. Correlation is not a measured uplift for your products. Check your own performance before assigning a revenue figure to a photo replacement.

The image-too-small guidance is separate. Google says images must be at least 500 by 500 pixels for all products when the new requirement begins enforcement on January 31, 2027. Until then, the documented general minimum is 100 by 100 pixels for non-clothing and 250 by 250 for clothing, with a 500 by 500 requirement for YouTube Shopping ads on TV. Google also says it may serve an optimized version of some undersized images. Do not assume that option covers every product.

The practical consequence is a two-queue review. One queue protects eligibility and deadlines. The other improves how an eligible product looks to a shopper. Combining them obscures which work restores access and which work is an image-quality investment.

Run the review from affected offers, not the warning count

First, confirm the exact issue and destination

In Merchant Center, open Products, then Needs attention, and filter by the issue title. Export the affected items if there are too many to inspect one by one. Google's fix instructions describe that workflow for the low-image-quality issue. Preserve the item ID, destination and current product status in your working list so a quality warning does not get mistaken for a disapproval.

Spot-check several actual listings and landing pages. A Merchant Center diagnostic explains a Google Shopping issue. It does not establish that an image is accepted, displayed or chosen the same way in every AI assistant. Keep Google ads and free-listing status separate from any assessment of ChatGPT or other channels.

Next, protect the products that matter commercially

Start with seasonal hero products, high-intent collections and products receiving meaningful shopping impressions or clicks. Compare the current image with the item a buyer expects to see: color, variant, crop, sharpness and whether the product is easy to distinguish on a small card. The merchandising question is whether the photo helps someone choose, not merely whether the file passes a minimum rule.

If the issue affects a promoted product and a cleaner source photo already exists, replace the image at the source and let the feed update. If photography must be commissioned, decide whether the likely customer-experience value merits that work relative to a true disapproval elsewhere. Keep this a prioritization judgment, not a claim that replacing the photo will cause a particular lift.

Then verify the correction after the feed refreshes

Track the image URL and affected item IDs before changing anything. After the feed refresh, confirm that Merchant Center reflects the new image and revisit the diagnostic. Google's instructions warn that the Needs attention page may take time to update. Verify the actual product and destination status rather than declaring success when an upload returns without an error.

For a controlled set of important products, compare impressions and clicks over a sensible before-and-after window, noting promotions, price changes and seasonality. A clean photo may be worth making even when the warning never suppressed eligibility. But a changed image and a changed click count alone do not prove causation.

What can wait, and what cannot?

Do not pause a feed-wide eligibility repair to polish every eligible product photo. Work through true blocks first, then address the most commercially important low-quality images. At the same time, audit images below 500 by 500 pixels against the January 2027 enforcement date. A warning that currently leaves a product serving is not permission to ignore a later size rule.

Google's revised wording also calls for a cleaner weekly report to the ecommerce lead. Show disapproved offers, eligible offers with quality warnings, and image replacements completed as distinct numbers. If you monitor paid Shopping and free listings, keep their outcomes distinct as well. That makes the team accountable for restoring access without presenting every photo improvement as recovered distribution.

Paz's product feeds service helps a lean team prioritize Merchant Center data issues against selling priorities. A Paz expert traces supported issues to the customer's source information, makes corrections within approved guidelines, brings exceptions to the customer, and tracks what changed after the feed refresh. If your team needs help separating eligibility work from quality work, Talk to us.