How to test your link preview before you share it anywhere
Do not debug your link preview live in front of an audience. Test it first: render it in a preview tool, fix what is wrong, and force a fresh scrape so a stale card does not haunt you. Here is the fast way to check before you post.
Last updated June 17, 2026Before sharing your launch, test how the link card renders, because fixing it live in front of an audience is the worst time to discover it is broken. Use a third-party link-preview tester (the official X card validator’s preview is deprecated) and the Facebook Sharing Debugger to see the card and force a fresh scrape. Watch for the caching gotcha: platforms cache previews, so an old or broken card can persist after you fix the tags. Re-scrape, and version your image URL if the image changed.
- Test before you post. A broken card discovered after launch has already cost you the best-shared moment you get.
- Use third-party preview tools and the Facebook Sharing Debugger. X retired the preview in its own card validator, so use a replacement.
- Caching is the gotcha: platforms cache the first scrape, so fix the tags then force a re-scrape, or you will keep seeing the old card.
- Quick private test: paste the link into a private Slack or Discord channel to see the real card without an audience.
Do not debug your link preview live in front of an audience. The moment you announce your launch is the moment the most people will ever paste and see your link at once, and discovering then that it renders as a bare URL or a broken image is the worst possible time. Test it first. Here is how to preview the card, the caching gotcha that makes a fixed card still look broken, and the checklist to run before you post anywhere.
01 · See the card firstPreview it before you post
You can see exactly how your card will render without sharing it publicly. Two approaches:
- Link-preview tools. Paste your URL into a third-party Open Graph or X card preview tool. It fetches your Open Graph and
twitter:tags and renders the card as it will appear across platforms, flagging anything missing. - The Facebook Sharing Debugger. It reads your OG tags, shows the card, lists warnings, and, crucially, lets you force a fresh scrape.
X retired the preview functionality of its own card validator, so it will not show you a visual card anymore. Use a third-party X or Open Graph preview tool instead; they read the same twitter: and og: tags and render the result. The tags themselves are unchanged, so this is purely about which tool you check them with.
For a real-world test, paste your link into a private Slack or Discord channel and look at the actual card the platform draws. It is the truest preview there is, and nobody sees it but you.
02 · Why a fixed card still looks brokenThe caching gotcha
This is the part that wastes an afternoon if you do not know it. Platforms scrape your tags once and cache the result, so after you correct your Open Graph tags, the old, broken card can keep appearing because the platform is serving its cached version, not re-reading your page.
The fix is to force a re-scrape. The Facebook Sharing Debugger has a “Scrape Again” button, and most preview tools offer a refresh. If the problem is specifically the image, change its URL, for example og.png?v=2, because platforms cache by image URL and will treat a new URL as a new image. Re-scrape after every change until the preview shows what you expect.
03 · Four things to confirmThe pre-launch checklist
Run this once before you share your launch anywhere:
- The card renders fully, with a title, description, and image, not a bare URL.
- The image loads and is correct: an absolute HTTPS URL, sized 1200x630.
- The tags are in your server-rendered HTML, so scrapers that do not run JavaScript can see them.
- You have re-scraped, so no stale cache is showing an old version.
Tick those four and your link will look like a real product the moment it matters most, which is the entire point of getting your Findable signals right before launch rather than after.
Common questions
og.png?v=2), since platforms cache by image URL.twitter: and og: tags and renders the card. The underlying tags are unchanged; only X’s own preview tool went away, and several free replacements cover the same job.Get your free launch-readiness score
See what else is between your product and its first real users — Nilkick scores your readiness and hands you the map. Free, no login.
https:// optional · no account · we don't email you
Why your link looks broken when pasted, and the Open Graph tags that fix it
When your link shows up as a bare URL in Slack or X, you are missing Open Graph tags. The four that matter, the X card tag, and why they must be in your server-rendered HTML.
The Open Graph image that actually gets clicks
Your OG image is the biggest element of a shared link card. The specs that matter (1200x630, absolute HTTPS URL), what makes one earn a click, and the mistakes that waste it.
The default-deploy metadata that screams "unfinished"
A 'Vite App' title, a missing description, a globe favicon, a bare-URL link card: the default metadata that ships with a template and tells everyone you never finished. The tells, and the 15-minute fix.