For LinkedIn shares
See how your URL looks when shared on LinkedIn — before you post.
LinkedIn fetches Open Graph tags on first share and caches them aggressively. A bad first preview can stick around for days.
Use the Post Inspector after fixing tags to force LinkedIn to re-scrape. This tool shows you what those tags actually contain right now.
The caching behavior is the trap that catches everyone: the first person to share a URL on LinkedIn locks in whatever tags existed at that moment — typically for about a week. If a colleague shares your launch page while the og:image is still the placeholder, that placeholder is what the whole company's shares will show until the cache expires or you force a re-scrape. The discipline that prevents it: check tags with this tool before the URL is shared anywhere, every time.
LinkedIn's scraper reads server-rendered HTML. If your og:tags are injected client-side by JavaScript (common on SPAs without SSR or prerendering), the scraper sees none of them and falls back to whatever's in the raw HTML — usually a generic title or nothing. This tool fetching your tags successfully is a good sign, but the definitive test for JS-heavy sites is the Post Inspector, which shows exactly what LinkedIn's own crawler extracted.
Title and description get truncated in the feed, and the exact cut-off varies by device and surface — desktop feed, mobile feed, and messaging previews each show different amounts. Front-load og:title with the words that matter (LinkedIn tends to show roughly 70 characters before cutting) and treat og:description as a supporting line that may not appear on every surface.
Company page shares, personal shares, and Sales Navigator messages all use the same underlying scrape, so one clean set of tags serves every distribution channel. What differs is the audience's scrolling speed — B2B feeds are skimmed ruthlessly, which makes the og:image carry most of the click-through weight. A 1200×627 image with legible text at feed size routinely outperforms a beautiful-but-unreadable one.
When previews misbehave, work the failure chain in order: does the URL return 200 to crawlers (not blocked by robots.txt or bot protection)? Are the tags in the server-rendered HTML? Is the og:image HTTPS, under 5 MB, and publicly fetchable without cookies? Then, and only then, force the re-scrape — otherwise you're just re-caching the same broken state.
Verify the og:image and title before sharing a launch post — and before anyone else's early share locks a bad preview into LinkedIn's cache.
Confirm that updated tags are live before forcing a re-scrape; re-scraping a page that still serves old tags just re-caches the problem.
Compare different og:title variants for the same page and preview each before committing the winner to the share cycle.
Verify your React/Vue/Next site serves OG tags in server-rendered HTML — the single most common cause of blank LinkedIn previews on modern stacks.
Before asking the whole company to share a post, confirm the preview once — a broken card multiplied by two hundred shares is a very public QA failure.
Pre-configured variants tuned to specific platforms and use cases.
For Slack unfurls
Check how your URL unfurls inside Slack messages and channels.
Open variantFor X / Twitter Cards
Preview how your URL renders as a Twitter Card on X.
Open variantFor Facebook shares
Inspect how your URL will render in a Facebook post or share.
Open variantFor Discord embeds
See how Discord embeds your URL inside a channel or DM.
Open variant