Open Graph Checker

Validate the Open Graph and Twitter Card tags on any web page to see exactly how it will appear when shared on social media. Our Open Graph Checker extracts all social meta tags, previews how your content displays on Facebook, Twitter, and LinkedIn, and identifies missing or misconfigured properties that could be reducing your social engagement. Stop guessing what your shares look like and start controlling them.

Key Features of Our Open Graph Checker

Multi-Platform Preview

See exactly how your URL will appear when shared on Facebook, Twitter, LinkedIn, and other platforms. Each preview uses the platform's actual display format, showing image cropping, title truncation, and description layout as they appear in real social feeds.

Complete Tag Extraction

Extracts every Open Graph and Twitter Card tag from the page, displaying the property name and value in a clear, readable format. Includes og:title, og:description, og:image, og:url, og:type, og:site_name, twitter:card, twitter:title, and all other social meta properties.

Image Validation

Verifies that the og:image URL is accessible, checks image dimensions against platform minimum requirements, validates file format compatibility, and reports image file size. Catches broken images before they result in preview failures on social shares.

Missing Property Alerts

Identifies required and recommended Open Graph properties that are absent from the page. Each missing property is flagged with an explanation of its impact and recommended value, helping you build a complete tag implementation.

Character Length Analysis

Checks og:title and og:description lengths against platform-specific display limits. Facebook truncates titles at approximately 88 characters and descriptions at 300 characters, while Twitter and LinkedIn have different limits. The checker flags values that will be truncated.

URL Consistency Check

Compares the og:url value with the actual page URL and any canonical tag present. Inconsistencies between these values can cause social platforms to associate shares with the wrong URL or create duplicate share counts across URL variations.

Twitter Card Type Validation

Validates Twitter Card markup including card type, image specifications for the selected card format, and proper twitter:site and twitter:creator attribution. Ensures your content uses the optimal card type for maximum Twitter engagement.

Raw Tag Code Display

View the exact HTML source code of each extracted tag for debugging purposes. This helps identify syntax errors, encoding issues, duplicate tags from conflicting sources, and other technical problems that are not visible in the formatted property display.

How to Use the Open Graph Checker

01

Step 1

Enter the full URL of the page you want to check into the input field. Make sure to include the https:// protocol prefix and use the exact URL that will be shared on social media, including any path segments or parameters.

02

Step 2

Click the check button to initiate the scan. The tool will fetch your page using a crawler simulation that mimics how social media platforms retrieve Open Graph data.

03

Step 3

Review the multi-platform preview section to see how your page appears on Facebook, Twitter, and LinkedIn. Compare the displayed title, description, and image with your intended presentation and note any discrepancies.

04

Step 4

Examine the extracted tags list to verify that all required and recommended Open Graph properties are present with correct values. Pay particular attention to og:image, og:title, og:description, and og:url.

05

Step 5

Check the validation results for flagged issues including missing tags, oversized or undersized images, truncated text, inaccessible image URLs, and URL inconsistencies. Each issue includes severity and recommendation.

06

Step 6

Fix any identified issues by updating your page's meta tags, then re-run the checker to confirm your changes resolved the problems. After verification, use Facebook's Sharing Debugger and Twitter's Card Validator to clear any cached preview data on those platforms.

Ready to Analyze?

Try Open Graph Checker now — completely free, no registration required

Use Tool Now

What Is an Open Graph Checker?

An Open Graph checker is a diagnostic tool that fetches a web page, extracts its Open Graph and Twitter Card meta tags, and displays exactly how the page will appear when shared on social media platforms. It bridges the gap between what you intended your social previews to look like and what platforms actually display based on the tags they find in your HTML.

When you enter a URL into our Open Graph Checker, the tool performs the same operation that social media platforms execute when someone shares your link. It sends an HTTP request to the URL, parses the HTML response, and extracts every og: and twitter: prefixed meta tag from the page head. The extracted data is then used to render simulated previews showing how the share will appear on Facebook, Twitter, LinkedIn, and other platforms.

