Social & Structured Data Checker

Check a page's Open Graph tags, Twitter/X card, and JSON-LD structured data — then build improved tags from the page and copy them.

Infrastructure

Page URL

Any public http(s) page. https:// is assumed if you leave the scheme off.

Summary

Final URL
Title
Description
Canonical

Open Graph

    Twitter / X card

      Structured data

        Build tags

        Pre-filled from the page's existing tags, falling back to its <title>, meta description, canonical URL, and first image. Edit anything below — the output and previews update as you type.

        1200×630 is the safe size for both large cards.
        X falls back to the Open Graph values when these are left out, so they're optional.
        Open Graph preview
        X preview

        You can edit the output directly, but changing a field above regenerates it — so make free-form tweaks last.

        The URL you submit is fetched by this server (browsers can't read another site's HTML directly) and only its tags are returned — nothing is logged or stored.

        What each set of tags is for

        Open Graph (og:*) is the protocol Facebook introduced and practically everything else adopted — LinkedIn, Slack, Discord, WhatsApp, iMessage, and Teams all read it to build the card shown when a link is pasted. The four required properties are og:title, og:type, og:image, and og:url; og:description and og:site_name are worth adding too. Twitter/X cards (twitter:*) only need twitter:card to pick the layout — X falls back to the Open Graph title, description, and image for anything not set explicitly. Structured data (JSON-LD using the schema.org vocabulary) is different: it's read by search engines rather than social platforms, and is what makes a page eligible for rich results like article bylines, product prices, and breadcrumbs.

        Why a preview might still look wrong after fixing tags

        Every platform caches the card it scraped the first time a URL was shared, often for days. After changing tags, force a re-scrape with Facebook's Sharing Debugger or LinkedIn's Post Inspector, or share the URL with a throwaway query string (?v=2) to get a fresh card. The previews on this page are approximations of each platform's layout — the real crop and truncation vary slightly between platforms and change over time.

        Common mistakes

        A relative og:image path (/images/share.png) is the most common — crawlers don't resolve it against the page URL, so it must be absolute. Images that are too small (under 200×200 for Facebook) or blocked from crawlers by robots.txt or authentication get silently dropped. Tags injected by client-side JavaScript usually don't count either: most social crawlers don't run scripts, which is why this tool reads the raw HTML the server returns rather than the rendered page. If a redirect is involved, check the status code it uses — crawlers follow 301s and 302s, but tags on the pre-redirect URL are ignored.