twitter:card type is appropriate for the content
Why it matters
Using summary_large_image uniformly on utility pages — login, settings, 404, dashboard — generates large image preview cards for pages that have no meaningful OG image and offer no shareable content value. The result is a card that shows a stretched or irrelevant image for a page that wasn't intended to be shared, which creates a confusing experience when users accidentally share these URLs. While this is a low-severity issue, it degrades visual polish: a /login page shared in a Slack channel or Twitter DM produces a prominent image-forward card for a page that serves no audience from that share.
Severity rationale
Low because incorrect card types on utility pages result in mildly incoherent previews but do not break sharing and are unlikely to cause user-facing failures.
Remediation
Override the card type on utility pages that do not warrant a large image preview:
// app/(auth)/login/page.tsx
export const metadata: Metadata = {
twitter: { card: 'summary' },
}
Apply summary to /login, /signup, /settings, /dashboard, and /404. Leave summary_large_image as the root default for all content pages. This is a low-priority change — address it after completing higher-severity OG tag gaps.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Social Sharing Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- external · twitter-cards — Twitter Cards — Cards Markup Tag Reference
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-social-sharing·automated