Check Open Graph Tags
Enter a URL to analyze its Open Graph and Twitter Card meta tags. See how your page will appear when shared on social media platforms.
Frequently Asked Questions
Master Open Graph tags for perfect social media sharing
Open Graph tags are HTML meta tags that control how your content appears when shared on social media platforms like Facebook, LinkedIn, Twitter, and messaging apps. Originally created by Facebook, they've become the standard for social sharing across the web.
Why You Need Them:
Control Your Brand Appearance: Without Open Graph tags, social platforms randomly select text and images from your page, often resulting in poor, unprofessional-looking previews.
Increase Click-Through Rates: Posts with properly configured Open Graph tags (especially images) receive significantly more engagement and clicks than plain text links.
Consistent Branding: Ensure your content looks professional and branded across all social platforms with properly sized images and compelling descriptions.
Better Analytics: When users share your content, Open Graph tags help you track which pages perform best on social media, informing your content strategy.
For businesses, marketers, and content creators, Open Graph tags are essential for maximizing the impact of social media sharing and driving traffic from social platforms.
The four essential Open Graph tags that every page should include are:
1. og:title - The title of your content as it should appear on social media. Keep it concise and compelling (50-60 characters recommended). Example: <meta property="og:title" content="Your Page Title">
2. og:description - A brief description that appears below the title. Summarize your content in 2-3 sentences (155-160 characters recommended). Example: <meta property="og:description" content="Your compelling description">
3. og:image - The image URL that appears in the social media preview. Use 1200x630 pixels for best results across platforms. Example: <meta property="og:image" content="https://example.com/image.jpg">
4. og:url - The canonical URL of the page being shared. This should be the permanent URL without tracking parameters. Example: <meta property="og:url" content="https://example.com/page">
Additional Recommended Tags:
- og:type - Type of content (website, article, product, etc.)
- og:site_name - The name of your overall website
- og:locale - Language and region code (e.g., en_US)
Open Graph tags and Twitter Card tags serve the same purpose but for different platforms:
Open Graph Tags: Originally created by Facebook, these tags (og:title, og:description, og:image) control how content appears on Facebook, LinkedIn, Pinterest, and most other social platforms. They're now the industry standard for social sharing.
Twitter Card Tags: Twitter-specific tags (twitter:card, twitter:title, twitter:description, twitter:image) that control how content appears specifically on Twitter/X. Twitter Cards offer additional card types like summary, summary_large_image, app, and player cards.
Do You Need Both? Twitter will actually fall back to Open Graph tags if Twitter Card tags aren't present. However, for best results on Twitter, include both:
- twitter:card - Card type (usually "summary_large_image")
- twitter:site - Your Twitter handle (@yourhandle)
- twitter:creator - Author's Twitter handle
Best Practice: Implement both Open Graph and Twitter Card tags for maximum compatibility and control. This ensures optimal appearance across all social platforms while giving you platform-specific customization options.
Adding Open Graph tags is straightforward - they go in the <head> section of your HTML. Here's how to implement them:
For Static HTML Sites: Add meta tags directly to your HTML <head> section:
<head> <meta property="og:title" content="Your Page Title"> <meta property="og:description" content="Your page description"> <meta property="og:image" content="https://example.com/image.jpg"> <meta property="og:url" content="https://example.com/page"> <meta property="og:type" content="website"> </head>
For WordPress: Use plugins like Yoast SEO, Rank Math, or All in One SEO. These provide simple interfaces to set Open Graph tags for every page without coding.
For React/Next.js: Use next/head or react-helmet to dynamically insert meta tags. For Next.js 13+, use the Metadata API in your page components.
For Other CMS Platforms: Shopify, Squarespace, Wix, and Webflow all offer built-in Open Graph settings in their page editors or SEO sections.
Dynamic Content: For blogs or e-commerce sites, programmatically generate Open Graph tags from your content database, ensuring each page has unique, relevant meta tags.
After Adding Tags: Use our Open Graph Checker above to verify your tags are implemented correctly and appearing as intended on social platforms.
The recommended size for Open Graph images is 1200x630 pixels with a 1.91:1 aspect ratio. This size works optimally across all major social platforms:
Why 1200x630: This resolution is large enough to display crisp, high-quality previews on high-DPI screens while being supported by Facebook, LinkedIn, Twitter, and other platforms. It also meets Facebook's minimum requirement of 1200x630 for high-resolution previews.
Image Best Practices:
- File Size: Keep images under 5MB for fast loading. Aim for 200-500KB for optimal performance
- Format: Use JPG for photographs, PNG for graphics with text or transparency. Both formats are widely supported
- Safe Zone: Keep important text and logos within a central 1200x600 area, as some platforms may crop edges
- Text Readability: If including text on images, use large, bold fonts (minimum 60px) for readability at smaller sizes
- Branding: Include your logo or brand elements consistently across all Open Graph images for recognition
Platform-Specific Dimensions: While 1200x630 works everywhere, you can also add og:image:width and og:image:height tags to specify exact dimensions. Twitter specifically supports 1200x628 for summary_large_image cards.
Testing: After uploading your image, use our Open Graph Checker to see exactly how it will appear on different social platforms and ensure it displays correctly.
What is an Open Graph Checker?
An Open Graph Checker is a validation tool that analyzes the Open Graph (OG) meta tags on web pages to ensure social media platforms like Facebook, LinkedIn, Twitter, and others display your content correctly when shared. Open Graph is a protocol developed by Facebook in 2010 that standardizes how web pages present themselves in social media feeds through structured metadata embedded in the page's HTML. These OG tags control the title, description, image, and other information that appears in social media previews, transforming plain URLs into rich, clickable cards that drive significantly higher engagement.
When someone shares a URL on social media, platforms scrape the page's Open Graph tags to generate a preview. The checker simulates this process, extracting og:title, og:description, og:image, og:url, og:type, and other tags to show exactly how your content will appear across different social networks. It validates that images meet size requirements, text fits within character limits, and required tags are present and properly formatted. Many checkers also test Twitter Card tags (twitter:card, twitter:image, etc.) which work similarly for Twitter/X-specific optimizations.
This tool is critical for marketers, content creators, and web developers who need social shares to drive traffic. A missing or broken OG image can reduce click-through rates by 80% compared to posts with compelling visuals. Truncated titles or generic descriptions fail to communicate value propositions, causing potential visitors to scroll past. An Open Graph Checker provides immediate feedback on how shared links will appear, allowing optimization before launching campaigns, publishing content, or sharing important pages across social channels.
How This Open Graph Checker Works
The Open Graph Checker operates by fetching the target URL and parsing its HTML to extract all Open Graph meta tags from the page's <head> section. When you enter a URL, the tool makes an HTTP request identical to what social media platforms perform when scraping links for preview generation. It extracts tags like <meta property="og:title" content="Your Title"> and analyzes their values against platform requirements and best practices.
The checker validates multiple aspects of your OG implementation: it verifies required tags are present (at minimum og:title, og:description, og:image, and og:url), tests that the og:image URL is accessible and loads correctly, checks image dimensions against platform minimums and recommendations, validates that text content fits within character limits for optimal display, and ensures no duplicate or conflicting tags exist. Many checkers also test Twitter Card tags, which work alongside OG tags for Twitter/X-specific optimizations.
Results are presented as visual previews showing exactly how your link will appear on different social platforms—Facebook, LinkedIn, Twitter, Pinterest, and others. This preview includes the title as it will display (with truncation if too long), the description text, the image as it will render, and additional metadata like site name or author information. The tool highlights issues with color-coded warnings (missing required tags, images too small, text exceeding limits) and provides specific remediation recommendations. Many advanced checkers include debugging features showing the raw tag values, cache-clearing tools to force platforms to re-scrape after changes, and comparison views showing before/after when you update tags.
Common Open Graph Configuration Mistakes
Missing or Inaccessible OG Image
The og:image tag is missing entirely, points to a broken URL, or references an image blocked by robots.txt or server permissions, causing social platforms to display no image or a generic placeholder.
- Create a dedicated OG image at 1200x630px (Facebook's recommended size)
- Upload the image to your server in a publicly accessible location
- Use absolute URLs (https://example.com/image.jpg) not relative paths (/image.jpg)
- Ensure the image URL isn't blocked by robots.txt or login requirements
- Test the image URL directly in a browser to verify it loads
- Add: <meta property="og:image" content="https://yoursite.com/og-image.jpg">
- Include og:image:width and og:image:height tags for faster rendering
Image Dimensions Too Small or Wrong Aspect Ratio
OG images smaller than platform minimums (typically 200x200px) or with wrong aspect ratios get cropped awkwardly, appear blurry, or are rejected entirely by some platforms.
- Use 1200x630px as the standard size—works well across all major platforms
- Maintain 1.91:1 aspect ratio (width to height) for Facebook/LinkedIn optimization
- Ensure minimum 200x200px to meet platform requirements
- Keep important content in the center—edges may be cropped on mobile displays
- Design with a safe zone: keep text and key visuals within the center 80% of the image
- Test images using the OG Checker's preview across different platforms
- Compress images to under 5MB file size for fast loading
Title or Description Exceeding Character Limits
og:title longer than 60-70 characters or og:description exceeding 200 characters gets truncated mid-sentence on social platforms, creating incomplete or confusing previews.
- Keep og:title to 60 characters maximum for Facebook mobile display
- Limit og:description to 200 characters for cross-platform compatibility
- Front-load important information—put key value in first 40 characters
- Write complete thoughts that make sense even if truncated
- Test different lengths using OG Checker's platform-specific previews
- Consider platform-specific variations: longer titles work on LinkedIn (120 chars) vs Facebook (60 chars)
- Avoid filler words—every character should add value
Missing Required Tags or Incomplete Implementation
Implementing only some OG tags (like og:image) without the full minimum set causes unpredictable display behavior and platform-specific failures.
- Implement the required minimum: og:title, og:description, og:image, og:url
- Add og:type (typically "website" for most pages, "article" for blog posts)
- Include og:site_name for brand consistency
- Add og:locale for internationalization (e.g., "en_US")
- For articles, add article:published_time and article:author
- Use og:image:alt for accessibility and context
- Validate complete implementation with OG Checker before publishing
Stale Cache Preventing Tag Updates
Social platforms cache OG data aggressively—updating tags on your page doesn't immediately change how shared links appear because platforms continue showing cached versions.
- Use Facebook's Sharing Debugger (developers.facebook.com/tools/debug/) to force re-scrape
- Submit URL to LinkedIn Post Inspector to refresh LinkedIn's cache
- Use Twitter Card Validator (cards-dev.twitter.com/validator) for Twitter/X
- Add version parameters to image URLs when updating: og-image.jpg?v=2
- Allow 24-48 hours for cache expiration on platforms without manual refresh tools
- Test OG tags BEFORE sharing widely to avoid cache issues
- For critical launches, prime the cache by sharing to test accounts days in advance
Duplicate or Conflicting Tags
Multiple og:title or og:image tags on the same page, or conflicts between OG tags and Twitter Card tags, cause unpredictable platform behavior.
- Ensure only ONE of each OG property exists per page (one og:title, one og:image, etc.)
- Check that plugins or themes aren't injecting duplicate tags
- Use browser DevTools to inspect the page source and identify duplicates
- For Twitter, use twitter:card alongside OG tags—they're complementary, not conflicting
- Remove any manually-added tags if your CMS or plugin auto-generates them
- Validate with OG Checker which will flag duplicate tag issues
Real-World Open Graph Success Stories
E-commerce Store Increases Social Referral Revenue 240%
News Publication Boosts Article Shares by 89%
SaaS Company Generates Leads Through LinkedIn Optimization
Event Platform Fixes Missing OG Tags, Recovers Ticket Sales
Frequently Asked Questions About Open Graph Tags
What's the difference between Open Graph tags and Twitter Card tags?
Open Graph tags (og:*) are Facebook's protocol used by Facebook, LinkedIn, Pinterest, and most other social platforms. Twitter Card tags (twitter:*) are Twitter/X's proprietary version offering similar functionality with platform-specific features. Twitter actually falls back to OG tags if Twitter Card tags aren't present, meaning OG tags work on Twitter too, but Twitter Card tags allow Twitter-specific optimizations like card types (summary, summary_large_image, player, app).
Best practice is to implement both: use OG tags as your foundation since they work across all platforms, then add Twitter Card tags for Twitter-specific enhancements. The two work together—Twitter uses twitter:card to determine display format, twitter:image if present (or falls back to og:image), and twitter:title (or falls back to og:title). Implementing both gives you maximum control: OG tags ensure compatibility everywhere, while Twitter tags let you optimize specifically for Twitter's display requirements and unique card types. Many websites successfully use only OG tags and accept Twitter's automatic interpretation, but adding Twitter tags takes minimal extra effort and provides additional optimization opportunities.
How do I force Facebook to refresh its cache of my Open Graph tags?
Use Facebook's Sharing Debugger tool at developers.facebook.com/tools/debug/. Enter your URL and click "Debug"—this forces Facebook to re-scrape your page and update its cache immediately. The tool shows you exactly what Facebook sees (the OG tags it extracted) and any errors or warnings. Click "Scrape Again" if you've made changes and need to refresh multiple times. This is essential after updating OG tags because Facebook caches aggressively and may show old data for days or weeks without manual refresh.
For LinkedIn, use the Post Inspector at linkedin.com/post-inspector/ which works similarly. For Twitter/X, the Card Validator at cards-dev.twitter.com/validator forces re-scraping. Pro tip: when launching important campaigns, use these tools to prime the cache before sharing publicly—ensure your OG tags appear perfectly before anyone else shares the link. If you're updating an already-viral URL, be aware that users who previously shared the link will see the old cached version indefinitely; only new shares will show updated tags. For this reason, test and perfect OG tags before initial sharing rather than trying to fix them after the fact.
Should I use different OG images for different social platforms?
You can, but for most use cases, a single well-designed image at 1200x630px works acceptably across all platforms. This 1.91:1 aspect ratio is Facebook's recommended size and works well on LinkedIn (which recommends 1200x627px—essentially the same), adequately on Twitter, and reasonably on Pinterest (though Pinterest prefers taller 2:3 ratio images like 1000x1500px for optimal pinning). The benefit of a single image is simplicity—one design, one implementation, consistent branding.
Platform-specific images make sense for advanced optimization or when a platform represents a critical channel. For example, if Pinterest drives significant traffic, create a tall pinterest-specific image and use og:image for the standard 1200x630px while adding a separate Pinterest meta tag. Some CMSs and plugins support platform-specific tags, serving different images to different platforms automatically. The ROI calculation: if you're a visual brand where Pinterest is crucial, platform-specific optimization is worth the effort. If you're B2B focused on LinkedIn, ensure your design works perfectly at LinkedIn's dimensions even if it's technically labeled for Facebook. For most websites, perfect one excellent 1200x630px image rather than creating mediocre platform-specific variants. Design conservatively with important content in the center to handle different crops gracefully.
Do Open Graph tags affect SEO or search rankings?
Open Graph tags don't directly influence Google's search rankings—Google has explicitly stated that OG tags are not ranking factors. However, they have indirect SEO benefits worth considering. First, Google sometimes uses og:title and og:description as fallbacks when standard title tags and meta descriptions are missing or poor quality, affecting how your page appears in search results (though this is not recommended practice—always set proper title and meta description tags independently).
More significantly, OG tags impact SEO indirectly through social signals. Content with optimized OG tags gets shared more, clicked more on social media, and generates more social referral traffic. This increased engagement can lead to more backlinks (as popular content gets referenced), more brand searches (as awareness grows), and more direct traffic (as audiences grow). While correlation doesn't equal causation, there's strong evidence that content performing well socially also tends to rank well in search. Additionally, the increased referral traffic from social media provides diversification—less dependence on Google for traffic. Treat OG tags as a social media and traffic optimization tactic with SEO side benefits rather than a direct SEO strategy. Optimize both independently: perfect your title tags and meta descriptions for search, perfect your OG tags for social.
Can I test how my Open Graph tags look without actually sharing on social media?
Yes, this is exactly what Open Graph Checkers do. Tools like Facebook's Sharing Debugger, LinkedIn's Post Inspector, Twitter's Card Validator, and third-party services like OpenGraph.xyz or Metatags.io show you visual previews of how your link will appear on each platform without requiring actual sharing. These previews are extremely accurate—what you see in the preview is what users will see when the link is shared.
This testing capability is invaluable for quality control. Before launching campaigns, publishing important content, or updating product pages, use these tools to verify OG tags display perfectly. Test different variations of images and copy to see which is most compelling. Check how text truncation works at different lengths. Verify images display crisply without awkward cropping. Catch errors like broken image links or missing tags before anyone shares publicly. This proactive approach prevents embarrassing situations where thousands of users share content that appears broken or unprofessional. Make OG testing part of your pre-publish checklist: write content, create OG image, add OG tags, test with checker, fix any issues, then publish. This workflow ensures every page is social-sharing-ready from day one.
Do I need to add Open Graph tags to every page or just important ones?
Ideally, every public-facing page should have OG tags because you can't predict which pages users will share. That said, prioritize strategically if resources are limited. Essential pages for OG implementation include: homepage (often the most-shared page), blog posts and articles (frequently shared content), product pages (for e-commerce), landing pages for campaigns (designed to be shared), and any page you link to in paid social ads (ads require good OG tags for preview display).
Lower priority pages include: utility pages (terms of service, privacy policy—rarely shared), search results pages (dynamic, typically not shared), account dashboards (behind login, can't be scraped), and purely navigational pages. Most modern CMSs and plugins can automatically generate OG tags for all pages using templates—homepage uses site-level defaults, blog posts dynamically pull featured images and post titles, products pull product photos and names. This automation makes universal coverage practical without manual work per page. If implementing manually or on legacy systems, start with high-value pages and expand coverage over time. Monitor your analytics to see which pages actually get social referrals—that data reveals which pages are being shared and deserve OG optimization priority. A pragmatic approach: set up templated OG tags site-wide for baseline coverage, then hand-optimize tags for your top 20-50 most-important or most-shared pages for maximum impact.