Best Open Graph Checker Tools 2027: Test Social Previews

The best Open Graph checker tools for 2027 and what a 298-page check found: every tag present, yet one share image on every page. Free script inside.

· BugViso Team

10 min read

The best Open Graph checkers for 2027 are Facebook's Sharing Debugger and LinkedIn's Post Inspector for how those two networks will show your link, a site-wide crawler such as BugViso for missing tags across every page, and a small script for checking that the share image actually loads. Each platform caches previews, so the platform's own tool is the only one that can also refresh them.

Passing a tag check and having good previews are not the same thing. We checked all 298 pages of bugviso.com: every page had og:title, og:description, og:image, og:url, og:type and a Twitter card, and every og:url matched the canonical. But all 298 pages pointed at the same share image, so every post looks identical when shared. No validator flags that.

By the end you will know which checker to use for each platform, the tags each one needs, and how to test the previews on any list of pages for free.

Data used: every URL in bugviso.com's sitemap (298 pages), fetched on 2026-11-16. We extracted the Open Graph and Twitter meta tags, compared og:url with the canonical link and og:title with the <title>, and downloaded the share image to check its type, size and dimensions. Platform requirements come from each network's own help pages, fetched the same day. We make BugViso, one of the tools listed.

What a 298-Page Open Graph Check Found

The tags were complete and consistent; the images were not varied at all. Here are the results.

Check (298 pages)Result
og:title, og:description, og:image, og:url, og:type present298 of 298
twitter:card present298 of 298, all summary_large_image
og:image is an absolute URL298 of 298
og:url matches the canonical URL298 of 298
og:title differs from the <title>5 of 298
og:title lengthmedian 55 characters, longest 60
og:description lengthmedian 156 characters
Distinct share images1 (a 1200 × 630 PNG, 30 KB)

The single image is the finding that matters. It meets LinkedIn's size rules and loads fast, so every checker passes it. But a reader scrolling a feed sees the same picture for a post about INP, a post about robots.txt and the pricing page. A share image is the largest part of a link preview; when it never changes, it stops telling anyone what the link is about.

That is the gap in Open Graph testing: tools check that tags exist and are valid, not whether they help the link get clicked.

What Each Platform Needs

Every major platform reads the Open Graph protocol tags, but each adds its own rules for images and caching. These are the requirements that most often decide whether a preview looks right.

PlatformTags it relies onImage rulesHow to refresh a cached preview
LinkedInog:title, og:image, og:description, og:urlAt least 1200 × 627 px, max 5 MB, 1.91:1 ratioPost Inspector
Facebookog:title, og:description, og:image, og:url, og:typeLarge landscape images look bestSharing Debugger
Xtwitter:card sets the card type, plus title, description and imagesummary_large_image shows a wide imageRe-share after the cache expires
Slack, Discord, iMessageOpen Graph tagsVariesVaries; most re-fetch after a while

LinkedIn's rules come from its own help page on making your website shareable on LinkedIn, which lists the four og: tags that must exist and the image limits above.

The 5 Best Open Graph Checkers

ToolBest forChecksPrice
Facebook Sharing DebuggerFacebook previews and clearing Facebook's cacheWhat Facebook scraped, with warningsFree
LinkedIn Post InspectorLinkedIn previews and clearing LinkedIn's cacheWhat LinkedIn scrapedFree
BugViso site auditMissing Open Graph tags on every pageog:title, og:description, og:image on each crawled pageFirst report free
The script belowA quick check of any URL list, including the imageAll OG and Twitter tags, image status, type and sizeFree
View sourceSeeing what a crawler receivesAnythingFree

Facebook Sharing Debugger: Facebook's view and cache

The Sharing Debugger shows what Facebook's crawler scraped from a URL, the preview it will build, and warnings about missing or wrong tags. Its "Scrape Again" button is the reliable way to replace an old cached preview after you change a title or image.

