Missing Open Graph Tags

No Comments
Missing open graph tags
TL;DR: Open Graph tags tell Facebook, LinkedIn, Slack and every other platform exactly how to render your link when someone shares it. Miss them and the platform guesses, usually badly, with the wrong title, no image, and a truncated blurb that kills clicks.
Element Code
SO-001
Severity
Medium
Where It Lives
<head> meta
Direct Ranking Factor
No
Fix Effort
Low

What "Missing Open Graph Tags" actually means

The Open Graph protocol is a small set of <meta> tags, originally published by Facebook in 2010, that let any page declare how it should look when it gets shared. The four that matter most are og:title, og:description, og:image, and og:url. When a platform's crawler hits your URL, it reads those tags and builds the share card: the headline, the summary line, and the big preview image people actually click.

When they are missing, the platform falls back to whatever it can scrape. Usually that means your <title> tag (often not the message you want on social), the meta description if one exists, and a random image the parser grabbed off the page, or no image at all. A link with no image gets a fraction of the engagement of one with a proper 1200x630 preview. I have watched a client's blog posts double their referral clicks from LinkedIn after we did nothing but add correct OG tags. No new content, no design change, just the tags.

Why it matters even though it is not a ranking factor

Google does not use Open Graph as a ranking signal, so let us be honest about that up front. This is not going to move you from position 8 to position 3. What it moves is social referral traffic and click-through on shared links, which in turn feeds engagement, brand impressions, and the kind of secondary signals that do matter over time. If your content marketing depends on people sharing your URLs, missing OG tags is a self-inflicted wound. You spent the effort producing the piece, then handed the platform a blank card to represent it.

Without OG tags no image parsed example.com Page Title | Site Name (truncated fallback text...) With OG tags og:image 1200x630 example.com Your Curated Share Headline A clean, intentional summary line.

The tags you actually need

TagPurposeNotes
og:titleHeadline on the share cardKeep under ~60 chars
og:descriptionSummary line under title~110 chars renders fully
og:imagePreview image1200x630, under 8MB, absolute URL
og:urlCanonical URL of the objectUse the clean canonical, no tracking params
og:typeObject typearticle for posts, website for pages
og:site_nameYour brand nameOptional but tidy

One thing people forget: Twitter and X read Twitter Card tags first, but they fall back to Open Graph. So if you add twitter:card plus the four core OG tags, you have covered nearly every major platform with one block of markup. There is rarely a reason to maintain two entirely separate sets.

How to detect the problem

  • Facebook Sharing Debugger and LinkedIn Post Inspector: paste a URL, see exactly what each platform scrapes, and force a re-scrape after you fix things. This is the fastest single check.
  • Screaming Frog SEO Spider: crawl the site, open the Open Graph tab, and sort for pages with empty og:title or og:image. This is how you catch it at scale across thousands of URLs instead of one at a time.
  • View source or DevTools: search the <head> for og:. Ten seconds, no tools, works on any single page.
  • Sitebulb flags missing social tags in its report set if you want it folded into a broader audit.

How to fix it, step by step

  1. Decide where OG values come from. On WordPress, an SEO plugin like Yoast or Rank Math generates them per page and lets you override title, description, and image individually. Use that rather than hand-coding.
  2. Set a sensible site-wide default image so pages without a custom one still get a branded card instead of nothing.
  3. Make sure og:image is an absolute URL (starts with https). Relative paths silently fail on most scrapers.
  4. Confirm the image is at least 1200x630 and publicly reachable. If it sits behind a login or a hotlink block, the platform sees nothing.
  5. Re-scrape in the Facebook and LinkedIn debuggers to bust their cache. Platforms cache aggressively, so an old blank card can linger for days until you force a refresh.

Do vs Don't

DO
  • Ship all four core tags on every indexable page
  • Use a dedicated 1200x630 image built for the card
  • Point og:url at the clean canonical
  • Re-scrape in platform debuggers after changes
  • Set a branded fallback image site-wide
DON'T
  • Rely on the platform to guess an image
  • Use a relative path for og:image
  • Stuff tracking parameters into og:url
  • Point at an image behind a login or hotlink block
  • Leave stale cached cards uncorrected

What "good" looks like

Every shareable page carries og:title, og:description, og:image, and og:url, the image renders crisp in the Facebook and LinkedIn debuggers, and there is a branded default so nothing ever shares as a blank rectangle. Pair that with the matching Twitter Card tags and you are done. It is a one-time setup that keeps paying every time someone hits share.

FAQ

Do Open Graph tags help my Google rankings?
No, Google does not use Open Graph as a ranking signal. They affect how links look when shared, which drives social referral clicks and engagement, not your position in organic search.
What image size should og:image be?
1200x630 pixels is the safe standard that renders large on Facebook, LinkedIn, and Slack. Keep the file under 8MB and serve it from an absolute https URL.
Do I still need Twitter Card tags if I have OG tags?
X falls back to Open Graph, so you can survive on OG alone. Adding twitter:card plus the OG block gives you full control on X with almost no extra work.
I fixed the tags but the old preview still shows. Why?
Platforms cache share cards. Run the URL through the Facebook Sharing Debugger or LinkedIn Post Inspector and force a re-scrape to refresh the cached version.
Want every social and technical tag audited across your whole site?

We crawl the full site, flag missing Open Graph and card markup at scale, and hand you a prioritized fix list.

Get an Advanced SEO Audit

Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.

About SEO ProCheck

Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.

Work With Me

Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.

Subscribe to our newsletter!

More from our blog