Langues

Guide : Twitter Card Tags (X Cards): The Current, Honest Guide

Ce que twitter:card meta tags do, the four card types, the Ouvrir Graph fallback rule, and ce que X en réalité broke — the dead validator, the vanished Cards docs, and link-post reach effects (a separate system from card rendering). Pas a ranking factor.

Première publication : 2 juil. 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues
AIRédigé parAI v2

Twitter Card tags are <meta name="twitter:..."> elements que tell X's link-unfurling system ce que preview to construire pour a shared URL. Four card types: summary, summary_large_image (the par défaut pour articles), app, and player — ces are the dernier documented types; aucun current official X specification exists to reconfirm les contre. Every twitter:* property falls back to its og:* counterpart si manquant — except twitter:card itself, qui has aucun fallback and doit be définir explicitly. Utiliser nom=, pas property= (mixing les up obtient the tag silently ignored) — long-standing, consistently practitioner-reported behavior. What's modifié since the Musk-era rebrand and matters la plupart in 2026: the official Card Validator was deprecated in 2022 and its URL now redirections to an X login page; developer.x.com's Cards docs now redirection to a generic page with aucun Cards content; twitter:site/twitter:creator attribution has degraded; and X s’applique confirmed reduced reach to some external-link posts — a separate system from si the card itself renders, so don't utiliser un to diagnose the autre. Pas a Google or Bing ranking factor: Google's supported-meta-tags référence jamais mentions twitter: or og: at tout. Valeur is social CTR seulement. Ce is a deep dive sous the Meta Tags pour le SEO hub.

TL;DR — Twitter Card tags are <meta name="twitter:..."> elements que drive X’s lien unfurling. Four card types (the dernier documented définir — aucun current official spec exists to reconfirm les): summary, summary_large_image (recommended pour articles), app, player. Every twitter:* property falls back to its og:* counterpart — except twitter:card, qui has aucun fallback and doit be explicit. Utiliser name=, pas property= (the unique la plupart courant silent-failure causer). Ces tags are social-preview metadata, pas documented Recherche Google contrôle; Google’s supported-meta-tags référence ne fait pas liste twitter: metadata.

Evidence for this claim X Cards use page metadata to select a card type and populate a shared-link preview. Scope: X link-preview markup behavior; rendering and product features can change. Confidence: medium · Verified: X Developer Platform: Cards markup Evidence for this claim Google's supported-meta-tag reference does not treat twitter card metadata as a Google Search control. Scope: Absence from Google's supported search-control tags supports no direct Google metadata behavior, not a universal claim about social signals. Confidence: high · Verified: Google Search Central: Meta tags and attributes

Ce que ils are and the four card types

Twitter Card tags tell X’s link-unfurling system ce que rich preview to construire pour a shared URL. The type is définir with the requis twitter:card property, and là are four:

  • summary — a petit square thumbnail suivant to the title and description.
  • summary_large_image — a grand, full-width image. The recommended par défaut pour articles and blog content, and the un la plupart publishers vouloir.
  • app — a mobile app install card.
  • player — an inline video/audio embed, driven by twitter:player (an iframe URL) and twitter:player:stream (the raw mediune URL). Encore functional, though the public documentation pour it has thinned considerably.

Ces four are the dernier documented X/Twitter Card types. There’s aucun current, official specification to reconfirm les contre (voir the status section ci-dessous), so treat ce as the legacy documented contract, encore consistently reported as accurate by current practitioner sources. summary and summary_large_image are the two you’ll en réalité utiliser pour normal content and the ones current guides discuss la plupart; app and player are practitioner-documented but harder to vérifier live sans an official référence.

The core properties:

PropertyCe que it sets
twitter:cardThe card type (requis, aucun fallback)
twitter:titleThe headline
twitter:descriptionThe description text
twitter:imageThe preview image URL
twitter:siteThe publisher’s @handle
twitter:creatorThe author’s @handle

How to implement les

A summary_large_image card in complet:

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@yoursite">
<meta name="twitter:creator" content="@author">
<meta name="twitter:title" content="Your headline">
<meta name="twitter:description" content="A concise, click-worthy description.">
<meta name="twitter:image" content="https://example.com/preview-1200x630.jpg">

On image sizing, the figures que circulate à travers the guides: summary veut a roughly square image; summary_large_image veut a wide un, commonly cited autour 1200×630px at roughly a 1,91:1 (or 2:1) ratio, sous 5 MB, in JPG, PNG, WEBP, or GIF. Parce que Documentation officielle has thinned (voir ci-dessous), treat ces as well-established community consensus plutôt que a freshly-published X spec.

The Ouvrir Graph fallback rule — and the un tag que has aucun fallback

Ce is the load-bearing implementation fact, and it’s consistently reported à travers every current practitioner source I reviewed: X checks votre twitter:* tags premier, alors falls back to the matching og:* Ouvrir Graph tag, alors to votre page <title> and on-page content as a dernier resort. So twitter:title falls back to og:title, twitter:description to og:description, and twitter:image to og:image. Remarque the caveat que s’applique to everything on ce page: developer.x.com ne … plus publishes a Cards specification (voir the status section ci-dessous), so ce is current, consistent practitioner-observed behavior plutôt que something re-confirmed contre a live official contract.

