The most reliable twitter card preview takes two steps: run the page through an Open Graph checker such as seogeoaeo.ai's to catch tag and image problems, then paste the link into a draft post on X to see the real card. X stopped showing previews in its Card Validator in mid 2022, so no single method does everything any more. Here are four, ranked by how much they tell you before you post.

Rank Method Shows X's real card Explains a broken card Cost
1 seogeoaeo.ai Open Graph checker Approximate Yes 5 credits per run
2 X post composer Yes No Free
3 curl as Twitterbot No Partly Free
4 Slack message to yourself No No Needs a Slack workspace

1. seogeoaeo.ai Open Graph checker

Best for: finding out why a card looks wrong before X ever fetches it.

Enter a public URL in the seogeoaeo.ai card checker. It lists the twitter: and og: tags in the page head, shows which tag supplied each part of the card and draws an approximate large-image card. It flags a missing or unknown twitter:card, relative or http image URLs and duplicate tags, then downloads the picture and tests format, size and file weight against X's 5 MB cap and the limits of LinkedIn, Facebook and Slack. One run covers all four networks, from the browser, the REST API or MCP.

Where it loses points: the card it draws is an approximation, not X's exact layout, and it cannot reach localhost or clear a card X has already cached.

2. X's post composer

Best for: the final look.

This is the method X's developer team points to since it pulled the preview from the validator, explaining that the old previews did not match the apps. Start a post on x.com or in the app, paste the URL, wait for the card to appear, then delete the draft. What you see is what followers get.

Where it loses points: when the card is missing or shows the small summary layout, the composer gives no reason.

3. curl as Twitterbot

Best for: proving X can fetch the page.

X's forum suggests requesting the page with the Twitterbot user agent and checking for a 200 status, a valid Content-Type header and a twitter:card tag in the head:

curl -v -A Twitterbot https://www.example.com/page

That confirms the tags sit in the raw HTML, which matters because X's crawler does not run JavaScript.

Where it loses points: you get text, not a card, and nothing about the image.

4. Slack, pasted into a message to yourself

Best for: a rough sanity check when you already live in Slack.

Slack's link robot reads Twitter Card and Open Graph tags and fetches the image to check it, so a link that unfurls well in Slack has working basics. Slack caches unfurls for around 30 minutes, so a fix can take a while to show up there.

Where it loses points: the result is Slack's layout, not X's.

Why the old validator is not on the list

The address cards-dev.twitter.com/validator now redirects to an X login page, and X's own forum post says the preview function is gone. Guides that still send you there are out of date as of November 2026.

Get the card type right first

One tag decides the layout. X's Cards markup reference, archived in May 2025, says a page without twitter:card may get the small summary card even when its Open Graph tags are complete. Set twitter:card to summary_large_image for the wide card, and size the picture for 2:1. X falls back to og:title, og:description and og:image for the rest, so you rarely need to repeat them as twitter: tags.

If you only ever post to X and want zero setup, the composer alone will do. For anything you share across networks, start with the checker.