Every shared link's social meta tags: resolved, fetched, measured.
Paste a URL. Previewcard fetches the page, resolves every Open Graph and Twitter Card tag relative to it, fetches each referenced image, and reports its real HTTP status and pixel dimensions — platform by platform, tag by tag.
Illustration — use the live app to run a real check.
What the report looks like
url: https://example.com/article
upstream: 200 (reliable)
title: "Example Article — A Deep Dive"
og:title ✓ present
og:description ✓ present
og:image ✓ resolved → https://example.com/hero.png (1200×630, 142KB, HTTP 200)
og:url ✓ present
og:type ✓ present
og:site_name ✓ present
twitter:card ⚠ present → "summary_large_image"
twitter:image ✓ resolved → (same as og:image)
twitter:title ✗ missing
1 of 10 required social tags missing.
title: "Example Article — A Deep Dive"
og:title ✓ present
og:description ✓ present
og:image ✓ resolved → https://example.com/hero.png (1200×630, 142KB, HTTP 200)
og:url ✓ present
og:type ✓ present
og:site_name ✓ present
twitter:card ⚠ present → "summary_large_image"
twitter:image ✓ resolved → (same as og:image)
twitter:title ✗ missing
1 of 10 required social tags missing.
How the check works
1
Fetch the page. Previewcard requests the URL with a 15-second timeout, following redirects. If the page cannot be reached, the report says so — no fabricated findings about tags.
2
Parse every meta tag. Every
<meta property> and <meta name> is extracted. Tags are classified by platform: Open Graph (og:), Twitter Card (twitter:), or standard HTML meta.
3
Resolve image URLs. Relative
og:image and twitter:image paths are resolved against the page URL. A relative path is the most common cause of a broken card — Previewcard catches it.
4
Fetch each image. Every referenced image is fetched. Its HTTP status, pixel dimensions (JPEG, PNG, GIF, WebP), and byte size are reported. A 404 image is reported as 404 — not silently ignored.
5
Report missing tags. Required social tags that are absent are listed explicitly. Previewcard never substitutes the HTML
<title> and presents it as an Open Graph title — it reports what the page declares, not what a platform might fall back to.
What the checker does
-
Platform-by-platform reporting Results are grouped by vocabulary (Open Graph, Twitter Card, standard meta). Each platform's tags are listed together so you can see at a glance what each social network will use.
-
Image dimension verification Previewcard fetches the actual image and reads its width and height from the first bytes of the file. A 200×200 image when the platform expects 1200×630 is flagged — no guesswork.
-
Relative URL resolution An
og:imageset to/images/hero.pngis resolved against the page URL. The report shows the full absolute URL and whether the image loads. -
Upstream reliability flag If the fetched page returned a non-2xx status, the report notes that the tag values might be from an error page. Findings are marked as potentially unreliable.
-
Graceful error handling If the page times out, the domain does not resolve, or an image cannot be fetched, the report says so in plain terms. A network failure is never described as a finding about the user's tags.
Try it now
Paste any URL and see what its social meta tags contain — resolved, fetched, and measured.
Open the app