A product photograph can look fine on your website and still cause problems in Google Merchant Center. The submitted file might be a small thumbnail, an old promotional graphic or a photograph of the wrong colour. Replacing the picture in your shop is only part of the repair: you also need to check what your product integration sends to Google.
Start with the exact issue attached to the product. A quality warning, a forthcoming size requirement and a disapproval need different responses. This guide explains how to identify the fault, correct the source and check that the replacement has reached Merchant Center.
First, establish whether the product is actually disapproved
Open Products → Needs attention and inspect an affected item. Record its product ID, the issue wording, the submitted image URL and the affected marketing method. Google’s image-status guidance explains where to inspect the crawled thumbnail, last crawl timestamp and active warnings. Keep that evidence so you can compare it after the repair.
Do not treat every image flag as a reason to switch off advertising. Google’s current Low image quality guidance says that products with this particular issue continue to show in ads and free listings. Replace a blurry or pixelated photograph, but investigate other issues if the product is unavailable.
For a large catalogue, begin with commercially important products you can supply, then group affected items by the actual error. A shared fault across one supplier’s range calls for a different repair from a single incorrect photograph.
Check the exact image submitted for the exact variant
Open the image URL recorded in Merchant Center, rather than relying on your shop’s gallery. Compare it with the item a customer would receive. Check colour, pattern, material, finish and any personalisation. Then compare the product ID with the corresponding variant in your shop or feed.
Google’s image link specification calls for a dedicated image representing the distinguishing details of each variant. A group photograph of several colours is not a substitute for the single version being sold. It also distinguishes the main image_link from additional images used for other angles and details.
Imagine a retailer selling a lamp in brass and black. If both variants submit the brass photograph, uploading another black image to the gallery will not prove the problem is fixed. Check that the black variant actually sends that file as its main image. This is a hypothetical example, not a client result.
Remove added promotions without changing the product
A graphic prepared for a social campaign can be unsuitable as a main Shopping image. Google’s Text on image guidance prohibits promotional additions such as price callouts, delivery offers, calls to action and retailer watermarks. Its rules distinguish a logo physically present on the product from one superimposed afterwards.
Use the clean photographic master where you have it. Remove the added promotional layer at source and export a replacement. Do not erase real packaging details or reshape the item to make a warning disappear: the photograph still needs to represent what you sell.
Check how the wrong graphic entered the feed. Did a campaign image become the featured product photograph? Is an export template adding a shop logo? Correcting that route is more useful than repeatedly repairing individual listings.
Keep separate assets for separate jobs. Your advertising creative can have its own production process, while the main catalogue photograph remains a clear view of the product.
Separate today’s size limits from the January 2027 change
As checked on 30 October 2026, Google’s Image too small guidance says the existing minimums remain 100 × 100 pixels for non-clothing and 250 × 250 pixels for clothing until 31 January 2027. YouTube Shopping ads shown on TV already require at least 500 × 500 pixels.
Google’s 2026 product data specification update schedules enforcement of a 500 × 500 pixel minimum from 31 January 2027, across product categories and marketing methods. That change covers both main and additional image links. An upcoming-enforcement warning therefore deserves a planned fix, even when the product is currently eligible.
Measure the file at the submitted URL. A large original in your media library does not help if your integration sends a reduced thumbnail. Check width and height, rather than the apparent size on your monitor. For new exports, aim comfortably above the forthcoming minimum; Google’s image specification recommends around 1500 × 1500 pixels or above where possible.
Use a higher-resolution original or arrange new photography when detail is missing. Simply stretching a small photograph does not restore it. Choose an export that preserves the product’s shape and useful detail, then check the actual resulting file before processing the rest of the catalogue.
Make sure Google can retrieve an actual image file
For a broken-link or format issue, inspect the destination itself. Google’s broken image link guidance requires a supported image file and advises using the appropriate filename extension. Supported formats include JPEG, PNG and WebP. A product page, file-sharing preview or script response is not the replacement photograph Google needs.
Ask your developer or hosting provider to check the exact URL and response. It should return the intended image without requiring a login or browser challenge. Check image-host permissions and security rules, including access for Googlebot and Googlebot-Image. If a whole range failed after a hosting or CDN change, investigate that shared delivery route before commissioning new photography.
Test the published replacement while signed out. This is a useful first check, although a successful browser visit does not by itself prove that Google’s crawler can retrieve the file. Keep a record of any server error or access block for the person repairing it.
Decide whether automatic image improvements are appropriate
Merchant Center can attempt to remove promotional overlays automatically. Google’s automatic image improvements guidance says this setting is off by default and is available through the product Automations area. Successful processing can replace the submitted image, but it cannot fix every case. Dense watermarks, complex collages and text covering important product features can remain unresolved.
Review the actual result before relying on it across a catalogue. Check that the product, colour and important details remain accurate. If the result is unsuitable, supply a clean replacement. Treat automation as an option to evaluate, rather than a substitute for controlling your product-image source.
Repair the data source and test one complete update
Before editing hundreds of items, identify where each submitted image comes from: your shop, a feed-management tool, a supplier file or a manually maintained source. Record the old and replacement URLs against the product ID.
For an integrated shop, make the repair in the place responsible for sending the image and allow its normal update to run. Then inspect the submitted value again. If the old photograph returns, investigate the mapping or competing source instead of repeatedly making the same edit in Merchant Center.
Test one representative product from each fault group first. Include a variant where relevant. Confirm that its replacement is correct before applying the same repair more widely. Keep unrelated fields steady so that you can tell which change resolved the issue.
If a separate price or stock error remains, use our guide to Merchant Center price and availability mismatches. A repaired photograph does not resolve a different product-data problem.
Verify the replacement after Google processes it
Use a new filename and URL when the photograph itself changes, then keep that URL stable. Google’s broken-link guidance warns that replacing the bytes at an unchanged address can take up to six weeks to be detected and crawled. Avoid changing the address on every routine feed run.
Return to the product after processing and compare the submitted URL, crawled photograph, issue wording and eligibility with your original record. Google’s image-status guidance says new images are typically crawled and approved within three days; treat that as an expectation, not a guaranteed deadline. Repeatedly uploading the same file is not evidence of progress.
Close the task when the intended image survives another normal source update and the relevant issue has cleared. Eligibility allows a product to serve; it does not guarantee impressions, clicks or sales.
If you need help tracing the fault between your shop, product feed and advertising, BuzzBoost’s paid media service can support that review. Contact BuzzBoost with the affected product IDs and exact issue wording so we can discuss the right next step.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
