Open Graph Checker

Preview and validate Open Graph meta tags by checking a live URL or pasted HTML. Inspect og:title, og:description, og:image, canonical links, Twitter fallbacks, duplicate tags and the share-preview issues that break social cards.

Free to useNo sign-up requiredUpdated Mar 2026

Open Graph CheckerTry it now — free ▼

Social card QA

Check the metadata that decides how a URL looks when someone shares it in Facebook, LinkedIn, Slack, Discord, iMessage, X, or other preview surfaces. You can inspect a live URL after deployment or paste HTML during staging to catch missing og:* tags before release.

Quick Examples

Source setup

Live URL mode checks what crawlers can fetch right now. Pasted HTML mode is useful before launch, inside a CMS, or when you want to validate server-rendered head markup without publishing it.

Audit mode Use live URL mode for production QA. Use pasted HTML mode for staging or template work.

URL or reference URL In live URL mode, this is the page to fetch. In pasted HTML mode, it acts as an optional base URL for resolving relative canonical or image paths.

HTML source

Paste the full HTML or at least the <head> section that contains your social metadata.

Pasted HTML The checker reads the raw source. JavaScript that injects tags after page load may still fail on real crawlers.

Result details appear below in the audit report and share-preview card. The result area is rendered server-side so the output also works without relying on front-end-only calculations.

Embed Open Graph Checker Widget

About Open Graph Checker

An Open Graph checker helps you verify the exact metadata that controls how a page appears when someone shares a link in social feeds, chat apps, email previews, or collaboration tools. Instead of relying on whatever title, excerpt, or image a platform guesses from the body, Open Graph tags give crawlers a clear set of instructions: which headline to show, which summary to display, which image to fetch, which canonical URL to associate with the share, and what type of content the page represents. That matters for SEO and GEO workflows because modern discovery systems often reuse these same page-level signals when generating previews, link cards, summaries, or source citations.

How to Use

Choose a source. Use live URL mode when you want to test what a crawler can fetch from a public page right now, or switch to pasted HTML mode when you are validating markup before launch.
Enter the URL or HTML. Paste the exact URL you expect users to share, or paste the page HTML with the head section intact so the checker can read Open Graph, Twitter, and canonical tags.
Run the checker. Review the preview card, missing-field warnings, duplicate-tag findings, redirect notes, and field comparison table after the scan completes.
Fix the final source before sharing. Update the page so the server-rendered response exposes one clear set of tags, then recheck before posting the link in campaigns, social posts, newsletters, or internal chat tools.

What the Checker Reviews

Signal	Why it matters	Typical problem
`og:title`	Gives crawlers an explicit share headline instead of reusing the HTML title or a random heading.	Very short titles look generic, while long titles often truncate in messaging previews.
`og:description`	Controls the supporting copy that explains the page after the title.	Thin descriptions waste preview space or let platforms assemble fragments from body text.
`og:image`	Usually determines the thumbnail or hero image in the card.	Relative URLs, HTTP images, or missing images lead to inconsistent previews across apps.
`og:url` and canonical	Help platforms consolidate shares and keep the preferred page URL consistent.	Redirects or mismatched URLs split engagement counts and confuse indexing signals.
`twitter:card`	Improves fallback behavior on X and some embed consumers even when Open Graph is present.	Teams assume OG alone is enough, then get a smaller or less consistent card on some surfaces.

Common Mistakes and Interpretation Tips

A page can look correct in a browser and still produce a weak social preview if the metadata is duplicated, injected late with JavaScript, or attached to the wrong canonical URL. One frequent mistake is publishing og:url for a non-canonical or parameterized version of the page, then sharing a different URL in campaigns or newsletters. Another is relying on relative image paths that work inside a browser but create ambiguity for crawlers. Duplicate og:title or og:description tags are also risky, because platforms may choose the first value, the last value, or a cached older value depending on how they fetch the page.

If the checker reports a redirect, compare the requested URL, final fetched URL, canonical link, and og:url together. Those four values should usually describe the same preferred page. If they do not, fix the page before a promotion or product launch so social shares, analytics, and indexing signals all point to one stable URL.

Use Cases

This tool is practical for editorial teams checking article shares before publication, ecommerce teams validating product cards before a campaign, and developers reviewing SSR output after a framework migration. It is also useful when debugging why Slack, Discord, LinkedIn, or Facebook is showing an outdated thumbnail, a homepage title, or a generic fallback image. In those situations, the problem is often not the platform itself but the metadata exposed by the page source it fetched.

Because many AI answer surfaces and preview systems reuse page metadata, controlled Open Graph tags can also improve how links are summarized or cited outside traditional social media. The tags are not a ranking factor by themselves, but they are part of the page-quality packaging that affects click-through and share confidence.

FAQ

How do I test Open Graph tags before posting a link on social media?

Fetch the live URL or paste the final HTML source, then confirm that og:title, og:description, og:image, og:url, and og:type are present in the page source a crawler actually receives. After that, compare the OG URL with the canonical link and make sure the page is not redirecting somewhere unexpected.

Why is my link preview showing the wrong image or title?

The usual causes are missing Open Graph tags, duplicate values, relative image paths, stale cache on the social platform, or a mismatch between the shared URL and the canonical or redirected page. If the final source does not expose one clear set of fields, preview systems may guess.

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

Open Graph covers many platforms, but twitter:card and optional Twitter-specific title, description, or image fields still improve fallback behavior on X and on some tools that read those tags directly. It is a small addition that usually improves consistency.

Can JavaScript-generated meta tags break social sharing previews?

Yes. Many crawlers inspect the initial HTML response and do not behave like a full browser that waits for client-side rendering. If your framework injects tags after load, a user may see the right page in the browser while a crawler still sees missing or outdated metadata.

Reference this content, page, or tool as:

"Open Graph Checker" at https://MiniWebtool.com/open-graph-checker/ from MiniWebtool, https://MiniWebtool.com/

by miniwebtool team. Updated: 2026-03-09