Open Graph Checker — Test OG Tags & Social Previews for Any URL

Q: What is an Open Graph checker?

An Open Graph checker is a free tool that reads the meta tags on a web page and shows how that page will look when shared on Facebook, WhatsApp, LinkedIn, X or Slack. It also flags missing or incorrect tags.

Q: Why does my OG image not show up?

The four most common causes are a relative URL instead of an absolute one, an image smaller than 600 by 315 pixels, a robots.txt file blocking the image directory, or a platform cache that has not been refreshed.

Q: What is the ideal OG title and description length?

Aim for 40 to 60 characters on the title (90 maximum) and 55 to 160 characters on the description (200 maximum). Both are counted live in the checker.

Q: Why are my OG tags not detected?

Single-page applications built with React, Vue or Angular often inject OG tags with JavaScript after the initial page load. Social crawlers do not execute JavaScript, so they see nothing. Server-side rendering or static tags in the initial HTML solve this.

Q: Do Open Graph tags help with AI search?

Yes. AI tools like ChatGPT, Perplexity and Google AI Overviews read page metadata to summarise content. Clean Open Graph tags give them a clear title, description and image, which makes your content easier to cite correctly.

Q: Is the URL I check stored on your server?

No. The fetch runs through a public proxy (or a PHP endpoint on our own server) and the result is returned to your browser. We do not log the URL. Your local history is stored only in your own browser.

Paste a public URL. The tool fetches the page, extracts every Open Graph and Twitter Card tag it finds, and renders previews for six platforms side by side.

Try:

Fetching page and extracting meta tags…

If the site blocks bots or is behind a paywall, the fetch will fail. Try a different URL, or run the page through our OG Generator to build tags from scratch.

Property	Value
No tags loaded yet.

Check multiple URLs at once. One URL per line. Perfect for auditing a site, comparing your pages against competitors, or checking a batch of client work before launch.

URLs to check (one per line)

URL	OG	TW	Image	Status
No URLs checked yet.

Your last 30 checked URLs, stored on your own device. Click any entry to load it back into the Single Check tab. Nothing is uploaded to our servers.

No checks yet. Run a check on the Single Check tab and it will appear here.

—

🔍 What an Open Graph checker actually does

An Open Graph checker fetches a URL, reads the meta tags inside the <head>, and tells you what social platforms will see when someone shares that link. It is the diagnostic companion to a generator: one tool builds the tags, this one verifies them on a live page.

The value is in the gap between what you intended to publish and what the platform actually receives. Almost every website has at least one OG tag that is wrong, missing, or pointing at a relative path that does not resolve. The problems are usually invisible until a link gets shared and the preview comes out looking broken — and by then the bad cache has already spread.

This tool closes that gap. It fetches the page exactly the way a social crawler would, extracts every tag it finds, validates the essentials against what each platform expects, and renders six live previews so you can see the result before you share.

📋 How to use the checker

Paste a public URL. Any URL that is accessible without login. Pages behind authentication or paywalls cannot be crawled by social platforms either, so there is no point checking them here.
Click Check URL. The tool fetches the page and extracts every og: and twitter: tag from the HTML.
Read the score badge. Green means all essential tags are present. Amber means at least one recommended tag is missing. Red means something critical is broken — usually og:image or og:title.
Switch between platform tabs. Each platform renders the same tags differently. Facebook, LinkedIn and WhatsApp share a card style; X switches between large and small layouts; Discord and Slack use their own embed formats.
Fix what is flagged. The validation list under the preview tells you exactly what is wrong and what the recommended range is. Most issues take five minutes to fix.
Re-check after fixing. Social platforms cache the OG data for days or weeks. Use Facebook's Sharing Debugger or LinkedIn's Post Inspector to force a fresh scrape, then run the URL through this checker again.

🖼️ What each platform actually expects

All six major platforms read the same underlying tags, but they crop, truncate and lay out the card differently. Here is what each one does with your metadata.

Platform	Preferred image	Title truncation	Notes
Facebook	1200 × 630 (1.91:1)	~60 chars, 2 lines	Ignores Twitter Card tags entirely. Falls back to scraping if `og:image` is missing.
X (Twitter)	1200 × 628 (large card)	~70 chars	Uses `twitter:*` tags first, falls back to OG if they are missing. `twitter:card` decides layout.
LinkedIn	1200 × 627	~70 chars	Often overrides the description with the first paragraph of the page. Reads OG tags only.
Discord	Any (thumbnail 80×80)	Full title, no truncation	Uses the `og:site_name` as the coloured left border accent. Reads OG tags only.
Slack	Any (thumbnail up to 360 wide)	~70 chars	Reads OG tags only. Also reads `twitter:image` as a fallback if `og:image` is absent.
WhatsApp	1200 × 630	~65 chars	Reads OG tags only. Very strict about image dimensions — small images often fail silently.

🚩 The six mistakes that break OG previews

These are the issues the validator flags most often. Every one of them has a concrete, quick fix.

Missing og:image

Social platforms show a plain grey box with no image. Always set og:image — if you only set one tag correctly, make it this one.

Image is too small

Anything smaller than 600 × 315 is often ignored entirely. Aim for 1200 × 630 for full-width cards on every platform.

Relative URL for og:image

Paths like /images/og.jpg do not work. Every crawler fetches the image over the public internet, so it must be an absolute URL with https://.

Duplicate tag sets

