Open Graph & social preview

See exactly how a page will look when someone shares it on Facebook, LinkedIn or X. We read the Open Graph and Twitter Card tags, render the share card, and flag any important tags that are missing so your links never show up plain.

How it works

  • We fetch the page and read its og: and twitter: meta tags, plus the <title>, meta description, canonical link and favicon.
  • The cards mirror how Facebook, LinkedIn and X build a share preview. When an Open Graph tag is absent we fall back the same way they do (og:title to <title>, og:description to the meta description).
  • X shows a big-image card only when twitter:card is summary_large_image; otherwise it uses a small summary card, which we render too.
  • Missing important tags are flagged with a short note on what they affect, so you know what to add.

After you fix your tags, re-run the tool to confirm the card looks right, then monitor the page with SiteGauge so you get alerted if the share card ever changes.

What to do with the results

  • Missing og:image: add one at 1200x630px on an absolute, publicly reachable URL. Without it, shared links show as plain text with no thumbnail, which gets far less attention.
  • Weak title or description: og:title and og:description do not have to match your SEO title and meta description word for word. Write them to earn a click on a social feed specifically.
  • Card still looks wrong on the real platform even though the tags check out here: the platform is very likely showing a cached copy. Force a re-scrape with Facebook's Sharing Debugger or the equivalent tool for the platform in question.
  • Everything present: re-check after any template, CMS, or redesign change, since Open Graph tags are easy to wipe out by accident and easy to miss because the page still looks fine in a browser.

Open Graph tags are exactly the kind of detail that goes unnoticed until a shared link looks broken. Ongoing SEO monitoring catches a wiped-out tag automatically instead of waiting for someone to point it out.

Frequently asked questions

Enter the URL and the tool fetches the page, reads its Open Graph and Twitter Card tags, and renders the share card the way Facebook, LinkedIn and X assemble it, applying the same fallbacks they do when a tag is absent (og:title falls back to the <title>, og:description to the meta description). You also get a table of every parsed tag and a list of missing ones, each with a note on what it affects.

Large share cards render at a wide 1.91:1 ratio, and 1200 by 630 pixels is the size the major platforms document as the safe choice. The image URL must be absolute and publicly reachable, because the social platforms' crawlers fetch it at share time. The preview here renders your image at that same ratio, so if it looks awkwardly cropped in the tool it will look wrong on the platforms too.

The usual causes are: no og:image tag at all, a relative rather than absolute image URL, an image the platform's crawler cannot fetch, or the platform holding a cached copy of your page from before you fixed it. This tool reads your live HTML, so if og:image is present and correct here but the share still looks plain, it is almost always the platform's cache: force a re-scrape with Facebook's Sharing Debugger or the equivalent for the platform concerned.

The twitter:card tag controls the layout on X. summary produces a small square thumbnail beside the text, while summary_large_image produces a full-width image above it, which is what most sites want for articles and landing pages. This tool renders whichever your page actually declares, and points it out when the large-image variant is not set so you can decide deliberately rather than by default.

Not directly: og: and twitter: tags are not ranking signals. They earn their keep in click-through, because a link with a proper image, title and description gets noticeably more attention when shared than a bare URL. They are also fragile: a template change or CMS migration can silently wipe them, which is why re-checking after every significant site change is worth the ten seconds it takes.