ToolSahla, Tools Sahla

My share image link starts with http:// rather than https://. Could that be why the picture does not show when the link is shared?

It can be. Some platforms and apps load only images served over a secure connection, and the builder accepts an http link with no warning, because it is well formed. If your server offers the image over https://, use that. Then check the other causes yourself, because the tool never opens the image.

Published · 3 min read

What the builder accepts and rejects

We tried an image link starting with http://cdn.example.com/a.jpg. The tags came out with no error and no warning, and the link was written into og:image and twitter:image as it was:

<meta property="og:image" content="http://cdn.example.com/a.jpg"> <meta name="twitter:image" content="http://cdn.example.com/a.jpg">

A link starting with ftp://, on the other hand, was rejected with a message that only http and https URLs are accepted. So the tool judges the form of the link, not whether it is secure or whether an image sits behind it.

How to tell if the image is available over https

  1. Copy the image link and change the start from http:// to https://.
  2. Open it in your browser. If the same picture appears, that is the link to use.
  3. If you get an error or a security warning, the image server does not serve it securely, and you need to upload the image somewhere that supports https, such as your store's media library.
  4. Paste the secure link into the Open Graph metadata builder in place of the old one and copy the tags again.

Other causes the tool cannot detect

The builder opens neither your page nor the image, so it cannot know whether the image exists or how large it is. These are common reasons a picture goes missing, each worth a check:

  • The link is wrong or the image was deleted: open it in a browser, and if nothing shows, that is the problem.
  • The file is very heavy: some platforms may skip large images. Lighten it in the Image compressor before uploading, and check the platform's documentation for any limits.
  • The server blocks its images from showing on other sites: if you turn on 'Load the image in the preview' and loading fails, this may be why, and a message says so instead of a fake picture.
  • An old preview is cached: the platform may have saved the card before you fixed the link. Some platforms offer an official inspection tool to fetch it again.

A note on loading the image in the preview

'Load the image in the preview' makes your browser request the image directly from its server, which sees your IP address like any visit. If it loads, that shows your browser could fetch it, not that every platform will. The preview is an illustration; the final word belongs to the platform itself.

Common questions

Why does the tool not warn about http links?

It checks only the form of the link: absolute, and starting with one of the two accepted schemes. It does not open it or judge its security.

Should the page URL be https too?

Yes, if your site runs on it. Use the address your site actually opens on in og:url.

I fixed the link and the image still does not show. Why?

Most likely the platform is still using the cached preview. Wait, or use the official inspection tool where one exists.