For X / Twitter Cards
Preview how your URL renders as a Twitter Card on X.
X looks for twitter:* tags first, then falls back to Open Graph. Most sites only need OG — twitter:* is for cases where you want a different preview on X.
summary_large_image is the card type that gets clicks. Default summary cards have small icons and underperform.
The fallback chain is worth knowing precisely: for each field, X checks the twitter:* tag first, then the og:* equivalent (twitter:title falls back to og:title, twitter:image to og:image, and so on). The one tag with no OG equivalent is twitter:card itself — the card type declaration. Without it, X may still render a card from OG data, but declaring twitter:card=summary_large_image explicitly is the reliable way to get the large-image layout.
X's card rendering has changed repeatedly in recent years — most notably, link cards on X have gone through periods of showing the image without the headline text overlaid, which shifts even more weight onto the image itself. Design og:image/twitter:image assets that communicate the story with zero caption support: legible title text baked into the image is the pragmatic response to a platform that keeps redesigning around your metadata (verify current rendering with a test post — it changes).
Like every scraper, Twitterbot reads server-rendered HTML only. SPAs that inject meta tags client-side produce blank cards; server-side rendering or prerendering fixes it. Twitterbot also respects robots.txt — a disallow rule that catches it is a surprisingly common cause of missing cards on otherwise well-tagged sites.
Card issues on X are harder to debug than they used to be: the official Card Validator's preview functionality was retired, so third-party tag checkers like this one plus a real test post from a private or low-stakes account are the practical validation workflow as of 2026.
Caching on X is real but shorter-lived than Facebook's or LinkedIn's. If you've fixed tags and the old card persists, give it time or test with a URL variant (adding a harmless query parameter forces a fresh scrape since the cache is keyed by URL) — a trick that works on most platforms when you need to see the corrected card immediately.
Verify large image cards render before tweeting your launch — a text-only launch tweet in the feed is a visibility tax you don't have to pay.
Confirm the card image and headline match the article on X, and that the image still tells the story if X renders it without overlay text.
Catch missing twitter:card meta before it costs you impressions — this tool shows exactly which tags the page serves right now.
Verify client-rendered sites serve meta tags to crawlers — the most common cause of blank X cards on modern frontend stacks.
Check that your twitter:* overrides (if any) and og:* base tags tell the same story, so shares look intentional on X, LinkedIn, and Slack alike.
Pre-configured variants tuned to specific platforms and use cases.
For LinkedIn shares
See how your URL looks when shared on LinkedIn — before you post.
Open variantFor Slack unfurls
Check how your URL unfurls inside Slack messages and channels.
Open variantFor Facebook shares
Inspect how your URL will render in a Facebook post or share.
Open variantFor Discord embeds
See how Discord embeds your URL inside a channel or DM.
Open variant