Overview
A broken LinkedIn link preview is more than an aesthetic problem. When a shared URL shows the wrong title, a missing image, or no preview at all, you lose immediate trust and click-through signal.
The LinkedIn Post Inspector is LinkedIn's free, official debugging tool. It shows how a shared link will appear on the platform and forces a fresh crawl when cached data is out of date.
This guide walks through a practical step-by-step workflow. It also addresses technical edge cases most articles skip — redirect chains, JavaScript-rendered pages, WAF allowlisting, image format precedence, and localization.
By the end you'll have a compact QA checklist to run before high-stakes shares. You'll also have clear decision logic for when to fix metadata at the source versus when to use a LinkedIn-side workaround.
---
What is the LinkedIn Post Inspector tool?
The LinkedIn Post Inspector is an official, free tool from LinkedIn. It lets you preview how links will render before — or after — posting them.
It scans a page's metadata and shows the image, title, and description LinkedIn has stored in its cache. The tool also shows a timestamp for the last crawl. Access it at LinkedIn Post Inspector; you must be logged into a LinkedIn account to use it.
The inspector reads Open Graph (OG) tags embedded in the page HTML <head>. It primarily looks for og:title, og:description, og:image, and og:url. These standardized tags tell social platforms how to represent a page when shared.
If OG tags are absent or inaccessible to LinkedIn's crawler, the Post Inspector surfaces the problem. It also lets you trigger a re-scrape to pick up fixes.
Crucially, the inspector shows LinkedIn's cached view of your page. That is not necessarily what a live visitor sees. This distinction matters when you've recently updated metadata. Confirming the live page shows correct OG tags is a necessary first step before asking LinkedIn to re-crawl.
---
How LinkedIn link previews are generated (OG tags, crawler access, and caching)
When a URL is pasted into LinkedIn's composer, LinkedIn's crawler fetches the page. The crawler is typically identified as LinkedInBot in server logs.
The crawler parses the HTML for Open Graph tags. The four most important tags are og:title, og:description, og:image, and og:url. If they are missing, LinkedIn may fall back to <title> and <meta name="description">, but results are less predictable.
After fetching, LinkedIn stores the preview data in a cache keyed to the URL it fetched. That cached version is served to subsequent users who share the same URL.
This caching is why updating OG tags on your site does not automatically update LinkedIn's preview for everyone. The Post Inspector's "Inspect" button requests a fresh crawl and replaces the cached data for the inspected URL.
The cache and the crawler create two common failure modes. Either the crawler couldn't reach your page at all, so there is no preview. Or the crawler reached it but the cached copy is stale. Distinguishing between those quickly tells you whether to fix access on your server or re-run the inspector after updating metadata.
---
Step-by-step: use the LinkedIn Post Inspector to refresh and debug a URL
The official tool lives at LinkedIn Post Inspector. You need to be logged into a LinkedIn account.
Worked example: a content lead updates the hero image and changes an og:title on a landing page. Days later a colleague pastes the URL into a post and the old image and title still appear. The resolution is straightforward if you follow the right sequence.
Here is the workflow:
1. Open the inspector and paste the exact URL you plan to share — include path components but avoid UTM parameters when possible. Go to LinkedIn Post Inspector and enter the URL.
2. Read the current cached state. The tool shows the title, description, image, and the last crawl timestamp; stale content confirms a caching issue.
3. Verify your OG tags are correct on the live page. View the page source and search for og: to confirm og:title and og:image are present before requesting a re-scrape.
4. Click "Inspect" to request a fresh crawl. LinkedIn will re-fetch the page and update its cache; the inspector will show a new crawl timestamp when complete.
5. Confirm the updated preview matches your intentions. If it doesn't, use the inspector output to diagnose the missing element.
6. Test the share flow by pasting the URL into a LinkedIn composer (no need to publish) to ensure the preview renders before posting.
In the worked example, the inspector picked up the new image and title immediately after the re-scrape. The composer refreshed, and the fix took under five minutes once the source metadata was confirmed.
---
Troubleshooting playbook: why your LinkedIn preview looks wrong and how to fix it
Most preview problems fall into a few root causes. The sections below map each failure to its likely origin and the fastest path to resolution.
"We cannot display a preview for this URL"
This error means LinkedIn's crawler either could not reach your URL or could not extract usable preview data. Common causes include non-200 HTTP responses (404, 403, 5xx), pages behind login walls or cookie gates, or WAF rules that block bots.
Check server logs for requests from LinkedInBot around the failed crawl and look for non-200 responses. Robots directives are another frequent cause: a Disallow: / in robots.txt, a page-level <meta name="robots" content="noindex, nofollow">, or an X-Robots-Tag: noindex response header can prevent crawling.
Finally, a page that returns an empty body or only JavaScript-injected content (see SPA notes) will leave the inspector nothing to display.
Immediate next steps:
- Confirm the URL returns 200 by opening it in a private/incognito window.
- Check robots.txt and any meta/HTTP robots directives for blocking rules.
- Verify the page contains OG tags or, at minimum, a <title> in the HTML source.
- If bots are being blocked, review WAF/CDN allowlist settings.
Wrong or missing image in the preview
Missing or incorrect images usually stem from one of three issues: no og:image tag, an inaccessible image URL, or an image that fails LinkedIn's size/format expectations.
Start by confirming an og:image tag exists and uses an absolute https:// URL. Relative or http:// URLs often fail.
Ensure the image loads in an incognito tab without authentication. Check CDN hotlink protection or signed URLs that might block LinkedIn's fetcher.
For dimensions and formats, JPG or PNG close to a 1.91:1 aspect ratio (commonly 1200×628) is the safest choice. Unusual formats (SVG, AVIF) and very large files increase risk.
Fix order:
1. Confirm og:image is present and uses an absolute https:// URL.
2. Verify the image loads in an incognito window with no cookies.
3. Check CDN hotlink protection and signed URL settings.
4. Use JPG or PNG near 1.91:1; avoid uncommon formats.
5. Remove duplicate og:image tags if more than one exists.
6. Re-run the Post Inspector.
Outdated cache after title/description/image changes
If your site shows updated metadata but LinkedIn still serves old content, the cached copy simply hasn't been replaced. Use the Post Inspector's "Inspect" button to force a fresh crawl for the exact URL you submit.
Note that if the URL redirects, LinkedIn may cache the preview against the resolved destination or create separate entries per variant. Verify the inspector's crawl timestamp and the final cached URL.
Also note: posts already published on LinkedIn will continue to display the old cached preview. The inspector only affects new shares.
Redirects, link shorteners, and tracking parameters
Redirect chains and shorteners add intermediate hops that can fail or be blocked. Standard 301/302 redirects are usually followed, but each hop increases failure risk.
JavaScript-based shorteners are risky because LinkedIn's crawler likely does not execute client-side JavaScript. The crawler can stall at the shortener page.
UTM parameters can fragment LinkedIn's cache into multiple entries for the same content. Set og:url to the canonical, parameter-free URL to consolidate previews around a single authoritative form.
JavaScript-rendered pages (SPAs) and missing metadata
LinkedIn's crawler generally does not execute client-side JavaScript. Single Page Applications that inject OG tags client-side will appear as empty shells to the crawler.
The solution is server-side rendering (SSR) or prerendering so the initial HTTP response contains correct OG tags in the <head>. If the inspector shows missing metadata despite correct tags in your browser, the tags are likely injected client-side and invisible to the crawler.
Private, staging, or document links (PDFs, Google Docs, Notion)
Authenticated or IP-restricted pages will not yield usable previews because LinkedIn crawls as an unauthenticated bot. For staging QA, temporarily make a staging URL public or add OG tags to a publicly accessible staging page for the duration of testing.
PDFs lack HTML <head> sections and cannot include OG tags. Consider creating a landing page with OG tags that links to the document instead of sharing the document URL directly.
---
Technical edge cases most guides miss
Redirect chains and UTM parameters: consolidate to a single canonical preview
Multiple redirects increase the chance of errors and cache fragmentation. Align your og:url with your HTML canonical tag and point both to the parameter-free canonical form.
Minimize unnecessary redirects — particularly http:// to https:// hops — by serving all pages over HTTPS natively. For UTM-tagged links, ensure the landing page's og:url always points to the canonical version so LinkedIn stores the preview against the canonical URL.
Robots, HTTP status, and cache headers: what can silently break previews
Hidden server settings can silently block previews. A robots Disallow: /, noindex meta tags, or X-Robots-Tag: noindex headers prevent crawling. Non-200 HTTP status codes (410, intermittent 503s) and too many redirect hops also cause failures.
Cache-control headers like Cache-Control: no-store or private can affect how LinkedIn stores the preview after a successful crawl. When the inspector reports access failures but shows no clear error, review server logs and response headers directly.
Crawler access and WAF/CDN allowlisting
WAFs and CDN bot-management may block LinkedInBot and return 403 or 429 responses. To verify genuine LinkedInBot requests, check the User-Agent for LinkedInBot and perform a reverse DNS lookup on the source IP to confirm it resolves to a LinkedIn-owned hostname. Then verify forward DNS resolves back to the same IP.
LinkedIn's documentation provides guidance on crawler ranges; only after such verification should you create allowlist rules. Avoid allowlisting by user-agent alone since user-agents can be spoofed.
High-level allowlisting steps:
- Identify LinkedInBot entries in access logs by user-agent.
- Verify source IPs via reverse DNS for LinkedIn-owned hostnames.
- Create WAF rules that allow verified LinkedInBot traffic.
- Avoid allowlisting on user-agent alone.
Image formats, secure URLs, and multiple og:image selection
JPG and PNG over HTTPS are the most reliably supported og:image formats. Avoid http:// image URLs due to mixed-content issues and be cautious with less common formats (AVIF, SVG).
Images behind hotlink protection, signed URLs, or geo-restrictions may be accessible to users but blocked for LinkedIn's fetcher. When multiple og:image tags exist, the first valid tag is likely used, but behavior is not guaranteed. The safest approach is a single og:image tag per page.
Localization: og:locale, hreflang, and preview language
On multi-language sites, LinkedInBot may be served a default language variant because it doesn't present a locale preference. Use og:locale to declare page language and ensure each language variant uses a distinct URL with its own OG tags and proper hreflang annotations.
Avoid serving language based only on IP or Accept-Language detection. That can return the wrong variant to the crawler. Instead ensure unauthenticated requests receive the language appropriate for your primary LinkedIn audience.
---
Operational best practices for teams
Preview quality is a publishing quality issue, not just technical. Teams that share many URLs on LinkedIn benefit from including a lightweight preview check in their publishing workflow instead of finding broken previews after posts go live.
The Post Inspector has no official API, so bulk checking is manual or semi-manual. Focus on spot-checking high-impact pages and gating preview checks in content approvals.
Pre-publish LinkedIn preview QA checklist
Run this checklist before sharing high-stakes URLs; it takes under five minutes and catches most failures.
- URL hygiene: confirm the canonical production URL — no staging domains, no http://, no unnecessary UTM parameters.
- OG tags present: view page source and confirm og:title, og:description, og:image, and og:url exist in the <head>.
- Image accessible over HTTPS: open the og:image URL in incognito to confirm it loads without authentication.
- No blocking robots directives: verify robots.txt and that the page has no noindex/nofollow meta robots tags.
- Single og:image tag: confirm only one og:image appears.
- Run the Post Inspector: submit the URL and confirm the preview renders with the expected image and title.
- Verify crawl timestamp: ensure the inspector shows a recent crawl after your latest changes.
- Final redirect target: if the URL redirects, confirm the final destination's metadata is reflected in the preview.
Monitoring and logging: confirm LinkedInBot hits and cache updates
After a successful re-scrape, verify server logs for entries where the User-Agent contains LinkedInBot and the requested path matches your URL. A recent 200 response confirms the crawler reached your server; 403 or 503 entries indicate access problems.
LinkedIn's autonomous recrawl cadence is not publicly specified and can be unpredictable. Use the Post Inspector when you need a reliable forced update.
When to fix metadata vs upload a manual image on LinkedIn
You can manually replace the auto-generated preview image in LinkedIn's composer for immediate, time-sensitive fixes. This is a useful tactical workaround for urgent campaign launches.
However, manual uploads only affect that post and create divergence from your site's metadata. Subsequent shares of the same URL will show the original OG image.
For long-lived content, fix metadata at the source and use the Post Inspector to refresh the cache as the sustainable workflow.
---
Comparisons and related tools (Facebook Sharing Debugger, X/Twitter Card Validator)
LinkedIn, Facebook, and X (Twitter) all primarily read Open Graph tags. Correctly implemented OG tags should produce reasonable previews across platforms.
Facebook's Sharing Debugger is similar to LinkedIn's inspector but exposes more granular diagnostics like HTTP response codes and parsing warnings. That can help debug access issues affecting LinkedIn.
X's Card Validator accepts both twitter: tags and OG tags; differences in rendering (for example, image crop behavior) can lead to platform-specific discrepancies. For multi-network shares, run each platform's validator independently to confirm previews on each.
---
FAQs: LinkedIn Post Inspector tool
What is the official URL of the LinkedIn Post Inspector and how do I access it quickly?
The official tool is at LinkedIn Post Inspector. You must be logged into a LinkedIn account to use it; bookmark it for fast access during publishing.
Does LinkedIn execute JavaScript when generating link previews for SPA pages?
LinkedIn's crawler generally does not execute client-side JavaScript. If your OG tags are injected by JavaScript after the initial load, the Post Inspector will typically show missing or empty metadata. The fix is to ensure OG tags are present in the server-rendered HTML returned in the initial response.
How does LinkedIn handle 301/302/307 redirects and UTM parameters when caching a preview?
LinkedIn's crawler generally follows standard HTTP redirects to the final destination and will typically cache the preview against the resolved URL. UTM parameters can create separate cache entries; set og:url to the canonical, parameter-free URL to signal the authoritative cache key.
Which image formats and dimensions are reliably supported for og:image on LinkedIn?
JPG and PNG over HTTPS are the safest choices. A 1.91:1 aspect ratio (commonly 1200×628) renders predictably. Avoid relying on SVG, AVIF, or animated GIFs for preview images and keep file sizes modest to reduce fetch failures.
Can I force-clear or bypass LinkedIn's cache without adding random query strings?
Yes — the Post Inspector's "Inspect" button is the supported mechanism to force a fresh crawl and update LinkedIn's cache. Adding random query strings creates separate cache entries and is generally not desirable.
What's the difference between og:url and canonical for LinkedIn previews, and which should I rely on?
og:url is the signal social crawlers read to determine the URL a preview should be associated with; the HTML canonical tag primarily targets search engines. For LinkedIn preview reliability, og:url is the directly relevant signal. Align both tags to the same canonical URL to avoid cross-tool confusion.
How do I configure a WAF/CDN to allow LinkedInBot without opening the site to bad bots?
Combine user-agent matching with IP/reverse DNS verification: identify LinkedInBot entries in logs, verify source IP reverse DNS resolves to a LinkedIn-owned hostname, then create WAF allowlist rules scoped to verified LinkedInBot traffic. Avoid allowlisting by user-agent alone.
Is there a way to bulk-check many URLs with LinkedIn Post Inspector or another workflow?
There is no public API for the Post Inspector, so bulk checking is manual or semi-automated. Practical approaches include spot-checking high-priority URLs, gating the inspector in content approvals, or scripting internal fetches to validate OG tag presence before public sharing. Third-party OG preview tools can simulate previews but cannot clear LinkedIn's cache.
Will LinkedIn generate a preview for PDFs, Google Docs, or private/staging pages?
Not reliably. PDFs lack HTML <head> and OG tags, so LinkedIn has no structured metadata to use. Google Docs and Notion may generate limited previews but offer little control. Private or staging pages behind authentication will not yield previews. For important documents, create a public landing page with proper OG tags linking to the document.
How can I ensure the correct language appears in the preview on multi-language sites?
Set og:locale on each language variant, use distinct URLs per language, and apply hreflang annotations. Avoid dynamic language detection that serves different content to the crawler; ensure unauthenticated requests receive the intended default language for your LinkedIn audience.
When should I upload a manual image on LinkedIn instead of fixing OG metadata on my site?
Upload a manual image when you need an immediate fix for a time-sensitive post and cannot wait to update site metadata and re-scrape. For content shared repeatedly or across platforms, fix metadata at the source and refresh via the Post Inspector for a long-term solution. For producing separate visual content like carousels, use dedicated design tools so metadata and visual production remain distinct workflows.