Open Graph Checker & Social Preview
Validate a public URL, preview its share card, and get clear fixes for weak titles, descriptions, URLs, and images.
Open Graph Checker and Social Preview
Test a public URL, preview the share card, and review the metadata quality that Microlink exposes for Open Graph and Twitter-style cards.
External metadata lookup
What works and what sucks
What works
- Healthy title and description lengths.
- A present, readable share image.
- A stable resolved URL served over HTTPS.
- Useful normalized metadata for public pages.
What sucks
- Missing or thin metadata.
- No share image or a broken image URL.
- Redirects, cache lag, and platform-specific crawler quirks.
- Private pages or pages that Microlink cannot reach.
What this OG checker actually tests
What it can validate
This checker looks at the normalized metadata returned for a public URL: title, description, resolved page URL, and any share-image details the lookup exposes such as width, height, file type, and approximate file size.
What it cannot promise
It cannot prove every raw `og:*` or `twitter:*` tag, platform-specific cache behavior, crawler allowlisting, or whether Facebook and X will crop the card exactly the same way.
How to use the results
1. Start with the score
The score helps you spot obvious weaknesses quickly: missing title, thin description, insecure URLs, or a share image that is absent or poorly sized.
2. Review the card preview
The preview helps you judge clarity and click appeal. Even technically valid tags can still create a weak card if the title is vague or the image is unreadable at small sizes.
3. Fix and re-scrape
After updating your tags, re-run this checker and then refresh the URL in the platform debugger you care about, because social caches often lag behind your live HTML.
Checker vs validator vs preview
This checker
Fast metadata sanity check, normalized preview, score, and remediation hints for public URLs.
Platform debuggers
Best for forcing a re-scrape and validating what Facebook or LinkedIn specifically cached.
View source / crawler tests
Best when you need to inspect raw og:* and twitter:* tags, canonical tags, robots directives, or server responses.
Examples of pages worth testing
Homepage and product pages
These usually get shared the most, but they often inherit generic site-wide tags. Check that each page has a title and image specific enough to earn the click.
Blog posts and changelog entries
Content pages are where weak descriptions show up fast. If multiple posts share the same fallback description or image, social engagement usually suffers.
Campaign landing pages
Paid traffic and launches deserve a dedicated 1200 by 630 image and message match between ad copy, page title, and shared-card title.
Pages behind redirects
URLs that hop through tracking parameters, locale redirects, or HTTP-to-HTTPS rewrites are common sources of broken previews and canonical confusion.
Frequently asked questions
What is the difference between an Open Graph checker and an Open Graph preview tool?
A preview tool shows the card. A checker goes further by grading whether the key metadata is present, secure, and likely to render well. This page does both, but only for the normalized data returned by the lookup service.
Does this tool work for LinkedIn, Facebook, Slack, and X?
It is useful for all of them because they rely on similar share metadata. The preview is a practical approximation, not a promise of pixel-perfect rendering on every platform.
What title and description lengths should I aim for?
A practical starting point is about 30 to 70 characters for the title and about 70 to 160 characters for the description. Different platforms may still truncate based on layout and device width.
What image size is safest for OG previews?
A dedicated 1200 by 630 image is the common safe choice because it matches the large-card format many platforms prefer. Keep key text away from the edges in case of crops.
Why might the checker miss an issue that a real crawler finds?
Some issues happen lower in the stack: blocked bots, redirect chains, robots rules, cache staleness, unsupported content types, or tags that the lookup service normalizes away. Use this as a fast first pass, then confirm with crawler-specific tools if needed.