Skip to content

Public preview · Free feed checks are available. Paid reports and downloads are not available yet.

How to investigate inaccessible product image URLs

An image URL can look valid while returning an error, requiring authentication or blocking crawlers. Investigate the response and hosting settings, not just the text format.

Reviewed October 4, 2026 · Independent guidance · Manual/live investigation; not a performed scan check

What does this issue mean?

Google needs to retrieve product images. A 404, access restriction or an expiring link can prevent that retrieval even when a normal logged-in browser displays the asset. Image fetching also involves crawl rules, content type and sometimes redirects. A HEAD response alone may differ from the actual GET used to deliver an image.

Why this happens

CDN anti-hotlink rules, signed URL expiry, deleted media, cookie-based authorization and robot restrictions are common causes. Some hosts return a HTML challenge page with status 200, so the status code by itself is not proof of a usable image. Check the final response and ensure the URL remains stable long enough for scheduled feed processing.

How to diagnose and fix it

  1. Open the exact image URL without store login cookies and follow the complete redirect chain.
  2. Confirm the final response is the intended image and that the server permits the relevant Google crawlers.
  3. Replace expired or private links with stable public media URLs through your media integration.
  4. Resubmit the source change and review Merchant Center after the image is recrawled.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

GET https://example.com/image.jpg → 404

After review

GET https://example.com/images/current-mug.jpg → image response

Feed Doctor does not run live image requests in this MVP. Its syntax check cannot certify reachability, image content or successful Google crawling. This guide provides a manual diagnostic workflow.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies image_link. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Scan your feed for this issue

Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Live page checks described above are not performed by this scanner.

Check My Feed

Frequently asked questions

Does this finding always mean my product is disapproved?

Feed Doctor does not run live image requests in this MVP. Its syntax check cannot certify reachability, image content or successful Google crawling. This guide provides a manual diagnostic workflow.

Can Feed Doctor fix image_link automatically?

This MVP does not run the live or account-level checks needed to establish this issue. It supplies static feed diagnostics and this manual investigation workflow.

Should I fix the exported file or my store?

Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.

Do I need to connect Google to scan a feed?

No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.

Related feed issues

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.