X Card Metadata is the social markup — still written with twitter:-prefixed meta properties — that tells X how to build the preview card shown when someone shares a page’s link.
| Term | X Card Metadata |
|---|---|
| Category | Structured Data, Social and Media |
| Also known as | Twitter Card, X Cards |
| Where it appears | Social metadata factors |
What it means in RankGear
RankGear checks X Card Metadata as one of its Social metadata factors. Despite the platform’s rename from Twitter to X, the markup keeps its historical twitter: prefix in the page’s <head> — properties such as twitter:card, twitter:title, twitter:description, and twitter:image. When a link is posted, X reads these tags to decide whether to render a rich preview card and what title, summary, and image to place inside it. In an analysis, RankGear reports whether your page and the ranking competitors carry this markup, so you can see how the shared-link presentation of your page compares.
How to interpret it
Treat this as a presence-and-correctness check rather than a score. What matters is whether the exact property names are used, whether the values are well formed, and whether they describe content a visitor can actually see on the page. Markup that inflates or misstates the page — a card image or headline that does not match the real content — is the failure mode to avoid. Read the factor as “is the shared-link card set up properly,” and compare your page against the competitors that already carry complete, honest tags.
| Property | What it supplies to the card |
|---|---|
twitter:card | The card type X should render (for example a summary card with or without a large image). |
twitter:title | The headline shown on the shared-link card. |
twitter:description | The short summary line beneath the title. |
twitter:image | The preview image the card displays. |
Example
Suppose you analyze a product review page and RankGear flags that six of the eight ranking competitors declare a full set of twitter: properties while your page declares none. Shared on X, their links unfurl into image-led cards with a clean headline and summary; yours appears as a bare link with no preview. The report surfaces the missing markup as a gap to close — add the four core properties, point twitter:image at a real on-page asset, and confirm the title and description match what the page actually says.
Important considerations
- Adding the markup makes a page eligible for a rich card — it does not guarantee X will display one, since the platform controls final rendering and can fall back to a plain link.
- Values must describe visible, real page content; markup that introduces claims or media a reader cannot find on the page is the misuse this factor is meant to catch.
- Many pages let X fall back to their Open Graph tags, so absent
twitter:properties are not always fatal — but explicit X Card Metadata gives you direct control over the card. - Correlation is not causation: competitors carrying this markup is a comparative indicator drawn from the analyzed SERP, not a Google ranking score, and the tags do not by themselves make a page rank.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.