RevealTheme logo

LinkedIn Share Preview

Enter a URL and this tool fetches its HTML, reads the Open Graph meta tags, and renders an approximate LinkedIn share card so you can spot missing or wrong tags before you post.

How to use this tool

  1. 1

    Paste the full URL you plan to share (including https://) into the input field.

  2. 2

    Submit the form — the server fetches the page and parses its <head> for Open Graph tags.

  3. 3

    Review the simulated card: image, title, and description as built from og:image, og:title, and og:description.

  4. 4

    Scan the tag table below the card and fix any row flagged 'missing' in your page's HTML, then re-test.

How does a LinkedIn share preview work?

When you paste a link into a LinkedIn post, LinkedIn's crawler fetches the page and builds a card from Open Graph meta tags in the HTML <head>: og:title for the headline, og:description for the snippet, and og:image for the thumbnail. og:url, og:type, and og:site_name refine how the card is attributed. If og:title is absent, scrapers fall back to the <title> element; if og:image is missing, no thumbnail renders. This tool reproduces that lookup: it requests your URL server-side, parses the returned HTML with an HTML parser (cheerio), and pulls the same property meta tags. It then displays a card plus a full table of every og:* value it found, marking absent ones as missing. Two caveats matter. First, this is an approximation — LinkedIn enforces its own image rules (around 1200x627px, roughly 1.91:1, under 5MB) and may crop or reject images this preview happily shows. Second, the tool reads tags live from your current HTML; it cannot see or clear LinkedIn's cache. For a definitive render and to force a cache refresh, use LinkedIn's official Post Inspector.

Common use cases

  • Verifying a blog post or landing page has a proper og:image before announcing it to your LinkedIn network.

  • Debugging why a shared link shows the wrong headline or a blank thumbnail by checking which og:* tags are missing.

  • Auditing a batch of product or campaign pages so every shared URL renders a complete card.

  • Confirming a CMS or framework actually emits Open Graph tags in the server-rendered HTML, not just via client-side JavaScript.

  • Checking that og:title and og:description are concise enough not to be truncated in the LinkedIn feed.

  • Spot-checking a competitor's or partner's page to see how their links present when shared.

Frequently asked questions

Is this LinkedIn's official preview?
No. This tool independently fetches your page and reconstructs a card from its Open Graph tags. It approximates LinkedIn's layout but does not call LinkedIn. For the authoritative render, use LinkedIn's Post Inspector at linkedin.com/post-inspector.
LinkedIn shows the wrong image — why?
LinkedIn caches Open Graph data per URL, sometimes for weeks. If you updated og:image after a link was first shared, LinkedIn may still serve the old thumbnail. Run the URL through LinkedIn's Post Inspector to force a re-scrape; this tool always reads your current live tags but cannot clear LinkedIn's cache.
Which tags does this tool read?
It extracts og:title, og:description, og:image, og:url, og:type, and og:site_name from your HTML head, plus the page <title> as a fallback headline. The card uses og:image, og:title, and og:description; the table lists every og:* value found and flags any that are absent.
Why does it say my image is missing when the page clearly has one?
The tool only reads the HTML returned by the server. If your og:image tag is injected by client-side JavaScript after load, the crawler never sees it — and neither does LinkedIn. Render Open Graph tags server-side so they exist in the initial HTML.
What image size should I use?
LinkedIn recommends roughly 1200x627px (about a 1.91:1 ratio) and under 5MB. This preview does not validate dimensions, so an image that looks fine here can still be cropped or rejected by LinkedIn. Confirm sizing against LinkedIn's current guidelines.
Does this work for pages behind a login?
No. The tool fetches the URL anonymously, just as a public crawler would. Pages requiring authentication, or that block automated requests, will return an error or incomplete tags — which is also roughly what LinkedIn's crawler will see.
Is the URL I enter sent to a server?
Yes. Unlike browser-only tools, this one must fetch the target page server-side to read its HTML, so the URL is sent to this site's backend to perform the request. Avoid submitting URLs containing private tokens or session parameters.

Related tools