LinkedIn Post Inspector: LinkedIn's view and cache

LinkedIn's Post Inspector shows how a URL will look when shared on LinkedIn and refreshes LinkedIn's cached copy. For B2B sites it is usually the preview that matters most, and LinkedIn's image rules are stricter than most.

BugViso: missing tags across a whole site

BugViso checks every crawled page for the core Open Graph tags (og:title, og:description, og:image) alongside the title, meta description and heading checks. It catches the template that forgot Open Graph tags on one section of the site, which single-URL debuggers only find if you happen to test that page. Where others go further: it doesn't render the platform preview or validate Twitter card markup; use the platform tools for that.

The free script: tags plus a working image

The script in this post prints every Open Graph and Twitter tag for each URL, warns about relative image URLs and long titles, and downloads the share image to confirm it loads. A broken or blocked image is the most common reason a preview shows a blank box.

View source: the HTML crawlers receive

Platform crawlers generally don't run JavaScript, so tags added in the browser after load may never be seen. Check the raw HTML (view source, not the DevTools Elements panel) when a debugger and your CMS disagree.

How to Fix the Common Open Graph Problems

Most broken previews come from five problems, and each has a one-line fix.

  • Relative image URL. Use an absolute https:// URL in og:image; many platforms won't resolve a relative path.
  • Image too small or blocked. Serve at least 1200 × 627 for LinkedIn, keep it under 5 MB, and make sure robots.txt and your firewall let platform crawlers fetch it.
  • Tags added by JavaScript. Render Open Graph tags in the server HTML, not in client-side code.
  • Old preview stuck in a cache. Use the Sharing Debugger or Post Inspector to force a fresh scrape.
  • The same image on every page. Generate a per-page image, even a simple one with the page title on a branded background, so each link looks different in a feed.
html
<!-- ✅ A complete set for an article -->
<meta property="og:type" content="article">
<meta property="og:title" content="What Is INP? The INP Metric Explained and How to Fix It">
<meta property="og:description" content="INP times a click, tap or keypress until the next paint.">
<meta property="og:url" content="https://example.com/blog/what-is-inp">
<meta property="og:image" content="https://example.com/og/what-is-inp.png">
<meta name="twitter:card" content="summary_large_image">

Titles and descriptions follow the same rules as search snippets, which our guide to writing title tags and meta description best practices cover.

Run It Yourself: Check Open Graph Tags and the Share Image

This script prints the Open Graph and Twitter tags for each URL and confirms the share image downloads, with its type and size. It uses only Python's standard library and identifies itself like Facebook's crawler, because some sites only serve tags to known crawlers.

python
#!/usr/bin/env python3
"""Show a page's Open Graph and Twitter card tags and check the share image actually loads.

Usage: python3 og_check.py <url> [more urls ...]
"""
import html
import re
import sys
import urllib.request
from urllib.parse import urljoin

NEED = ["og:title", "og:description", "og:image", "og:url", "og:type", "twitter:card"]
UA = {"User-Agent": "facebookexternalhit/1.1 (og-check)"}  # some sites only serve tags to crawlers


def tags(page):
    found = {}
    for tag in re.findall(r"<meta[^>]+>", page, re.I):
        key = re.search(r'(?:property|name)=["\']([^"\']+)["\']', tag, re.I)
        val = re.search(r'content=["\']([^"\']*)["\']', tag, re.I)
        if key and val and key.group(1).lower().startswith(("og:", "twitter:")):
            found.setdefault(key.group(1).lower(), html.unescape(val.group(1)))
    return found


