See what your link looks like before you hit post.
Paste a URL. Previewcard fetches the page, reads the Open Graph and Twitter Card tags the way a social platform does, and tells you exactly what will show up — or what's broken.
The problem
Your page can be perfect and your card still broken.
An og:image that's a relative path, or a 404, or 200×200 when the platform wants 1200×630 — nothing on the page itself signals it. You don't find out until the post is already out.
What Previewcard checks
og:title twitter:title
Does the page have a dedicated title for social sharing? Which platform reads which tag, and what happens when one is missing?
og:description twitter:description
Is there a social description? Facebook, LinkedIn and Twitter use different fallback chains, and the result differs per platform.
og:image
Is the image URL absolute or relative? Does it resolve? What HTTP status does it return, what are its real dimensions, and are they large enough for each platform's requirements?
Relative URL 404 Too smallHow it works
Paste a URL
Enter any public URL — your own, a client's, a draft you are about to publish. No account needed.
We fetch and parse
Previewcard fetches the page, reads the <meta> tags with a streaming HTML parser, then fetches the image itself to confirm it resolves and reads its real dimensions.
See per-platform verdicts
Facebook, LinkedIn and Twitter each get their own analysis — which tags they will use, what the image looks like to them, and exactly what is missing or broken.
Why this matters
First impressions are final
Most people will decide whether to click based on the card they see in their feed. A missing image or truncated title costs that click.
You cannot un-share it
Once a link post is out, the broken card is public. Fixing the underlying page does not retroactively fix every share.
Platforms are not consistent
Twitter falls back to og:title when twitter:title is missing. LinkedIn ignores twitter:image entirely. A card that looks fine on one platform can be broken on another.
Silent failures
A relative og:image path passes every validator because the tag exists. The browser shows nothing. Only a real fetch to the resolved URL catches it.