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 errorsIf LinkedIn shows an old or incorrect preview for your link, check the Open Graph metadata served by the page, fix it if needed, then enter the URL in LinkedIn Post Inspector and confirm the preview. Refreshing affects new posts; it does not update previews on posts already published.
Check the Open Graph tags your page actually serves
Start with the public page, not just the settings in your CMS or the metadata you expect your code to generate. Inspect the delivered HTML and look in the document <head> for the values LinkedIn should use.
As an Amazon Associate I earn from qualifying purchases.
The Open Graph Protocol identifies four required properties: og:title, og:type, og:image and og:url. It describes og:description as optional but generally recommended. See the Open Graph protocol for the standard.
og:title: the intended title for the shared page.og:type: the page’s Open Graph object type.og:image: the image URL intended for the preview.og:url: the page’s canonical object URL for sharing.og:description: a concise description to accompany the title when available.
Check the values in the HTML returned for the URL you plan to share. Confirm the image URL is the intended one and that the title, description and URL reflect the live page. If a property appears more than once with conflicting values, the Open Graph Protocol says the first value takes precedence; remove or correct duplicates so the intended value appears first.
Refresh the URL in LinkedIn Post Inspector
- Open LinkedIn Post Inspector.
- Enter the URL you intend to share.
- Review the preview window and confirm it shows the correct content.
- If the preview is wrong, return to the page’s delivered HTML, correct the metadata or image URL, and inspect the URL again.
LinkedIn’s help guidance describes this as refreshing the URL and confirming the displayed preview. Its article notes that an old image may appear because the URL has already been shared and stored in cache, but it does not specify a cache-expiration period. Do not assume that a particular wait time will clear the preview.
Understand what the refresh changes
LinkedIn says a refreshed URL affects the preview image and information for new posts that include it. Existing posts with that URL keep their existing preview. If you correct metadata after a post has already been published, validate the URL for future shares, but do not expect the old post’s preview to be rewritten. LinkedIn’s exact explanation is in its Post Inspector help article.
Troubleshoot an incorrect preview
- The title or description is wrong: Check the values in the public HTML head, not only the CMS editor. Correct the delivered tags and inspect the URL again.
- The image is still old: Verify the live
og:imagevalue points to the intended image, then refresh the URL in Post Inspector. LinkedIn’s documentation does not give a guaranteed cache duration. - Different values appear in duplicate tags: Remove the duplicates or put the intended value first. Under the Open Graph Protocol’s ordering rule, the first conflicting value takes precedence.
- The existing LinkedIn post has not changed: That is expected; LinkedIn says refreshed information applies to new posts, not existing ones.
- You need a specific LinkedIn image size or format: LinkedIn’s help pages refer to platform image requirements, but the official material cited here does not establish exact dimensions, formats or size limits. Avoid relying on an unverified specification; consult LinkedIn’s current website-sharing guidance.
The official refresh instructions do not provide a complete technical troubleshooting matrix. In particular, they do not establish crawler behavior, JavaScript-rendering behavior, robots.txt rules or a cache-expiry schedule. The most grounded checks are the page’s served metadata, duplicate values and intended image URL, followed by another inspection.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. A screenshot can help you visually inspect what a page displays, but it does not replace checking the Open Graph tags in the delivered HTML or refreshing the URL in LinkedIn Post Inspector.
Rank #3
For example, this cURL request captures a page as a WebP image; replace the target URL with your page URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for API details. ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server provides screenshot, page-info and PDF-capture tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Sign up free for 1,000 screenshots a month, with no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Does Post Inspector change previews on LinkedIn posts that are already published?
No. LinkedIn says the refreshed preview applies to new posts; existing posts keep their old preview.
What should I check first if a LinkedIn preview is wrong?
Inspect the public page’s delivered HTML head, confirm the Open Graph values and image URL, and check that conflicting duplicate properties do not put the wrong value first.
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.
