Why didn't fetching my URL work?

Most ordinary websites don't send permissive CORS headers, so a browser blocks a client-side fetch to them - this is expected, not a bug. Copy the page's HTML via "View Page Source" and paste it into the box below; it checks the same tags either way.

Which og:* tags are actually required?

The Open Graph protocol specification lists four as required for any page: og:title, og:type, og:image, and og:url. og:description and og:site_name are commonly added but technically optional - most consumers still show a usable preview without them, just a less complete one.

Why does this tool flag a relative og:image URL?

Open Graph consumers like Facebook, Slack, and LinkedIn fetch the image URL from their own servers, not the visitor's browser, so a relative path like /images/photo.jpg has no page to resolve itself against and typically fails to load - og:image needs to be a full absolute URL starting with http:// or https://.

Does this replace Facebook's Sharing Debugger?

No - Facebook's own debugger also shows you what its crawler actually fetched (useful for catching caching issues) and lets you force a re-scrape. This tool is faster for a quick tag-completeness check during development, but re-run Facebook's debugger before a launch if the preview looks wrong on the platform itself.

Open Graph Checker - Validate og:title, og:image & More

Overview

Introduction

Open Graph tags control how a page's link preview looks when shared on Facebook, LinkedIn, Slack, Discord, and dozens of other platforms that support the protocol - get them wrong and your carefully designed page shows up as a bare link with no image or a broken thumbnail.

This tool fetches a page (or reads pasted HTML) and checks its og:* tags against the protocol's required and recommended set, explaining what each missing tag actually breaks rather than just flagging it.

What Is Open Graph Checker?

An Open Graph tag auditor that extracts every og:* meta property from a page and checks it against the four properties the Open Graph protocol specification requires (og:title, og:type, og:image, og:url), plus the commonly-expected og:description.

It works two ways: fetching a URL directly when the target allows cross-origin requests, or reading HTML you paste in, which works regardless of CORS.

How Open Graph Checker Works

The HTML is parsed with the browser's DOMParser, every <meta property="og:..."> tag is collected, and each of the protocol's required properties is checked for presence.

og:image gets an extra check: whether its value starts with http:// or https://, since a relative path won't resolve for a third-party crawler fetching it from its own servers.

When To Use Open Graph Checker

Before sharing a new page's link for the first time, to catch a missing og:image before it shows up as a blank thumbnail on social platforms.

While debugging why a page's link preview looks wrong on Slack or Facebook, since a relative og:image URL is a common silent cause.

Often used alongside Open Graph Generator, Meta Tag Checker and Twitter Card Validator.

Features

Advantages

Checks against the Open Graph protocol's actual required-property list, not just a generic guess at what matters.
Specifically flags relative og:image URLs, a mistake that's invisible in a browser (where relative URLs resolve fine) but breaks for external crawlers.
Works on any page via the paste-source fallback, not just pages with permissive CORS.

Limitations

This tool checks tag presence and basic URL shape, not whether the image itself loads, meets platform size/aspect-ratio recommendations, or whether a platform has a stale cached version of the page.
A live fetch only works when the target sends permissive CORS headers, which most ordinary websites don't; use the paste fallback for anything else.

Examples

A complete Open Graph tag set

Input

<meta property="og:title" content="Buy Running Shoes Online">
<meta property="og:type" content="website">
<meta property="og:image" content="https://example.com/shoes.jpg">
<meta property="og:url" content="https://example.com/running-shoes">

Output

og:title: good
og:type: good
og:image: good
og:url: good
og:description: warning (missing, recommended)

All four required properties are present and og:image is absolute; og:description is optional but flagged as a recommendation.

A page with a relative image URL

Input

<meta property="og:title" content="Home">
<meta property="og:image" content="/img/hero.jpg">

Output

og:title: good
og:type: missing
og:image: warning (relative URL)
og:url: missing

og:image is present but relative, which will fail to load for most link-preview crawlers; og:type and og:url are both missing entirely.

Best Practices & Notes

Best Practices

Always use a full absolute URL for og:image, including the scheme (https://), since crawlers fetch it independently of the page.
Set og:type accurately (article for blog posts, product for product pages) since some platforms change how they render the preview based on it.

Developer Notes

og:image size matters for how platforms render a preview even though it isn't a required tag: most recommend at least 1200x630px for a large-image-style card. This tool doesn't fetch or measure the image itself, only checks the URL is present and absolute.

Open Graph Checker Use Cases

Verifying a new blog post or landing page has a complete Open Graph tag set before sharing it
Debugging a broken link-preview thumbnail by checking whether og:image is relative
Auditing a site template for pages missing og:type or og:url

Common Mistakes

Using a relative path for og:image because it looks fine when viewing the page directly in a browser, not realizing external crawlers can't resolve it.
Copying an og:title from the page's <title> tag without adjusting it, missing the chance to write share-specific copy that reads better as a link preview.

Tips

If a platform still shows a stale preview after fixing your tags, use that platform's own debugger/cache-buster tool (e.g. Facebook Sharing Debugger) to force a re-scrape.

Open Graph Checker