Is this the official Twitter/X Card Validator?

No. This is a RankGrow validator and preview tool. Use it to diagnose tags and preview output, then use the official X validator when you need X to refresh its cached card.

Does X still use Twitter Card tags?

Yes. X still reads twitter:card, twitter:title, twitter:description, twitter:image, and related tags for card previews.

Can Open Graph tags replace Twitter tags?

Open Graph tags can act as fallbacks, but explicit Twitter tags are easier to test and make rendering more predictable.

What image size should I use?

Use a wide image near 1200 by 630 pixels for summary_large_image cards. The validator warns below 300 by 157 pixels.

Why does the official preview differ from this preview?

The mock preview approximates the card from resolved metadata. X can still apply its own cropping, cache, content checks, and rendering changes.

Can the validator check private staging URLs?

No. The public endpoint blocks local and private network targets. Use a public preview URL for validation.

Does this refresh the X cache?

No. Cache refresh requires the official X card validator. This tool helps you fix the metadata before requesting that refresh.

Why is twitter:image:alt only a note?

The card can render without alt text, but adding it improves accessibility and gives the preview better context.

Twitter/X Card Validator & Preview

Check a public page for twitter:card tags, Open Graph fallbacks, image sizing, HTTPS image issues, and missing metadata before sharing it on X.

Refresh X cache in the official validator

What this validator checks?

Paste a public URL and see whether the page is ready to share on X - card type, title, description, image, and the tags that shape the preview.

Check a live page

Enter any public HTTP or HTTPS URL. The page needs to be reachable on the open web; local or password-protected staging URLs cannot be validated.

Review the resolved preview

See the title, description, and card type X would likely use, including when the page leans on Open Graph tags or plain page metadata instead of explicit Twitter tags.

Catch image problems early

Large summary cards need a shareable image. The validator flags missing images, non-HTTPS URLs, and sizes that are too small for a clear feed preview - aim for around 1200 by 630 pixels.

Fix gaps with a snippet

Copy a ready-to-paste block for any required Twitter tags that are still missing, so you can update the page head without rewriting everything else.

Twitter Card types supported by X

Most marketing and editorial pages use either summary or summary_large_image. Player and app cards are more specialized and require additional fields.

summary_large_image

Best for blog posts, landing pages, product updates, and reports. It gives the image the most room and usually produces the highest visual clarity in feeds.

summary

A compact card with a smaller thumbnail. It is useful for pages where the title and description matter more than an image.

player

Used for embedded video or audio experiences. It needs player URL, width, and height tags in addition to the standard metadata.

app

Used for app install cards. It requires platform-specific application IDs and is not the right choice for most SEO content pages.

Twitter Card tags that matter

A reliable implementation keeps Twitter tags explicit even when Open Graph tags already exist. That makes X rendering predictable and easier to debug.

Tag	Purpose
`twitter:card`	Selects the card layout, usually summary_large_image for marketing pages.
`twitter:title`	Controls the card title. Keep it concise enough to avoid awkward truncation.
`twitter:description`	Controls the card summary. Keep it direct, specific, and below 200 characters.
`twitter:image`	Points to the preview image. Use an absolute HTTPS URL and a wide image.
`twitter:image:alt`	Adds accessible image context and improves the quality of the preview for assistive technology.
`twitter:site`	Associates the card with the publisher's X handle.
`twitter:creator`	Associates the card with an author or creator handle when that differs from the publisher.

Why Twitter Cards fail?

Most broken X previews come from missing explicit tags, blocked images, stale cache, or image assets that are too small for large cards.

The preview still shows the old image

X caches card metadata. After fixing tags, use the official X validator to request a fresh crawl.

The image does not render

Use an absolute HTTPS image URL, avoid redirects to protected files, and make sure the asset returns an image content type.

The page falls back to Open Graph

Fallbacks can work, but explicit Twitter tags make behavior easier to predict when multiple templates or CMS plugins touch metadata.

The title gets cut off

Long titles are truncated in feeds. Keep the core search intent and value proposition near the front.

Audit every page before sharing

Link your site with Google Search Console and get a quick, actionable site audit - free to try.

Try for free See pricing

Loved by 100+ users

Frequently asked questions

Answers for the practical edge cases that usually slow down a social preview launch.