Element Code: SO-002
What "Missing Twitter Cards" Actually Means
A Twitter Card is a set of meta tags in your page's HTML head that tells X how to render a link when it's shared in a post. Without them, X has to guess. This check flags pages where those tags are absent entirely: no twitter:card, no twitter:title, no twitter:description, no twitter:image. The core tag is twitter:card, and it sets the layout type: summary (small square thumbnail, text beside it), summary_large_image (full-width hero image, the one you want for blog posts and product pages), app (deep links into an iOS or Android app), or player (embedded video or audio). If that tag is missing, X falls back to whatever Open Graph tags you have, and if those are also missing, the post shows as a plain text link with no preview at all.
People treat Open Graph and Twitter Cards as the same thing. They're related but not identical. Open Graph (og:title, og:description, og:image) was built by Facebook and is the broader standard most platforms read from. Twitter Cards are a parallel, X-specific set of tags that override the OG values or add things OG doesn't cover, like twitter:site (your brand's handle) and twitter:creator (the author's handle). With solid OG tags, X will usually render something, but it defaults to the smaller summary card unless twitter:card is explicitly set to summary_large_image, and it won't attribute the share without twitter:site.
Why It Actually Costs You Something
A user scrolling their feed decides whether to click in under a second, and that decision is driven almost entirely by the image and headline in the card. A link with no image, or with a randomly-selected image X scraped from the page, looks amateurish next to a competitor's clean, branded large-image card. I've watched identical content get meaningfully different click-through rates on X purely because one version had a proper summary_large_image card and the other didn't.
There's also a branding leak most people miss. Without twitter:site set, X can't attribute the credit line that normally appears under a reshared card, so you lose free brand exposure on every reshare. Without a controlled twitter:image, X sometimes pulls whatever image it finds first in the DOM, which on many WordPress themes is a sidebar logo, not your content thumbnail.
To be clear about what this isn't: missing Twitter Cards have zero direct effect on Google rankings. This is a social-sharing and brand-presentation issue, not a crawlability issue. It tanks your social CTR and resharing rate, which indirectly affects referral traffic, but Googlebot doesn't read twitter:card tags and doesn't care whether they're missing.
How the Fallback Actually Works
The diagram above is the actual decision path X's crawler runs through. This is why "I already have Open Graph tags, I don't need Twitter Cards" is only half right. You'll get something, but you're leaving the large-image layout and the attribution credit on the table.
How to Detect It
The official Twitter Card Validator (cards-dev.twitter.com/validator) was retired when Twitter rebranded to X. Here's what works in its place:
- View page source manually. Right-click the page, View Page Source, and search for "twitter:card". If nothing comes back, the tags don't exist. Fast and requires no tools.
- Browser devtools. Open the Elements panel, expand <head>, and scan the <meta> tags. This confirms the tags render server-side and aren't getting injected late by JavaScript, which some X crawlers won't wait for.
- Screaming Frog custom extraction. Set up an extraction rule for meta[name^="twitter:"] and crawl the whole site. This is the realistic way to audit coverage across hundreds of URLs instead of checking pages one by one.
- Third-party card preview tools. Since Twitter's own validator is gone, replacement tools fetch a URL and render what the card would look like, catching image-dimension and truncation issues a raw tag check won't.
- What won't help: Google Search Console. GSC reports on indexing and Google SERP behavior. It has no visibility into X card rendering, that's a separate platform reading separate meta tags.
How to Fix It, Step by Step
- Decide on a card type. For nearly every blog post or article, use summary_large_image. Reserve summary for utility pages, app only if you're driving installs, player only for native video or audio.
- Add the four core tags to the <head>: twitter:card, twitter:title (under 70 characters), twitter:description (under 200 characters), twitter:image (absolute URL, not relative).
- Size the image correctly. For summary_large_image, X wants roughly 1200x630 pixels, minimum 300x157, aspect ratio near 1.91:1. Undersized or oddly-cropped images get rejected or render awkwardly. Keep the file under 5MB, JPG or PNG.
- Set twitter:site to your brand handle so shares carry attribution, and twitter:creator to the author's handle for bylined content.
- Keep Open Graph populated too as a safety net, not a replacement. If a Twitter tag is missing by accident, X still pulls from OG rather than showing nothing.
- Clear any page or CDN cache so the new tags are actually served, then test with a preview tool. X caches card renders per URL, so expect a delay before an updated image shows up in shares.
What Good Looks Like
| Tag | Required? | Purpose |
|---|---|---|
twitter:card | Yes | Sets layout: summary, summary_large_image, app, or player |
twitter:title | Yes (or falls back to og:title) | Headline shown on the card, keep under 70 characters |
twitter:description | Yes (or falls back to og:description) | Supporting text, keep under 200 characters |
twitter:image | Yes (or falls back to og:image) | Absolute URL, roughly 1200x630 for large-image cards |
twitter:site | Recommended | Brand handle, enables attribution on shares |
twitter:creator | Optional | Author handle for bylined content |
Do This / Don't Do This
- Set twitter:card to summary_large_image for content pages
- Use absolute image URLs, not relative paths
- Keep the image at or near 1200x630 pixels
- Set twitter:site so shares credit your brand
- Re-test with a card preview tool after any template change
- Assume Open Graph tags alone give you the large-image layout
- Inject the tags with JavaScript only, some crawlers won't render it
- Use a tiny or oddly-cropped image and expect it to render cleanly
- Forget to update the cached card preview after changing the image
- Look for this issue's cause inside Search Console, it won't be there
Frequently Asked Questions
Does X still support Twitter Cards after the rebrand?
Do I need both Open Graph and Twitter Card tags?
Will fixing missing Twitter Cards improve my Google rankings?
Why does my card still show an old image after I updated it?
Can I use the same image for Open Graph and Twitter Cards?
Our Advanced SEO Audit covers meta tag coverage, structured data, crawlability, and the dozens of smaller issues that quietly erode click-through rate across search and social.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
