Technical Specifications & Google Search Constraints
OpenGraph Image Standard
1200 x 630 pixels (1.91:1 aspect ratio)
Minimum Image Dimension
600 x 315 pixels (smaller images render as tiny thumbnails)
Max File Size
5 MB for LinkedIn/Facebook, 5 MB for X (Twitter)
Twitter Card Types
summary_large_image (preferred) vs. summary
Canonical Meta Rule
Must always be an absolute HTTPS URL
1. The OpenGraph Protocol Hierarchy
The OpenGraph protocol (originally developed by Facebook) is supported universally by modern social and messaging platforms. Essential tags include:
og:title: Clear, punchy headline without excessive brand suffixes.og:description: 2 to 3 sentences summarizing the core value proposition.og:image: Direct absolute HTTPS URL to an optimized 1200x630 graphic.og:url: The canonical permanent URL of the shared resource.
2. Configuring Twitter Summary Cards with Large Images
By default, if only basic metadata is present, X (Twitter) renders a tiny square thumbnail beside the title. Declaring <meta name="twitter:card" content="summary_large_image"> forces Twitter to render a full-width panoramic card that commands 3x greater engagement on mobile feeds.
Common Technical Mistakes & Fixes
| Common Mistake | Algorithmic Consequence | Recommended Fix |
|---|---|---|
| Using relative image URLs in og:image (e.g., /images/og.jpg) | Social crawlers cannot resolve relative paths; the preview card renders blank. | Always declare complete absolute URLs: https://example.com/images/og.jpg. |
| Serving slow, uncompressed PNG files over 5MB | Social crawlers timeout waiting for image download, resulting in missing preview cards. | Compress OG images to WebP or optimized JPEG under 1 MB. |
Frequently Asked Questions
Why does LinkedIn or Facebook still show my old preview image after updating it?
Social platforms cache OpenGraph images for up to 7 days. Use the official LinkedIn Post Inspector or Facebook Sharing Debugger to force an immediate cache purge.