Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsPut an og:image tag in your page’s HTML <head>, pointing to an image that anyone can fetch over the public web. Add the other core Open Graph tags—og:title, og:type and og:url—then test the page in the sharing inspector for the platform you care about. This gives social services a preferred image, but each crawler can apply its own rules, cache, cropping and fallback behavior.
The minimum metadata you need
The Open Graph protocol defines four basic properties for a page: og:title, og:type, og:image and og:url. A description is optional but generally useful. Put the tags in the document head, not in the visible body.
<head>
<meta property="og:title" content="A clear page title">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page">
<meta property="og:image" content="https://example.com/images/page-share.jpg">
<meta property="og:description" content="A short description of this page.">
<meta property="og:image:alt" content="A concise description of the preview image">
</head>Use an absolute URL for both the page and image. The image address should resolve without a login, expiring token, browser-only JavaScript or an internal network route. If you provide several og:image tags, the first one has preference when a conflict occurs, so put your intended default first.
How to add the tags
Static HTML
- Open the template that outputs your page’s
<head>. - Insert the Open Graph tags after the character-set and viewport declarations.
- Replace the example title, canonical URL and image URL with values for that specific page.
- Deploy, then fetch the raw HTML (view source, rather than only inspecting a rendered DOM) to confirm the tags are present in the server response.
Content-management systems
Most CMS platforms generate Open Graph fields through an SEO or social-sharing panel. Set a page-specific social image when the page needs one; otherwise configure a site-wide default. Check the generated source after publishing because a plugin can override your template, strip tags, or emit a relative image path. Do not place the image only in a CSS background or in client-side code that a crawler may not execute.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Images generated at build time
If your site creates images from a title or template, publish the finished file at a stable HTTPS URL before the page is shared. Keep the URL unchanged when possible. A crawler that receives a temporary 404, a redirect chain or an image requiring an authorization header may show no image even though the tag itself looks correct.
Choosing an image that survives platform processing
- Make it representative. Use an image that explains the page, rather than a generic site logo. Google’s guidance favors relevant, representative imagery and warns against extreme aspect ratios.
- Leave room for cropping. Social cards can crop edges and overlay a title, domain or controls. Keep essential text and faces away from the extreme edges.
- Use a high-resolution source. A large source gives a platform more pixels to work with, but it still must meet that platform’s file-size and format rules.
- Describe the image. Add
og:image:altfor a concise text alternative. This does not force every service to display the text, but it makes the metadata more useful. - Serve a normal web image. Return the correct image content type and a successful response to an unauthenticated request. Avoid a page of HTML masquerading as an image.
LinkedIn’s published limits
LinkedIn’s sharing guidance specifies a minimum of 1,200 × 627 pixels, a recommended 1.91:1 ratio and a maximum file size of 5 MB. Images narrower than 401 pixels are displayed as thumbnails. These are LinkedIn-specific values, not universal requirements for every social network, and LinkedIn’s help page carries an older update notice, so verify the current rules before designing a production template.
Why the image still may not appear
Open Graph metadata is a preference, not a guarantee. A platform may choose another image, apply a different crop, use its own page-understanding system, or retain an earlier result in its cache. Google’s image-selection guidance, for example, says its choice is automated even when metadata is present.
- The crawler cannot reach your page because of a firewall, robots policy, DNS problem, TLS error or server outage.
- The crawler can read the page but cannot fetch the image because it is protected, blocked, rate-limited or hosted behind a private network.
- The response is not the expected content: a redirect goes to a login page, the image returns an error, or a security layer serves a bot challenge.
- The tag is absent from the initial HTML, malformed, duplicated with an unwanted value, or points to a stale image.
- The platform has cached the previous card and has not revisited the URL yet.
A practical debugging checklist
- Inspect the source. Search the raw HTML head for all four basic properties and verify spelling, quotes and the exact image URL.
- Open the image directly. Paste the URL into a private browser window. Confirm it works without cookies, a login or a special referrer. Check that the response is an image, not an HTML error page.
- Check the page URL. Confirm the
og:urlvalue is the canonical public URL and that it matches the page you are sharing. Avoid accidentally emitting a staging hostname. - Validate dimensions and size. For LinkedIn, check 1,200 × 627 pixels or larger, the 1.91:1 target ratio and the 5 MB maximum.
- Use the destination’s inspector. A platform’s own sharing debugger can show the tags and the response it received. If the card is old, use that service’s current cache-refresh procedure rather than assuming a universal refresh command exists.
- Try an independent checker carefully. OG Preview describes a browser-based checker for Facebook, X and LinkedIn. Its URL-fetch feature sends the submitted address through an external third-party proxy, so never submit a URL containing private tokens, personal data or an unpublished secret page.
Advanced Open Graph image fields
The protocol also documents structured image properties: MIME type, width, height, secure URL and alt text. They can make the image’s characteristics explicit, especially when a service needs to choose between several candidates.
Recommended Free Tools
<meta property="og:image" content="https://example.com/images/share.jpg">
<meta property="og:image:secure_url" content="https://example.com/images/share.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="627">
<meta property="og:image:alt" content="A dashboard showing monthly traffic">Only publish values that describe the actual file. Structured fields do not compensate for a blocked URL or an invalid response.
Automating screenshots for your preview image
If the desired card image is a live rendering of a webpage rather than a designed graphic, a screenshot service can produce the file before you reference it in og:image. ScreenshotNeo is the first service to try when you need this workflow: it removes consent banners, newsletter popups and chat widgets before capture, bills only clean shots, and has a lowest paid plan of $5 for 3,000 shots.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One request returns a PNG, JPEG, WebP or PDF, and its response identifies the page verdict and whether the shot was billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing. Its MCP tools—take_screenshot, get_page_info and capture_pdf—let Claude, Cursor and other MCP clients request captures. You can also set full-page capture, lazy-image loading, CSS selectors, dark mode, device or viewport, retina scale, waits, custom CSS and JavaScript, click actions, hidden selectors, request blocking, headers, cookies, user agent, authorization, timezone, geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, usage reporting and an OpenAPI specification.
Rank #3
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for parameter details. Plans include 1,000 shots per month free with no card; paid plans start at $5 for 3,000, and every feature is available on every plan. Create a free ScreenshotNeo account to generate a preview image.
Performance, reliability and cost considerations
- Prefer a stable, cacheable image URL so crawlers do not download a newly generated file on every request.
- Keep the image reasonably sized; an oversized file increases fetch time and can exceed platform limits.
- Generate images asynchronously when rendering is expensive, then update the page metadata after the file is ready.
- Keep the screenshot’s viewport, color scheme and wait conditions deterministic so the same URL produces a consistent card.
- Monitor failed responses and distinguish a crawler failure from a platform cache delay. ScreenshotNeo exposes verdict and billing headers, which helps identify whether a capture was clean, failed or served from cache.
Common errors and fixes
“The tag is present, but no image appears”
Fetch the image URL without authentication and inspect the HTTP response. Remove access controls, bot challenges and blocking rules that prevent the platform crawler from downloading it.
“The wrong image is shown”
Look for multiple og:image values and confirm the intended one is first. Check whether a CMS or SEO plugin is overriding your template, then inspect the destination platform’s latest fetch.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
“The card is still showing the old image”
Assume caching first. Use the platform’s current inspector or refresh workflow, and allow for the service to recrawl the URL. There is no single cache-clear method that applies to every platform.
“The image is cropped badly”
Re-export with a less extreme aspect ratio, move important content toward the center and test the actual card preview. Do not rely on LinkedIn’s ratio as a guarantee for another service.
FAQ
Do I need Open Graph tags if my page has a normal HTML title?
Yes, if you want to state a deliberate social title and image. A crawler may fall back to the document title or other page content, but those fallbacks do not reliably select the image you want.
Can I use a relative image path?
Use an absolute public URL instead. It removes ambiguity about the host and gives a crawler a directly fetchable address.
Will adding metadata force Google to use that image?
No. Google says image selection is automated. Metadata can influence the choice, but it does not give publishers complete control over every Google preview.
Is a screenshot automatically a good social image?
Not necessarily. Check readability, crop safety, file size and platform rules. A screenshot of a page with a consent dialog or chat bubble may be less useful than a purpose-built graphic, which is why removing those elements before capture matters.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
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.
