Check Open Graph and Twitter Card meta tags for any URL. Free OG checker with social media previews for Facebook, X/Twitter, LinkedIn, Discord, WhatsApp, and Slack.
Enter a URL and click Check OG Tags. That is the entire workflow.
The checker validates your og:title, og:description, og:image (including file size and accessibility), og:url, og:type, og:site_name, og:locale, and all Twitter Card properties. Results include a pass/warn/fail status for each tag with specific recommendations.
Open Graph tags are HTML meta tags that control how a URL appears when shared on social media platforms. Facebook introduced the Open Graph protocol in 2010, and it has since become the universal standard adopted by LinkedIn, Discord, WhatsApp, Slack, Telegram, and most messaging apps.
Without Open Graph tags, platforms scrape whatever they can find, usually the page title and a random image or no image at all. The result is an unappealing link preview that gets fewer clicks. With properly configured OG tags, you control the exact title, description, and image that appear in every social share.
Open Graph tags live in the <head> section of your HTML and use the property attribute instead of the name attribute:
<meta property="og:title" content="Your Page Title" />
<meta property="og:description" content="A short summary of the page content." />
<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" />Not every OG property carries equal weight. Here are the five tags that matter most and what each one controls:
| Tag | Required? | What it does |
|---|---|---|
| og:title | Yes | The headline shown in the link preview. Keep it under 88 characters to avoid truncation on Facebook. This is the single most important tag. It determines whether someone clicks. |
| og:description | Recommended | A one or two sentence summary shown below the title. Keep it under 200 characters. If missing, platforms may auto-generate one from the page content, which rarely looks good. |
| og:image | Yes | The image displayed in the preview card. This is what makes or breaks engagement. Posts with images get 2-3x more interaction. Must be an absolute URL. |
| og:url | Recommended | The canonical URL for the page. This tells platforms which URL to associate with the content, preventing duplicate entries when the same page is accessible at multiple URLs. |
| og:type | Recommended | The content type. Use website for homepages and general pages, article for blog posts and news. Defaults to website if not set. |
Two additional properties are worth setting: og:site_name (your brand name, shown on Discord and Slack) and og:locale (the language of the content, defaults to en_US). This checker validates all seven and flags anything missing or misconfigured.
X/Twitter uses its own meta tag system called Twitter Cards. The good news: if you have Open Graph tags, X/Twitter falls back to them automatically. The bad news: the fallback behavior is not always ideal, and you lose control over the card format.
The most important Twitter-specific tag is twitter:card, which controls the card layout:
summary -- a small square image on the left with title and description on the right. Good for articles and general content.summary_large_image -- a large image above the title and description. Best for visual content, product pages, and anything where the image tells the story.
Other useful Twitter Card tags include twitter:title (overrides og:title on X/Twitter only), twitter:description, twitter:image, and twitter:site (your @username). This OpenGraph checker validates all of them and shows whether X/Twitter will use your dedicated tag or fall back to OG.
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@yourbrand" />
<meta name="twitter:title" content="Your Page Title" />
<meta name="twitter:description" content="A concise summary." />
<meta name="twitter:image" content="https://example.com/twitter-image.jpg" />Each platform has its own quirks for rendering link previews. Here is what you need to know:
| Platform | Image aspect ratio | Max title length | Notes |
|---|---|---|---|
| 1.91:1 | ~88 chars | Caches aggressively. Use the Facebook Sharing Debugger to force a re-scrape after updating tags. | |
| X / Twitter | 2:1 (large) or 1:1 (summary) | ~70 chars | Requires twitter:card for the best layout. Falls back to OG tags if Twitter-specific tags are missing. |
| 1.91:1 | ~150 chars | Reads OG tags directly. Uses og:image, og:title, og:description. Caches previews and can take hours to update. | |
| Discord | Flexible | ~256 chars | Shows og:site_name as a label above the title. Displays the image below the description in an embed card with a colored left border. |
| 1.91:1 | ~60 chars | Previews appear inside the message bubble. Truncates aggressively on mobile. Caches hard. May need 24-48 hours to refresh. | |
| Slack | Flexible | ~100 chars | Unfurls links using OG tags. Shows og:site_name, title, description, and image in an indented card with a left border. |
The safest approach: design for Facebook's 1.91:1 aspect ratio at 1200×630 pixels. Every other platform handles this size well. This OpenGraph checker shows you a live preview for all six platforms so you can see exactly how your link will render before sharing it.
After checking thousands of URLs, these are the issues that come up most often:
https://). A relative path like /images/og.jpg will not resolve when platforms fetch the page.name instead of property. OG tags use <meta property="og:...">, not <meta name="og:...">. Some platforms tolerate the wrong attribute, but others silently ignore it.The og:image is the most visually impactful tag. Getting it right is worth the effort:
| Property | Recommendation |
|---|---|
| Dimensions | 1200×630 pixels (1.91:1 aspect ratio). Works on every platform. |
| Minimum size | 600×315 pixels. Below this, Facebook may not display the image. |
| File size | Under 1MB for fast loading. Maximum 8MB (Facebook's hard limit). |
| Format | JPEG or PNG. WebP support varies by platform, so stick with JPEG/PNG for universal compatibility. |
| Content | Include your headline text on the image itself. Many users see the image before reading the title, especially on mobile feeds. |
| Safe zone | Keep important content away from edges. Some platforms crop the image slightly depending on the card type and device. |
This OG checker validates your image by fetching it and reporting the content type, file size, and HTTP status. If the image returns a non-200 status or is not a recognized image format, it flags the issue immediately.
No. The URL is sent to our server so we can fetch the page on your behalf (since browsers cannot make cross-origin requests to arbitrary URLs), but we do not store the URL or the results. The analysis happens in real-time and is discarded after the response is returned.
The OG Score is the percentage of validation checks that passed. It evaluates og:title, og:description, og:image (including accessibility and file size), og:url, og:type, og:site_name, og:locale, and all Twitter Card properties. A score of 80% or higher means your page is well-configured for social sharing. Below 50% means you are missing critical tags.
Facebook caches OG tags aggressively. If you recently updated your og:image, the old image may still appear. Use the Facebook Sharing Debugger to force a re-scrape. Also check that you do not have multiple og:image tags. Facebook may pick an unintended one.
Not strictly, but it is recommended. X/Twitter falls back to OG tags when Twitter Card tags are missing, so your content will still display. However, setting twitter:card at minimum gives you control over the card layout (summary vs. summary_large_image), which OG tags alone cannot specify.
The HTML <title> tag appears in the browser tab and search engine results. The og:title tag is used exclusively for social media previews. They can (and often should) be different. Your SEO title might include your brand name, while your og:title should focus on the content being shared. This checker compares both in the "Page Meta vs OG Tags" table.
This checker fetches the page as an anonymous visitor, the same way social media platforms would. If your page requires login, the checker will see whatever an unauthenticated user sees, which is exactly what Facebook, X/Twitter, and other platforms will see when someone shares the link. If the page redirects to a login screen, the OG tags from that login page will be analyzed instead.
Check after every deployment that changes page templates, CMS updates that modify metadata, or before any major social media campaign. It is also worth running this checker on your most-shared pages periodically. Template changes or CMS migrations can silently break OG tags.
Use JPEG for photographs and complex images, PNG for graphics with text or transparency. Avoid WebP. While browser support is universal, some social media crawlers still have inconsistent WebP handling. Keep the file under 1MB for fast loading.
If you are debugging how your pages appear to crawlers, bots, and social media platforms, these tools handle related tasks:
<head> section where they belong.Structured page data instead of raw HTML. Your agent processes less, decides faster, and costs less to run.