Open Graph checker

Open Graph is how LinkedIn, Slack, Discord and WhatsApp build the preview card. Search tags do not fill this in. If og:image is missing, you get a text row.

Uses the public POST /api/audit. After the free daily check, continue in the workspace.

What we measure

The six properties this product already extracts: title, description, image, url, type, site_name. Title, description and image are the ones that decide whether the card looks finished.

How to set them

Absolute http(s) URLs only — relative og:image is dropped by most platforms. 1200×630 is the size that does not get cropped into a square.

og:url should be the canonical address, not the campaign link the person pasted.

How the preview card is built

When a link is pasted in WhatsApp, Slack, LinkedIn or Discord, the platform fetches the page once, reads the og:* tags in <head> and caches the result. og:title becomes the card headline, og:description the line under it, og:image the picture, og:url the address the card links to. None of these platforms fall back to the search tags; a page with a perfect title and meta description but no Open Graph gets a plain text row, or a card built from whatever image the scraper found first.

The checker reads the six properties the audit already extracts — title, description, image, url, type, site_name — and flags the three that decide whether the card looks finished when they are missing. It reads the raw HTML, so tags injected by JavaScript are not seen, and neither are they by the scrapers.

Common mistakes

A relative og:image ("/og.png"), dropped by most platforms. An image smaller than 200 pixels wide, which many scrapers ignore. A single site-wide og:image for every page, so every shared article shows the logo. og:url pointing at the campaign link that was shared instead of the canonical page, which splits the share counts. Changing the image and forgetting that the platforms cached the old card.

What the audit of https://example.com/ returned on 5 September 2026

As found

<!-- no og:title, og:description or og:image → three warnings; a share shows a bare link -->

Fixed

<meta property="og:title" content="Example Domain" />
<meta property="og:description" content="Reserved names for documentation and tests, usable without permission." />
<meta property="og:image" content="https://example.com/og.png" />
<meta property="og:url" content="https://example.com/" />
<meta property="og:type" content="website" />
<!-- absolute image URL, 1200×630, the canonical address -->

example.com ships no Open Graph tags, so a shared link renders as text. The five lines above are the whole fix; the image is the only part that needs an asset.

Questions

Is Open Graph a ranking factor?

No. It decides how the page looks when someone shares it, which decides whether the share gets clicked. Search engines read the search tags; messaging apps read these.

Which image size should I use?

1200×630 pixels is the size that is shown without cropping on the large-card layouts and scaled down on the small ones. Keep the subject in the centre; some platforms crop to a square.

I changed the tags and the preview did not change. Why?

The platform cached the old card. Each one has a debugger or a re-scrape button (Facebook Sharing Debugger, LinkedIn Post Inspector); until you use it, the cached card stays.

See the full audit in your workspace

Other tools