2 min read
You updated your og:image or title, shared the link on LinkedIn — and the old preview still appears. This is almost never a bug in your code. LinkedIn caches Open Graph data aggressively.
How LinkedIn caching works
When a URL is shared for the first time, LinkedIn's crawler fetches the page and stores the OG metadata. Subsequent shares of the same URL reuse that cached snapshot — even if you changed the tags minutes ago.
Cache duration varies but can last days to weeks for high-traffic URLs.
Force LinkedIn to re-scrape
- Go to the LinkedIn Post Inspector.
- Enter your URL and click Inspect.
- Review the fetched title, description, and image.
- Click Refresh if the data is stale.
This forces LinkedIn to re-fetch your page and update the cache.
What to verify before refreshing
Make sure the live page actually serves the new tags:
- View page source — confirm
og:title,og:description, andog:imagereflect your changes. - Open
og:imagedirectly in a browser — confirm the new image loads. - Check that your CDN or hosting is not serving a cached HTML response to bots.
Common reasons refreshes still fail
| Issue | Fix |
|---|---|
| Tags only updated in JS, not server HTML | SSR or static meta tags in <head> |
| CDN caches old HTML for bots | Purge CDN cache or exclude bot user agents |
og:image URL unchanged but image file replaced | Use a new filename or add a version query (?v=2) |
| Redirect chains confuse the crawler | Point og:url to the final canonical URL |
| Image too large or slow | Optimize to 1200 × 630, under 1 MB |
LinkedIn image requirements
LinkedIn recommends 1200 × 627 px images. Formats: JPG, PNG, or GIF. Minimum width: 200 px. Images smaller than 1200 × 627 may appear with letterboxing.
Prevent future cache headaches
- Use versioned image filenames when updating OG images (
og-v2.jpg). - Set
og:urlto a stable canonical URL. - Test with OpenGraph Check after every deploy to confirm crawlers see the latest tags.
