Why Social Meta Tags Matter
Social meta tags control how your content appears when shared on social platforms. Open Graph tags for Facebook and LinkedIn, Twitter Cards for X, and structured data for rich previews all ensure your content looks professional and drives clicks.
The 14 Checks
Every check ranked by impact. Start at the top and work down.
| # | Check | Category | Impact | Difficulty |
|---|---|---|---|---|
| 1 | Add og:title — the headline shown in the social preview card. Keep under 60 characters; use your page title or a shorter variant. | Open Graph | Critical | Easy |
| 2 | Add og:description — the snippet below the title. 120–155 characters works best; front-load the value proposition. | Open Graph | Critical | Easy |
| 3 | Add og:image — the thumbnail shown on share. Use an absolute URL to a 1200×630 px image (min 600×315 px). Under 8 MB. | Open Graph | Critical | Easy |
| 4 | Add og:url — the canonical URL of the page. Must match the canonical tag exactly, including https:// and trailing slashes. | Open Graph | Critical | Easy |
| 5 | Add og:type — content type: "website" for homepages, "article" for blog posts, "product" for ecommerce. Defaults to "website" if omitted. | Open Graph | Critical | Easy |
| 6 | Add Twitter Card meta tags — set twitter:card to "summary_large_image" or "summary" and include twitter:title, twitter:description, twitter:image. | High | Easy | |
| 7 | Use 1200×630 px OG images — this ratio renders correctly on Facebook, LinkedIn, and Twitter. Smaller images get cropped awkwardly. | Images | High | Easy |
| 8 | Add og:locale — set to your audience locale, e.g. "en_US". Helps platforms serve the right language variant. | Open Graph | Medium | Easy |
| 9 | Add og:site_name — your brand name. Displayed above the title on some platforms. Use your site's name, not a tagline. | Open Graph | Medium | Easy |
| 10 | Test with Facebook Debugger — paste your URL to see the scraped preview, check for errors, and force a cache refresh. | Testing | Medium | Easy |
| 11 | Test with Twitter Card Validator — previews how your Card renders on X and flags missing or invalid tags. | Testing | Medium | Easy |
| 12 | Add structured data (Article, FAQPage, Product schema) — enhances rich previews and can add extra elements like author, date, and ratings. | Schema | Medium | Easy |
| 13 | Use consistent branding in OG images — include your logo, brand colors, and a legible headline so users recognize your content across platforms. | Branding | Low | Easy |
| 14 | Update OG tags when content changes — if you change the title, image, or URL, update the meta tags and re-scrape with each platform's debugger tool. | Maintenance | Low | Easy |
Open Graph Code Example
Copy-paste this into your <head> and swap the values per page.
<!-- Open Graph -->
<meta property="og:title" content="12-Point Technical SEO Audit Checklist 2026" />
<meta property="og:description" content="The exact audit process we use to find and fix crawl, indexation, and speed issues. 14 checks, free to use." />
<meta property="og:image" content="https://www.clienvora.com/images/og/technical-seo-audit.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Technical SEO Audit Checklist preview" />
<meta property="og:url" content="https://www.clienvora.com/checklists/on-page-seo/technical-seo-audit/" />
<meta property="og:type" content="article" />
<meta property="og:site_name" content="Clienvora" />
<meta property="og:locale" content="en_US" />
<!-- Twitter / X -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@clienvora" />
<meta name="twitter:title" content="12-Point Technical SEO Audit Checklist 2026" />
<meta name="twitter:description" content="The exact audit process we use to find and fix crawl, indexation, and speed issues." />
<meta name="twitter:image" content="https://www.clienvora.com/images/og/technical-seo-audit.png" />
<meta name="twitter:image:alt" content="Technical SEO Audit Checklist preview" />Platform-Specific Differences
Facebook, LinkedIn, and Twitter/X each handle OG tags differently.
- Image: 1200×630 px (min 600×315)
- Title: ~60 characters before truncation
- Description: ~110 characters visible
- Uses og:* tags exclusively
- Facebook Sharing Debugger to test & force re-scrape
- og:type determines the card behavior
- Image: 1200×627 px (min 200×200)
- Title: ~70 characters before truncation
- Description: ~100 characters visible
- Reads og:* tags; ignores twitter:* tags
- LinkedIn Post Inspector to test
- Larger image preview than Facebook
Twitter / X
- Image: 1200×675 px for summary_large_image
- Title: ~70 characters
- Description: ~200 characters
- Prefers twitter:* tags; falls back to og:*
- Card Validator to test
- Four card types available (see below)
Twitter Card Types
Choose the right card type for your content.
| Card Type | twitter:card Value | Image Size | Best For |
|---|---|---|---|
| Summary | summary | 144×144 px | Small thumbnails — blog lists, products with small images |
| Summary Large Image | summary_large_image | 1200×675 px | Blog posts, articles, landing pages — most common choice |
| Player | player | Aspect ratio required | Video/audio embeds — must provide iframe player URL |
| App | app | Not required | Mobile app downloads — link to App Store / Play Store |
For most websites, summary_large_image is the right default. Use summary only when your images are small or square.
Good vs Bad OG Previews
What separates a clickable share from an ignored one.
Bad Example
- No og:image — shows a blank icon or site favicon
- Title is just "Home" or the domain name
- Description is empty or says "Lorem ipsum…"
- Image is 300×200 — gets stretched and blurry
- og:url points to a staging subdomain
- Multiple conflicting og:title tags on the same page
Good Example
- 1200×630 px branded image with headline overlay
- Title includes the primary keyword and brand
- Description is a clear value proposition under 155 chars
- og:url matches the canonical URL exactly
- og:type is set to "article" for blog posts
- Tested on all three platforms before publishing
How to Debug OG Tags
Step-by-step process when your social previews look wrong.
View Source
Right-click the page → View Source → search for og:. Verify all five core tags exist and have correct values. Check for duplicates.
Use the Debuggers
Paste your URL into Facebook Sharing Debugger, Twitter Card Validator, and LinkedIn Post Inspector. Each shows what the platform actually sees when it scrapes your page.
Fix and Re-scrape
Fix the tags in your HTML, deploy the changes, then hit "Scrape Again" in Facebook Debugger or re-validate on Twitter. Facebook caches aggressively — you may need to use the "Scrape Again" button multiple times.
OG Testing & Optimization Tools
Free tools to test, preview, and fix your Open Graph tags.
Facebook Sharing Debugger
FreeShows exactly how Facebook scrapes your page — all OG tags it finds, the image it downloads, and any errors. Use "Scrape Again" to force a cache refresh after fixing tags.
Twitter Card Validator
FreePreviews your Twitter Card on X and flags missing or malformed tags. Also shows the raw HTTP response and any crawl errors the platform encountered.
LinkedIn Post Inspector
FreeLinkedIn's equivalent of Facebook Debugger. Shows what OG data LinkedIn reads, the image it displays, and lets you refresh the cache for a URL.
OpenGraph.xyz
FreeOne tool to preview how your URL looks on Facebook, Twitter, and LinkedIn simultaneously. Shows all extracted OG tags and lets you copy the correct markup.
Screaming Frog SEO Spider
Free / PaidCrawls your entire site and reports missing, duplicate, or too-long OG tags across every page. Free version handles up to 500 URLs — enough for most small sites.
Yoast SEO / RankMath
FreeWordPress plugins that auto-generate OG and Twitter Card tags from your post title, excerpt, and featured image. Lets you override the defaults per page without touching code.
Frequently Asked Questions
Open Graph (OG) is a protocol created by Facebook that controls how URLs are displayed when shared on social media. It uses meta tags in your HTML <head> to define the title, description, image, and type of a shared link. Without OG tags, platforms guess what to show — usually pulling the first text and image they find, which often looks broken or generic.
The recommended OG image size is 1200×630 pixels — this ratio renders correctly on Facebook, LinkedIn, and Twitter/X without awkward cropping. The minimum size is 600×315 pixels; anything smaller will be stretched or ignored. Keep the file under 8 MB and use JPG or PNG format. For Twitter's summary_large_image card, 1200×675 px is the ideal ratio.
Social signals (likes, shares, comments) are not direct Google ranking factors — Google has confirmed this multiple times. However, social media drives referral traffic, increases brand searches, and earns natural backlinks when people reference your content, all of which indirectly improve SEO. Well-optimized OG tags increase click-through rates from social shares, which compounds over time.
Paste your URL into Facebook Sharing Debugger (developers.facebook.com/tools/debug), Twitter Card Validator (cards-dev.twitter.com/validator), and LinkedIn Post Inspector (linkedin.com/post-inspector). Each tool shows what the platform actually scrapes — the tags it finds, the image it downloads, and any errors. You can also use OpenGraph.xyz to preview all three platforms at once.
The HTML <title> tag appears in browser tabs and search results, while og:title appears in social media preview cards. They can be different — for example, you might use a shorter, punchier og:title optimized for social clicks, while keeping a longer, keyword-rich HTML title for SEO. Most CMS plugins default og:title to match the HTML title unless you override it.
The most common causes are: the og:image URL is relative instead of absolute (use https://example.com/image.png, not /image.png), the image is smaller than 200×200 px, the image URL returns a 404 or redirect, or the platform has cached an old version. Use the platform's debugger tool to force a re-scrape after fixing the tag. Also check that your server isn't blocking social media crawlers.