LinkedIn Link Preview Not Working
You share a link on LinkedIn and the preview is broken — "Cannot Display Preview" error, wrong image, missing description, or a blank card. LinkedIn's crawler (LinkedInBot/1.0) is stricter than most platforms: it doesn't execute JavaScript, doesn't follow most redirects, and rejects several common image formats. Here's how to fix every common issue.
Common Causes
1. OG tags missing or rendered by JavaScript — LinkedInBot/1.0 does not execute JavaScript. Tags must be in the raw HTML.
2. Image URL redirects — LinkedIn's crawler is strict about redirects. Even a simple HTTPS-to-HTTPS redirect on the image URL can cause failure.
3. Image too small — LinkedIn requires at least 200px on the shortest side for any image. For a full-width card, the image should be 1200x627px.
4. WebP image format — LinkedIn does not support WebP. Use JPEG or PNG.
5. HTTP instead of HTTPS — LinkedIn requires all URLs (page and image) to use HTTPS.
6. Image over 5MB — LinkedIn silently drops images exceeding 5MB.
7. Cached old preview — LinkedIn caches link previews for approximately 7 days.
8. robots.txt blocking LinkedInBot — The crawler respects robots.txt and will return nothing if blocked.
How to Fix
Step 1: Run LinkedIn Post Inspector
1. Go to LinkedIn Post Inspector
2. No login is required
3. Paste your page URL
4. Click "Inspect"
The Post Inspector shows the scraped title, description, image, and any errors. It also forces a cache refresh — every inspection triggers a re-scrape.
Step 2: Fix "Cannot Display Preview" Errors
If Post Inspector shows "Cannot Display Preview," work through these checks in order:
1. Verify the page is accessible. Open the URL in an incognito browser window. If it requires login, a VPN, or is geo-restricted, LinkedIn's crawler can't reach it either.
2. Check robots.txt. Open https://yourdomain.com/robots.txt and make sure LinkedInBot is not disallowed:
# Bad — blocks LinkedIn
User-agent: LinkedInBot
Disallow: /
# Good — allows LinkedIn
User-agent: LinkedInBot
Allow: /3. Confirm OG tags are in the static HTML. View Page Source (not DevTools Inspect) and search for og:title. If the tags only appear after JavaScript runs, LinkedIn won't see them.
4. Check for redirects on the page URL. LinkedIn handles 301/302 redirects on the page itself, but complex redirect chains (3+ hops) or JavaScript-based redirects will fail. Use a direct, canonical URL.
Step 3: Fix Image Issues
LinkedIn's image requirements are strict:
Format: JPEG or PNG only. WebP is not supported. LinkedIn will silently ignore WebP images and may show no image at all.
Size: Minimum 200x200px. Recommended 1200x627px for a full-width card.
File size: Maximum 5MB. Keep it under 1MB for reliability.
URL: Must be HTTPS. Must not redirect. Must return a 200 status code directly.
Dimensions tag: Include og:image:width and og:image:height for reliable rendering.
<meta property="og:image" content="https://example.com/images/preview.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />Step 4: Clear the Cache
LinkedIn caches link previews for approximately 7 days. To force a refresh:
1. Go to Post Inspector
2. Enter the URL
3. Click "Inspect"
This triggers an immediate re-scrape. The new preview will be used for all future shares of that URL. Unlike Facebook, LinkedIn updates reliably after a single re-scrape — you don't need to click twice.
Step 5: Verify the Fix
After running Post Inspector:
1. Check that the preview shows the correct title, description, and image
2. Create a new LinkedIn post with the URL to confirm the live preview matches
3. If posting to a Company Page, note that the preview may take a few additional minutes to propagate
Platform-Specific Notes
No JavaScript execution: LinkedInBot/1.0 is a simple HTTP crawler. It fetches the raw HTML and parses meta tags. Single-page applications (React, Vue, Angular) must use server-side rendering (SSR) or static pre-rendering for OG tags to work on LinkedIn.
Redirect handling: LinkedIn's crawler follows simple 301 and 302 redirects on the page URL, but is strict about image URLs. If your image URL returns any redirect (even 301), LinkedIn may fail to load it. Always use the final, direct image URL.
og:description display: LinkedIn does not always display the og:description in the feed preview. Whether the description appears depends on the post format and feed layout. Always set it anyway — it may appear in some contexts and is used for accessibility.
Organic vs. paid post previews: LinkedIn changed how organic link posts render in the feed in 2024. Organic posts may show a smaller preview card compared to paid/sponsored posts, which still get full-width image cards. This is a LinkedIn platform decision, not something you can control through OG tags.
Company Page vs. personal profile: Preview behavior is identical for both. The same OG tags and caching rules apply regardless of whether the link is shared from a personal profile or a Company Page.
Article vs. link post: When you create an Article on LinkedIn (the native publishing feature), OG tags from the external link are not used. OG tags only apply when sharing an external URL as a link post.
Prevention Checklist
Use this checklist before sharing any link on LinkedIn:
OG tags are in static HTML (not JavaScript-rendered). og:image is JPEG or PNG (not WebP, GIF, or SVG). Image is at least 1200x627px. Image file size is under 5MB (ideally under 1MB). Image URL uses HTTPS with no redirects. og:image:width and og:image:height are declared. robots.txt allows LinkedInBot. Page URL uses HTTPS. No complex redirect chains on the page URL. After changes, re-inspect with LinkedIn Post Inspector.
FAQ
Most likely your OG tags are rendered by JavaScript, which LinkedIn's crawler doesn't execute. View your page source (not Inspect Element) — if the OG tags aren't in the raw HTML, LinkedIn can't see them. Use server-side rendering or a pre-rendering service.
LinkedIn caches previews for about 7 days. Go to Post Inspector, enter your URL, and click "Inspect" to force a re-scrape. The updated preview should appear immediately for new shares.
Yes. LinkedIn does not support WebP for OG images. The simplest approach: create your OG image as JPEG (1200x630px) and use it across all platforms. Even platforms that support WebP handle JPEG perfectly. There's no advantage to using WebP for OG images since they're typically small files (under 300KB).