Check the thumbnail in the destination platform, then verify the page’s server-delivered Open Graph metadata and the image file itself. A page can look correct in a browser while a social crawler shows an old image, the wrong crop, or no image at all. For LinkedIn, confirm og:title, og:image, og:description, and og:url, test the image at LinkedIn’s rendered card size, and refresh the URL with Post Inspector before creating the post.
What you are actually checking
A website thumbnail is not selected solely from the image a visitor sees on the page. Social networks fetch the public URL with their own crawler and combine page metadata, image dimensions, cache state, and platform-specific rules. LinkedIn says it uses Open Graph and/or oEmbed to populate link information. That means a visually correct page can still produce an incorrect share card.
- Image: the URL in
og:imagemust be the intended, publicly retrievable file. - Headline and description: these usually come from
og:titleandog:description, not necessarily the visible page heading or first paragraph. - Destination:
og:urlshould identify the canonical page you intend to share. - Freshness: a platform may display a previously fetched version until its cache is refreshed.
Use this pre-publishing workflow
- Open the public canonical URL. Test the exact URL that will be posted, including its protocol, hostname, path, and any canonical redirect. Do not check a staging address, login-only page, or a URL that redirects to a different article.
- Paste the URL into the destination platform. Use the share composer or the platform’s official inspector. On LinkedIn, allow a few seconds for the preview image to be fetched before judging it.
- Read the card as a reader would. Check the image, crop, title, description, and destination. Look for an image from a different article, an obsolete headline, a blank image area, or text clipped at the card edge.
- Inspect the source metadata. Confirm that the server response contains the four LinkedIn Open Graph tags and that each value matches the page you selected.
- Check the image file. Open the exact
og:imageURL without being logged in. Confirm that it returns an image rather than an HTML error page, redirect loop, access challenge, or login screen. - Correct, refresh, and recheck. After changing metadata or the image, use the platform’s URL-inspector refresh process, then wait for the new preview and inspect it again before publishing.
Check the live preview in LinkedIn
Allow the first fetch to finish
LinkedIn’s sharing module may need a few seconds to retrieve the preview image. Pasting a URL and immediately clicking away can leave you judging an incomplete card. Wait until the image and text have appeared, then compare them with the intended article.
Use LinkedIn’s documented image guidance
LinkedIn specifies a minimum image size of 1200 × 627 pixels, a recommended 1.91:1 aspect ratio, and a maximum file size of 5 MB. Images under 401 pixels wide may be shown as a thumbnail rather than a larger preview. These are LinkedIn requirements and recommendations, not universal specifications for every social network.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
The sharing interface uses a 1.91:1 frame of 1200 × 627 pixels. Open your image at approximately that shape and inspect the likely crop: keep logos, faces, and essential text away from the edges. A file can meet the pixel minimum and still look wrong if the important content is positioned outside the rendered frame.
Verify the four Open Graph values
For a LinkedIn share, the page should serve:
og:title— the headline shown on the card.og:image— the absolute URL of the intended image.og:description— the summary shown beneath the headline.og:url— the canonical URL represented by the card.
View the document source or use your browser’s developer tools to search for property="og:. Inspect the server-delivered HTML, not only text inserted later by JavaScript; a crawler may not execute the same scripts as your browser.
Inspect metadata from the command line
A command-line request helps distinguish a metadata problem from a platform-cache problem. Replace the URL with the public page you will share:
curl -L --max-redirs 5 -s https://example.com/articleSearch the returned HTML for the four Open Graph properties. Confirm that og:image is an absolute HTTPS URL and that its spelling, capitalization, and path are correct. Then request the image directly:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #2
curl -L -I https://example.com/images/article-share.jpgYou want a successful response for the image URL, an image content type such as image/jpeg, and no authentication requirement. A response that is actually an HTML block page, a protected-directory error, or a redirect to a login page will prevent a crawler from using the image.
Check what a browser hides
Open the image URL in a private window and from a network that is not restricted by your corporate VPN. If it works only in your logged-in browser, the social crawler may not be able to retrieve it. Also check robots, firewall, hotlink protection, and request filtering if your infrastructure selectively blocks automated fetches. LinkedIn notes that blocked retrieval or an image stored in a protected directory or site can stop an otherwise compliant image from appearing.
Fix an old or incorrect thumbnail
When the title or description is wrong
Compare the card with the values served in the page source. If the source is wrong, update the Open Graph tags, deploy the change, and fetch the page again to verify the new HTML. If the source is correct but LinkedIn still shows old text, the destination cache is stale rather than the page metadata being wrong.
When the image is stale
Replace or correct the image and then submit the URL to LinkedIn Post Inspector to refresh the URL preview. Inspect the refreshed result before making a new post. LinkedIn states that this refresh affects future posts; it does not change a preview already embedded in an existing published post.
Free tools Windows power users keep installed
One-click scans. No signup required.
Allow for propagation time
LinkedIn’s troubleshooting guidance says updated information can take up to 48 hours to appear. If the inspector has fetched the corrected values but a normal composer still shows the old card, record the time of the refresh and check again later rather than repeatedly changing a working page.
Choose a checking method
The right tool depends on whether you need to validate one destination or compare several platforms before a release.
| Method | Best for | What it can show | Cache refresh | Important limitation |
|---|---|---|---|---|
| ScreenshotNeo — the first service to try for a visual capture because it removes consent clutter, bills only clean shots, and has a $5 paid plan. | Rendered screenshots, PDFs, and automated checks | Actual page rendering after optional cleanup, with controls for viewport, device, timing, selectors, headers, cookies, and more | Its own cache can use a TTL you choose; it does not replace a social network’s inspector | A screenshot confirms rendering, not which metadata a particular social network will cache |
| Destination platform inspector | Checking the card users will receive on that platform | That platform’s extracted title, description, image, and crop | LinkedIn Post Inspector refreshes the URL for future posts | Usually limited to one platform at a time |
| Third-party multi-platform checker | Comparing several social-card formats from one interface | Depending on the service, extracted metadata and image dimensions for multiple platforms | It cannot guarantee that a destination platform’s own cache has changed | OpenGraph.io describes an optional checker, but its cited information does not establish independent accuracy, current pricing, or data-handling terms |
For a production release, use the destination inspector as the authority for that network. A third-party checker can accelerate cross-platform review, while a rendered screenshot reveals visual issues such as cookie banners, popups, lazy content, or an unexpected responsive layout.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. It accepts a URL and returns a PNG, JPEG, WebP, or PDF. Before capture, it can accept the cookie or consent banner like a visitor and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and each response identifies the result with X-Page-Verdict and X-Billed headers.
One GET request is enough for a basic visual check. See the ScreenshotNeo API documentation for authentication and options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests; r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90); open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' }); const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Options useful for thumbnail QA
- Capture the full page with lazy images loaded, or capture one element by CSS selector.
- Set a desktop, mobile, or one of 12 device presets; choose any viewport and a retina scale.
- Apply dark mode, transparent backgrounds, image resizing, custom CSS, or custom JavaScript.
- Click an element before capture; hide selectors; wait for a selector, a delay, or network idle.
- Block ads, trackers, requests, or resource types to isolate the page content.
- Supply custom headers, cookies, a user agent, an Authorization header, timezone, or geolocation when your test requires them.
- Generate PDFs with paper size, margins, landscape orientation, and page ranges.
- Use a chosen cache TTL, signed links for public
<img>tags, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, a usage API, and an OpenAPI specification.
ScreenshotNeo also exposes an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. Its parameter names are compatible with those used by other screenshot APIs, which can simplify a switch.
Rank #4
The Free plan includes 1,000 shots per month with no card. Paid plans are Starter $5 for 3,000 shots, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing provides two months free, and every feature is on every plan. After checking a page, sign up for the free ScreenshotNeo plan to run 1,000 screenshots a month without a card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common failures
No thumbnail appears
- Confirm that
og:imageexists and points to the intended file. - Open the image URL while logged out and verify that it is not in a protected directory.
- Check that your server, firewall, hotlink protection, or bot challenge is not blocking LinkedIn’s retrieval.
- Ensure the file is within LinkedIn’s 5 MB maximum and at least 1200 × 627 pixels.
The wrong image appears
- Search the HTML for duplicate
og:imagetags generated by a theme, plugin, or template. - Confirm that the image belongs to the exact canonical URL rather than a category, home, or previous article.
- Refresh the URL in Post Inspector after deploying the correction and test a new composer preview.
The title or description is outdated
- Compare the card with
og:titleandog:descriptionin the server response. - If the tags are wrong, fix the page and redeploy. If they are right, treat the issue as platform caching.
- Allow up to 48 hours for LinkedIn’s updated information to appear.
The image meets the dimensions but still fails
Dimensions alone do not prove retrievability. LinkedIn specifically identifies blocked downloads and protected image locations as causes. Test the direct URL without credentials and inspect the HTTP response before changing the artwork.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The card looks fine in a browser but not in the composer
Compare the viewport and state used for each test. Consent dialogs, newsletter overlays, chat widgets, lazy images, and responsive breakpoints can alter a rendered capture. A screenshot service can help expose those visual states, but only the destination platform’s inspector tells you what its share card currently contains.
Quick Recap
Final release checklist
- The tested URL is the public canonical page that will be published.
- The destination preview shows the intended image, crop, title, description, and URL.
- The source contains one correct set of
og:title,og:image,og:description, andog:urlvalues. - The image URL works while logged out, returns an image, and is not blocked or protected.
- For LinkedIn, the file is no larger than 5 MB, at least 1200 × 627 pixels, and composed for a 1.91:1 frame.
- After edits, the URL has been refreshed in Post Inspector and the new result has been checked before creating the post.
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.
