Blog

Open Graph Best Practices 2026: Complete Guide for Articles

If your articles still use Open Graph tags from 2024 or earlier, you’re leaving social traffic on the table.

Facebook, Twitter, LinkedIn, and WhatsApp have all updated how they handle OG tags. What worked two years ago might now result in broken previews, missing images, or truncated titles.

Here’s what changed in 2026 and exactly how to fix your Open Graph setup.

Old standard: 1200 × 627 pixels
New standard: 1200 × 630 pixels (landscape orientation)

The extra 3 pixels might seem minor, but Facebook now crops images that don’t match the 1.91

Generic OG tags aren’t enough anymore. If you want rich previews on Facebook and better indexing, you need article-specific properties:

• article:published_time
• article:author
• article:section
• article:tag

Twitter/X no longer falls back to Open Graph automatically for some card types. You need explicit Twitter Card meta tags, especially for summary_large_image.

Social platforms now consider article:published_time and article:modified_time when prioritizing content in feeds. Evergreen articles with recent modification dates perform better.

Here’s the minimum you need for any blog article in 2026:

<!-- Core Open Graph -->
<meta property="og:title" content="Your Article Title Here" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://www.yoursite.com/article-slug/" />
<meta property="og:image" content="https://www.yoursite.com/images/og-image.jpg" />
<meta property="og:description" content="A compelling description that makes people want to click." />
<meta property="og:site_name" content="Your Site Name" />

og:title
The headline that appears when your article is shared. Keep it 60-90 characters. Longer titles get cut off with ”…” which reduces click-through rates.

og:type
Must be set to "article" for blog posts. This tells social platforms to look for article-specific tags and display article metadata.

og:url
Your canonical URL. Use the full URL including https:// and trailing slash if that’s your site’s standard. Avoid query parameters unless necessary.

og:image
The most important tag for CTR. Use unique images for each article. Generic stock photos perform poorly—custom images get 2-3x more clicks.

og:description
150-200 characters works best. Shorter descriptions feel incomplete. Longer ones get truncated.

og:site_name
Helps with brand recognition across multiple shares from your domain.

These tags only work when og:type="article":

<meta property="article:published_time" content="2026-04-05T14:00:00+07:00" />
<meta property="article:modified_time" content="2026-04-05T16:30:00+07:00" />
<meta property="article:author" content="Jane Doe" />
<meta property="article:section" content="SEO" />
<meta property="article:tag" content="open graph" />
<meta property="article:tag" content="social media" />
<meta property="article:tag" content="seo" />

article:published_time
When the article was first published. Use ISO 8601 format with timezone. This affects freshness signals on social platforms.

article:modified_time
When the article was last updated. Useful for evergreen content that gets refreshed periodically.

article:author
The author’s name. Some platforms display this in the preview card, adding credibility.

article:section
A high-level category (e.g., “SEO”, “Marketing”, “Technology”). Helps with categorization on Facebook.

article:tag
Multiple tags are allowed. Use relevant keywords that describe the article’s topics.

Twitter requires its own meta tags. For articles, use summary_large_image:

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Your Article Title Here" />
<meta name="twitter:description" content="A compelling description for Twitter." />
<meta name="twitter:image" content="https://www.yoursite.com/images/twitter-image.jpg" />

• Size: 1200 × 628 pixels
• Aspect ratio: 1.91
• Max file size: 5MB
• Format: JPEG, PNG, or GIF

Twitter will fall back to Open Graph if Twitter tags are missing, but explicit tags give you more control and ensure consistent appearance.

Generic stock photos hurt your CTR. Data from social platforms shows:

• Custom images: 2-3x higher click-through rates
• Unique images per article: Better brand recognition
• Text overlay on images: Works well for CTR (title, key stat)

Do:

• Use unique images for each article
• Include the article title or key concept
• Use high contrast and readable fonts
• Keep it simple—don’t overcrowd

Don’t:

• Use generic stock photos
• Add too much text overlay
• Use low-quality images
• Ignore the aspect ratio

Problem: Using the same generic image for multiple articles
Impact: Lower CTR, poor brand recognition
Fix: Create unique images for each article

Problem: Title exceeds 90 characters
Impact: Gets cut off with ”…” reducing clarity
Fix: Keep titles 60-90 characters

Problem: Using only basic OG tags
Impact: Less rich previews, weaker freshness signals
Fix: Add article:published_time, article:author, etc.

Problem: Images don’t match 1.91

Problem: Relying on OG fallback for Twitter
Impact: Inconsistent appearance on Twitter/X
Fix: Add explicit Twitter Card tags

URL: https://developers.facebook.com/tools/debug/ (opens in a new window)

What it does:

• Shows how your article appears when shared on Facebook
• Identifies missing or incorrect tags
• Caches your OG data
• Allows you to force-refresh the cache

How to use:

1. Paste your article URL
2. Click “Debug”
3. Review the preview
4. Fix any errors or warnings
5. Click “Scrape Again” after making changes

URL: https://cards-dev.twitter.com/validator (opens in a new window)

What it does:

• Previews your Twitter Card
• Validates Twitter-specific tags
• Shows how your content appears in tweets

