Open Graph & Twitter Card preview
Paste a URL. See exactly how Twitter, LinkedIn, and Facebook will render the link preview — with every og:* and twitter:* tag your page actually emits, plus every common mistake surfaced as an issue list.
Free. No signup. Rate-limited to 30 checks per IP per hour. Every fetch is server-side and SSRF-guarded.
Four ways social cards quietly break
og:image returns HTML, not an image. The most insidious failure mode: your og:image URL goes through a single-page-app catch-all route, returns text/html, and Twitter / Facebook silently refuse the preview. The page tag looks fine; the image just never shows up on social. This tool HEAD-probes the image URL and flags the content-type mismatch.
twitter:card mismatches og:image. You set twitter:card="summary_large_image"but forgot the image. Twitter degrades silently to the small “summary” card without telling you. We catch the inconsistency and flag it.
og:url disagrees with canonical. One URL form gets shared; a different one gets indexed. Engagement splits across two URLs that should be one. The tool checks both and reports any disagreement.
og:image too small. Below 600 × 315 pixels Facebook falls back to a small thumbnail. The recommended size is 1200 × 630 at 1.91:1. The checker reads og:image:width + og:image:height and flags anything below the cliff.
Common Open Graph questions
What is an Open Graph preview generator?
It fetches a URL, reads the Open Graph (og:*) and Twitter Card (twitter:*) meta tags from the HTML <head>, and renders the link preview exactly as Twitter, LinkedIn, and Facebook would show it. Useful before you publish — you see what the card looks like without having to post the link first.
Why does my og:image not show up on Twitter?
Three common causes: (1) the og:image URL returns a non-image content-type (an SPA fallback returning HTML is the most common silently-broken case); (2) the image is below 600 × 315 pixels — Twitter falls back to a small thumbnail; (3) twitter:card is set to "summary_large_image" but neither og:image nor twitter:image is defined, so Twitter degrades to the small "summary" card without telling you. This checker flags all three.
What's the ideal og:image size?
1200 × 630 pixels at a 1.91:1 aspect ratio. Facebook recommends this exact size; Twitter, LinkedIn, and Slack all render it correctly. Going wider than 2.1:1 or narrower than 1.7:1 causes the image to be cropped unpredictably on some platforms.
Do I need both og:* and twitter:* tags?
No — Twitter falls back to og:* values when twitter:* is not set. You only need to override the Twitter tags when you want a different title / image specifically for Twitter (e.g. a square image for the summary card). LinkedIn and Facebook ignore twitter:* entirely and use only the og:* values.
Why does og:url need to match my canonical tag?
Both should point to the same authoritative URL for the page. When they disagree, social platforms may scrape one URL and link to another, splitting engagement across two URL variants. Pick one form — typically the canonical — and use it in both places.
Why aren't my og:image dimensions detected?
The checker only reads og:image:width and og:image:height tags, not the actual pixel dimensions of the image. Always declare both — it prevents a layout shift in the card preview when the image loads, AND it lets validators (this one, Facebook's, Twitter's) report problems instantly.
Want the full audit, not just social cards?
A Seoxpert scan checks Open Graph plus 230+ other signals across SEO, security, performance, AI search readiness, and EU privacy compliance. Free first scan.