LinkedIn Post Inspector alternative: preview your LinkedIn link cards
LinkedIn's Post Inspector works, but it is slow, requires a LinkedIn login, and caches results aggressively. This free alternative fetches any URL using LinkedInBot's exact user-agent and shows you the raw HTML LinkedIn receives - including every Open Graph tag that drives your post preview.
For B2B companies, SaaS products, and professional services, LinkedIn is the most important social channel. A broken link preview directly undermines content marketing, company page engagement, and employee advocacy. If your og:title, og:description, or og:image tags are injected client-side, LinkedIn shows a blank card - or no card at all.
Paste a URL below to see what LinkedIn actually sees when your team shares a link.
How to use this tool
- 1
Enter the URL you or your team will post. LinkedInBot is preselected on this page.
- 2
Click 'Simulate crawl' to fetch the page with LinkedIn's user-agent.
- 3
Check the 'Social preview card' for the title and image LinkedIn would attach to the post.
- 4
Read through 'Open Graph tags detected'. LinkedIn looks for og:title, og:image, og:description and og:url in the HTML it receives.
- 5
After a fix, paste the URL into LinkedIn's Post Inspector to refresh its stored copy before anyone shares the link again.
How it works
We request the page with the header 'LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://www.linkedin.com)' and parse the Open Graph tags out of the returned HTML. The preview card is built only from what that single response contains.
LinkedIn keeps the preview data for a shared URL for about seven days, which is why an old image can keep appearing after you have changed the page. Running the URL through Post Inspector fetches it again and updates the stored copy.
LinkedIn's own guidance is an image with a 1.91:1 ratio at 1200 by 627 pixels, and it may leave the image out if the file is too small or cannot be fetched. Titles and descriptions are cut short in the feed, so put the important words first. If this test shows the tags but your posts still appear without a card, the usual cause is a redirect, a cookie wall or a firewall rule that treats LinkedInBot differently from our request.
Understanding LinkedIn
LinkedIn is the primary professional networking platform with over 900 million members. When you share a link in a LinkedIn post, article, or message, LinkedInBot fetches your page to generate a link preview card with a title, description, and image.
LinkedInBot does not execute JavaScript. It reads the raw HTML response and extracts Open Graph meta tags (og:title, og:description, og:image) to build the preview. If these tags are injected client-side by a JavaScript framework, LinkedIn shows a generic preview - typically just the URL with no image, no title, and no description.
For B2B companies, SaaS products, and professional services, LinkedIn is often the most important social channel. A broken link preview on LinkedIn directly impacts content marketing effectiveness, company page engagement, and employee advocacy programmes. When team members share company links and the preview looks broken, it undermines credibility.
Pre-rendering ensures LinkedInBot sees your OG tags in the raw HTML, producing rich, professional link previews that drive clicks and engagement on the platform where your professional audience lives.
Frequently asked questions
Why do my LinkedIn post previews look broken?▾
LinkedIn's crawler reads OG tags from raw HTML only, without executing JavaScript. If your React, Vue, or Angular app injects OG tags client-side, LinkedIn cannot see them. This results in a generic or missing preview.
How do I refresh a cached LinkedIn preview?▾
Use LinkedIn's Post Inspector tool (linkedin.com/post-inspector) to force a fresh crawl of your URL. If your OG tags are still missing from the raw HTML, the preview will remain broken until you implement pre-rendering or server-side rendering.
Does LinkedIn support Twitter Card tags?▾
LinkedIn primarily reads Open Graph tags (og:title, og:description, og:image). It falls back to the page title and meta description if OG tags are missing, but does not support Twitter Card-specific tags.
Related crawler tests
Facebook debugger alternative
Preview how Facebook and Messenger display your shared links. Facebook's crawler reads Open Graph meta tags from the raw HTML - it does not execute JavaScript, so dynamically-injected OG tags will not appear.
Social mediaTwitter Card validator
See how your links appear on Twitter/X. Twitterbot reads Twitter Card meta tags from static HTML. Client-rendered meta tags are invisible to this crawler, resulting in missing images and descriptions in tweets.
Social mediaWhatsApp link preview debugger
Preview your link as it appears in WhatsApp messages. WhatsApp fetches the page itself when a link is pasted and does not execute JavaScript. Missing OG tags mean no thumbnail, no title, and no description in chat.
Social mediaRelated free tools
What bots see
Enter any URL and see the raw HTML that search engine bots, AI crawlers, and social platforms receive - before and after JavaScript rendering.
Try it freeOG image checker and Open Graph debugger
Test your Open Graph and Twitter Card meta tags. Preview exactly how your links appear when shared on Facebook, LinkedIn, Twitter/X, and WhatsApp.
Try it freeSEO audit
Run a free SEO audit on any website. Check meta tags, headings, structured data, alt text, canonical URLs, and crawler accessibility.
Try it freeLLMs.txt generator
Build a valid llms.txt for your site - the proposed standard that helps AI assistants navigate your content. Spec-compliant, copy or download.
Try it freeMeta tag checker
Test every SEO and social meta tag on any page. Title, description, canonical, robots, viewport, Open Graph, Twitter - with bot-eye-view validation.
Try it freeLovable SEO audit
Audit any Lovable site for the JavaScript SEO problem. Lovable apps render in the browser - bots see an empty shell. This tool shows you what's missing.
Try it freeMake every crawler see your content
PageGlass automatically serves rendered HTML to all bots. No per-crawler configuration needed - one simple change covers Googlebot, AI crawlers, and social platforms.