What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
og:image:secure_url is an optional Open Graph property for giving a page an HTTPS alternate image URL. Add it when your primary og:image is not HTTPS and you need an HTTPS version; if og:image already points to the HTTPS image, the protocol does not require a duplicate secure URL.
What og:image:secure_url does
The Open Graph protocol defines og:image:secure_url as “An alternate url to use if the webpage requires HTTPS.” It is a structured property that belongs to an og:image declaration. It is not one of Open Graph’s four required basic properties, and it is not a separate preview image in its own right. The Open Graph protocol
Use it when the primary image URL is HTTP but you can provide the same preview image at an HTTPS URL. If the primary og:image is already HTTPS, the specification does not say to repeat that URL in og:image:secure_url.
Add the HTTPS alternate to your page
Place the secure URL immediately after the image property it qualifies. This example follows the protocol’s example structure; the HTTP primary URL is illustrative, not a recommendation to use HTTP.
#1 Best Overall
<meta property="og:image" content="http://example.com/ogp.jpg" />
<meta property="og:image:secure_url" content="https://secure.example.com/ogp.jpg" />
<meta property="og:image:type" content="image/jpeg" />
<meta property="og:image:width" content="400" />
<meta property="og:image:height" content="300" />
<meta property="og:image:alt" content="A shiny red apple with a bite taken out" />Replace the example URLs and image details with the actual image used for your page. Keep the HTTPS alternate accessible to the services that read the page metadata.
Include alt text that describes the image
The protocol says that a page specifying og:image should also specify og:image:alt. Describe what the image contains, rather than writing a caption. In the example, “A shiny red apple with a bite taken out” describes the image contents.
Keep metadata grouped when you use multiple images
Open Graph represents multiple image values by repeating og:image. Put each image’s structured properties—such as og:image:secure_url, type, dimensions, and alt text—after the root og:image they describe and before the next og:image root tag.
Ordering matters: the protocol says the first value from top to bottom takes preference in conflicts. When another root image is encountered, the preceding image’s structured-property group is complete. A second image therefore needs its own adjacent properties where applicable; do not put all secure URLs or dimensions in a detached block after the image declarations.
Check whether the HTTPS alternate is needed
- Your
og:imageURL is already HTTPS: keep that image declaration; a duplicateog:image:secure_urlis not specified as necessary. - Your
og:imageURL is HTTP and you have an HTTPS version: add the HTTPS alternate directly after the correspondingog:image. - You declare several images: keep each image’s structured properties with its own root image, in the intended top-to-bottom preference order.
Validate the markup
After publishing the page, use Facebook Object Debugger, which the protocol identifies as Facebook’s official parser and debugger, to inspect Facebook’s interpretation of the markup. This does not establish how other platforms will display the preview or how their caches behave.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
To capture a rendered page programmatically while checking the result, you can use ScreenshotNeo. Its screenshot API accepts a page URL in one GET request; the example below uses the page you want to inspect. See the ScreenshotNeo API documentation for parameters.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; these steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
