Open Graph tag checker

Check how your page will look when shared on social media and messengers

Free
No sign-up
Instant results

Check results

This check only covers Open Graph. For a full picture of your page, run a page audit.

For issues across your whole site — duplicate titles, orphan pages, broken internal links — run a site audit.

Want us to fix what we found? Our team can help.

What is Open Graph and why it matters

Open Graph (OG) is a markup protocol — a set of <meta property="og:*"> tags in <head> — that tells social platforms and messengers how to render your page when shared. Developed by Facebook (Meta) and adopted across LinkedIn, Slack, Discord, WhatsApp, Telegram, iMessage, and Twitter/X (with Twitter Card extensions). Without OG tags, platforms either skip the preview entirely or build one from whatever they can guess, usually with poor results. A correctly configured OG preview measurably increases the click-through rate of shared links.

What this tool checks

  • Core tags — og:title, og:description, og:image
  • og:image accessibility — the declared image URL must return a valid response (not 404)
  • og:image absolute URL — external platforms can't resolve relative paths
  • og:image format — SVG is poorly supported in previews; PNG/JPG is safer
  • og:image:width / og:image:height — declared dimensions speed up preview rendering
  • og:image size — if dimensions are declared, they should be ≥600×315px (1200×630 is ideal)
  • og:title / og:description length — platforms truncate at ~60 and ~160 characters
  • og:url — declares the preferred URL; should match canonical
  • og:type — content type (website, article, music.song, video.movie, etc.)
  • og:site_name — brand name shown on the card
  • og:locale — language/region declaration
  • Twitter Card — twitter:card tag for full control over Twitter/X previews
  • Duplicate tags — multiple tags with the same property are malformed markup

Why Open Graph matters

  • Higher CTR on social — image-rich cards outperform plain text links by a wide margin
  • Brand control — you decide what headline, description, and image appear when people share your URL
  • Platform coverage — one set of OG tags works across Facebook, LinkedIn, Slack, Discord, WhatsApp, iMessage, Telegram
  • Indirect SEO effect — better social distribution brings traffic, referral links, and brand queries
  • Fails silently — a broken OG configuration doesn't throw an error. The bad preview just underperforms in social feeds until someone notices

Good vs bad examples

Good — full set of tags with explicit dimensions and Twitter Card:

<meta property="og:title" content="Free SEO Audit Tool — 26 Checks in Seconds">
<meta property="og:description" content="Run a free audit and get a prioritized list of issues damaging your Google rankings — in seconds.">
<meta property="og:image" content="https://seorado.com/og-image.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:url" content="https://seorado.com/">
<meta property="og:type" content="website">
<meta property="og:site_name" content="Seorado">
<meta property="og:locale" content="en_US">
<meta name="twitter:card" content="summary_large_image">

Bad — relative og:image URL (won't load on external platforms):

<meta property="og:image" content="/images/og-card.jpg">

Bad — SVG as og:image (LinkedIn, Slack may skip it):

<meta property="og:image" content="https://example.com/card.svg">

Bad — missing dimensions (platforms delay or skip the preview while they fetch the image to measure):

<meta property="og:image" content="https://example.com/card.jpg">
<!-- no og:image:width / og:image:height -->

Bad — duplicate tags (malformed HTML; platforms use the first, the rest is dead code):

<meta property="og:title" content="Homepage">
<meta property="og:title" content="SEO Tool">

Common mistakes

  • No OG tags at all — platforms generate previews from random page content, often with a broken image and wrong text
  • Missing og:image — text-only cards have much lower CTR than image cards
  • Relative og:image URL — works in your browser, invisible to external crawlers
  • og:image 404 — shared links show a broken-image placeholder
  • No og:image:width / og:image:height — platforms delay preview rendering while they fetch the image to measure
  • Title too long — 60+ chars get truncated mid-sentence in feed previews
  • og:url doesn't match canonical — confuses platform-level URL consolidation (same page shared via different URL variants won't aggregate)
  • No Twitter Card — Twitter/X falls back to OG but produces a smaller, less rich card
  • Forgetting og:site_name — users see only the title on the card, missing the brand signal

Frequently asked questions

Minimum set: og:title, og:description, og:image, and og:url. Without them, most platforms can't build a proper preview card. It's also recommended to include og:type (usually "website" or "article").
Not necessarily, but it's recommended. Title and description are optimized for search results, while OG tags are for social media. On social platforms, you can use a more informal tone, calls to action, or emotional headlines that work better in feeds.
Recommended size is 1200×630 pixels (1.91:1 aspect ratio). Minimum for most platforms is 600×315. Below that, Facebook and LinkedIn may fall back to a square thumbnail instead of a full banner. Format: JPG or PNG (WebP works on most platforms, SVG is unreliable), file size under 5 MB.
Not strictly — Twitter/X falls back to OG tags when Twitter Card tags are missing. But you lose control of the card type. Adding one line — <meta name="twitter:card" content="summary_large_image"> — gives you a full-width image preview instead of a compact summary card. That's a meaningful CTR bump for no real effort. For custom titles/images on Twitter specifically, add twitter:title, twitter:description, twitter:image.
Use the platform's own debugger to see what it sees — don't rely on re-sharing the link in the platform's UI, since platforms aggressively cache previews. Facebook: Sharing Debugger. LinkedIn: Post Inspector. Twitter/X: the Card Validator was retired in 2023 — test by pasting the link into a tweet draft. Each tool lets you force a re-scrape if the preview is stuck on an old version.