Beyond simply displaying the tags, the checker validates each property against platform-specific requirements. It verifies that og:image points to an accessible image file of adequate dimensions, that og:url returns a valid HTTP response, that required properties are present, and that property values conform to expected formats. Each issue is flagged with a severity level and a specific recommendation for correction.

The tool also identifies common discrepancies between platforms. Because Facebook, Twitter, LinkedIn, and Pinterest each have slightly different display requirements and fallback behaviors, the same set of OG tags can produce different results on each platform. The checker shows these variations side by side, helping you optimize for all platforms simultaneously rather than discovering problems after content has already been shared.

For teams managing content at scale, the Open Graph Checker serves as a quality assurance step in the publishing workflow. Before a blog post, product page, or campaign landing page goes live, running it through the checker confirms that social previews meet quality standards. This prevents the common and embarrassing scenario of sharing a major piece of content only to discover that it displays with a missing image, wrong title, or generic description on social media.

The checker is particularly valuable after site migrations, CMS updates, or template changes that may inadvertently alter or remove Open Graph tags. These technical changes can break social sharing across your entire site without any visible indication on the pages themselves. A systematic check across key pages immediately after any technical change catches these issues before they affect your social media performance.

Why Checking Open Graph Tags Is Essential

Creating Open Graph tags is only half the equation. Without verification, you cannot be certain that your tags are properly formatted, accessible to social crawlers, and producing the previews you expect. Here are the critical reasons why regular Open Graph validation should be part of your workflow.

Social Crawlers Behave Differently Than Browsers

Your page may look perfect in a web browser, but social media crawlers process pages differently. They have strict timeout limits, typically two to five seconds, and will abandon the crawl if your page takes too long to respond. They do not execute JavaScript, so OG tags generated dynamically by client-side scripts may be invisible to social crawlers. They follow redirect chains differently and may not process tags on the final destination URL. The Open Graph Checker simulates this crawler behavior, revealing issues that are invisible during normal browser testing.

Image Accessibility and Size Compliance

The most common Open Graph failure is an image that does not display in social previews. This happens when the og:image URL returns a 404 error, when the image is blocked by robots.txt or authentication, when the image is too small for the platform's minimum requirements, or when the image server is too slow to respond within the crawler's timeout window. The checker validates image accessibility and dimensions to catch these issues before they result in image-less shares.

Preventing Cached Preview Problems

Social platforms aggressively cache Open Graph data. When you update your OG tags, the old cached data may persist for hours or even days, meaning shares continue to display outdated information. If the original cache captured incorrect or missing data, the problem compounds. Checking your OG tags before the first share ensures that the initial cached data is correct. If you need to update cached data, the checker's results confirm what needs to change, and you can then use platform-specific tools to clear their caches.

Cross-Platform Consistency

Each social platform displays OG data with slightly different formatting. Facebook shows og:site_name above the title, Twitter omits it, and LinkedIn displays it differently. Image cropping varies between platforms. Character limits for titles and descriptions differ. The checker previews your share on multiple platforms simultaneously, ensuring your content looks professional everywhere, not just on the one platform you tested manually.

Protecting Brand Reputation

When your content is shared with a broken image, wrong title, or irrelevant description, it reflects poorly on your brand. In professional contexts like LinkedIn or Slack channels, a poorly formatted link preview can undermine the credibility of otherwise excellent content. Regular OG checking ensures that every share of your content maintains the professional appearance your brand demands.

Maximizing Social Traffic ROI

If you invest time and budget in social media marketing, content promotion, or influencer outreach, poorly configured OG tags waste that investment. Every share that displays without a compelling preview represents lost potential clicks and engagement. Checking OG tags before launching campaigns ensures that your social investment produces maximum return.

Common Open Graph Issues and How to Fix Them

Through millions of URL checks, certain Open Graph problems appear consistently. Here are the most frequent issues, their causes, and step-by-step solutions for each one.

