Ttooleras
👁️

Open Graph Debugger

SEO Tools

Debug Open Graph and Twitter Card metadata — inspect raw tags, validate requirements, and get links to force social platform cache refresh.. Free, private — all processing in your browser.

Google Search Preview

Page Title
https://example.com › page
Your meta description will appear here. Write a compelling description to improve click-through rates.

Mobile Preview

Page Title
https://example.com › page
Your meta description...
⚠️ Title is empty
⚠️ Description is empty
Advertisement

The OG Debugger is a diagnostic tool for Open Graph and Twitter Card metadata issues. When a shared link shows the wrong image, stale content, missing description, or broken preview, this tool helps identify exactly what is happening and how to fix it. Inspects the raw meta tags present in the HTML, detects common issues (cached old image, invalid URLs, missing requirements, image format problems), and provides direct links to Facebook Sharing Debugger and LinkedIn Post Inspector to force cache refresh.

Unlike Open Graph Preview (which renders how the link looks), this tool focuses on debugging. It shows raw tag values, fetched image dimensions and file size, validation against platform requirements, and cache status indicators. When a preview looks wrong, start here to understand why before trying to \"fix\" the tags. Most \"broken preview\" issues are actually cache problems on the social platform side; this tool distinguishes between \"bad tags\" and \"cached old version\" so you apply the right fix.

Open Graph Debugger — key features

Raw tag inspection

Shows every og:* and twitter:* meta tag’s raw value for direct debugging.

Image validation

Fetches og:image and reports dimensions, file size, and format compliance.

URL accessibility check

Verifies every URL in metadata (og:url, og:image) is actually reachable.

Required tags audit

Platform-specific checklist of required tags; flags what is missing.

Cache refresh links

Direct links to Facebook Sharing Debugger, LinkedIn Post Inspector, Twitter Card Validator.

Platform-specific warnings

Different platforms have different requirements; warnings are labeled by platform.

Fix-ready suggestions

Specific meta tag code to add or modify, copy-ready.

Client-side only

URL is fetched and analyzed; no data about you or the URL is stored.

How to use the Open Graph Debugger

  1. 1

    Enter URL

    Paste the problematic URL that’s showing wrong or broken preview.

  2. 2

    Analyze

    The tool fetches the page and parses all social metadata.

  3. 3

    Review raw tags

    See every og:* and twitter:* tag with its value — spot obviously wrong values.

  4. 4

    Check image status

    Verify og:image loads, has correct dimensions, and meets size requirements.

  5. 5

    Force cache refresh

    Use the provided direct links to Facebook and LinkedIn debuggers to re-fetch the URL.

Common use cases for the Open Graph Debugger

Content debugging

  • Broken preview diagnosis: Investigate why a specific URL shows wrong image, title, or description when shared.
  • Post-update verification: After updating meta tags, verify tags are correct and clear platform caches.
  • Multi-platform consistency: Verify shared link looks consistent across Facebook, Twitter, LinkedIn, WhatsApp.

Marketing operations

  • Campaign preparation: Before launching a campaign that relies on social sharing, verify all landing pages have correct metadata.
  • Content audit: Regular audits of published content to catch broken previews before they impact sharing.
  • Rebrand check: After brand update, verify old pages show new brand imagery and messaging in social previews.

Technical support

  • Client issue investigation: When users report broken social previews, quickly determine if the issue is on the page or at the platform cache.
  • CMS template debugging: Identify systematic issues in CMS templates that generate incorrect Open Graph tags.
  • SSR/SPA metadata debugging: Verify server-side rendering actually produces og:* tags (SPAs often fail here).

Open Graph Debugger — examples

Missing og:image

Page that lacks an image tag.

Input
https://example.com/page-without-image
Output
issue: og:image missing
impact: no image in Facebook/LinkedIn previews
fix: add <meta property=\"og:image\" content=\"https://example.com/hero.jpg\">
image must be 1200x630, JPEG or PNG, under 1MB

Relative image URL

Common mistake in CMS templates.

Input
<meta property=og:image content=/images/hero.jpg>
Output
issue: og:image URL is relative
impact: most social platforms cannot resolve relative URLs
fix: use absolute URL starting with https://

Image cached

Platform showing old image after update.

Input
page updated og:image, but Facebook shows old one
Output
status: page has correct new image
issue: Facebook cached old image
fix: visit Facebook Sharing Debugger, click \"Scrape Again\" to refresh cache

Twitter missing

Page has og:* but no twitter:* tags.

Input
partial social metadata
Output
Twitter preview will use og:* tags as fallback
for full Twitter control, add twitter:card, twitter:image, twitter:title, twitter:description

Inaccessible image

og:image URL returns 404.

Input
og:image pointing to deleted file
Output
issue: og:image URL returns 404 (not found)
impact: broken social preview
fix: update og:image to a working URL or restore the image file

Technical details

Common Open Graph issues and debugging approach:

Issue 1: Preview shows old image after update.
- Root cause: Facebook/LinkedIn caches images aggressively (often indefinitely). Updating og:image doesn\u2019t automatically update cached previews.
- Fix: Use Facebook\u2019s Sharing Debugger (developers.facebook.com/tools/debug/) or LinkedIn Post Inspector to force re-fetch. The tool shows direct links for easy access.

Issue 2: Preview missing image entirely.
- Root cause: og:image missing, broken URL, or image requirements not met
- Debugging: check that og:image is present, URL is absolute (https://example.com/image.jpg), image is reachable, image is at least 600x315, file size under 1 MB, and format is JPEG or PNG.

Issue 3: Preview shows wrong title or description.
- Root cause: missing og:title / og:description, or tags contain outdated content
- Fix: verify og:title and og:description match current content; force cache refresh if recent update.

Issue 4: Twitter shows different preview than Facebook.
- Root cause: twitter:* tags exist and differ from og:* tags, or missing twitter:card type
- Fix: ensure consistency, or deliberately vary for platform-specific optimization.

Issue 5: Preview works in some apps but not others.
- Root cause: each platform has slightly different requirements and caching behavior
- Debugging: check each platform\u2019s specific rules and use their debugging tools.

The tool automates this debugging:
- Fetches the URL and extracts all og:* and twitter:* meta tags
- Validates each against platform requirements (image size, file size, URL format, content length)
- Checks image accessibility and reports dimensions
- Highlights missing required tags per platform
- Provides direct debugging links to Facebook and LinkedIn tools

Cache busting techniques:
- Facebook: scrape URL in Sharing Debugger; this forces Facebook to re-fetch and updates preview
- LinkedIn: Post Inspector has a \"refresh\" action
- Twitter: validator fetches the URL, but caching is less aggressive; waiting 24 hours often works
- WhatsApp: open the URL in WhatsApp web, which triggers a re-fetch
- Slack: repost the URL in a test channel; Slack caches per-URL, per-user

Manual cache bust: add a query parameter (?v=2) to the URL. Social platforms treat this as a different URL and fetch fresh. Then you can canonical back to the real URL.

Common problems and solutions

Updating tags but not clearing cache

Platforms cache previews. After updating og:image, force cache refresh in Facebook Sharing Debugger and LinkedIn Post Inspector. Otherwise old preview persists.

HTTPS vs HTTP

Most platforms require HTTPS for og:image. HTTP images fail or cause mixed content warnings. Always host og:image on HTTPS.

SPA rendering issue

Single-page apps that set og:* tags via JavaScript don’t work — social platforms don’t run JS. Use server-side rendering or pre-rendering for meta tags.

Image too small

Below 600x315 pixels, platforms may reject. 1200x630 is recommended for optimal display across all platforms.

Wrong image aspect ratio

1.91:1 aspect ratio (1200x630) is ideal. Square or vertical images may be cropped awkwardly on some platforms.

Special characters in content

Quotes, apostrophes, and HTML entities in og:description can confuse parsers. Use plain text or properly escaped HTML entities.

Multiple conflicting tags

Duplicate og:title tags are ignored (first one wins on some platforms, last on others). Use exactly one of each property tag.

Open Graph Debugger — comparisons and alternatives

Compared to Facebook Sharing Debugger, this tool covers multiple platforms and provides more specific fix suggestions. Facebook Debugger is essential for refreshing Facebook cache specifically; this tool is for broader diagnosis.

Compared to LinkedIn Post Inspector, this tool gives holistic view across all platforms. Use LinkedIn\u2019s tool to refresh LinkedIn cache; use this tool first to understand the issue.

Compared to Open Graph Preview (also in this suite), this tool focuses on debugging rather than visual preview. Use OG Preview to see what the link looks like; use OG Debugger to understand why it looks wrong.

Frequently asked questions about the Open Graph Debugger

Why is my shared link showing the wrong image?

Two common reasons: either og:image is missing/incorrect (fix the tag), or the platform has the old image cached (force refresh in Facebook Sharing Debugger or LinkedIn Post Inspector). This tool helps you distinguish which.

How do I force Facebook to re-fetch my link preview?

Go to developers.facebook.com/tools/debug/, enter your URL, click \"Scrape Again\". Facebook re-fetches the page and updates its cache. This tool provides a direct link to speed the process.

Why does LinkedIn show a different preview than Facebook?

LinkedIn and Facebook have slightly different image cropping and rendering. Also, their caches update at different times. Content should appear similar but not identical. Use both platforms’ debuggers to see what each currently has cached.

What if my page uses client-side rendering?

Social platforms don’t execute JavaScript when fetching meta tags. If your SPA relies on JS to set og:* tags, social previews will be broken. Solution: server-side rendering, static site generation, or pre-rendering for share-targeted pages.

Should Open Graph tags match exactly between og:* and twitter:*?

Usually yes, for consistency. Differences are fine if you want to tailor specifically for Twitter audience. Most sites start with og:* only and add twitter:* if they need Twitter-specific optimization (summary_large_image card, specific @handles, etc.).

What’s the difference between this and Open Graph Preview?

Open Graph Preview renders how the link will look when shared (visual preview). OG Debugger diagnoses why it’s not working (raw tag inspection, error detection, cache refresh). Use Preview for new content; use Debugger when previews are broken.

Can I test unpublished pages?

This tool requires a public URL that can be fetched. For unpublished content, first stage it at a public URL (even behind an obscure path) or use Open Graph Preview with direct HTML paste.

Is my URL logged anywhere?

The tool fetches the URL to analyze it. We don’t log the URLs analyzed or the results. Privacy-safe for sensitive internal URLs (that are nonetheless publicly reachable).

Additional resources

Advertisement

Related tools

All SEO Tools

Learn more

Explore more tools

200+ free tools that run in your browser.

Browse all tools →