Open Graph preview checker

Paste your live HTTPS URL and click Analyze page. Switch the platform tabs to see approximate card layouts for X, Slack, Facebook, LinkedIn, Discord, and WhatsApp. The metadata table lists every og: and twitter: tag in your HTML so you can fix missing images or titles before you share.

No tag is strictly required, but weak previews are common without them. At minimum, set og:title, og:description, and og:image (absolute HTTPS URL). Add og:url and og:site_name when you want a canonical share URL and brand label. Pair with twitter:card, twitter:title, twitter:description, and twitter:image for X and other Twitter-tag consumers.

A widely used default is 1200×630 pixels (1.91:1) in JPG or PNG under each platform's file-size limits. Facebook and LinkedIn documentation historically recommend similar large-image dimensions; X large cards expect comparable aspect ratios. This tool displays your declared image URL but does not verify file dimensions unless og:image:width and og:image:height tags are present in the HTML.

Open Graph (og:*) is the cross-platform baseline Facebook, Slack, and LinkedIn read. Twitter Card tags (twitter:*) control X-specific card types such as summary versus summary_large_image. When Twitter tags are absent, this tool falls back to Open Graph and the HTML title and meta description for preview text.

Social networks cache scraped metadata aggressively. After you fix tags, use each platform's sharing debugger or cache-clear tool to force a refresh. This checker shows what your HTML returns today; it does not purge Facebook, LinkedIn, or Slack caches. Layout also differs slightly from our stylized previews.

First confirm your live HTML is correct with Analyze page. Then request a re-scrape in platform-specific tools like Facebook Sharing Debugger or LinkedIn Post Inspector. If a platform has no public debugger, sharing a cache-busting URL variant (for example with a query parameter) can help trigger a fresh crawl.

Common causes: no og:image or twitter:image in the HTML; a relative URL that could not be resolved; an image host that blocks hotlinking or requires authentication; or the image failing in your browser (shown as an error placeholder). Use an absolute HTTPS image URL on a public CDN. Tags injected only by client-side JavaScript after load are invisible to Analyze page.

No. It reads the fetched HTML response and parses meta tags from that server-returned document. If your framework injects tags only after client-side hydration, many social crawlers can miss them too. Publish critical og: and twitter: tags in initial HTML whenever possible.

It parses standard meta tags from server-rendered HTML and approximates six platform layouts. It does not call Facebook, LinkedIn, or X APIs for official validation scores. iMessage, Telegram, and others may use different fallbacks. Treat warnings here as a fast preflight, then use each network's debugger when you need platform-certified results.

Analyze page sends the HTTPS URL to our server for a one-time HTML fetch. We do not persist page content or meta after the response. Localhost and private network hosts are blocked. Only analyze staging URLs that are already reachable on the public web; do not expose confidential paths you have not published.

The SERP snippet tool focuses on organic search title and description truncation in Google results, with pixel meters for desktop and mobile. This Open Graph checker targets social and chat link cards—og:image, twitter:card, and multi-platform share previews. Use both when you care about search listings and how links look in Slack or X.