for url in sys.argv[1:]:
    page = urllib.request.urlopen(urllib.request.Request(url, headers=UA), timeout=20).read().decode("utf-8", "replace")
    t = tags(page)
    print(url)
    for k in NEED:
        print(f"  {k:16} {t.get(k, 'MISSING')[:90]}")
    img = t.get("og:image")
    if img:
        if not img.startswith("http"):
            print("  ! og:image is relative; many platforms need an absolute URL")
        try:
            r = urllib.request.urlopen(urllib.request.Request(urljoin(url, img), headers=UA), timeout=20)
            size = len(r.read())
            print(f"  image: HTTP {r.status}, {r.headers.get('Content-Type')}, {size / 1024:.0f} KB")
        except Exception as e:
            print(f"  ! og:image does not load: {e}")
    if len(t.get("og:title", "")) > 60:
        print("  ! og:title over 60 characters may be cut off")

A real run on one of our posts, unedited:

text
https://bugviso.com/blog/what-is-inp-and-how-to-fix-it
  og:title         What Is INP? The INP Metric Explained and How to Fix It
  og:description   What is INP? The INP metric times a click, tap or keypress until the next paint. Learn the
  og:image         https://bugviso.com/og-image.png
  og:url           https://bugviso.com/blog/what-is-inp-and-how-to-fix-it
  og:type          article
  twitter:card     summary_large_image
  image: HTTP 200, image/png, 30 KB

Everything passes, and the image is the same one every other page uses, which is exactly the problem the script can't see on its own. Run it over your sitemap and count the distinct og:image values to spot it.

How BugViso Checks Social Tags Across a Site

BugViso's on-page checks look at each crawled page's title, meta description, Open Graph tags and headings together, so a missing og:image on one template shows up as a pattern across many pages. The crawl runs in a real browser and follows links from the rendered page, so whole sections that a sitemap misses are included.

Findings land in the ranked fix list, and the AI-written fixes include rewritten titles and descriptions you can reuse for og:title and og:description. The technical SEO feature page lists the on-page checks.

Frequently Asked Questions

How do I check Open Graph tags?

Paste the URL into Facebook's Sharing Debugger or LinkedIn's Post Inspector to see the preview each network will build. For many pages, use a crawler such as BugViso, or the script in this post, which prints every Open Graph tag and checks that the share image loads.

Platforms cache previews. After you change og:image or og:title, use Facebook's Sharing Debugger ("Scrape Again") or LinkedIn's Post Inspector to force a fresh fetch. Changing the image file name also helps, because some platforms cache images by URL.

What size should an Open Graph image be?

LinkedIn requires at least 1200 × 627 pixels, a maximum of 5 MB, and recommends a 1.91:1 ratio. A 1200 × 630 image meets that and works well on Facebook and in X's large image card. Keep the important text away from the edges, which some apps crop.

Do Open Graph tags help SEO?

They don't directly affect Google rankings. They control how your links look when shared on social networks and in chat apps, which affects how many people click. Good titles and descriptions usually serve both search snippets and share previews.

Do I need Twitter card tags if I have Open Graph tags?

Add at least twitter:card to choose the card type, such as summary_large_image for a wide image. X can read the title, description and image from your Open Graph tags, so you don't need to repeat everything, but setting the card type makes the preview predictable.

The Open Graph Check Validators Skip

Every validator will tell you whether the tags exist; none will tell you that every page shares the same picture. Count your distinct og:image values, give your most-shared pages their own images, and run a BugViso audit to catch the templates where the tags are missing entirely.

Written by

· BugViso Team

Kazi writes BugViso’s guides on website audits, Core Web Vitals, technical SEO, accessibility and AI search. The data in them comes from audits BugViso runs in a real Chromium browser, including our 219-site study of website health.

Found this useful? Share it.

Summarise with AI

Open this guide in your assistant.

Follow BugViso

New guides and audit data as we publish them.

AI visibility tracker

Is your brand in AI answers?

See how often AI assistants mention you, cite your site and rank you against your competitors.

  • ChatGPT
  • Gemini
  • Perplexity
  • Claude
  • AI Overviews
See how it works

See where your site stands

Run a free BugViso audit for SEO, speed, accessibility and AI search readiness — with fixes you can ship today.