Twitter or X card metadata audit
Check the fields that shape an X share card: `twitter:card`, title, description and image. Compare dedicated Twitter metadata with Open Graph and SEO fallbacks, preview large and summary card layouts, inspect image readiness and keep a copyable report for the publish checklist.
This checker keeps Twitter-specific fields visible even when a preview can fall back to Open Graph or page metadata. Platforms can cache old card data after a page changes.
What a Twitter Card preview should expose
A page can look fine in the browser and still share badly on X. The social card is built from a small set of metadata, and the weakest field often decides the result. A page may declare a card type but no image. It may inherit a decent title from Open Graph while the Twitter description is missing. It may use the SEO title as a fallback even though that title is longer than a compact social card needs.
This tool keeps those layers separate. It shows dedicated Twitter or X fields first, then the Open Graph and SEO values that can act as fallbacks. That distinction matters when you want deliberate share cards instead of previews that work by accident because another plugin or template happened to fill a nearby tag.
Card type, title, description and image work together
The card type sets the shape of the preview. A large image card is often useful for articles, tools and tutorials that benefit from a visual. A summary-style card can still be useful when the image is secondary. The copy should be page-specific either way. A short, concrete title tells readers what they are opening. A description should add the payoff or context rather than repeat the same noun phrase three times.
- `twitter:card` tells the card format the page is asking for.
- `twitter:title` gives X a deliberate title instead of only a fallback.
- `twitter:description` gives the share a concise human summary.
- `twitter:image` gives the card a visual that survives cropping.
- Open Graph fields should stay aligned when other preview surfaces read them.
How to review X card fallbacks
Fallbacks are useful but they should not hide quality problems. If your selected preview source says SEO fallback for every field, the card may still render, but your social metadata is not intentionally controlled. If the title comes from Twitter fields and the image only comes from Open Graph, that can be fine when it is planned. The source matrix makes that handoff visible before you share the URL in a post, direct message or campaign.
A practical publishing workflow
- Preview the exact public URL you plan to share.
- Check whether Twitter-specific fields exist, not only whether a card appears.
- Read the image in both large and summary-like card layouts.
- Compare the card title with the page topic so the click promise stays honest.
- Retest after metadata fixes and remember that platform caches can lag.
Common questions
Do I need Twitter tags if Open Graph tags exist?
Open Graph fallbacks can help, but dedicated Twitter or X fields give you clearer control over card type and copy. The right setup depends on the page template and how much social sharing matters for it.
Why does the checker say the image is missing when the page has images?
A page image in the body is not the same as a selected social card image. The preview needs a metadata image URL from a Twitter or Open Graph field to be predictable.
Should the card description be stuffed with keywords?
No. It should explain the page to a person deciding whether to click. Search metadata and social metadata can support SEO work without sounding mechanical.
What is the difference between summary and summary_large_image cards?
summary shows a small square thumbnail beside the text; summary_large_image shows a full-width banner image. Use the large image card for articles and visual content.
Do I still need Twitter card tags if I have Open Graph?
X falls back to Open Graph for most fields, so you mainly need twitter:card to pick the layout. Explicit twitter:title and twitter:image give you precise control.
Why is my X card not showing an image?
The image URL must be absolute and publicly reachable, the card type must be set, and X caches previews, so re-validate the URL to refresh it.
