Social preview

See how a page looks when shared on social sites and chat apps, and which tags are missing.

A page URL or a domain; a domain means its home page.

A few free checks a day without an account. Sign in to use your credits.

What the social preview check tells you

When someone pastes a link into LinkedIn, X, Facebook, Slack or WhatsApp, the platform fetches the page and builds a small card from a handful of tags in its head: a title, a description, an image and the site name. Those tags decide whether the link looks inviting or like a bare address. The social preview check fetches the page the way those platforms do, reads the same tags, resolves them in the same order, and draws an approximate card for each platform so you can see the result before anyone shares it.

What we check

  • Open Graph tags. The og:title, og:description, og:image, og:url, og:type and og:site_name tags that most platforms read. We list every one we find, and flag duplicates of tags that should appear once.
  • X card tags. The twitter:card, twitter:title, twitter:description and twitter:image tags. X reads these first and falls back to Open Graph, so a page can work well on X with only Open Graph tags. We flag a card type X doesn't know.
  • How each field resolves. For the title and description we try the X tag, then the Open Graph tag, then the page's own title and meta description, and say which one won. For the image we try og:image:secure_url and og:image, then twitter:image.
  • The image itself. We fetch the image, follow its redirects and check that it loads, that it really is an image, how large the file is and its size in pixels. Images under 600 × 315 get small cards, images under 200 × 200 are ignored by most platforms, and files over 5 MB are often skipped. We also note an image far from the 1.91 to 1 shape platforms crop to, a relative address and an image served over plain http.
  • The page address. When og:url names a different page, shares of this page are counted for that one.

How images are shown

We never show the site's image directly. We fetch it once on our side, check it and make a resized copy of at most 600 pixels, stripped of its metadata, which travels inside the result. Your browser doesn't contact the site or the image host, nothing is hotlinked, and a shared report keeps its picture even if the site changes later. SVG images are never converted; most platforms don't show them, so we flag them instead.

Reading the result

The top of the result lists the resolved title, description and image, each with the tag it came from, so a missing og: tag that was quietly covered by the page title is easy to spot. Below it are five cards, one per platform, each marked as an approximate preview. Where a platform offers its own tool to read the page again, the card links to it: LinkedIn's Post Inspector and Facebook's Sharing Debugger both clear their cached card for a page. A collapsed table at the bottom lists every og: and X tag on the page with all its values.

Findings come with a fix and, for the common problems, a step-by-step guide. A page with no Open Graph tags, no image or an image that doesn't load are the ones worth fixing first; a long title or a slightly off image ratio are notes, not failures. The check has no score: it reports facts about the tags rather than grading the page.

What the check doesn't do

We fetch only the page you name and its preview image, with an honest user agent that links to a page about our checker. We don't run JavaScript, so tags added by scripts after the page loads aren't seen, and neither are they by most platforms. When a site blocks our checker or doesn't answer, the check stops with a plain message and you aren't charged. If the image can't be checked because it timed out or the host asked us to slow down, the result says so and is marked partial rather than claiming the image is broken.

Questions

Why does my preview look different on each site?
Each platform reads the tags in its own order and draws its own card. X prefers its twitter: tags, the others read og: tags first, and each crops the image a little differently. Our cards are approximations of the common layouts, built from the same tags.
I fixed the tags but LinkedIn still shows the old card. Why?
Platforms cache what they read, often for days. Use the refresh links under the LinkedIn and Facebook cards to ask them to read the page again. Our own answer is cached for 15 minutes; tick fresh to check again straight away.
Do you load my image in my browser?
No. We fetch the image once on our side, read its size, and show a small copy we made ourselves. Your browser never contacts the site or the image host, and a shared report carries the copy with it.
Can I check a page that isn't the home page?
Yes. Paste the full address. Results for pages other than the home page are kept per account, so nobody else can see that a particular page was checked.
How much does a check cost?
In the browser you get a few free checks a day without an account. Through the API or MCP a check costs 1 credit, and a cached answer costs the same. Checks that fail on our side, such as a site that doesn't answer, are free.