image.http-error

Image URL returns an HTTP error. Level: Error.

When it is raised

Raised when the API's crawler requests the image, follows at most 7 redirects (8 requests), and ends on a response that is not 2xx and is not 401 or 403. Examples are 404, 410, 429, any other 4xx except 401 and 403, 5xx responses, and a 3xx response with no Location header; the message gives the status code. A 401 or 403 raises one of the image.refused-* checks instead.

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 still run when robots.txt on the image URL's host returns 2xx or 404.

How to fix it

  1. Open the image URL in a browser and confirm it returns the image with status 200.
  2. If it returns 404 or 410, publish the file at that path or change the tag to the image's current URL.
  3. If it returns 429 or 5xx, check the image host's rate limiting or server errors, then run the check again.
  4. If a redirect has no Location header, fix the redirect or point the tag at the final URL.
<meta property="og:image" content="https://example.com/card.png">

Related checks