LinkedIn builds a preview the first time it sees a URL, stores it, and reuses that stored version for every subsequent share. There is no TTL you can set from your side, and there is no header that opts out. The only supported invalidation path is the Post Inspector.
What LinkedIn reads
- og:title first, then the page title as a fallback.
- og:description first, then the meta description.
- og:image for the card, preferring 1.91:1 at 1200 × 627 or larger.
- og:url to resolve the canonical, which is why a mismatched canonical can attach the wrong preview.
LinkedIn ignores twitter: tags. A page configured only for X will fall back to page title and description, which often produces a card that looks like a search result rather than a designed share.
Why changing the tag is not enough
The crawler fetches once. Editing the HTML does not notify LinkedIn, and no webhook pushes the change. Even after invalidation, the share composer can lag by minutes because the refresh runs asynchronously on their side.
The invalidation procedure
- 01 Open Post Inspector and paste the exact final URL, including https.
- 02 Press Inspect and wait for the card to render. This is the moment the cache is replaced.
- 03 Open a new post composer and paste the link again to confirm the new card.
- 04 If the card is still stale, the crawler fetched a cached CDN copy — purge the page at your CDN and repeat.
Use a new filename, not just a new tag
LinkedIn caches the image by URL. Replacing the file behind the same path leaves the old bytes in their cache until the next re-scrape. Publishing the new image under a versioned filename — og-card-v2.png — guarantees a cache miss even before invalidation.
What a clean LinkedIn card requires
- A 200 response with text/html, reachable without cookies.
- og:title under about 70 characters, or it truncates mid-word.
- og:description under about 160 characters for the large card.
- A 1200 × 627 image served over HTTPS with no redirect.
- og:url matching the canonical, with no trailing-slash mismatch.
Test the page with a crawler-style request before sharing: fetch the HTML, not the rendered DOM, and confirm those five items are present in the first response. If they are, invalidation is the only remaining variable.