Open Graph Preview

// One fetch, every platform's card

Every platform renders the same page differently: X reads twitter:* tags and falls back to Open Graph, while WhatsApp, Facebook, LinkedIn, Telegram, Discord, and Slack read og:* tags and fall back to the page's plain title and description (Telegram is the one that leads with og:site_name). This tool fetches your page once, applies each platform's real fallback chain, and renders the card each one would build — including the actual og:image, loaded live, so a broken image URL fails here instead of in your launch tweet.

Anything that would degrade the share is called out plainly: a missing og:image (most platforms render a bare text link), a relative image URL (some scrapers won't resolve it), a missing twitter:card, a description long enough to truncate.

// Why the previews sometimes differ from the real thing

These are faithful reconstructions of each platform's layout rules, not screenshots of the platforms themselves — fonts and pixel spacing are approximated, and platforms tweak their designs constantly. The tag resolution is the part that matters, and that follows each platform's documented behavior exactly.

Platforms also cache aggressively: if you've shared the URL before, they may keep showing the old card after you fix your tags. The per-platform list under the previews links each official debugger (Facebook Sharing Debugger, LinkedIn Post Inspector, Telegram's @WebpageBot) pre-filled with your URL, with honest notes for the platforms that don't have one.

// fair questions

Why does my page show no image here but an image on Facebook?

Facebook may be serving a cached card from a previous scrape, or guessing an image from page content when og:image is absent. This tool shows what your tags actually declare right now — which is what every platform will converge on after their caches expire.

The fetch failed on my site — now what?

Sites with bot protection sometimes block automated fetches. The Meta Tag Checker's paste mode accepts raw HTML and runs the same tag extraction locally; view source, copy, and paste there to audit the tags. The visual preview needs a fetchable URL.

What size should og:image be?

1200×630 (1.91:1) is the safe universal choice — it fills the large card on X, Facebook, and LinkedIn without cropping surprises. Keep the file under ~5MB and use an absolute https URL; several scrapers refuse relative or http image URLs.

Do I need twitter:* tags if I already have Open Graph?

Strictly, no — X falls back to og:* tags. Declaring twitter:card (usually summary_large_image) is still worth one line, because it makes the layout explicit instead of leaving it to fallback behavior.

Is my URL stored?

Fetched pages are cached briefly (minutes) so repeated checks don't hammer the target site, then expire. Nothing is stored beyond that and nothing is associated with you. Checks are rate-limited per visitor to keep the fetcher healthy.