Toolkit ShelfFind

Utility Tools

Open Graph + Twitter Card Checker

Use this social preview checker to verify share cards before launching a page, posting a campaign link, sending a newsletter, or handing off a URL for distribution.

Method shown June 6, 2026Source note includedFree tool

Live checker

Open Graph + Twitter Card checker

Status
Run a guarded HTML check to inspect share preview tags.
Final statusNot checked

No request is sent until you run the check.

Open GraphNot checked

Checks og:title, og:description, og:image, og:url, og:type, and og:site_name.

Twitter CardNot checked

Checks card, title, description, image, site, and creator tags.

Review notes
  • Checks one public HTML URL. Local, private, reserved, non-http, and credentialed URLs are blocked.
Scope note

This checker reads the fetched HTML response only. It does not render JavaScript, upload images, validate image dimensions, or simulate each platform preview crop.

Quick answer

Open Graph + Twitter Card Checker: what it checks

Open Graph + Twitter Card Checker checks social preview metadata report from page URL, HTTP status, final URL, title, meta description and open Graph tags, and additional inputs. The visible check method is Share preview report = guarded HTML fetch + redirect follow + title + meta description + Open Graph tags + Twitter Card tags + preview image checks.

Check outputSocial preview metadata report
InputsPage URL, HTTP status, Final URL, Title, Meta description, Open Graph tags, Twitter Card tags, Preview image
Check methodSocial preview check method

Check method

Social preview check method

Share preview report = guarded HTML fetch + redirect follow + title + meta description + Open Graph tags + Twitter Card tags + preview image checks

The checker fetches one public HTML URL, follows up to 5 redirects, and blocks local, private, reserved, credentialed, and non-http destinations before each request.

How to use

Steps

  1. Paste the exact public page URL you want to preview-check.
  2. Run the check to fetch the final HTML response and share metadata.
  3. Review title, meta description, Open Graph fields, Twitter Card fields, preview image URL, and warnings.
  4. Fix missing images, mismatched URLs, missing descriptions, or incomplete card tags before sharing the link.

Example

Sample check

Launch pageVerify og:image and social title before posting a new page
Newsletter linkCheck whether the shared URL has a readable title and description
Campaign QACapture final URL, Open Graph, and Twitter Card fields in one handoff

Checker use

Best for

  • Use this social preview checker to verify share cards before launching a page, posting a campaign link, sending a newsletter, or handing off a URL for distribution.
  • Checking social preview check method with the method and assumptions visible.
  • Comparing the output with the sample check and benchmark table before using it elsewhere.
  • Browser-side link, file, format, and web utility tasks that need an output now.

Before relying on it

Check first

  • Using the social preview metadata report without checking that page URL, HTTP status and final URL, and additional inputs match the same task and context.
  • Ignoring that the checker fetches one public HTML URL, follows up to 5 redirects, and blocks local, private, reserved, credentialed, and non-HTTP destinations before each request.
  • Skipping the source notes when the formula, benchmark, or warning depends on outside context.
  • Publishing a generated file or code without testing it in the real destination.

Details

What to know before using the output

These notes make the assumptions explicit, especially where the same search query can mean slightly different things.

GuardrailsPublic http/https only

Localhost, private networks, reserved IPs, credentials, and non-http redirects are blocked to avoid internal-network fetches.

Fetch scopeOne HTML response

The checker reads the fetched HTML. It does not render JavaScript, upload images, or simulate every social network crop.

Image validationURL presence

The checker reports image URLs from tags. It does not download image dimensions or validate platform-specific safe areas.

Source notes

References used for this checker

Open Graph protocolDocuments the core Open Graph metadata fields used by social previews.X Developer PlatformDocuments Twitter Card markup fields used for card previews.MDN Web DocsDocuments the Fetch API used for bounded HTTP requests.

Benchmarks

How to read the output

This checker is a decision aid, not a fixed rule. Use the output to compare scenarios and document your assumptions. Benchmark ranges are broad planning heuristics unless this page names a specific source for the range.

Open Graph: Title, description, image, URL.

These fields drive many link previews and are the minimum useful share-card check.

Twitter Card: summary_large_image.

Large-image cards usually need twitter:card plus title, description, and image fields.

Final response: 200-range HTML.

Share metadata checks are most useful after redirects resolve to a successful HTML response.

Method and limitations

Methodology and assumptions

The method, inputs, example, and limitations are shown so the check is transparent, not just a pass/fail label.

Check method

Share preview report = guarded HTML fetch + redirect follow + title + meta description + Open Graph tags + Twitter Card tags + preview image checks

Inputs used

Page URL, HTTP status, Final URL, Title, Meta description, Open Graph tags, Twitter Card tags, Preview image

Limitations

Utility outputs depend on the encoded payload, file format, target app, scanner, printer, browser, and real-world testing before sharing.

Last reviewed

June 6, 2026

Cite this page

Toolkit Shelf. Open Graph + Twitter Card Checker. Last reviewed June 6, 2026. https://toolkitshelf.com/tools/social-preview-checker

FAQ

Common questions

Does this show the exact preview every platform will render?

No. It reads page metadata and flags missing fields. Platforms can cache old metadata, crop images differently, or apply their own fallback rules.

Does it validate image size?

No. It reports the image URLs found in Open Graph and Twitter tags. Check dimensions and crops in the target platform's preview tool before launch.

Why does the checker block private or localhost URLs?

A public metadata checker must not fetch internal network targets. Blocking local, private, reserved, credentialed, and non-http destinations reduces SSRF and proxy-abuse risk.

Do utility tools upload my payload?

Use the page notes for each tool. Browser-side utilities can generate outputs locally, but the final file or code may still reveal whatever you encode or share.

Why should I test the generated output?

Scanners, printers, file viewers, apps, and platform previews can behave differently, so test the exact downloaded output before using it publicly.

Why might another checker show a different output?

Different tools may use different rounding, assumptions, default rates, methods, formulas, or input timing. Compare the visible method and inputs before relying on the output.