Open Graph Meta Checker

Check Open Graph and Twitter Card meta tags for any HTML page. Extract og:title/og:description/og:image plus Twitter tags, highlight missing or invalid values, and generate shareable JSON/PDF reports. Designed for SEO and social preview debugging with redirect support and raw-text output.

Loading…

About Open Graph Meta Checker

Paste a URL to verify what social platforms can read from your page: Open Graph (og:*) tags and Twitter Card metadata. This tool helps you spot missing titles/descriptions, broken or non-public og:image URLs, redirect problems, and common preview pitfalls—so your links look right on X/Twitter, Facebook, LinkedIn, Slack, Discord, and more.

Features

  • Extract Open Graph meta: og:title, og:description, og:image and related OG properties when present.
  • Extract Twitter Card tags (twitter:card, twitter:title, twitter:description, twitter:image) when present.
  • Follow redirects to inspect the final canonical destination (common for HTTP→HTTPS, www, locale routes).
  • HTML-only validation mode to focus on meta tags (not non-HTML resources).
  • Findings + score card and "only problems" filter for fast cleanup.
  • Raw-text output that's easy to copy, diff, and share.
  • Copy results for tickets and documentation.
  • Export JSON for automation and auditing.
  • Export PDF reports for client deliverables and SEO audits.

🧭 How to use for open-graph-meta-checker

1

Paste the page URL

Enter the URL of the page you want to preview (e.g., a landing page, blog post, product page). This tool is intended for HTML pages, not images or APIs.

2

Follow redirects if your site redirects

Keep "Follow Redirects" enabled so the tool checks the final destination that social crawlers will likely reach.

3

Review OG and Twitter values

Check title, description, and image fields. Look for empty values, placeholders, duplicates, or mismatches between OG and Twitter tags.

4

Fix common preview issues

Ensure og:image is an absolute URL, publicly accessible, and points to the correct asset. Confirm titles/descriptions are concise and unique per page.

5

Export and share a report

Download JSON for automation or PDF for SEO/client reporting. Use the raw-text view to quickly paste values into tickets.

Technical specs

Request and parsing model

This tool fetches the target page (HTML) and extracts Open Graph and Twitter Card meta tags from the document's meta elements. It supports redirect following to inspect the effective destination.

SettingBehaviorDefault
HTML-onlyFocuses on HTML pages and meta extractionEnabled (by tool capability)
Follow RedirectsFollows redirects to inspect the final URLEnabled
Max RedirectsRedirect cap to prevent loops10
TimeoutRequest timeout limit15000 ms
User-AgentIdentifies the request user agentEncode64Bot/1.0 (+https://encode64.com)
Private networksBlocks access to private network ranges for safetyDisabled (private networks not allowed)

Recommended meta set (baseline)

A solid baseline includes both Open Graph and Twitter Card fields so previews render consistently across platforms.

PlatformMinimum tagsNotes
Open Graphog:title, og:description, og:imageAdd og:url and og:type when applicable
Twitter Cardtwitter:card, twitter:title, twitter:description, twitter:imagetwitter:card is commonly summary or summary_large_image
Even if your page looks fine in a browser, crawlers only see what's in the HTML response they fetch. Client-only meta injection may not be picked up reliably.

og:image pitfalls to watch

The most common preview failures come from the image URL: it must be reachable, absolute, and compatible with crawler fetch rules.

IssueSymptomFix
Relative image URLPreview shows no imageUse an absolute URL for og:image and twitter:image
Blocked by auth / robots / firewallPreview missing or inconsistentEnsure public access for crawlers; allow social user agents if you filter
Redirecting image URLSome platforms fail to fetch itPrefer a direct, stable image URL (no redirects)
Wrong content typeImage not recognizedServe correct Content-Type (e.g., image/png, image/jpeg)

Command line

You can validate OG/Twitter tags from the terminal by fetching the HTML and grepping meta tags. Useful for CI checks and debugging SSR issues.

macOS / Linux

Fetch HTML and list OG/Twitter meta tags

curl -Ls https://example.com/page | grep -i -E "<meta[^>]+(property=\"og:|name=\"twitter:)"

Shows meta tags that affect social previews. Use -L to follow redirects.

Check the final URL after redirects

curl -ILs https://example.com/page | awk '/^HTTP\//{print} /^location:/I{print}'

Prints the redirect chain status lines and Location headers.

Windows (PowerShell)

Download HTML and search for OG/Twitter tags

$html = (Invoke-WebRequest https://example.com/page).Content; $html -split "`n" | Select-String -Pattern "<meta" | Select-String -Pattern "og:|twitter:"

Quick way to confirm tags exist in the delivered HTML.

If your app is SPA-heavy, make sure OG/Twitter tags are rendered server-side (SSR/SSG) for reliability. Crawlers may not execute your client JavaScript the way browsers do.

Use cases

Fix broken social previews

When a link shares with the wrong title, no image, or outdated text, this tool helps you locate the missing or incorrect meta fields quickly.

  • Validate og:title and twitter:title
  • Confirm og:image is reachable and absolute
  • Detect empty descriptions or placeholders

QA for dynamic pages and SSR

Ensure your framework outputs OG/Twitter tags in the HTML response for each route (especially with Next.js, Nuxt, SvelteKit, etc.).

  • Confirm per-page meta is present in HTML
  • Catch client-only meta generation
  • Validate redirects to canonical locales

SEO and content publishing workflows

Standardize previews across a site: consistent titles/descriptions, correct OG type, and stable images improve CTR when links are shared.

  • Audit templates for missing OG fields
  • Export PDF/JSON for editorial checklists
  • Detect duplicated meta across multiple pages

Client reporting and audits

Generate a clean, exportable report to document social preview status and recommended fixes.

  • PDF report for stakeholders
  • JSON report for tracking changes over time

❓ Frequently Asked Questions

❓What's the difference between Open Graph and Twitter Cards?

Open Graph (og:*) is used by many platforms (Facebook, LinkedIn, Slack/Discord, etc.). Twitter Cards (twitter:*) are used by X/Twitter. Many sites publish both for best coverage.

❓Why does my preview show an old image or title?

Platforms cache previews. After fixing tags, you often need to re-scrape using the platform's debugger tools, and you may need to wait for cache refresh.

❓Why is my og:image not showing?

Common causes: the URL is relative, blocked (auth/WAF/robots), redirects too much, wrong content type, or not publicly reachable. Use this tool to verify the extracted value and then test the image URL directly.

❓Do I need both og:title and twitter:title?

It's recommended. Some platforms rely on OG, others on Twitter tags. Having both reduces inconsistencies.

❓Can I test a page behind login?

Social crawlers generally can't access authenticated content, so previews won't work reliably. Prefer public preview pages or public OG endpoints for shareable content.

❓Is it safe to paste URLs here?

The tool makes server-side requests to the provided URL and blocks private-network targets. Avoid putting secrets (tokens) in query strings.

Pro Tips

Best Practice

Use absolute URLs for og:image and twitter:image and keep them stable (avoid redirects) to reduce crawler failures.

Performance Tip

Generate OG images deterministically (template + parameters) so you can update branding while keeping URLs stable per page.

Best Practice

For Next.js/SSR apps, verify tags in the initial HTML response (View Source), not only in the DOM after hydration.

Best Practice

Keep titles concise and unique per page; overly long titles may be truncated in previews and reduce CTR.

CI Tip

Export JSON reports and add them to your release checklist to catch regressions in meta templates.

Additional Resources

Open Graph protocol
Technical specification
Twitter Cards (X) documentation
Documentation
Meta tags for social previews (MDN: <meta>)
Documentation
Google Search Central: control snippets (meta tags)
Reference

Other Tools