image.unloadable
Image URL could not be loaded. Level: Warning.
When it is raised
Raised when the image cannot be fetched for a reason other than an HTTP status, a non-image content type or a network failure. That is: the image's hostname, or the hostname of a redirect it follows, does not resolve in DNS; that host is one the API never fetches (localhost, a .localhost, .local or .internal name, or a name with any address that is private, loopback, link-local, carrier-grade NAT, multicast or reserved); or a redirect leads to a host on the API's fixed list of hosts it does not fetch. An image that is too large or is not an image does not raise this check.
What it does to a shared link
No image was received, so no image dimensions, size or crop are measured and the image checks that depend on a loaded image do not run. The robots.txt checks report nothing when the image's own host could not be fetched, since robots.txt is requested from that same host. They can still run when the failure came from a redirect target, if robots.txt on the image's own host returns 2xx or 404.
How to fix it
- Check the image hostname, and the hostname of any redirect it follows, for a typo and confirm it resolves in public DNS.
- Host the image on a public address; the API does not fetch development hosts such as localhost or an internal name.
- If the image URL redirects, point the tag at a publicly hosted copy of the file instead.