Zap.Tools
By Updated

Open Graph Preview

Preview how a URL appears on Facebook, LinkedIn, Twitter, Slack, and Discord, with a checklist for missing OG and Twitter card tags

Interactive tool

URL to inspect

Routes through our SSRF-safe backend. Non-public addresses are rejected and the URL is not logged.

What is the Open Graph Preview tool?

The Open Graph Preview tool inspects how a URL or HTML snippet renders when shared on social platforms. It fetches the page (or parses pasted HTML), extracts the Open Graph and Twitter card meta tags, and renders three platform-style preview cards alongside a checklist of missing or broken tags. Fix the gaps before you publish to make every share look polished.

How to Use This Open Graph Preview

  1. 1Pick "Fetch URL" to test a published page or "Paste HTML" for a draft
  2. 2Enter the URL or paste the <head> contents
  3. 3Click Preview to see Facebook/LinkedIn, Twitter, and Slack cards
  4. 4Read the checklist for missing or weak tags
  5. 5Copy the suggested meta tags and paste them into your <head>
  6. 6Re-run the preview to confirm the fixes are live
What you get

Key features

Three platform previews

Facebook/LinkedIn, Twitter/X, and Slack/Discord renderings side by side

URL fetch with SSRF guard

Server-side fetch validates URLs and blocks non-public addresses

HTML paste mode

Test drafts before they are deployed by pasting the head HTML

Smart checklist

Severity-tiered list of missing tags: errors, warnings, and info

Suggested meta block

Ready-to-paste <meta> snippet that fills in the gaps the checklist found

All detected tags

Browse the full list of meta and link tags the page exposes

Edge cached

Repeated URL fetches are cached for 10 minutes to keep the tool fast and polite

Nothing logged

We never log the URL you test, your IP, or any user-identifying data

Why Test Open Graph Cards Before Sharing?

Open Graph and Twitter card metadata control how your URL looks in feeds, chats, and search snippets. A missing og:image makes a link look like spam. A title that is too long gets truncated awkwardly. Worse, platforms cache previews aggressively: once an ugly card is cached on Facebook or LinkedIn, it can stick for days. Catching mistakes locally first is cheaper and faster than chasing platform sharing debuggers afterwards.

Common use cases

  • Pre-publish QA for marketing pages and blog posts
  • Validating dynamic OG tags rendered by your CMS
  • Testing canonical URLs and og:url alignment
  • Spotting missing twitter:card before a Twitter ad campaign
  • Auditing landing pages for an A/B test rollout
  • Comparing how a competitor's page renders across platforms

Image size recommendations

  • Facebook & LinkedIn: 1200 × 630 (1.91:1), minimum 600 × 315
  • Twitter summary_large_image: 1200 × 628 (keep important content centered)
  • Slack and Discord: roughly the og:image, scaled down to a thumbnail
  • Use under 5 MB image size; PNG or JPEG (animated GIF works on Twitter only)
  • Always use absolute URLs (https://…) (relative paths fail on every platform)

Open Graph vs Twitter cards

Open Graph (og:*) is the de-facto standard for Facebook, LinkedIn, Slack, Discord, and most modern platforms. Twitter still reads twitter:* tags first when available, then falls back to og:*, so for parity, set og:* tags and include twitter:card to opt into a richer Twitter preview.

Pro tips

Tips & best practices

Bust platform caches after fixing tags

Facebook caches OG tags up to 24 hours. After fixing, re-scrape via the Facebook Sharing Debugger; for LinkedIn, use the Post Inspector; Twitter no longer offers a public debugger.

Use absolute URLs for og:image

Relative paths like /og.png break on every platform. Always use a full https:// URL, including the domain.

Write a 60 to 70 char title

Twitter truncates around 70 characters; Facebook around 100. Aim for under 70 and place the strongest words first.

Match og:url to the canonical URL

When the URL with tracking parameters and the canonical version differ, set og:url to the canonical to prevent duplicate cards.

Test from a clean session

Some sites serve different metadata to bots than to logged-in users. Run the URL through this tool in incognito to confirm what crawlers will actually see.

Built for trust

Privacy & security

When you fetch a URL, the request is proxied through our backend to avoid CORS and to protect against SSRF. The backend blocks non-public addresses and applies redirect, size, and timeout caps. We do not log the URL, your IP, or any user-identifying data. HTML paste mode never leaves your browser.

Related tools

Frequently Asked Questions

What is Open Graph?

Open Graph is a meta tag protocol introduced by Facebook that lets web pages declare a title, description, image, and other metadata for use in shared link previews. It is now supported by virtually every major chat and social platform.

What is the difference between og:* and twitter:* tags?

Open Graph (og:*) is the cross-platform standard. Twitter cards (twitter:*) are an X-only enhancement that override og:* tags when present. For best coverage, set og:* tags and add twitter:card to opt into Twitter's richer preview formats.

What size should my og:image be?

The recommended size is 1200 × 630 pixels (a 1.91:1 ratio). The image must be at least 600 × 315 to be eligible for a "large image" treatment. Use absolute URLs and keep the file under 5 MB.

Why does my preview differ across platforms?

Each platform has its own caching rules, image size guidelines, and rendering quirks. Facebook may cache for up to 24 hours; LinkedIn even longer. After updating tags, use the platform-specific debugger to force a re-scrape.

Is the URL I test logged or shared?

No. Our backend does not log the URL, your IP, or any user-identifying data. Responses are briefly cached at the edge to keep the tool fast and reduce load on the upstream site.

Why are private IPs blocked?

Allowing arbitrary URL fetches can be abused to scan internal networks (a class of vulnerability called SSRF). Our backend resolves each hostname and refuses to connect to non-public addresses.