1. Home
  2. Products
  3. Social card preview
  4. API
  5. Checks
  6. images-differ.other-broken

images-differ.other-broken

Image in twitter:image is a different file and does not load. Level: Warning.

When it is raised

Raised when the page sets both og:image (or og:image:url) and twitter:image (or twitter:image:src), both resolve against the page's final URL, after redirects, to http or https URLs, the two URLs differ, and the og:image file loads as an image. The API also fetches the twitter:image URL, and raises the check when that fetch fails for any reason or returns a Content-Type that does not start with image/. Failures include a network error, a timeout, a hostname that does not resolve, a host or address the API does not fetch, a URL redirected 8 or more times, since the API follows at most 7 redirects (8 requests), a response that stops before any data arrives, and a non-2xx status.

What it does to a shared link

The og:image file, which every other image check measures, loads; the twitter:image file does not. Facebook, LinkedIn and WhatsApp document og:image as the image tag. X's Cards documentation, since withdrawn, described X reading twitter:image first and falling back to og:image, so by that description X would use the file that does not load. Slack documents reading both Open Graph and X Card metadata and publishes no precedence between them.

How to fix it

  1. If both files are meant to show the same picture, set twitter:image to the og:image URL; this clears the check.
  2. If the second picture is deliberate, open the twitter:image URL and make it return HTTP 200 with an image/png or image/jpeg Content-Type.
  3. Alternatively remove twitter:image. X's Cards documentation, since withdrawn, described X falling back to og:image when no twitter:image is set.
<meta property="og:image" content="https://example.com/card.png"> <meta name="twitter:image" content="https://example.com/card.png">

Related checks

Sources