Check two separate things: whether a page supplies usable card metadata, and whether X can fetch and display it. A validator or source inspector can help with the first task without guaranteeing a live preview.
What you are testing
A link card is generated from a destination page. It is different from an image you attach to a post. Card type, title, description and image tags are useful diagnostic inputs. A valid page can still fail to display a card because of access restrictions, redirects, cached data or platform behavior.
Inspect the returned HTML
This is an illustrative large-image metadata pattern. Replace the example values and test the returned page; it is not a guarantee of X’s final layout.
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="A clear page title">
<meta name="twitter:description" content="What the reader will find">
<meta name="twitter:image" content="https://example.com/card.jpg">Use one coherent set of tags in the document head. Check for duplicate values from plugins or templates. Open the absolute image URL directly. A file that requires a login or returns an error page will not become a usable preview image merely because its URL ends in .jpg.
Try the validator, then use fallbacks
The legacy X Card Validator may require access or may not provide the preview you expect. Its preview behavior was not confirmed in this review. If it is unavailable, inspect the server’s returned HTML and test a public URL in the actual X composer. Do not submit private preview links or access tokens to an unfamiliar checking service.
Work through fetch failures
| Symptom | Check next |
|---|---|
| No card | Public response status, login wall, robots rules and crawler blocking |
| Wrong title or image | Duplicate tags, final redirect destination and cached values |
| Image fails | Direct image response, content type, access and dimensions |
| Works in a browser only | JavaScript-generated tags, cookies, firewall or bot challenge |
A successful browser visit does not prove an unauthenticated crawler receives the same HTML. Ask the site owner to inspect server logs when access is unclear.
A repeatable publishing check
- Record the exact page URL and its final redirect target.
- Inspect the initial HTML response and image response.
- Fix metadata at the template level if several pages share the issue.
- Check the real composer or post when accessible.
- Save the date and a screenshot of the observed result.
Use a new image URL when you deliberately version an asset, but do not promise that this forces every cache to refresh.
Limits of card validation
There is no guaranteed refresh time established here. Open Graph tags can support other platforms, but their presence does not prove X displayed a card. Use website analytics for destination visits and define any click-rate denominator. Tweet Archivist is not presented here as an automated card validator, monitoring service or preview-alert tool.