A LinkedIn post can carry your sharpest announcement, best article, or strongest case study - then arrive as a blank gray card, an old thumbnail, or a random logo pulled from the page. That is exactly the problem to solve when you need to fix LinkedIn link preview image behavior. The issue is rarely LinkedIn itself. It is usually a missing, blocked, outdated, or overwritten Open Graph image.
For a founder or content team, this is not a cosmetic detail. A link preview is the first piece of your site people see in the feed. If it looks broken, generic, or stale, the post loses credibility before anyone has read the headline.
Why LinkedIn Shows the Wrong Preview Image
LinkedIn builds its link card by reading Open Graph metadata from the URL you share. The key field is `og:image`. Your page should also provide `og:title` and `og:description`, but the image gets most of the attention in a fast-moving feed.
When LinkedIn cannot find a usable `og:image`, it may show no image, select an image from the page, or keep showing a previous version from its cache. That is why a page can look perfect in your browser while the LinkedIn preview still looks wrong.
There are four common causes:
- The page has no `og:image` tag, or the tag points to the wrong file.
- The image URL is inaccessible to LinkedIn's crawler because of login requirements, bot protection, redirects, or server errors.
- Your CMS, SEO plugin, theme, or code is outputting multiple conflicting Open Graph tags.
- LinkedIn has cached the old card and has not fetched your new metadata yet.
Treat these as separate problems. Changing the image in a CMS will not help if the crawler cannot access it. Refreshing LinkedIn's cache will not help if the page still serves an old `og:image` tag.
Fix LinkedIn Link Preview Image Problems Step by Step
Start with the exact URL you plan to post. Small URL differences matter. Your homepage, a URL with a trailing slash, a campaign URL with parameters, and a redirected URL can each produce different metadata or cached previews.
1. Check what your page actually publishes
View the page source, not only the visible page. Search for `og:image`. You want one clear image URL in a tag that looks like this:
``
The URL should be absolute, meaning it starts with `https://`, not `/images/card.jpg`. It should point directly to an image file or an image endpoint that returns an image reliably.
Also check for `og:title` and `og:description`. LinkedIn needs a complete card, and a mismatched title or description often signals that another plugin or template is controlling the metadata.
If you find two or more `og:image` tags, do not assume LinkedIn will choose the one you want. Different crawlers may interpret duplicates differently. Find the source of each tag and remove the conflict. In WordPress, the overlap may come from an SEO plugin plus a social-sharing plugin or theme. In a custom app, it may come from a global layout and a page-level component both rendering metadata.
2. Use an image built for the card, not a leftover page asset
A tiny square author photo, a tall blog image, or a transparent logo is technically an image. It is not necessarily a useful LinkedIn preview.
For most shared pages, use a 1.91:1 landscape image. A 1200 by 627 pixel image is a dependable target. It gives LinkedIn enough resolution to render cleanly while keeping the composition familiar across social platforms.
Put the page title, key visual, and brand elements inside the safe center area. Avoid placing essential text near the edges. LinkedIn's display can change with feed placement, screen size, and other platform-specific behavior.
The best card answers three questions at a glance: what is this page, who made it, and why should I click? A large readable headline, a relevant visual, and restrained brand treatment will usually outperform a screenshot of the page or a logo floating in empty space.
3. Make sure LinkedIn can fetch the image
Paste the `og:image` URL into a private browser window. If it does not load without signing in, LinkedIn likely cannot load it either.
The image must be publicly available over HTTPS and return a successful response. It should not require cookies, session data, a referrer, or JavaScript to generate. Your server should return an image content type such as JPEG, PNG, or WebP, rather than an HTML error page disguised behind an image URL.
This is where modern site setups can get tricky. A CDN rule, firewall, rate limit, hotlink setting, or bot-management product may block social crawlers. A staging-domain image URL accidentally published on a production page creates another quiet failure. If your card generator uses signed or short-lived image URLs, LinkedIn can cache a URL that expires later.
Dynamic images are fine when they are rendered reliably before the crawler requests them. The trade-off is operational: a custom image-generation service gives you flexibility, but it also adds another endpoint that must stay fast and publicly accessible.
4. Refresh LinkedIn's cached version
Once the live page source and image URL are correct, use LinkedIn's Post Inspector to inspect the URL. It shows the metadata LinkedIn detects and prompts a new scrape. This is the fastest way to replace a stale preview after you have fixed the underlying page.
Do not rely on repeatedly pasting the link into a draft post. LinkedIn may continue showing a cached card there. Inspect the canonical page URL first, then create a fresh post after the debugger reports the right title, description, and image.
If the inspector still displays the old image, verify that the page itself is not cached upstream. Your browser may show a new page while a CDN serves the crawler an old HTML document. Purge the page cache where necessary, then inspect again.
5. Check redirects, canonical URLs, and JavaScript rendering
LinkedIn reads the URL you share, including any redirects. A long redirect chain can complicate debugging, especially if the destination has different metadata than expected. Share the final canonical URL whenever possible.
JavaScript-only metadata is another frequent issue. If your site inserts Open Graph tags after the page loads in the browser, a crawler may never see them. The tags need to be present in the initial HTML response. For Next.js and other app frameworks, render page-specific metadata on the server or through the framework's supported metadata system.
A fast test is simple: if `og:image` is missing from View Source but appears in browser developer tools after the page runs, it is too late for dependable link previews.
Stop Recreating Cards One URL at a Time
Fixing one broken post is useful. Fixing the process is better.
Manual Canva exports work for a launch page or occasional announcement. They become fragile when your site publishes dozens of blog posts, changelog entries, docs pages, products, or programmatic landing pages. Someone has to name files, upload them, connect them to the right URL, and remember to update them when the headline or offer changes.
A scalable setup uses a single branded card design and maps live page data into it: page title, featured image, author, price, date, category, domain, or URL. Design once, connect once, and every page gets its own OG image. You keep editorial control without turning social previews into recurring production work.
That is the operating model behind getwowlink: branded Open Graph images are generated and hosted from your site data, while your existing CMS and SEO workflow stay in place. It is particularly useful when content volume is high or several people publish pages without a designer or developer reviewing every share card.
A Better Pre-Publish Check
Before promoting a major URL, verify the live canonical URL, inspect the Open Graph tags in source, and run it through LinkedIn's Post Inspector. Then check the preview on a phone as well as desktop. A card that is technically valid can still have a headline that is too small or an image crop that hides the point.
For evergreen sites, audit older high-traffic pages too. They are often the URLs that get shared most, and they are the most likely to carry legacy plugin settings, weak images, or expired asset paths.
Your LinkedIn card should not be a surprise discovered after publication. Make it part of the page itself, so each shared URL arrives looking like it belongs to your brand - clear, current, and worth the click.