Open Graph checker

Use this Open Graph checker to inspect source tags, test social images and build an editable social media preview. Platforms may render and cache cards differently.

What the Open Graph checker tests

Required source tags

Title, type, image and URL in server HTML; HTML title is a simulation fallback, not an OG protocol pass.

Order and conflicts

Every captured occurrence, including structured image properties, with escaped evidence.

Source vs rendered

Added, removed and changed values after a bounded JavaScript render.

Image availability

Status, redirects, MIME, byte count, decoded dimensions and aspect ratio.

Platform simulations

Facebook, LinkedIn, X, Slack, Discord, WhatsApp and Telegram with disclosed fallbacks.

Editable markup

Try copy changes and generate escaped generic HTML without touching your website.

Sample result

Illustrative evidence from a fictional product page, not a live test.

FAIL · Missing og:image

Evidence: no og:image or og:image:url in the source head. Fix: publish an absolute, public image URL.

REVIEW · Rendered-only title

Evidence: og:title appears only after JavaScript. Fix: emit it in the original HTML so source-only crawlers can see it.

PASS · Image bytes

Evidence: HTTP 200, image/jpeg, 1200 × 630, 145 KB. This proves the observed fetch; it does not guarantee a platform card.

Reference: Open Graph protocol.

Open Graph tags and fallback order

The source report keeps tag order and duplicate values. Multiple images can be intentional; conflicting titles need review. Our generic simulations use og:title before HTML title and og:description before meta description. X first uses Twitter title, description and image. Canonical is comparison evidence and never silently replaces og:url.

Why a social image may fail to load

A redirect may lead to a login page, the response may contain HTML despite an image extension, or the origin may block a crawler. We inspect up to three candidates with six redirects each. We reject non-public addresses, images above 5 MB and raster images above 16 million pixels or 12,000 pixels on a side. SVG and unsupported formats remain unverified. GIF previews show the first frame; animation and transparency are not separately certified.

Platform previews and cache limitations

Simulated preview — platforms may render or cache cards differently. Card layout, crop and truncation are approximations. Use the official Facebook debugger or LinkedIn inspector for their own observations. We cannot purge platform caches or rewrite cards on existing posts.

How it works and methodology

Enter one public page URL, without credentials or secrets.
Inspect source metadata, compare a bounded rendered document and fetch image candidates.
Fix the source template, recheck, then set up project monitoring if you need repeat checks.

Catalog and simulation profiles: 2026-09-19.1. Last substantive review: 19 September 2026. Open Graph supplies the required properties and source-order guidance. Presence and MIME checks are deterministic or observed; rendering differences and platform layouts are advisory. UNKNOWN means a check could not complete. A browser gets 80 requests, 10 MB total and a short post-load observation; blocked resources can make it partial.

Reports and derived images are generated in memory for this response and are not publicly archived. Validation errors can keep entered values in your browser session. Monitoring continuation stores the page context under the account flow. Do not submit private or token-bearing URLs.

Fix examples

Missing image → publish a public image

<meta property="og:image" content="https://example.com/share.jpg">
<meta property="og:image:alt" content="A red travel backpack">

JavaScript-only title → include source metadata

<meta property="og:title" content="Travel backpack">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/backpack">

Frequently asked questions

Is the tool free?

Yes. One-off public checks need no account; repeated requests are rate limited. Project monitoring requires an account and follows plan limits.

What data is stored?

The public report is not archived. Validation input may remain in your session. Continuing to a project stores the URL context; see the privacy boundary above.

Does a pass guarantee the exact preview?

No. It records our observed tags and image response. Platforms have their own caches, crawlers and layout rules.

Can you refresh a platform cache?

No. Use the platform's official inspector where available; existing posts may retain earlier cards.

Can social crawlers see rendered-only tags?

Support varies. Publish the intended sharing tags in source HTML to avoid depending on JavaScript execution.

Which image dimensions should I use?

A 1200 × 630 landscape image is a common design starting point, not a protocol requirement or universal platform rule. Keep essential content away from crop edges and verify the actual platform.

What cannot be checked, and when should I recheck?

Private URLs, platform cache state and exact card rendering cannot be certified. Recheck after template, image, redirect or CDN changes.