MUTools

OGP Checker

OGP Checker pulls Open Graph and Twitter Card metadata from a URL and previews how it will look as a share card on X, Facebook, and similar networks — without actually posting to the platform.

Enter a URL and press "Check OGP" to see diagnostics, metadata, and share-card previews here.

Each input URL is fetched server-side for HTML parsing. Connections to private IPs or localhost are rejected. Each fetch times out after 8 seconds and reads only the first 2MB of the HTML body.

About OGP Checker

OGP Checker pulls Open Graph and Twitter Card metadata from a URL and previews how it will look as a share card on X, Facebook, and similar networks — without actually posting to the platform.

Beyond listing the page's og:title, og:description, og:image, and other key tags, it includes a diagnostic that flags missing required fields, recommended length overruns, or an unset og:image:alt, classified as "needs fix" or "recommended".

Useful for pre-publish reviews of articles or landing pages, and for tuning share cards to improve click-through from social.

How to use

  1. Paste the URL you want to check (must start with https://) into the input.
  2. Click "Check OGP" — the page is analyzed and the results are shown.
  3. The "OGP diagnosis" section flags missing required fields and gaps versus recommended settings.
  4. The "Metadata list" section shows extracted title / og:* / twitter:* tags.
  5. The "Share card preview" lets you switch between X (Twitter) and Facebook, light and dark themes.

Use cases

  • Editors and marketers verifying that share cards look right before publishing a new article or landing page.
  • Operators tuning titles, descriptions, and OG images to improve click-through from social.
  • Web agencies sweeping every page on a corporate site to confirm OGP is set correctly.
  • Planners reviewing the share cards used by competitors or reference sites.
  • Engineers verifying CDN cache behavior after swapping an OG image.

Notes

  • Connections to private IP addresses or localhost are refused for safety. Internal sites are not reachable.
  • Each fetch has an 8-second timeout — slow servers may error.
  • Only the first 2 MB of HTML is read; very large pages may not yield metadata.
  • Sites that rewrite metadata via JavaScript (SPAs) yield only the values present in the initial HTML, which may differ from what social crawlers see.
  • The preview approximates X / Facebook layouts. The actual card may differ as each platform updates its specs.
  • Social networks cache card images; changes may take time to propagate (X and Facebook both have official debuggers that force a re-fetch).

FAQ

What is OGP?
Open Graph Protocol is a metadata standard used to share page info with other services. By placing og:title, og:description, og:image, and friends inside <head>, your page can render as a rich card with imagery on social networks. Defined by Facebook and supported by X (Twitter), LinkedIn, Slack, and many others.
How does OGP relate to Twitter Card?
Twitter Card is X's own metadata spec using twitter:card, twitter:title, twitter:image, and similar tags. Most fields fall back to OGP, so it is common to set twitter:* only when you want to override the OGP defaults. Both are extracted and diagnosed here.
Why does the preview not match the real social card?
The preview here is an approximation of X / Facebook layouts. Each platform continuously updates its specs — image aspect ratios, title truncation, light/dark behavior — and they can differ. Use each platform's official debugger (X Card Validator, Facebook Sharing Debugger) for the authoritative view.
What is a good length for og:title?
On X, around 70 characters tends to be the cutoff, so a warning is shown above 70. og:description is recommended at 200 characters or less. Use the preview to confirm where truncation will hit and tune accordingly.
Some sites cannot be checked.
Sites that exceed the 8-second timeout, hide meta tags below the first 2 MB of HTML, or block fetches via basic auth or bot blocking will error. Connections to private IPs or localhost are also refused. If any of these match, the site itself needs adjusting.