Debug Your Open Graph Tags Instantly
Preview how your page may appear when shared on Facebook, X, LinkedIn, and other social platforms — with social card previews and complete tag extraction.
What is the Open Graph Protocol?
A set of meta tags that control how your page appears when shared on social media — title, description, image, and more.
Turning Pages into Rich Social Objects
The Open Graph protocol, created by Facebook, lets any web page become a rich object in a social graph. By adding og: meta tags to your HTML <head>, you can provide the title, description, image, and other metadata used by many social platforms. Without OG tags, social platforms guess — often picking the wrong image, truncated title, or irrelevant description.
The Click-Through Advantage
A well-crafted social preview with an eye-catching image, compelling title, and clear description can improve engagement and click-through rates. Posts with proper OG tags perform more predictably than pages where platforms auto-generate previews from raw page elements.
X Cards Fallback
X (formerly Twitter) has its own tag system (twitter:), but when its parser doesn't find X-specific tags, it automatically falls back to your Open Graph tags. Setting proper OG tags covers most major social networks with one implementation.
How This Tool Works
Enter any URL and our server safely fetches the page, parses all og:, twitter:, and standard meta tags, then renders previews in the style of Facebook, X, and LinkedIn. You see a realistic preview of how your metadata may appear when your link is shared.
Open Graph Checker
Enter the full URL of any public webpage. Our server fetches it and extracts detected Open Graph, X Card, and selected SEO meta tags.
The Open Graph Tags Every Page Needs
These are the tags social platforms use to build preview cards. Missing any of the essentials degrades your social shares.
| Tag | Importance | What It Does | Recommended Value | Example |
|---|---|---|---|---|
| og:title | Essential | The headline shown in the social preview card. Most visible element. | 40–60 characters. Front-load keywords. | 10 Tips to Boost Your SEO in 2026 |
| og:type | Essential | Tells platforms what kind of content this is (article, website, video, etc.). | website for homepages, article for blog posts. |
article |
| og:image | Essential | The main image displayed in the preview. | 1200 × 630 pixels is a common recommended size. Use an absolute URL. | https://example.com/images/og-post.jpg |
| og:url | Essential | The canonical URL. Aggregates shares to one URL regardless of query parameters. | Use the clean, canonical URL without tracking parameters. | https://example.com/blog/seo-tips |
| og:description | Recommended | The description text below the title. Helps drive click-through. | 100–200 characters. Include a benefit and CTA. | Learn the proven SEO strategies that top marketers use to rank #1 in 2026. Free guide inside. |
| og:site_name | Recommended | Your brand/site name shown above the URL in previews. | Short brand name, consistent across all pages. | All In One Tools |
| og:locale | Optional | The language and region of the content. | Use language_TERRITORY format (e.g., en_US). | en_US |
| og:image:width | Recommended | Width of the og:image in pixels. Helps platforms pre-allocate space. | Match actual image width (e.g., 1200). | 1200 |
| og:image:height | Recommended | Height of the og:image in pixels. Helps platforms pre-allocate space. | Match actual image height (e.g., 630). | 630 |
| twitter:card | Recommended | Tells X which card layout to use. | summary_large_image for most content. |
summary_large_image |
| twitter:site | Optional | Your X @handle shown in the card. | Your official brand handle. | @allinonetools |
| Essential | Fallback title if og:title missing. Also used by search engines. | 50–60 chars. Should match or complement og:title. | SEO Tips 2026 — All In One Tools | |
| Recommended | Fallback description. Used by search engines and some social platforms. | 150–160 characters for SEO. | Complete guide to SEO in 2026... |
How to Use This Open Graph Checker
Four steps from URL to social previews.
Enter URL
Paste the full URL of the page you want to check (including https://).
Click Check
Our server safely fetches your page and extracts all OG, X, and meta tags.
Review Previews
See styled Facebook, X, and LinkedIn previews plus a full tag list.
Fix and Re-check
Edit your meta tags, re-check to verify, then use platform debuggers to refresh cache.
Social Image Requirements by Platform
Each platform has different image size and format preferences. Follow these for best results.
Facebook / LinkedIn
Ideal size: 1200 × 630 pixels (1.91:1 ratio).
Minimum: 600 × 315 pixels.
Max file size: 8MB.
Formats: JPG, PNG. Avoid text-heavy images — they render poorly in the feed.
X (Twitter)
Ideal size: 1200 × 628 pixels for summary_large_image.
Summary card: 240 × 240 (1:1 square).
Max file size: 5MB.
Formats: JPG, PNG, GIF (non-animated), WEBP.
Ideal size: 1000 × 1500 pixels (2:3 vertical).
Minimum: 600 × 900 pixels.
Formats: JPG, PNG. Vertical images perform best on Pinterest.
Slack / Discord
Ideal size: 1200 × 630 pixels (same as Facebook).
Fallback properties: Both fallback to OG tags when no platform-specific tags exist.
Image Caching
Important: Social platforms cache images aggressively. After updating an og:image, use each platform's debugger to force a refresh:
• Facebook: Sharing Debugger
• X (Twitter): Card Validator
• LinkedIn: Post Inspector
Common Image Mistakes
Avoid: Using relative URLs (/images/pic.jpg), images behind authentication, images smaller than 200×200, or images with excessive text overlay.
Master Social Link Previews Before Sharing
A guide explaining how social link previews work, how Open Graph and X Card tags control them, why thumbnails sometimes don't appear, and how to preview and fix link previews before sharing.
📘 Read Full Social Preview Guide →Honest by Design — What This Tool Does and Doesn't Do
This tool fetches and parses your page's meta tags. Here is exactly what it does and does not do:
- ✓ Fetches your page server-side and extracts all
og:,twitter:, and standard meta tags. - ✓ Renders previews in Facebook, X, and LinkedIn styles.
- ✓ Warns you about missing essential tags.
- ✓ Copies individual tags or the full report to clipboard.
- ✓ Does not force-refresh cached images on social platforms — use their debuggers for that.
- ✓ Does not validate image dimensions — check your actual image file.
- ✓ Does not show how your page will appear in every platform (only the big 3).
- ✓ Does not modify your site's tags — you edit your own HTML.
This tool does
- Extract detected og: and twitter: tags
- Render Facebook, X, LinkedIn style previews
- Show standard meta tags as fallbacks
- Warn about missing essential tags
- Copy individual tags or full report
- Fetches the target page server-side
This tool does not
- Force-refresh cached social images
- Validate image dimensions or file size
- Show previews for every social platform
- Modify your site's meta tags
- Store the URLs you check
- Require an account or API key
When to Use This OG Checker
Use the tool for these common scenarios.
Open Graph Problems and How to Fix Them
The most frequent issues that break social previews.
Image Not Showing
Social preview shows no image or a placeholder.
Fix: Verify og:image uses an absolute URL (https://), the image is publicly accessible, and meets minimum size. Use Facebook's Sharing Debugger to force cache refresh.
Title Truncated
Your title gets cut off with "..." in the preview.
Fix: Keep og:title under 60 characters. Front-load the most important words since platforms truncate from the end.
Old Image Still Showing
You updated the image but social previews still show the old one.
Fix: Social platforms cache images aggressively. Use each platform's debugger tool to force refresh: Facebook Sharing Debugger, X Card Validator, LinkedIn Post Inspector.
No OG Tags Found
Tool reports no Open Graph tags detected.
Fix: Tags must be in the HTML <head>. Check they're not loaded via JavaScript after page load — crawlers only see the initial HTML. Add them server-side.
Wrong URL in Preview
Preview shows a different URL than your page.
Fix: Add or fix the og:url tag to point to the canonical URL. Without it, platforms may pick up URLs with tracking parameters.
Blocked by Server
Tool can't fetch the page — timeout or forbidden error.
Fix: Your server may be blocking crawlers. Check robots.txt, WAF rules, and ensure user-agents aren't being rejected.
Open Graph Checker FAQs
Answers based strictly on how OG tags work.
Why is my image not showing up?
Common causes: relative URL instead of absolute (https://), image blocked by authentication, image smaller than 200×200, or the image is cached from a previous version. Use Facebook's Sharing Debugger to force refresh and verify the image URL is publicly accessible.
Open Graph vs X Cards?
Open Graph is Facebook's standard, used by Facebook, LinkedIn, Pinterest, Slack, Discord, and many others. X Cards is X's own system. When X doesn't find twitter: tags, it falls back to your og: tags. Set both for complete coverage.
Do I need og:url?
Yes, highly recommended. The og:url tag should be the canonical URL for the page. It aggregates all likes and shares to one URL even if the page is accessed via different URLs (with tracking parameters, mobile variants, etc.).
What image size should I use?
1200 × 630 pixels is a common recommended size for social previews. Platform-specific image and file-size limits may vary.
Why do platforms show old images?
Social platforms cache images for performance. After updating an og:image, use each platform's debugger (Facebook Sharing Debugger, X Card Validator, LinkedIn Post Inspector) to force a cache refresh.
My tags are in the HTML but the tool shows nothing?
OG tags must be present in the initial HTML response — not loaded via JavaScript after page load. Social crawlers do not execute dynamic scripts. If you are using React or Vue, ensure tags are rendered server-side (SSR) or statically generated.
Can I have multiple og:image tags?
Yes. Open Graph supports multiple images. While social platforms choose based on local placement layouts, this checker displays the first detected image in cards and lists all extracted instances below.
Are the URLs I check stored?
No. The URL is fetched for analysis but not stored after the request completes. Only a temporary rate-limit record (IP hash + count) is kept for abuse prevention. The target site sees our server's IP, not yours.