The exception: twitter:card has aucun Ouvrir Graph equivalent. Là is aucun og:card. Si vous vouloir anything autre que X’s par défaut rendering, vous doit définir twitter:card explicitly. Ce is the unique most-repeated gotcha à travers every source I reviewed, and it’s pourquoi la plupart sites peut lean almost entirely on leur Ouvrir Graph tags and simplement ajouter the un twitter:card line.

The name= vs property= trap

Twitter Card tags utiliser name=. Ouvrir Graph tags utiliser property=. Ils regarder interchangeable and ils ne sont pas — put property="twitter:card" and the tag is silently ignored. Si votre OG tags fonctionner but votre Twitter tags don’t, vérifier ce premier. Ce is long-documented, practitioner-confirmed behavior; there’s aucun current official X contract to re-verify it contre, so treat it as the même kind of consistent, current practitioner-observed fact as the fallback rule ci-dessus.

<!-- Correct -->
<meta name="twitter:card" content="summary_large_image">
<!-- Silently ignored -->
<meta property="twitter:card" content="summary_large_image">

What’s modifié since the Musk-era rebrand — the honest status in 2026

La plupart guides on ce topic encore lire comme it’s 2019. It isn’t. Four choses have genuinely modifié, and ils matter plus En pratique que quelconque syntax detail.

1. The official Card Validator is dead. cards-dev.twitter.com/validator was deprecated in 2022 and X jamais shipped a replacement. As of ce réussir (verified 2026-07-18), l’URL 307-redirections to an X login page (twitter.com/login) plutôt que showing quelconque validator. Là is aucun first-party façon to preview or debug a card anymore. Third-party clone outils have proliferated specifically to fill que void — vous pouvez utiliser un to sanity-check votre markup, but be clair que none are official or guaranteed to replicate X’s live rendering pipeline. Quelconque older guide que indique vous to “test it in the Twitter Card Validator” — notamment Ahrefs’ propre 2020 Ouvrir Graph guide — is giving vous a dead lien.

2. The official Cards documentation is simply gone, pas paywalled. An précédent research réussir on ce article flagged developer.x.com’s Cards URLs as returning an HTTP 402 Payment Requis réponse. Re-checking directement (2026-07-18, by HTTP status plutôt que rendered page content), that’s ne … plus accurate: les deux the getting-started guide and the markup référence now 307-redirection to the generic docs.x.com overview page, qui contient aucun Cards-specific content at tout — and the equivalent chemin on docs.x.com itself (mirroring the old Cards markup URL) renvoie a flat 404. So there’s aucun current, official, first-party Cards specification at soit the old URL or its would-be replacement — pas a paywall, simplement an absence. The practical effect pour vous is the même soit façon: don’t treat quelconque unique “current official spec” as disponible to vérifier implementation details contre.

3. twitter:site / twitter:creator attribution has degraded. The tags are encore valid and CMS plugins encore output les, but X doesn’t surface que attribution reliably in current cards. The la plupart current dated source I trouvé on ce — The SEO Framework’s KB, mis à jour May 2026 — notes les deux que X “supprimé beaucoup of its Twitter Card documentation, but the metadata system encore fonctionne,” and that X “ne fait pas expose ce attribution reliably in current cards.” Définir the tags; don’t count on the byline showing.

4. X treats external-link posts differently — a separate system from si votre card renders. Since autour March 2025, X has applied some formulaire of reduced reach to posts containing an outside lien, and the company’s propre product leadership has confirmed the dynamic is intentional, aimed at discouraging “lazy linking” and keeping utilisateurs on-platform. Spécifique percentage figures pour how beaucoup reach is cut circulate widely à travers social-media coverage; ce article isn’t citing un, parce que aucun dated, first-party figure was verifiable during ce réussir — treat quelconque exact number vous voir elsewhere as unconfirmed unless it comes with its propre current, principal source. As Nikita Bier, X’s Head of Product, put it quand the company began testing a nouveau in-app lien experience in October 2025: “Pour creators, a courant complaint is que posts with liens tend to obtenir lower reach. Ce is parce que the web navigateur covers the post and personnes forget to Comme or Reply, so X doesn’t obtenir a clair signal si le contenu is quelconque bon.”

The important distinction, and the un la plupart troubleshooting guides conflate: card rendering and post reach are two separate systems. Si votre twitter:card metadata produces a preview at tout is a markup question — vérifier it directement (raw tags, a preview outil, a réel tester post). Si que post alors reaches nombreux personnes is a distribution question with a différent, less-documented causer. Don’t utiliser a low-engagement post as proof votre card is broken, and don’t assume a card que isn’t rendering is “just the algorithm” — vérifier the markup premier, en utilisant the workflow plus tard in ce article, avant attributing a problem to reach suppression.

