Social and link preview

How to use it

1. 1Enter the address you want to checkType or paste it into the field marked "Address to check", including the https:// at the front. Use the exact URL people will share — the one that gets pasted into chat.
2. 2Press Check and wait a few secondsThe request runs from our server rather than from your browser, so your cache, your extensions and your login session cannot affect the answer. That is the point of it: you are seeing what an anonymous visitor sees.
3. 3Check the card against each platformOpen Graph drives most platforms and X reads its own tags with an Open Graph fallback. The preview shows what each would build, so a card that works in one place and breaks in another is visible.
4. 4Confirm the image is actually reachableThe most common broken card is a perfectly correct og:image tag pointing at a file that 404s, sits behind a login, or is too small. A tag that exists is not a tag that works.
5. 5Watch for the title that is right in the wrong placeA page can have an excellent SEO title and an og:title left over from a template. Shares use the second one, and nobody notices until a link goes out.
6. 6Share or keep the result within 24 hoursThe result has its own link you can send to whoever needs to act on it. It is deleted 24 hours after the check ran, so save anything you need to keep — and re-run the check after a change rather than trusting an old link.

About this tool

When someone shares a link on WhatsApp, Slack, LinkedIn, Facebook or X, the preview card they see is built from Open Graph tags in the page. This tool reads those tags, works out what each platform would actually display, and requests the preview image to confirm it exists.

It reads the raw HTML — and here that is not a limitation, it is the point. Social preview crawlers do not run JavaScript at all. Tags added by a framework after the page loads do not exist as far as any share is concerned.

Understanding the result

The card shown is built from the page's own declared image and text. If the picture does not appear here, it will not appear in a share either.

The per-platform table shows which tag supplied each value. A missing twitter:title is not a fault — X falls back to Open Graph — and the table makes that visible rather than reporting a tag you do not need.

The image is actually requested. A declared og:image that returns 404 produces a share card with a blank rectangle, and nothing on the page itself reveals the problem.

Example

https://example.com/article

og:title, og:description present · og:image missing
Facebook: title from og:title, image from nothing
X: falls back to og:* — no twitter:card declared
Critical: no og:image — the card will have no picture

Limitations

• Platforms cache preview data aggressively. After fixing a tag you usually need to ask the platform to re-scrape the URL before the new card appears; the old one can persist for days otherwise.
• Each platform renders cards slightly differently and changes its layout without notice. The preview shown here is representative, not pixel-exact.
• We check that the image exists and what it weighs, not its pixel dimensions. 1200×630 is the size that renders well nearly everywhere.
• Pages that vary their tags by visitor — by country, by login state — may serve us something different from what a given person sees.

Questions