Open Graph Readiness Score
Separate passes, warnings, and failures with specific fixes.
Run a live Open Graph test for any URL. Inspect the tags and share image, preview the resulting cards, trace redirects, and copy the exact fixes your page needs.
Reviewed September 23, 2026 · Maintained by LinkGlimpse · How the diagnostics work
Separate passes, warnings, and failures with specific fixes.
Verify the exact Open Graph, Twitter, robots, and canonical values found.
Check whether the image responds publicly, its format, byte size, and dimensions.
Copy, share, or download the live report for a developer, client, or release checklist.
Need a platform-specific workflow? Use the Twitter Card validator, LinkedIn post preview, or Facebook Open Graph debugger.
Generate a self-contained repair prompt with the failed checks, current tags, suggested code, and verification requirements.
Diff a production URL against staging or a replacement page before you ship metadata changes.
Compare two URLs →Share a re-runnable report link. It fetches the page again so collaborators see the latest deployed metadata.
View report examples →The best checker for a release workflow should fetch the live public URL, show both the visual result and the underlying metadata, test the share image and redirects, and explain what to fix. It should also be clear about what it cannot verify, including private platform rendering and cache-refresh timing.
Confirm the final URL, response, redirect path, canonical, robots directives, and metadata returned by the deployed page.
Review representative cards alongside the exact Open Graph and Twitter Card values instead of relying on a screenshot alone.
Verify image reachability, format, byte size, and detectable dimensions, then connect each warning to a practical fix.
Keep a report that another person or agent can rerun after deployment, with limitations and methodology stated plainly.
Use it when you want a free, open-source, no-signup workflow that combines multi-platform previews, metadata diagnostics, copy-ready fixes, shareable reports, before-and-after comparison, and an AI-agent handoff.
Use the official Facebook debugger or LinkedIn Post Inspector when you need that platform to refresh its cache. LinkGlimpse can verify the public metadata you deployed, but it cannot clear a platform cache or guarantee a private renderer's final card.
The checker follows and records redirects, fetches the HTML, and inspects the declared share image.
Confirm the visible title, description, and crop, then work through warnings in the diagnostic report.
Paste the suggested code or AI-agent prompt into your workflow, deploy, and rerun the same URL to verify it.
A reliable link preview starts with one clear value for each core property. Use absolute HTTPS URLs for the page and image.
<meta property="og:title" content="A clear, specific title" />
<meta property="og:description" content="A concise reason to open this page." />
<meta property="og:image" content="https://example.com/social-card.jpg" />
<meta property="og:url" content="https://example.com/page" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />Debug missing, blocked, relative, or incorrectly sized share images.
Fix card type, image, fallback, crawler, and cache problems.
Separate live metadata problems from LinkedIn cache problems.
Correct stale titles, images, descriptions, and canonical mismatches.
Choose a safe aspect ratio, dimensions, format, and file size.
Copy implementation examples for HTML, Next.js, React, and WordPress.
It fetches the public page, extracts Open Graph and Twitter Card tags, checks canonical and robots directives, inspects the share image response, and turns the findings into actionable checks.
Yes. Expand the raw-tag view, copy a fix for any warning, download the JSON report, or copy a complete repair prompt for an AI coding agent.
No checker can control platform caches or private crawler rules. The score confirms that the public metadata and assets contain the core signals those platforms use.