How to use:

1. Paste your article URL
2. Click “Preview card”
3. Check the preview
4. Fix any issues
5. Re-test after changes

URL: https://www.linkedin.com/post-inspector/ (opens in a new window)

What it does:

• Shows how your article appears on LinkedIn
• Identifies issues with OG tags
• Provides caching information

URL: https://search.google.com/test/rich-results (opens in a new window)

What it does:

• Tests structured data and rich results
• Shows how your article appears in Google Search
• Validates article schema

File size matters:

• Target < 500KB for fast loading
• Use JPEG for photos (85% quality)
• Use PNG for graphics with text
• Compress images before uploading

Tools:

• TinyPNG (https://tinypng.com/ (opens in a new window))
• Squoosh (https://squoosh.app/ (opens in a new window))
• ImageOptim (macOS)

Add these to your <head> for faster OG image loading:

<link rel="preconnect" href="https://www.facebook.com" />
<link rel="preconnect" href="https://twitter.com" />
<link rel="preconnect" href="https://www.linkedin.com" />

If your article has multiple images, lazy load secondary images:

<img src="article-image.jpg" loading="lazy" alt="..." />

Keep your OG image in the critical rendering path.

Here’s a complete example for a blog article:

<!DOCTYPE html>
<html lang="en">
<head>
  <!-- Core Meta -->
  <title>Open Graph Best Practices 2026: Complete Guide for Articles</title>
  <meta name="description" content="Learn the latest Open Graph best practices for 2026 with updated image sizes, article-specific tags, and Twitter Cards integration." />

  <!-- Open Graph -->
  <meta property="og:title" content="Open Graph Best Practices 2026: Complete Guide for Articles" />
  <meta property="og:type" content="article" />
  <meta property="og:url" content="https://www.sewwa.com/blog/open-graph-best-practices-2026/" />
  <meta property="og:image" content="https://www.sewwa.com/blog/open-graph-best-practices-2026/og-image.jpg" />
  <meta property="og:description" content="Learn the latest Open Graph best practices for 2026 with updated image sizes, article-specific tags, and Twitter Cards integration." />
  <meta property="og:site_name" content="SEWWA" />
  <meta property="og:locale" content="en_US" />

  <!-- Article-Specific -->
  <meta property="article:published_time" content="2026-04-05T14:00:00+07:00" />
  <meta property="article:modified_time" content="2026-04-05T16:30:00+07:00" />
  <meta property="article:author" content="SEWWA Team" />
  <meta property="article:section" content="SEO" />
  <meta property="article:tag" content="open graph" />
  <meta property="article:tag" content="social media" />
  <meta property="article:tag" content="seo" />
  <meta property="article:tag" content="twitter cards" />

  <!-- Twitter Card -->
  <meta name="twitter:card" content="summary_large_image" />
  <meta name="twitter:title" content="Open Graph Best Practices 2026: Complete Guide for Articles" />
  <meta name="twitter:description" content="Learn the latest Open Graph best practices for 2026 with updated image sizes and Twitter Cards integration." />
  <meta name="twitter:image" content="https://www.sewwa.com/blog/open-graph-best-practices-2026/twitter-image.jpg" />

  <!-- Preconnect for Performance -->
  <link rel="preconnect" href="https://www.facebook.com" />
  <link rel="preconnect" href="https://twitter.com" />
  <link rel="preconnect" href="https://www.linkedin.com" />
</head>
<body>
  <!-- Article content -->
</body>
</html>

Before publishing any article, verify:

• og:title is 60-90 characters
• og:type is set to "article"
• og:url is the canonical URL
• og:image is 1200 × 630 pixels
• og:description is 150-200 characters
• og:site_name is set
• article:published_time uses ISO 8601 format
• article:author is set
• article:section is defined
• At least 2-3 article:tag entries
• Twitter Card tags are present
• twitter:card is set to "summary_large_image"
• Image file size is under 500KB
• Tested on Facebook Sharing Debugger
• Tested on Twitter Card Validator
• Tested on LinkedIn Post Inspector

Properly implemented Open Graph tags can increase CTR by 2-3x compared to articles with broken or missing previews. When your article looks professional on social media, people are more likely to click.

Unique images per article, consistent branding with og:site_name, and proper titles help users recognize your content across multiple shares and platforms.

Social platforms prioritize content that renders well. Articles with proper OG tags are more likely to be featured in feeds and recommendations.

Broken images, truncated titles, and missing previews look amateurish. Proper OG implementation shows attention to detail and technical competence.

1. Audit existing articles - Use Facebook Debugger to check current OG implementation
2. Update image dimensions - Ensure all OG images are 1200 × 630 pixels
3. Add article-specific tags - Implement article:published_time, article:author, etc.
4. Create unique images - Design custom OG images for each article
5. Implement Twitter Cards - Add Twitter-specific meta tags
6. Test everything - Validate on all major platforms before publishing

The investment is small—about 30 minutes per article—but the return in terms of increased social traffic makes it well worth the effort.

Need help with structured data and SEO? Check out SEWWA’s Schema Generator to create JSON-LD markup for each articles and improve your search visibility.