How to Use the X Card Validator to Check a Website Link Preview
Check a website’s social preview by inspecting its metadata, then compare it with the preview in X’s post composer. Here’s how to diagnose mismatches.
To check a website link preview for X, inspect the page’s social metadata with a URL preview checker, then paste the URL into X’s post composer and compare the draft preview when available. A third-party checker shows what its own fetch found; it does not guarantee that X will render the same card. The current official status and behavior of the former X Card Validator are not established by the official sources reviewed for this guide, so verify any tool’s destination before relying on it.
What an X Card Validator checks
A card validator fetches a page and reports metadata used for a social link preview, such as the card type, title, description, and image. Some tools also render those values as a preview card. This is useful for finding missing or unexpected metadata, but it is an independent diagnostic: X’s crawler, cache, or rendering behavior may differ from the tool’s. [ilo’s Twitter Card Validator]
The name “X Card Validator” can also refer to the former official validator. The available official evidence reviewed here does not establish whether that validator remains available or how it currently behaves. A third-party guide says the old validator no longer shows the preview and recommends checking the X composer, but that availability claim is not confirmed by current official X documentation. [Keywords Everywhere’s guide]
How to check a website link preview
- Make the page publicly reachable. Open the exact URL you intend to share in a private browsing window or another session without your site’s login. Check that it loads without a challenge page, access restriction, or redirect to a different page.
- Inspect the page with a preview checker. Enter the complete URL, including the scheme (
https://) and any path or query parameters needed to identify the page. Check the detected card type, title, description, image URL, and rendered preview. - Compare the report with the intended page. Confirm that the title and description describe this page, the image is the one you want, and the image URL is reachable. A checker reports what it fetched; it cannot prove that X fetched the same response or will display it identically.
- Check the draft in X. If the post composer is available, paste the URL into a draft and inspect the preview before publishing. This is a closer check of what X is showing for that draft than an independent renderer, though cache state and platform behavior can still affect the result. The composer workflow is described by third-party guidance, not confirmed in the official evidence reviewed here. [Keywords Everywhere’s guide]
- Diagnose any disagreement. First confirm the metadata and image the page actually serves. Then compare that with the draft preview. Record the exact URL and the values each tool reports so you can distinguish a page metadata problem from a difference in platform fetching, caching, or rendering.
Metadata to review
For a useful check, review the values the checker reports rather than treating its visual card as a pass/fail result.
| Value | What to check |
|---|---|
| Card type | Does the detected format match the kind of preview you expect? |
| Title | Is it present, accurate for this page, and free of a site-wide default that masks the page title? |
| Description | Does it summarize this page rather than showing an empty value or unrelated boilerplate? |
| Image | Is the detected image the intended one, and does its URL load publicly? |
| Fetched URL | Did the checker end up on the intended page after redirects? |
Do not assume that a preview tool’s refresh button clears X’s cache or forces X to scrape the page again. The official evidence located for this guide does not establish that behavior.
How to investigate a mismatch
- Copy the exact URL you tested and note any redirect, trailing slash, or query string.
- Use the checker’s report to identify the title, description, image, and card type it fetched.
- Open the page and image URLs directly in a browser session that is not signed in to your site. Look for access controls, an error page, or a redirect.
- Compare the checker’s result with the X composer preview, if available. If they differ, report the difference as a mismatch between the two observations; do not infer from the third-party result alone what X’s crawler received.
- If the X preview is missing or stale, make sure the page is publicly accessible and the page itself serves the intended metadata. Recheck later if platform caching may be involved, but do not promise a particular refresh or cache-clearing method without current official instructions.
X’s official developer data dictionary describes link data that can include a fully unwound URL and webpage title and description. It is useful context for link data, but it is not a current guide to an organic Card Validator. [X developer data dictionary]
Common problems and fixes
| Symptom | Likely cause | What to do |
|---|---|---|
| The checker cannot fetch the page | The URL is private, unavailable, or redirects somewhere the checker cannot access. | Test the exact URL in a signed-out browser and check its redirect destination. Make the intended page publicly reachable if it is meant to be shared. |
| The title or description is blank or wrong | The fetched page is serving missing, stale, or page-inaccurate metadata. | Compare the checker’s reported values with the page you intended to share. Check that the tested URL resolves to that page rather than a default or redirect. |
| The wrong image appears | The checker detected a different image URL than the one you expected, or the intended image is not publicly retrievable. | Inspect the reported image URL directly and confirm which image the page serves. Then compare the result with X’s draft preview when available. |
| The third-party preview and X composer disagree | They may have fetched or rendered the page differently, or platform caching may be involved. | Use the checker to diagnose page metadata and the composer to observe X’s current draft preview. Neither result establishes what the other system will show in every context. |
| A tool called “X Card Validator” is unavailable | The former official validator’s current status is not established by the official sources reviewed here; a third-party page may describe an old destination. | Verify the destination before entering a URL. Use a third-party metadata checker as a diagnostic and the X composer preview when available. |
Or skip the browser setup
If you need a screenshot of the page itself alongside its metadata check, ScreenshotNeo is a website screenshot API and MCP server. It captures a URL as PNG, JPEG, WebP, or PDF. A screenshot can help review what the page visibly renders, but it does not validate the metadata X uses for a link card.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers say the page verdict and whether the request was billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for 1,000 free screenshots a month, with no card required.
FAQ
Does a third-party card checker prove what X will show?
No. It shows what that tool fetched and rendered. X’s crawler, cache, and rendering can produce a different result.
Is the former official X Card Validator still available?
Its current status is unresolved in the official evidence reviewed for this guide. Third-party sources make claims about its availability, but those claims are not official confirmation.
Can a website screenshot API validate the link card?
No. A screenshot shows the page’s rendered appearance. A card checker inspects link-preview metadata, and X’s composer preview is the platform-side observation when available.
Does X’s website-card advertising guide explain organic link previews?
No. The official X Business troubleshooting PDF concerns website cards in the advertising workflow, so it should not be treated as evidence about organic card validation. [X Business website cards troubleshooting guide]
