Website Checker - What Are Open Graph Tags? A Practical Guide for Site Owners

What Are Open Graph Tags? A Practical Guide for Site Owners

Jul 20, 2026 · SEO Glossary

Paste one of your URLs into Slack and watch what renders. If you get a title, a description, and a big image card, your Open Graph tags are doing their job. If you get a naked grey link, they're missing or broken — and every share of that page is losing clicks it should've earned.

So what is Open Graph tags markup, exactly? It's a set of <meta> elements in your page's <head> that tell social platforms and chat apps how to build a link preview. Facebook introduced the protocol in 2010, and it's since become the de facto standard: LinkedIn, Slack, Discord, WhatsApp, Telegram, and (with fallbacks) X all read it.

What Are Open Graph Tags Actually Doing?

When someone shares your URL, the platform's scraper fetches the page server-side, parses the head, and caches what it finds. It doesn't execute your JavaScript in most cases, and it doesn't guess politely when tags are absent — it grabs whatever title tag and first image it can find, which is how you end up with a preview showing your hamburger-menu icon at 48×48 pixels.

The scraper visit shows up in your server logs with distinct user agents: facebookexternalhit/1.1, LinkedInBot, Slackbot-LinkExpanding, TelegramBot. If you see those hitting a page and the preview still looks wrong, the platform is almost certainly serving a stale cached version — more on that below.

The Five Tags Worth Getting Right

The protocol defines dozens of properties. In practice, five carry nearly all the weight:

  • og:title — the headline of the preview card. Keep it under ~60 characters; platforms truncate hard.
  • og:description — the supporting line. Around 110 characters displays cleanly on most surfaces.
  • og:image — the preview image. Use an absolute URL, 1200×630 pixels (a 1.91:1 ratio), under 5 MB. Smaller than 200×200 and Facebook won't render it at all.
  • og:url — the canonical URL for the object. This should match your canonical tag, because platforms consolidate share counts against it.
  • og:type — usually website for a homepage or article for content pages.

A minimal, correct block looks like this:

  • <meta property="og:title" content="Redirect Chains: Why Every Hop Costs You" />
  • <meta property="og:image" content="https://example.com/img/redirects-card.png" />
  • <meta property="og:url" content="https://example.com/blog/redirect-chains/" />

Do Open Graph Tags Affect Rankings?

Not directly. Googlebot reads them, and Google may use og:title or og:description as one of many candidate sources when it rewrites your snippet, but there's no ranking signal attached to the markup itself. The SEO value is second-order: pages with proper cards get shared more and clicked more, and that traffic, brand recall, and occasional earned link is real. Treat Open Graph as conversion optimization for the social click, not as a ranking lever.

Common Failure Modes I Keep Seeing in Audits

  • Relative image URLs. og:image="/img/card.png" fails on several platforms. Always absolute, always HTTPS.
  • One global card for every page. Template-level tags that never change mean every blog post shares with the homepage's title. Each URL needs its own values.
  • Images blocked by robots.txt. If your CDN path is disallowed, scrapers can't fetch the image and the card renders text-only.
  • JavaScript-injected tags. If your framework adds OG tags client-side, most scrapers never see them. They must be in the initial HTML response — verify with curl, not with your browser's element inspector.
  • og:url pointing at a redirect. Scrapers follow it, but engagement counts can split across variants.

How to Test and Force a Re-Scrape

Every major platform caches previews aggressively — Facebook for up to 30 days. Fixing the tags doesn't fix old shares until the cache refreshes. Use the platforms' own debuggers to force it: Facebook's Sharing Debugger and LinkedIn's Post Inspector both show you exactly what was scraped and offer a re-scrape button. For Slack, appending a throwaway query parameter to the URL gets you a fresh preview instantly.

A note on X/Twitter: it reads its own twitter:card tags first, but falls back to Open Graph for title, description, and image when they're absent. In practice that means one well-formed OG block covers every platform, and the only Twitter-specific tag most sites benefit from is <meta name="twitter:card" content="summary_large_image"> to request the full-width card instead of the small thumbnail. Adding the complete parallel set of twitter tags duplicates data for no gain.

For a quick raw check without any tool, request the page the way a scraper does:

curl -A "facebookexternalhit/1.1" -s https://example.com/page/ | grep "og:"

If the tags aren't in that output, no debugger will save you — the fix belongs in your server-rendered HTML.

Checking Open Graph Coverage at Scale

Spot-checking one page is easy; the problem is the 400 other pages nobody has shared yet. Missing and duplicate OG tags follow the same pattern as missing meta descriptions — they cluster in template types someone forgot about (author pages, category archives, old landing pages). A site-wide crawl surfaces every page missing og:title or og:image in one pass, alongside the duplicate-meta and broken-image issues that usually travel with them. Fix the template once and the whole cluster resolves.

One last habit worth building: whenever you change a page's title or hero image, update the OG tags in the same commit. They drift apart otherwise, and a preview card showing last year's pricing is worse than no card at all.

Frequently Asked Questions

What size should an og:image be?

Use 1200×630 pixels, which gives the 1.91:1 aspect ratio most platforms crop to. Keep the file under 5 MB and serve it over HTTPS from a URL that isn't blocked by robots.txt. Anything below 200×200 pixels gets ignored by Facebook entirely.

Why does my link preview show old content after I updated the tags?

Platforms cache scraped previews, sometimes for weeks. Run the URL through Facebook's Sharing Debugger or LinkedIn's Post Inspector and trigger a manual re-scrape. For Slack, adding any new query parameter to the URL forces a fresh fetch.

Do Open Graph tags help Google rankings?

Not as a ranking factor. Google can read them and occasionally uses them as snippet candidates, but the benefit is indirect: better previews earn more social clicks and shares, which drives traffic and occasionally links. Think of them as click-through optimization, not ranking optimization.

Try WebsiteChecker.Tech Free

Run a free technical SEO audit on any website. Get a client-ready report in minutes.

Start Free Scan