Open Graph vs Twitter Cards: What's Missing on Your Site
Updated July 2026 · 7 min read
Not sure which tags your site is missing? Run a free audit and find out in 2 seconds →
When someone shares your URL on Facebook, LinkedIn, or Twitter, the platform scrapes your page for special meta tags that control the preview card — the image, title, and description that appear alongside the link. Two tag systems control this: Open Graph (used by most platforms) and Twitter Cards (used by X/Twitter). If either is missing or broken, your shared links look unprofessional and get fewer clicks.
What Is Open Graph?
Open Graph is a protocol created by Facebook in 2010. It uses og:prefixed meta properties to describe a page. Today it's supported by Facebook, LinkedIn, Slack, Discord, Telegram, iMessage, WhatsApp, and many other platforms.
<meta property="og:title" content="Free Meta Tag Checker & SEO Auditor">
<meta property="og:description" content="Instant on-page SEO audit for any URL.">
<meta property="og:image" content="https://example.com/og-image.png">
<meta property="og:url" content="https://example.com">
<meta property="og:type" content="website">
<meta property="og:site_name" content="Meta Tag Checker">What Are Twitter Cards?
Twitter Cards are X's own meta tag system, using twitter: prefixed names. They exist because Twitter launched its card system before adopting Open Graph. Twitter Cards can override OG tags on Twitter specifically, giving you platform-specific control.
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Free Meta Tag Checker & SEO Auditor">
<meta name="twitter:description" content="Instant on-page SEO audit for any URL.">
<meta name="twitter:image" content="https://example.com/twitter-card.png">
<meta name="twitter:site" content="@yourhandle">Key Differences at a Glance
| Feature | Open Graph | Twitter Cards |
|---|---|---|
| Used by | Facebook, LinkedIn, Slack, Discord, WhatsApp, most platforms | X / Twitter only |
| Tag prefix | og: (property) | twitter: (name) |
| Image size | 1200×630px recommended | 1200×628px (large image card) |
| Title limit | ~60 chars visible | ~70 chars |
| Description limit | ~200 chars | ~200 chars |
| Card type control | No — type is inferred | Yes — explicit card type |
| Fallback behavior | Twitter falls back to OG tags | Overrides OG on Twitter |
Do You Need Both?
Short answer: yes.Here's why:
- Open Graph covers ~90% of platforms. If you only implement one set, make it OG.
- Twitter Cards give you explicit control on X. The
twitter:cardtag lets you choose betweensummary(small square image) andsummary_large_image(big banner). Without it, Twitter guesses. - Twitter falls back to OG. If you have OG tags but no Twitter tags, Twitter will use your OG tags. But the reverse is not true — Facebook will not use Twitter tags.
Image Specifications
The image is the single most impactful element of a social card. Here are the specs that work across all platforms:
- Dimensions: 1200×630 pixels (the universal standard)
- File size: Under 8MB (under 1MB is ideal for fast loading)
- Format: JPG, PNG, or GIF (WebP has inconsistent support)
- Safe zone: Keep important content in the center — platforms crop edges differently
- Text: Use large, readable text. Small text becomes illegible on mobile.
Pro tip: create one 1200×630 image and use it for both og:image and twitter:image. It works everywhere.
Common Issues We See
1. Missing og:image entirely
This is the #1 issue. Without an OG image, platforms either show no image or pick a random one from your page. Shared links with no image get dramatically fewer clicks.
2. Relative image URLs
OG and Twitter image URLs must be absolute. This fails silently:
<!-- BROKEN: relative URL -->
<meta property="og:image" content="/images/og-card.png">
<!-- CORRECT: absolute URL -->
<meta property="og:image" content="https://example.com/images/og-card.png">3. Image too large
If your og:image is a 15MB photo from a phone, platforms may time out trying to fetch it and show no preview. Compress images to under 1MB.
4. No twitter:card tag
Without twitter:card, X defaults to a basic summary which is small and easy to scroll past. Adding twitter:card set to summary_large_image immediately makes your tweets more eye-catching.
5. Cached previews showing old data
Platforms cache your OG data aggressively. After updating tags, force a re-scrape:
- Facebook: Sharing Debugger → click "Scrape Again"
- Twitter: Card Validator
- LinkedIn: Post Inspector
The Minimal Setup That Works Everywhere
If you want to cover all platforms with the least effort, add these 11 tags to every page:
<!-- Open Graph (covers Facebook, LinkedIn, Slack, WhatsApp, etc.) -->
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A compelling 1-2 sentence description.">
<meta property="og:image" content="https://example.com/card.png">
<meta property="og:url" content="https://example.com/page">
<meta property="og:type" content="website">
<!-- Twitter Cards (overrides OG on X) -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling 1-2 sentence description.">
<meta name="twitter:image" content="https://example.com/card.png">
<meta name="twitter:url" content="https://example.com/page">That's it. 10 tags and your links will render beautifully on every major platform.
How to Check What's Missing
Rather than viewing source and hunting through the HTML, our free checker scans any URL and tells you exactly which OG and Twitter Card tags are present, missing, or broken — with image dimensions validated.
Find your missing social tags
Get a full report on your OG and Twitter Card tags in 2 seconds.
Check My Social Tags Free →Summary
Open Graph and Twitter Cards are two complementary systems that control how your links appear when shared. Implement both — OG covers most platforms, Twitter Cards give you explicit control on X. Use a single 1200×630 image, absolute URLs, and always include twitter:card set to summary_large_image. Run an audit, fix what's missing, and watch your social click-through rates climb.
Questions? Email us at support@appsnap.co.uk