Rich Link Preview Tester

What each platform will build from the tags your page actually has — including the fallbacks when tags are missing.

View the page source in your browser (Ctrl+U or ⌘+U) and paste the whole thing. Nothing is uploaded.

0Open Graph tags
0Twitter tags
0Missing essentials
Card type

Tags found

    Previews

    X / LinkedIn / Slack (large card)

    WhatsApp / iMessage (compact)

    What each platform will do

      Runs in your browser. The HTML you paste is parsed in this tab with the browser's own DOMParser, which builds an inert document — scripts in your markup never run and nothing is requested from the pages it references. That means you can safely audit a staging site, a client page behind a login, or an unpublished draft.

      What the rich Link Preview Tester does

      Every platform builds its link preview slightly differently, and every one of them falls back to something when a tag is missing. This tester extracts the sharing tags from your HTML, shows what each platform will find, and renders the card that results — including the degraded version you get when the tags are absent.

      The fallback chain is the part worth understanding. If og:title is missing, platforms use the <title> tag — which usually carries a | Brand Name suffix that is useful in a search result and wasted in a feed where the site name is already displayed. If og:description is missing, they use the meta description, written for a different audience. If both are missing, they scrape body text, and what they find first is often your navigation menu.

      The image is the tag that matters most. Without og:image, X, Facebook, LinkedIn and Slack all render a text-only card, and text-only cards are dramatically less likely to be clicked in a scrolling feed. The tool checks not only that the tag exists but that it is an absolute URL — a relative path is the most common reason an image tag is present and the card still comes out blank, because an external scraper has no base to resolve it against.

      Two previews are shown because platforms split into two families. X, LinkedIn and Slack render a large card with the image above the text. WhatsApp and iMessage render a compact card with a small thumbnail beside it, where the title has far less room. Copy that works in one can be truncated to nonsense in the other.

      How to use it

      1. Paste the HTML of the page you are about to share.
      2. Check the tags list for anything marked with an amber warning.
      3. Look at both previews — the compact one truncates titles much earlier.
      4. After fixing the tags and republishing, re-scrape the URL in each platform's own debugger to clear their cache.

      A worked example

      A page with only a title and meta description, and no Open Graph tags at all, produces:

      ✗ No image on any platform    Text-only card everywhere
      ! No og:title                 Falls back to "Best Running Shoes for Flat Feet in 2026 | Stride Lab"
      ! No og:description           Falls back to the meta description
      ! No og:url                   Tracking variants will not consolidate

      The card that results shows the full title including the brand suffix, in a context where the site name already appears above it — so “Stride Lab” is displayed twice and the headline is truncated to make room. Adding four tags fixes all of it, and the largest single improvement is the image.

      Frequently asked questions

      Why does the platform still show my old preview?

      Every platform caches scraped previews, sometimes for weeks. Use their debuggers to force a refresh: Facebook's Sharing Debugger, LinkedIn's Post Inspector and X's card validator. Until you do, everyone sharing your link sees the stale card.

      Can this tool fetch my live page?

      No. Browsers block cross-origin requests, so a client-side tool cannot fetch another site's HTML — any tool claiming to do so in the browser is either failing silently or routing through a server. Paste the source instead, which also lets you test staging pages.

      Do I need separate Twitter Card tags?

      Not usually. X falls back to Open Graph when Twitter tags are absent. Setting twitter:card to summary_large_image is worth doing explicitly to guarantee the larger layout; the rest are only needed if you want different copy for that audience.

      What size should the share image be?

      1200 × 630 pixels for large cards. Use an absolute URL, keep it under about 5 MB, and keep important content away from the edges since platforms crop to different ratios. Declaring width and height helps the card lay out before the image loads.