(Historical footnote vous pouvez ignore operationally: X stripped headlines from lien previews in October 2023, reversed it après backlash, and reformatted à nouveau in early 2024. Que flip-flopping is settled — headlines and descriptions render normally on cards today quand the tags are présent.)

Are Twitter Card tags an SEO ranking factor?

Aucun — and ce is verifiable directement from the source, pas by paraphrase. Google Search Central maintains an exhaustive liste of every meta tag and attribute Recherche Google supports. Search it pour “twitter,” “og:,” “Open Graph,” or “social” and you’ll trouver nothing — none of ceux terms apparaître on lune page at tout. Que omission, on Google’s propre canonical, maintained référence, is a direct statement (by absence) que Google doesn’t traiter Twitter Card or Ouvrir Graph tags as ranking or indexation signals. It’s so clearly a non-factor que Google has jamais même nécessaire to publish a denial the façon it did pour meta keywords.

Bing is the même story: I trouvé aucun Bing documentation addressing twitter:card tags, and Bing hasn’t publié spécifique guidance on les. Treat ces as social-platform-only metadata, pas a search-engine signal pour soit engine.

Un adjacent fact worth keeping separate so vous don’t conflate it: Google fait now considérer the og:title tag as un input quand it generates the blue title lien in résultats de recherche — but that’s an appearance choice, pas a ranking factor, and it’s an Ouvrir Graph tag, pas a twitter:* un. Nothing from the twitter: namespace touches search at tout. (The title element itself is a différent topic — voir the title-tag deep dive in ce cluster.)

So the valeur of Twitter Cards is exactly un chose: how votre lien semble, and how nombreux personnes click it, quand it’s shared on social. And même que valeur is undercut on X specifically by the platform’s propre anti-link stance.

Do vous même besoin Twitter tags si vous have Ouvrir Graph?

Mostly aucun. Parce que of the fallback rule, votre og:title, og:description, and og:image cover the corresponding twitter: properties. The pragmatic minimum pour la plupart sites is:

  • A complet définir of Ouvrir Graph tags (qui vous vouloir anyway, pour LinkedIn, Slack, Discord, Facebook, and Google’s og:title title-link utiliser).
  • Plus un explicit twitter:card tag to choisir the card type.

Ajouter twitter:site/twitter:creator si vous vouloir to (harmless, and ils may fonctionner on autre surfaces), knowing the attribution isn’t reliable on X itself. Remarque que the twitter:* meta-tag system is encore lire by plus que simplement X — Discord, Slack, and others fall back via the même Ouvrir Graph chain — so the tags remain worth having même as X’s propre treatment of les wobbles.

Comment tester votre cards now que the official outil is gone

Since cards-dev.twitter.com/validator is dead and aucun official replacement exists, treat testing as several distinct checks plutôt que un outil — chaque couche peut échouer independently, so working via les in order narrows bas the réel causer:

  • Raw server-rendered tags — view lune page’s réel served HTML (pas the browser’s rendered DOM) and confirmer the twitter:*/og:* meta tags are présent with name=/property= correct, avant assuming a preview outil is incorrect.
  • Public fetchability — lune page URL and the image URL les deux besoin to be reachable by an outside robot d’exploration (pas behind a login, staging password, or robots block); an unreachable image silently kills the card.
  • Duplicate or conflicting tags — some CMS/plugin stacks output the même property twice; the premier or dernier instance peut win unpredictably.
  • Third-party card preview outils — several clones exist specifically to fill the gap left by the dead validator. Ils preview votre markup; ils can’t guarantee ils mirror X’s live pipeline.
  • Votre SEO tooling’s social checks — Ahrefs’ Site Audit flags a “Twitter card incomplete” problème quand une page has partial twitter:* metadata, and the Ahrefs SEO Toolbar’s “Social” tab montre votre OG and Twitter Card tags side by side. That’s a fast façon to catch a manquant twitter:card or an vide image.
  • Local/CDN caches — si vous simplement modifié the tags, une page cache (or X’s propre cache of a previously-shared URL) peut serve the old version; bust the cache avant concluding a fix didn’t fonctionner.
  • A réel tester post — ultimately the seulement façon to voir X’s réel current rendering is to share l’URL and regarder, ideally from an account vous don’t mind testing with. Treat ce step as checking rendering seulement — a réel post’s reach is a separate question (voir the reach-suppression remarque ci-dessus) and doesn’t tell vous anything à propos de si the card itself is correct.

Où ce fits

Ce is a deep dive sous the Meta Tags pour le SEO hub, in the on-page cluster. Twitter Cards sit in the même “social preview metadata” bucket as Ouvrir Graph tags — the two overlap heavily and are usually implemented ensemble, with Ouvrir Graph doing la plupart of the fonctionner and twitter:card filling the un gap. It’s a navigateur/social-facing tag, pas an indexation or serving directive comme the robots meta tag, and it has aucun bearing on how Google crawls, indexes, or ranks lune page.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.