Seo May 22, 2026 5 min read

What Your LinkedIn Share Card Actually Looks Like Before You Post

Learn how to preview how your site looks when shared on LinkedIn, debug broken thumbnails, and fix OG tags before your post goes live.

You hit post on LinkedIn, the link appears with no image, a truncated title, or worse — your old logo from two redesigns ago. Now the post is live, your reach window is closing, and editing the link won't refresh the preview. The fix is to check exactly what LinkedIn will pull before you publish.

Here's how to preview how your site looks when shared on LinkedIn, what controls the card, and how to force LinkedIn to refresh stale data.

What LinkedIn actually reads from your page

LinkedIn's share card is built from Open Graph (OG) meta tags in your page's <head>. It does not use Twitter Cards, and it largely ignores generic <meta name="description"> tags when OG equivalents exist.

The tags LinkedIn cares about:

og:title — the headline shown on the card
og:description — the snippet beneath the title
og:image — the thumbnail (absolute URL only)
og:url — the canonical link
og:type — usually article or website

If any of these are missing, LinkedIn falls back to whatever it can scrape — often producing the broken previews you've seen on your feed.

Image requirements that trip people up

Minimum 1200 x 627 px for a large card (1.91:1 ratio)
Maximum file size 5 MB
Must be a fully qualified URL (https://example.com/image.jpg, not /image.jpg)
Image must be publicly accessible — no auth walls, no robots.txt blocking the crawler
JPG, PNG, or GIF (static frame used)

Anything smaller than roughly 200 x 200 px gets rendered as a tiny square thumbnail instead of a hero image, which kills click-through.

Three ways to preview the card before posting

1. LinkedIn Post Inspector

LinkedIn provides an official tool at linkedin.com/post-inspector. Paste your URL and it returns:

The rendered card exactly as it will appear
The OG tags it detected
Any errors (missing image, oversized file, 4xx responses)
The last time LinkedIn cached the URL

This is the source of truth. If the inspector shows the wrong image, your post will too.

2. Inspect your meta tags directly

Before you even paste a URL into LinkedIn, confirm the tags are correct. Open the page, view source, and search for og:. You're looking for something like:

<meta property="og:title" content="Your headline here" />
<meta property="og:description" content="A 1-2 sentence summary." />
<meta property="og:image" content="https://example.com/share-card.jpg" />
<meta property="og:url" content="https://example.com/post-slug" />
<meta property="og:type" content="article" />

For a faster audit across multiple URLs, the AXOX Hub Meta Tag Analyzer pulls every relevant tag in one view and flags missing or malformed OG properties — useful when you're auditing a batch of articles or checking a client's site.

3. Test in a private LinkedIn message

If the Post Inspector cache is being stubborn, paste the link into a draft direct message to yourself. LinkedIn renders the preview the same way it would in a feed post, and you can confirm the final appearance without publishing.

Fixing a broken or stale preview

The most common complaint: "I updated my OG image but LinkedIn still shows the old one." LinkedIn caches aggressively — sometimes for 7+ days. Here's the working sequence:

Confirm the new og:image is live by loading the image URL directly in your browser
Run the URL through LinkedIn Post Inspector
If the old image still shows, the cache is stale — click Inspect again, which forces a re-scrape on most URLs
If LinkedIn still won't refresh, append a query string (e.g. ?v=2) to the share URL. LinkedIn treats it as a new resource and fetches fresh data
For persistent issues, check that your server returns a clean 200 for both the page and the image — redirect chains often break the scrape

When redirects are the real problem

If your share URL goes through one or more redirects (e.g. http → https → www → final), LinkedIn may give up before reaching the destination, or it may scrape the wrong page entirely. Run the URL through a redirect checker to confirm it resolves in one hop. The redirect analyzer will show the full chain and any 301/302/307 hops you didn't know existed.

A pre-publish checklist

Before sharing any new article or landing page on LinkedIn, run through this:

✅ og:title is under 70 characters (LinkedIn truncates around there)
✅ og:description is 100–200 characters, written for humans not SEO
✅ og:image is 1200 x 627, absolute URL, publicly fetchable
✅ og:url matches the canonical URL exactly
✅ The page returns 200 OK with no redirect chain
✅ Post Inspector renders the card correctly
✅ The image still looks readable when shrunk to mobile feed size (~400 px wide)

That last point matters more than people realize. A card that looks crisp on desktop often turns into illegible mush on mobile because the text overlay was too small or too low-contrast. Always preview at the size LinkedIn will actually display it.

Common patterns that kill share previews

SPA frameworks rendering OG tags client-side. LinkedIn's scraper doesn't execute JavaScript. Tags must be in the initial HTML response — use SSR, prerendering, or build-time generation
CDN or WAF blocking the LinkedInBot user agent. Check your firewall rules and allow LinkedInBot/1.0
Conflicting plugins. WordPress sites often have Yoast, RankMath, and a theme all injecting OG tags — only one wins, and it's not always the one you configured
Lazy-loaded images referenced in og:image. The URL must serve the actual image directly, not a placeholder

Audit the rendered HTML — not the source in your CMS — to see what LinkedIn really gets.

Run a quick check now

If you've got a post going out today, paste your URL into the AXOX Hub Meta Tag Analyzer first. It'll surface missing OG properties, oversized images, and mismatched canonical URLs in a few seconds — before LinkedIn caches a broken version of your card.

Try the free tool

Open Tool

← Back to Blog