An open graph checker fetches a live URL and reads the actual og:* and twitter:* tags in its HTML — not what you think you shipped, but what Facebook, LinkedIn, X and Slack really see when someone shares the link. This og checker goes further than a raw tag dump: paste a URL and it renders three realistic social share previews — a Facebook/LinkedIn card, an X (Twitter) large-image card, and a compact Slack/iMessage-style unfurl — plus a table of every Open Graph and Twitter Card tag found and a red-flag list of what's missing, with the concrete consequence of each gap. It's free, needs no signup, and checks any public URL in seconds.
Open Graph tags decide what your link looks like everywhere it travels, and the failure modes are ugly. No og:image and platforms scrape a random image off the page — a nav icon, an ad, or nothing at all. A missing twitter:card tag downgrades your X share from a big clickable card to a bare text link. A relative image path, a client-side-injected tag, or a bot-blocked image URL all render as an empty grey box. And because every platform caches previews aggressively, a broken card keeps circulating long after you fix the page. Every share into a feed, a DM, a Slack channel or a group chat is a small ad you either designed or left to chance.
Checking one URL by hand is exactly how you should debug a broken opengraph preview. Keeping the tags correct across an entire site — every blog post, product page and landing page, through every template change and CMS migration — is the part that doesn't scale by hand, and it's what Black & Gold SEO automates: it audits Open Graph and Twitter Card coverage site-wide, generates correct replacements, and ships the approved fixes to your pages.
How to use it
- 1
Paste the URL you want to check
Use the full URL of the exact page people will share — including https:// and any trailing slash. The tool fetches the live HTML the same way facebookexternalhit, Twitterbot, LinkedInBot and Slackbot do, so you're testing what the scrapers actually receive, not what your browser renders after JavaScript runs.
- 2
Read the three share previews
The Facebook/LinkedIn card, the X large-image card and the Slack/iMessage unfurl are built from your real tags using each platform's fallback chain — og:title falls back to your <title> tag, og:description to your meta description, and twitter:* tags fall back to og:*. If a preview looks wrong here, it will look wrong in the feed.
- 3
Scan the full tag table
Every og:* and twitter:* tag found is listed with its value. Look for stale titles from an old template, a relative og:image path (must be an absolute https:// URL), an og:url that doesn't match your canonical, and duplicated or conflicting tags left behind by SEO plugins.
- 4
Fix the missing tags
The red missing-tags section tells you exactly what's absent and what each gap costs you — for example, no og:image means platforms scrape a random page image or show none. Add the tags to your page's <head>: og:title, og:description, og:image (1200×630px, under 5 MB), og:url, og:type and twitter:card cover almost every platform.
- 5
Re-scrape the platform caches
Platforms cache cards aggressively, so a fix isn't live until they re-fetch. Force a refresh with Facebook's Sharing Debugger and LinkedIn's Post Inspector; X refreshes on its own crawl cycle, so the fastest guaranteed fix there is changing the og:image filename. Then re-run this checker to confirm the tags are correct at the source.
The og:image is where most share cards are won or lost, and the spec is simple once you know it: 1200×630 pixels (a 1.91:1 ratio), under 5 MB, JPG or PNG, served from an absolute https:// URL. That one size renders cleanly on Facebook, LinkedIn, X's summary_large_image card and Slack. Keep logos and text away from the edges — X and Slack crop tighter than Facebook — and add og:image:width and og:image:height tags so Facebook can render the card correctly on the very first share instead of showing a blank box until its scraper finishes processing the image asynchronously.
The gotchas that actually break cards in production are rarely about the tag values — they're about delivery. Social scrapers do not execute JavaScript, so Open Graph tags injected client-side by a React app or a tag manager are invisible to every platform; the tags must be present in the server-rendered HTML. A WAF or robots rule that blocks facebookexternalhit, Twitterbot or LinkedInBot returns them an error page instead of your tags. A redirect chain or non-200 status often yields no card at all — scrapers give up where browsers persist. And og:url should always match your canonical URL, or engagement counts fragment across http/https, www and tracking-parameter variants of the same page.
In 2026 the Open Graph layer is effectively your page's public API for every surface that unfurls links: Slack, Discord, WhatsApp, Teams and iMessage all read og tags, and AI assistants increasingly pull og:title and og:description when they cite or preview your pages. That makes a systematic check worth more than a one-off fix. The pattern that holds up: set the six core tags (og:title, og:description, og:image, og:url, og:type, twitter:card) on every indexable template, keep share images on stable URLs so caches stay warm, and re-verify with an og tag checker after any template, CMS or CDN change — those are exactly the deploys that silently strip meta tags.
More free SEO tools
SERP Snippet Preview
Preview how your title and meta description appear in Google results, with live pixel-width and character limits.
Meta Tag Generator
Build copy-paste title, description, canonical, Open Graph and Twitter Card meta tags with a live preview.
Schema Markup Generator
Create valid JSON-LD structured data for Organization, LocalBusiness, Article, FAQ, Product and Breadcrumb.
See all free SEO tools or compare Black & Gold SEO vs other platforms.