Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesPut a fully qualified image URL in og:image in the shared page’s delivered HTML <head>, allow crawlers to reach both the page and image, and check the result with the social platform’s sharing preview or debugger. Add og:image:alt describing the image. The Open Graph protocol does not set universal image dimensions, file formats, or size limits, so check the current requirements of each platform where the link will be shared.
Put the Open Graph tags in the delivered page head
Open Graph metadata belongs in the HTML document’s <head>. The protocol’s four required properties are og:title, og:type, og:image, and og:url. See the Open Graph protocol for the property definitions.
As an Amazon Associate I earn from qualifying purchases.
Use an absolute HTTPS URL for the image as a robust deployment choice. The protocol defines og:image as a URL and provides og:image:secure_url as an optional secure-URL field; it does not guarantee that every social platform accepts every URL arrangement.
<head>
<meta property="og:title" content="Example article title">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/article">
<meta property="og:image" content="https://example.com/images/article-share.jpg">
<meta property="og:image:alt" content="A person reading a map at a desk">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
</head>The sample width and height simply illustrate the optional fields; they are not universal recommendations. The protocol says that when a page specifies og:image, it should also specify og:image:alt. Write alt text that describes the image’s contents, not a caption or promotional message.
#1 Best Overall
Make the image reachable to the crawler
A correct tag is not enough if a social crawler cannot fetch the page or the image. Open the exact shared page and exact image URL in a public, unauthenticated context and confirm each resolves to the intended content. Look for login requirements, expired tokens, geographic restrictions, or human-only challenges that might block an automated request. This is practical troubleshooting: the protocol identifies an image URL but does not define a universal HTTP-status workflow for every platform.
Check robots.txt rules for both the page path and image path, including rules for the crawler’s user agent. RFC 9309 says crawlers must follow parseable rules when they successfully download the file. It also distinguishes unavailable files from unreachable ones: a 4xx response may be treated as unavailable, while a 5xx response or network error makes the file unreachable and calls for complete disallow under the RFC; crawler implementations may have additional details. Read RFC 9309 for the specification.
Robots rules are not a security boundary. As RFC 9309 puts it, “These rules are not a form of access authorization.” Do not use robots.txt to protect private images or other sensitive assets.
Check JavaScript-rendered pages and multiple image tags
Verify what the crawler can see
For a JavaScript application, inspect the raw HTML response for the shared URL or the rendered HTML available to the crawler. A tag inserted only after browser-side code runs may not be visible to every social crawler. Confirm that the delivered page contains the intended Open Graph properties before testing a preview.
Put the intended image first
If the page declares several og:image values, the protocol says the first conflicting value from top to bottom is preferred. Put the intended primary image first, followed immediately by its applicable structured properties—such as og:image:alt, og:image:type, og:image:width, or og:image:height—before declaring another og:image.
Debug a missing or stale link-preview image
- Inspect the shared page’s delivered HTML. Confirm that
og:imageis in the document head, its URL is fully qualified, and the value is the image you intend to show. - Fetch the exact image URL publicly. Make sure it loads as the intended image without authentication, an expiring link, a regional restriction, or an interactive challenge.
- Review crawler access rules. Check the applicable
robots.txtdirectives for both the page and image paths and the user agent involved. - Use the platform’s current official preview or sharing debugger. Inspect which image the platform parsed, whether it fetched that image, and whether the displayed result may be cached. Tool availability and cache-refresh behavior vary by platform.
- Retest after a correction. If the tags or access rules were wrong, fix the delivered page or image access and run the preview check again. A previously cached preview may not change immediately.
Do not assume one image specification works everywhere
The Open Graph protocol defines image metadata fields, including width and height, but it does not prescribe a universal set of accepted pixel dimensions, aspect ratios, formats, or byte limits across social services. Before choosing production image specifications, check the current official guidance for each destination platform. Compare its supported formats, preferred or minimum dimensions, maximum file size, crop behavior, crawler policy, and preview-cache behavior. These details can differ and change; a value that works on one service is not proof of compatibility with another.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need to generate or inspect the share image itself, ScreenshotNeo can return a website screenshot through one GET request. This does not replace adding and testing Open Graph metadata in the shared page.
Recommended Free Tools
For example, request an image of the page to use as a starting point for the social image:
Quick Recap
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before capture; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for free.
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.
