Start here
Before You Fix It: What This Check Means
X/Twitter card tags influence preview fidelity and click-through context on shared posts. In plain terms, this checks whether links from this page will show a complete title, description, and image when shared on X. Scavo inspects these meta tags in the live HTML.
Why this matters in practice: incorrect signals here can dilute indexing clarity and search traffic quality.
How to use this result: treat this as directional evidence, not final truth. Search indexing outcomes depend on crawler recrawl cadence and ranking systems outside your direct control. First, confirm the issue in live output: verify raw HTML output and crawler-facing validators Then ship one controlled change: Render required `twitter:*` tags in your global metadata layer. Finally, re-scan the same URL to confirm the result improves.
Background sources
TL;DR: Twitter card tags are missing, so your links appear as plain text instead of rich preview cards when shared on X/Twitter.
Rich social cards with images and descriptions get significantly more engagement than plain text links. Without Twitter card meta tags, every time someone shares your link, it appears as a bare URL with no preview — reducing clicks, shares, and the viral potential of your content. This applies to X/Twitter and many other platforms that read card markup.
What Scavo checks (plain English)
Scavo inspects these meta tags in the live HTML:
twitter:cardtwitter:titletwitter:descriptiontwitter:imagetwitter:url(tracked but not required for pass)
Exact logic:
Fail:twitter:cardis missing, or 3+ required tags are missing.Warning: some required tags are missing.Warning: iftwitter:cardissummaryorsummary_large_imageandtwitter:imageis missing.Pass: required card metadata is present.
How Scavo scores this check
Scavo assigns one result state for this check on the tested page:
- Pass: baseline signals for this check were found.
- Warning: partial coverage or risk signals were found and should be reviewed.
- Fail: required signals were missing or risky behavior was confirmed.
- Info: Scavo could not gather enough reliable evidence on this run to score pass/fail confidently.
In your scan report, this appears under What failed / What needs attention / What is working for twitter_card, followed by Recommended next steps and Technical evidence (for developers) when needed.
- Scan key:
twitter_card - Category:
SEO
Why fixing this matters
Incomplete card tags create inconsistent previews, weaker click-through from social shares, and lower trust in shared links.
For SaaS teams, this directly affects launch posts, feature announcements, and content distribution performance.
Common reasons this check flags
- Shared head template does not include X card tags.
- Per-page social fields are blank in CMS.
- Migration from older social plugin dropped
twitter:*output. - Image URL is missing when using image-based card type.
If you are not technical
- Ask your content/dev team to fix metadata in the shared page-head template.
- Confirm title, description, and image values are populated for key pages.
- Test with one URL from each major template.
- Re-run scan and confirm status improves.
Technical handoff message
Copy and share this with your developer.
Scavo flagged Twitter card metadata (twitter_card). Please ensure this URL includes twitter:card, twitter:title, twitter:description, and required twitter:image for image card types. Share source proof and re-run the scan.If you are technical
- Render required
twitter:*tags in your global metadata layer. - For
summary/summary_large_image, always providetwitter:image. - Use absolute image URLs and stable media assets.
- Keep
twitter:titleandtwitter:descriptionaligned with page intent.
Example
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Scavo Website Monitoring for SaaS Teams">
<meta name="twitter:description" content="Track uptime, SEO, security and legal checks in one weekly report.">
<meta name="twitter:image" content="https://www.example.com/assets/social/scavo-card.jpg">How to verify
- Inspect source and confirm required tags are present.
- Confirm image URL is absolute and publicly fetchable.
- Share URL in X post composer and validate preview output.
- Re-run Scavo and confirm
Pass.
What this scan cannot confirm
- It does not confirm final X cache behavior for every share context.
- It does not validate image dimensions, crop quality, or file size limits.
- It does not check Open Graph parity directly (that is a separate concern).
Owner checklist
- [ ] Assign one owner for social metadata defaults.
- [ ] Keep template-level fallback values for pages with missing CMS fields.
- [ ] Add publish QA for missing social image/title/description.
- [ ] Re-check social metadata after CMS/plugin upgrades.
FAQ
Why can this fail even when Open Graph tags exist?
Because this check specifically evaluates twitter:* tags. Open Graph alone does not satisfy this check's required fields.
Is twitter:url required to pass?
Not currently. Scavo records it, but pass/fail depends on the required card/title/description/image logic.
Do all page types need summary_large_image?
Not necessarily. Pick card type by content strategy, but include matching required fields.
Can one global default image work?
Yes as a fallback, but per-page images generally perform better for campaigns and content shares.
Sources
- X Developer docs: Cards markup reference
- X Developer docs: About X Cards
- Open Graph protocol reference
Need help designing a social metadata fallback strategy that works across product, blog, and docs pages? Send support your page types.
