You post a LinkedIn update with a link. The preview card shows a blurry logo from three years ago, a title that has nothing to do with your post, or a completely blank image. You go to the source page, update the Open Graph tags, and share it again. LinkedIn still shows the old version. A week passes. Now it's correct, but your post is buried and the moment is gone.
This is not a glitch. It is how LinkedIn is designed to work, and understanding it is the first step to working around it.
Why LinkedIn Caches So Aggressively
When you paste a URL into a LinkedIn post, LinkedIn's crawler (called LinkedInBot) visits the page, reads the Open Graph tags in the HTML head, and stores what it finds: the og:title, og:description, og:image, and og:url. From that point on, every time anyone shares that URL on LinkedIn, the platform serves the cached version rather than re-scraping the page. The cache typically lasts several days, sometimes longer.
This is intentional. LinkedIn has hundreds of millions of users sharing millions of links every day. Without caching, every share and every feed load would trigger a fresh HTTP request to an external server. Caching is what keeps the system fast. The tradeoff is that when the metadata on a page changes, LinkedIn is slow to notice.
How to Force a Refresh
LinkedIn provides a tool specifically for this: the Post Inspector. Paste your URL, click Inspect, and LinkedIn re-scrapes the page immediately. After running it, wait a few minutes before publishing your post. The next share of that URL will reflect whatever the crawler found during the forced refresh.
The Post Inspector also shows you diagnostics: what og:title, og:description, and og:image LinkedIn found, whether any tags are missing, and whether the image met LinkedIn's minimum size requirements. If something looks wrong in the preview, this is where you find out why.
When Fixing the Source Isn't Possible
The Post Inspector is useful when you control the destination page. But most of the time, LinkedIn marketers are sharing URLs they don't own: a news article they want to comment on, a partner's landing page, a tool they're recommending, an affiliate or referral link. You cannot edit the Open Graph tags on someone else's site.
Referral and affiliate redirect URLs are the worst case. A link like go.example.com/ref/12345 typically has no OG metadata at all, because the redirect layer was never built to serve it. LinkedIn's crawler follows the redirect, hits the destination, and either renders the destination's generic metadata or produces a blank card. Neither option represents your endorsement well.
Even when a third-party page has technically correct OG tags, they're written for that site's purposes, not yours. A product page's og:title might be optimised for search. A news article's og:image might be the author's headshot. A SaaS tool's preview might show the pricing page rather than the feature you're recommending. The metadata exists, but it doesn't serve your post.
Why This Matters More on LinkedIn
LinkedIn's audience is professional. The people scrolling your feed are evaluating content quickly and making credibility judgements in seconds. A blank preview card or a generic company logo on a shared link signals one of two things: either the poster did not check what their link looked like, or the link leads somewhere generic and untrustworthy. Neither impression is the one you want to make.
On other platforms, a weak link preview might cost you clicks. On LinkedIn, it can cost you the professional credibility you have built with your connections. A polished preview card with a relevant image and a headline written for your audience signals that you know what you are doing. Over time, that consistency compounds into a reputation for sharing content worth reading.
Controlling the Preview Without Controlling the Page
The way to solve this is to separate the preview from the destination. Instead of sharing the raw URL and hoping its OG tags are appropriate, you create a hosted preview page that serves your custom metadata to LinkedIn's crawler and then redirects real visitors to the original destination. LinkedIn sees your title, your description, your image. Your audience clicks and lands on the page you intended. Nothing about the experience changes for them.
This is exactly what Prelinq does. You paste the destination URL, upload or select an image that fits the professional context of your post, and write the headline and description that frame the content for your specific LinkedIn audience. Prelinq gives you a new URL that carries your metadata. When LinkedIn's crawler visits it, it finds polished, relevant OG tags. When your connections click, they reach the original page.
Because the Prelinq URL is distinct from the destination URL, you also bypass LinkedIn's cache on the original. If you want to share the same article twice with different angles for different audiences, you create two Prelinqs with different headlines and images. Each one is a fresh URL that LinkedIn has never cached.
What to Do Before Your Next Post
Before you share any link on LinkedIn, run it through the Post Inspector first. If you own the destination and the tags are wrong, fix them, then re-inspect. If you don't own the destination, or the default preview just isn't right for your post, create a Prelinq with the image and copy that actually serve your audience. Share the Prelinq URL instead of the raw link.
Your LinkedIn posts are already competing for attention in a professional feed full of polished content. The preview card is the first thing your connections see. Making it deliberate takes about sixty seconds. Not making it deliberate means letting someone else's outdated metadata represent your recommendation.