No Image Displayed in Social Preview

This is the most reported OG issue. Common causes include: the og:image tag is completely missing from the page, the image URL returns a 404 error or redirect, the image is served over HTTP while the page uses HTTPS causing mixed content blocking, the image is too small to meet platform minimums, or the image takes too long to load and the crawler times out. Solution: Add a valid og:image tag pointing to an HTTPS URL of an image at least 1200 by 630 pixels, hosted on a server that responds within two seconds.

Wrong Image Appearing in Preview

When the specified og:image fails validation, platforms fall back to scanning the page body for any available image, which may select a logo, icon, sidebar image, or advertisement. Solution: Verify your og:image URL loads correctly when accessed directly in a browser. Ensure the URL does not require authentication or cookies. Test that the image server responds quickly and does not block crawler user agents.

Outdated Preview After Tag Updates

Social platforms cache OG data for efficiency, so updating your tags does not immediately change existing previews. Facebook may cache data for up to 30 days. Solution: After updating OG tags, use the Facebook Sharing Debugger to click Scrape Again, which forces Facebook to re-fetch your page. For Twitter, submit the URL to the Card Validator. For LinkedIn, use the Post Inspector and click the refresh button. Allow 24 hours for caches to fully propagate.

Title or Description Truncated on Social Preview

Facebook truncates titles at approximately 88 characters and descriptions at about 300 characters. Twitter is more restrictive with titles at 70 characters. LinkedIn truncates at similar limits. Solution: Keep og:title under 60 characters and og:description under 200 characters to ensure complete display across all platforms. Front-load the most important information in case of truncation on stricter platforms.

OG Tags Present But Not Being Read

If your OG tags are generated by JavaScript after page load, social crawlers cannot see them because they do not execute JavaScript. Single-page applications built with React, Angular, or Vue often have this issue. Solution: Implement server-side rendering (SSR) or use a prerendering service that serves static HTML with OG tags to social crawler user agents. Verify by viewing your page source without JavaScript enabled.

Inconsistent og:url and Canonical URL

When og:url differs from the canonical tag or the actual page URL, social platforms may consolidate share counts under the wrong URL or display unexpected content. Solution: Ensure og:url, the canonical tag, and the page's actual URL all point to the same preferred URL. Do not include tracking parameters, session IDs, or URL fragments in any of these values.

Platform-Specific Open Graph Requirements

While the Open Graph protocol provides a universal standard, each social platform interprets and displays OG data with its own nuances. Understanding these platform-specific requirements ensures optimal previews everywhere your content is shared.

Facebook

Facebook was the creator of the Open Graph protocol and has the most comprehensive support. Required tags are og:title, og:type, og:image, and og:url. Facebook strongly recommends og:description and og:site_name. For images, the minimum size for a large preview is 600 by 315 pixels, but 1200 by 630 pixels is recommended for high-resolution displays. Facebook supports multiple og:image tags and will use the first valid one. The platform caches OG data aggressively, so use the Sharing Debugger to clear cache after updates.

Twitter

Twitter uses its own Card markup with twitter: prefixed tags but falls back to Open Graph tags when Card tags are absent. The twitter:card property is required to activate Card functionality. Twitter supports Summary, Summary with Large Image, App, and Player card types. For Large Image cards, the minimum image size is 300 by 157 pixels, and the aspect ratio is cropped to approximately 2:1. Twitter does not support multiple image tags and will use only the first one.

LinkedIn

LinkedIn reads standard Open Graph tags and displays them in a format similar to Facebook. The platform prefers images of 1200 by 627 pixels and supports JPEG and PNG formats. LinkedIn's Post Inspector allows you to preview and refresh cached OG data. One important difference is that LinkedIn displays the og:description more prominently than some other platforms, so investing in a compelling description particularly benefits LinkedIn sharing performance.

Pinterest