When an SEO plugin and a theme both output OG tags, platforms pick one at random. The result is unpredictable. Only one set of tags should exist per page.

Tags added by JavaScript

React, Vue and Angular apps often inject OG tags client-side. Social crawlers do not run JavaScript, so they see nothing. Render the tags on the server or use static HTML.

Stale platform cache

You fixed the tags but the preview still looks wrong. Facebook, LinkedIn and X cache OG data for days. Use the Sharing Debugger or Post Inspector to force a fresh scrape.

🤖 Why Open Graph matters for AI search in 2026

This is the part most OG guides have not caught up with yet.

People do not only find websites through Google anymore. They ask AI assistants — ChatGPT, Perplexity, Google AI Overviews, Microsoft Copilot. Those assistants read pages to answer questions, and they lean heavily on structured metadata when deciding what a page is about and whether it is worth citing.

Clean Open Graph tags give an AI assistant three things it needs: a precise title, a concise description, and a representative image. When those are present and accurate, the assistant summarises your content correctly. When they are missing or vague, the assistant either guesses — often wrongly — or moves on to a page that has done the work.

It is not a direct ranking factor in Google's algorithm the way a canonical tag or a schema markup is. But it feeds the same discovery pipeline that AI Overviews and every conversational search tool use. Treating your OG tags as "social stuff" in 2026 is like treating your <title> tag as "browser stuff" in 2010. It misses the point.

💡 Practical takeaway: if your title is longer than 60 characters or your description reads like marketing copy rather than a summary, AI tools will misrepresent your page. Run the URL through this checker and rewrite anything the validator flags.

🔒 Your privacy and how we handle data

We do not log the URLs you check. The fetch is performed by a public CORS proxy or a PHP endpoint on our server, and the result is returned directly to your browser. We do not store, aggregate, or analyse which URLs are checked.

History is local only. Your last 30 checked URLs are stored in your browser's localStorage so you can revisit them. They are visible only to you and disappear if you clear your browser data. The "Clear all history" button also removes them.

Cookies and advertising. Advertising and analytics cookies are switched off by default. They only turn on if you press Accept all, or select them individually under Manage preferences. You can change your choice at any time from the Cookie Policy page. Full details are in our Privacy Policy.

About the author

Khalil Rahman — Front-end developer and tool builder

Khalil has spent the last eight years building browser-based tools for SEOs, marketers and developers. He built this checker after one too many client launches where the OG tags looked fine in the source code but rendered as grey boxes on every platform — because of a relative image path, a stale cache, or a plugin conflict. The multi-platform preview exists specifically so that the failure mode is visible before launch, not after. He maintains the SkillsInsider SEO and developer toolset.

More about SkillsInsider · Editorial policy · Report an issue

❓ Frequently asked questions

What is an Open Graph checker?

An Open Graph checker fetches a URL and reads the meta tags in the page's <head>. It then shows how the page will look when shared on Facebook, WhatsApp, LinkedIn, X or Slack — and flags any tags that are missing, wrong, or set to values that will be truncated. It is the diagnostic counterpart to a generator: the generator builds the tags, the checker verifies them on a live page.

Why does my OG image not show up?

Four causes cover almost every case. First, the og:image URL is relative rather than absolute — it must include https://. Second, the image is smaller than 600 × 315 pixels and the platform silently ignores it. Third, robots.txt is blocking the image directory. Fourth, the platform has cached an old version — use the Sharing Debugger or Post Inspector to force a fresh scrape.

What is the ideal OG title and description length?

Aim for 40 to 60 characters on the title. The absolute maximum before truncation on most platforms is around 90 characters. For the description, aim for 55 to 160 characters. Anything past 200 will be cut off with an ellipsis on every platform. Both are counted live by this checker, with a warning when you go over.

Why are my OG tags not detected at all?

If the checker returns zero tags, the page is almost certainly rendering them client-side with JavaScript. Social crawlers do not execute JavaScript, so they see the raw HTML before any scripts run — and if the tags are not there yet, they never appear. This is common with React, Vue and Angular applications. Fix: render the tags server-side, or add static tags to the initial HTML response.

Do Open Graph tags help with AI search?

Yes, indirectly. AI tools like ChatGPT, Perplexity and Google AI Overviews read page metadata to summarise content. Clean OG tags give them a clear title, description and image, which makes your content easier to cite correctly. It is not a direct ranking factor in Google's algorithm, but it feeds the same discovery pipeline that conversational search uses.

What is the difference between Open Graph and Twitter Cards?

Open Graph is the universal standard created at Facebook in 2010, used by Facebook, LinkedIn, Slack, Discord, WhatsApp and most other platforms. Twitter Cards are X's own metadata format with a few properties that have no Open Graph equivalent — most importantly twitter:card, which controls the layout. X falls back to OG tags when its own tags are missing, but adding both gives you more control over the final result.

How do I force a platform to re-scrape my tags?

Every platform caches OG data for days or weeks. Use the official debuggers to force a fresh crawl: Facebook's Sharing Debugger, LinkedIn's Post Inspector, or X's Card Validator. For platforms without a public debugger — Slack, Discord, WhatsApp — change the image filename and share again; a new filename is treated as a new resource and forces a re-fetch.

Is the URL I check stored on your server?

No. The fetch runs through a public CORS proxy or a PHP endpoint, and the result is returned to your browser. We do not log or store URLs. Your local history of recent checks is stored only in your own browser's localStorage and can be cleared at any time from the History tab.