ItemlumeAssets & tasks / DECISION CHECK
Why can I see my product image while Google reports a broken image link?
Your browser may carry a session, cached file or access permission that Google does not have. Test the submitted image URL itself as a public resource. A working product page is insufficient evidence that its image is fetchable by a crawler.
Inspect the actual feed URL
Copy the current image_link value from the affected product or source record, not the image address you remember uploading. Record the final host, file path and any redirects. A preview URL, signed link or link to an HTML download screen can work for the editor and fail for a crawler. Confirm that the response is the intended image rather than a login page with a successful page status.
Use a fresh anonymous browser window and ask your technical colleague to inspect a normal request and the relevant server access log. This is a delivery diagnosis, not permission to disable authentication across your website. Private source photographs should stay private; publish only the approved delivery copy.
Distinguish the failure point
| Evidence | Possible cause to investigate | Bounded repair |
|---|---|---|
| 401 or login redirect | Private asset or authenticated download | Dedicated public delivery copy |
| 403 in relevant access logs | Host or WAF rule rejects access | Review the narrow image-path rule |
| 404 on submitted path | Moved file or incorrect source mapping | Correct the feed URL |
| 200 with HTML content | Page URL used as an image | Use the actual supported image asset |
| Works now; old error persists | Earlier fetch or processing state | Check crawl history before more edits |
These observations narrow an investigation; a 403 alone does not identify which security rule caused it. Do not expose account storage or allow unrestricted access merely to remove an error.
Run a small controlled repair
Suppose a fictional bag image is hosted at an expiring task download. Export the approved asset to the store’s ordinary public media hosting, update only the corresponding feed image URL, and retain the old value in your change record. Recheck the public resource and the platform’s subsequent fetch. Keep the product ID and factual attributes unchanged unless their own evidence requires a correction.
Close with delivery evidence
Record the submitted URL, public response type, inspection time and later Merchant Center status. Never include a signed URL containing a credential in a public help post. When access is fixed but an image policy issue remains, evaluate the fetched picture separately. Itemlume generation does not configure your CDN, feed connector or firewall. Use the linked Google documentation to check the destination’s current image requirements.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Is a storefront screenshot enough?
No. Check the directly submitted image resource.
Should I turn off my firewall?
Investigate the specific approved asset path with your administrator; avoid broad security changes.
Will changing the AI model repair a 403?
A model change does not change an external host’s access rules.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits