Open Graph Checker
Extract and review all Open Graph meta tags from any URL.
Extract and review all Open Graph meta tags from any URL.
This free Open Graph Checker from KX Toolkit is part of our all-in-one online toolkit. It runs entirely in your browser, so your data never leaves your device for client-side operations. 100% free, forever - no paywall, no credit card, no trial.
How to use the Open Graph Checker
- Enter the URL or domain.
- Pick the depth or check options if the tool supports them.
- Run the audit - results stream in as each check completes.
- Export the report or fix the issues flagged.
What you can do with the Open Graph Checker
- Pre-flight a new website before going live.
- Quick monthly health check on client sites.
- Diagnose why a page is slow or returning errors.
- Verify redirects after a domain or URL migration.
Why use KX Toolkit's Open Graph Checker
- Browser-based: Works on Windows, macOS, Linux, iOS and Android - no install, no extension.
- Privacy-first: Client-side tools never upload your data; server-side tools delete files right after processing.
- Mobile-friendly: Full feature parity on phones and tablets - not a stripped-down view.
- Fast: Optimised for instant feedback. No artificial waiting screens, no email-gated downloads.
- One hub for everything: 300+ tools across SEO, text, image, PDF, code, color, calculators and more - skip switching between sites.
Tips for the best results
Always run an audit BEFORE you publish, not after - most issues are easier to fix while the page is still in staging.
Related Website Management Tools
If you find this tool useful, explore the full Website Management Tools collection or browse our complete tool directory. KX Toolkit is built for marketers, developers, designers, students and anyone who needs a quick utility without signing up for yet another SaaS.
What are the essential Open Graph tags every page should have?
The minimum set is og:title, og:type, og:image, and og:url. Recommended additions are og:description, og:site_name, og:locale, and twitter:card with twitter:image. og:type should match the content (website, article, product). og:image must be a public absolute URL, ideally 1200x630 pixels in JPEG or PNG under 8MB. Missing any of the four required tags causes Facebook, LinkedIn, and Slack to fall back to the page title and a random thumbnail, producing ugly previews that suppress click-through.
Why does my shared link show the wrong image or no image at all?
Common causes are missing og:image tag, image URL is relative instead of absolute, image is behind authentication or a robots.txt block, image dimensions below 200x200 minimum, image file too large (over 8MB), or Facebook has cached an older version. Use the Facebook Sharing Debugger to force a re-scrape. For LinkedIn use the Post Inspector. After fixing tags, debuggers update the cache and show the corrected preview within seconds, but propagation to existing shared links can lag.
What image dimensions work best across all social platforms?
1200x630 pixels (1.91:1 ratio) is the universal sweet spot. Facebook, LinkedIn, Slack, and Discord all render this size cleanly. Twitter prefers 1200x675 (16:9) for summary_large_image cards. Provide both dimensions when possible, with og:image at 1200x630 and twitter:image at 1200x675. Keep file size under 1MB for fast scraping. Place key text in the center 1100x570 safe zone, since some platforms crop edges. Avoid text under 24pt because mobile thumbnails render small.
Do Open Graph tags affect SEO or only social sharing?
Open Graph tags do not directly affect Google rankings, but they heavily influence social click-through, which drives referral traffic, brand impressions, and indirect SEO signals like backlinks and brand searches. A well-tagged page on LinkedIn or Twitter can earn 3-5x the engagement of an untagged one. Some search engines like Bing and DuckDuckGo also use og:image as a fallback for image search results. Treat OG tags as part of your distribution strategy, not just metadata.
How do I handle Open Graph for dynamic pages or single-page apps?
OG tags must be present in the initial HTML response because most scrapers (Facebook, LinkedIn, Slack) do not execute JavaScript. Single-page apps that inject tags client-side will appear blank to crawlers. Solutions: use server-side rendering (Next.js, Nuxt), prerender pages with services like Prerender.io, or detect crawler user agents and serve static HTML. Test with the Facebook Sharing Debugger, which shows exactly what Facebook sees when scraping your URL.
Should each page have unique Open Graph tags, or can I reuse them?
Each page should have unique og:title, og:description, og:url, and og:image to maximize relevance. Generic site-wide tags lead to identical-looking previews regardless of which page is shared, which kills click-through on blog posts and product pages. Article pages should use og:type=article with article:author and article:published_time. Product pages should use og:type=product. Unique, contextual tags signal quality and relevance to the recipient, materially improving share-driven traffic.
No reviews yet
Be the first to share your experience with the Open Graph Checker.