Unable to Show Image in Merchant Center: How to Fix It

What this issue means

Merchant Center doesn't use your image directly from the feed; it fetches the file from your server. If that fetch fails or hasn't happened yet, the product can't show. Google's help page for this issue lists four main causes: slow crawling, images that aren't live or were recently changed, HTTP header problems, and robots.txt blocking.

New products are especially affected because crawling has a natural delay. A bulk upload of thousands of new images can take a while to process.

Why it happens

• robots.txt blocks image crawling. A rule like Disallow: /images/ or Disallow: /wp-content/uploads/ blocks Googlebot-Image. Staging-era rules left in place after launch are a classic cause.
• Server errors under load. If your server returns 500-type errors or times out while Google crawls many images at once, the fetch fails.
• Firewall or bot protection. Security plugins, Cloudflare bot rules, hotlink protection or geo-blocking can block Google's crawlers from image files.
• Broken or temporary URLs. Images deleted, moved during a theme change, or URLs that include session IDs or timestamps that change on each request.
• Redirects and scripts. Image URLs that redirect several times or go through a script instead of pointing directly to the file.
• Incorrect headers. Dynamically generated images with missing or wrong Content-Type or Content-Length headers can fail to cache. Google also advises against setting cache-control on these.
• Slow crawl rate. Google may be crawling your images more slowly than you're submitting them.

How to fix it

1. Test the image URL yourself. Copy an image_link from the affected list in Products > Needs attention and open it in a private browser window. It should load the image directly, with no login, redirect chain or HTML page. Test a few from different products.

2. Check robots.txt. Visit yourdomain.com/robots.txt and make sure image paths aren't disallowed. Google's help page gives an example that allows both crawlers: a User-agent: Googlebot group followed by an empty Disallow: line, and a User-agent: Googlebot-Image group followed by an empty Disallow: line. If you use a CDN on a separate domain for images, check that domain's robots.txt too.

3. Check your server and security settings.

   • Look at server logs for 5xx errors or timeouts on image requests.
   • In Cloudflare or a security plugin, make sure verified Google crawlers aren't challenged or blocked, and that hotlink protection allows Google.
   • If your hosting struggles with crawl spikes, consider moving images to a faster server or CDN.

4. Make URLs stable and direct. Remove changing query parameters (timestamps, session IDs) from image URLs, avoid script-based image delivery where possible, and URL-encode spaces and symbols (a space becomes %20).

5. Check headers on dynamic images. If images are generated on the fly, make sure the response includes the correct Content-Type (such as image/jpeg) and Content-Length.

6. Platform notes:

   • Shopify (Google & YouTube app): Shopify serves images from its own CDN, so robots.txt and server issues are rare. If this appears, check whether the product image was deleted or replaced, and whether a third-party app is rewriting image URLs. Re-saving the product media usually triggers a fresh sync.
   • WooCommerce: Check robots.txt for wp-content rules, security plugins (Wordfence, iThemes and others) that block bots, and image optimization or CDN plugins that rewrite URLs. Make sure the feed uses the final, public image URL.

7. Resubmit after fixing. Once the URLs are reachable, re-fetch your data source or let the store app resync. Google suggests pacing very large bulk image updates, for example about 10% of images per day.

How long until it's fixed

This is the slowest image issue to clear. Google says image crawling can take up to 30 days. With a new image URL, updates are typically processed within three days but can take longer, and changing an image while keeping the same URL can take up to six weeks to show. After you fix a blocking problem, give it at least several days before assuming something else is wrong, and check the Needs attention page for progress.

How to prevent it

• Review robots.txt after every site launch, migration or theme change.
• Whitelist Google's verified crawlers in your firewall and bot protection.
• Use stable, direct image URLs without session or timestamp parameters.
• Stagger large catalog uploads rather than pushing all new images at once.
• Monitor server errors during big product launches.

If you've checked everything and products still won't pick up images, a server or CDN configuration issue is usually hiding somewhere. Mercantads can diagnose crawl problems and fix the feed side; contact us or see our Merchant Center service. You can also test URLs with our product image checker.