Pinterest reads og:image for Rich Pins and prefers vertical images with a 2:3 aspect ratio for optimal display in the pin feed. Pinterest also supports its own metadata through Pinterest Rich Pin markup, which can be validated through their Rich Pin Validator. For e-commerce sites, Pinterest can pull product pricing and availability from structured data alongside OG tags.

WhatsApp and Messaging Apps

WhatsApp, Telegram, Slack, and Discord all read Open Graph tags to generate link previews in messages. These platforms typically display og:title, og:description, and og:image in a compact card format. Image requirements are generally less strict than social media platforms, but images should still be at least 300 by 200 pixels and load quickly. Messaging app crawlers often have very short timeout windows, making fast server response times particularly important.

Frequently Asked Questions

Everything you need to know about Open Graph Checker

The Open Graph Checker analyzes all social media meta tags on a web page including og:title, og:description, og:image, og:url, og:type, og:site_name, og:locale, Twitter Card tags, and any additional OG or social properties. It validates each tag against platform requirements, checks image accessibility and dimensions, identifies missing required properties, and generates simulated social media previews showing how the page will appear on Facebook, Twitter, and LinkedIn.

This typically happens because your og:image tag either points to a URL that returns an error, references an image that is too small for Facebook's minimum requirements of 200 by 200 pixels, or the image server is too slow to respond before Facebook's crawler times out. It can also occur if your og:image tag is being generated by JavaScript, which Facebook's crawler cannot execute. Fix the image URL, ensure it loads quickly over HTTPS, and use Facebook's Sharing Debugger to clear the cached preview.

Each platform has its own cache clearing method. For Facebook, visit developers.facebook.com/tools/debug, enter your URL, and click Scrape Again. For Twitter, submit your URL to cards-dev.twitter.com/validator. For LinkedIn, use linkedin.com/post-inspector and click the refresh button. WhatsApp caches are harder to clear and typically require waiting 24 to 48 hours for automatic refresh. After clearing caches, verify the updated preview by sharing the link in a private test post.

Yes, you can check Open Graph tags on any publicly accessible URL, including competitor websites. The checker fetches the page in the same way social media crawlers do, extracting all available OG and Twitter Card tags. This makes it a valuable competitive research tool for seeing how competitors present their content on social media. Pages that require authentication or are blocked by robots.txt may not be fully accessible to the checker.

The minimum og:image size varies by platform. Facebook requires at least 200 by 200 pixels for a thumbnail and 600 by 315 pixels for a large preview. Twitter requires at least 144 by 144 pixels for Summary cards and 300 by 157 pixels for Large Image cards. LinkedIn requires at least 200 by 200 pixels. The universally recommended size is 1200 by 630 pixels, which works well across all major platforms and looks sharp on high-resolution displays.

If the checker finds no OG tags, the most likely causes are: your tags are generated by client-side JavaScript that the crawler cannot execute, your page redirects and the tags exist only on the original URL not the destination, your server blocks crawler user agents, or the tags are placed outside the HTML head section. Check your page source by right-clicking and selecting View Page Source to verify the tags appear in the raw HTML before any JavaScript execution.

Yes, every page that might be shared on social media should have its own unique set of Open Graph tags with content specific to that page. Using the same og:title, og:description, and og:image across all pages results in every share looking identical regardless of which page was shared, which confuses users and reduces engagement. CMS platforms and SEO plugins can automate unique OG tag generation based on page content, making per-page customization manageable even for large sites.

Check Open Graph tags whenever you publish new content, update existing pages, change your site template or theme, install or update CMS plugins, or migrate your site to a new platform. For high-traffic sites, establish a quarterly audit of your most-shared pages to catch any degradation. Always check OG tags before launching social media campaigns or sending content to influencers, as broken previews waste promotional investment and damage brand perception.

Related SEO Tools

Explore other tools to improve your SEO strategy

Open Graph Generator

Create Open Graph tags for rich social media sharing previews

Meta Tag Generator

Create optimized meta tags for better search engine visibility

Meta Tags Analyzer

Analyze and evaluate the meta tags on any webpage for SEO