Free Open Graph Checker & Twitter Card Validator
Share cards fail quietly. A duplicate title, missing tag, or broken image can leave your link preview blank.
Open Graph and Twitter Card tags sit in your page’s <head>, so they remain invisible on the rendered page.
A template or plugin change can break tags across every page using that setup, and the only clue may be an incorrect card turning up in Slack or on social feeds.
Paste a URL into the tool above to inspect its current tags and previews. For ongoing checks, use Sprout SEO while browsing each page.
A useful check starts with knowing which tags each platform expects.
What are Open Graph and Twitter Cards?
Open Graph defines the title, description, image, and address shown when someone shares a URL. Facebook and LinkedIn read these tags.
<meta property="og:title" content="How we fixed hreflang" />
<meta property="og:description" content="One missing return link sent Google to the wrong market." />
<meta property="og:image" content="https://example.com/og/hreflang.png" />
<meta property="og:url" content="https://example.com/blog/hreflang/" />
Twitter Cards are a separate set of tags used by X. Despite the platform’s name change, the markup still uses the twitter: prefix.
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="How we fixed hreflang" />
<meta name="twitter:description" content="One missing return link sent Google to the wrong market." />
<meta name="twitter:image" content="https://example.com/og/hreflang.png" />
X needs twitter:card before it can build a card. Open Graph tags alone are not enough.
The OG fallback rule
Once twitter:card is present, an empty Twitter field can use the matching Open Graph value.
- Missing
twitter:titlecan useog:title. - Missing
twitter:descriptioncan useog:description. - Missing
twitter:imagecan useog:image. twitter:sitehas no Open Graph fallback.
Facebook’s sharing documentation for webmasters explains its requirements. X provides a separate Cards overview.
This checker offers a practical reading of your tags, but it is not an official debugger for either platform.
Those tags shape presentation and clicks, even though their SEO role is indirect.
Why Open Graph tags matter for SEO (and where they don’t)
Open Graph and Twitter Card tags do not directly improve Google rankings, so treat them as presentation metadata rather than a ranking shortcut.
Their value shows up the moment someone shares your page, when a complete card makes the link easier to assess, with more clarity and credibility.
A broken card interrupts that path, costing the page clicks, shares, links, and brand mentions it could otherwise earn.
Audit social previews as carefully as search snippets. Both shape how people respond after discovering a URL, and that response still depends on what Facebook, LinkedIn, and X can actually read.
What Facebook, LinkedIn, and X actually read
| Platform | Fields needed for a complete result | Notes |
|---|---|---|
| Facebook and LinkedIn | og:title, og:description, og:image, og:url |
og:type is collected but not required for a Complete result. |
| X large image card | twitter:card, title, description, and image |
Twitter fields can use eligible Open Graph fallbacks. |
| X summary card | twitter:card, title, and description |
An image is optional for a Complete result. |
X without twitter:card |
None | The result is No card, even when Open Graph tags exist. |
Watch for four details when interpreting the result:
- Image shape: Facebook points toward a roughly 1.91:1 image for a large link preview. A common implementation is 1200×630.
- Measured dimensions: A smaller image can still produce a Complete result with a warning. The checker measures the file itself rather than trusting the declared
og:image:widthorog:image:heightvalues alone. - Conflicting tags: Repeating the same
og:titleis redundant. Two different title values create uncertainty. - URL mismatches: The checked URL and
og:urlshould match in scheme, host, path, and query.
Differences involving www, trailing slashes, or query strings can trigger a conflict. These small mismatches make an otherwise invisible error easy to diagnose.
Common Open Graph and Twitter Card issues
Broken previews tend to come from missing tags, conflicting values, inaccessible images, or crawler-invisible markup.
The issues, one by one
- Missing core tags: The template omits
og:title,og:description,og:image, orog:url. - Conflicting tags: A theme and plugin output different values for the same property.
- Broken images: The image path is relative, blocked, login-protected, or returns an error.
- Missing
twitter:card: Facebook works, but X has no instruction to build a card. - JavaScript-only tags: The browser renders the tags after load, but the crawler receives none.
Fix missing fields in the template that renders the page, rather than relying on a plugin default.
For duplicate tags, choose one source and remove the other. Platforms may otherwise select an unintended value.
Serve social tags in the server-rendered <head> so crawlers can access them without running client-side JavaScript.
Common Open Graph issues at a glance
| Issue | Result | Fix |
|---|---|---|
| Missing core Open Graph tag | Partial | Output all four core tags |
| Conflicting values | Duplicate or conflicting | Keep one value per property |
| Broken or relative image URL | Broken image | Use an absolute, public image URL |
No twitter:card |
No card on X | Add summary or summary_large_image |
| Client-rendered tags only | Tags appear missing | Include them in server HTML |
A checker turns those hidden states into a concrete repair list.
How to check your Open Graph and Twitter Card tags
Check one URL in four steps:
- Paste the full URL into the tool above.
- Choose the crawler. Facebook Crawler is the practical default.
- Review both previews and each tag’s status.
- Fix the template, deploy the change, and check the same URL again.
Choose another crawler if you suspect the server returns different HTML to Twitterbot, LinkedInBot, or Slack’s preview bot.
Check a single page with the Sprout web tool
Paste a URL into the tool at the top of this page. It fetches the server HTML as your selected crawler and reads the page’s <head>.
Open Graph and Twitter Card results are classified separately:
- Complete
- Partial
- Duplicate or conflicting
- Broken image
- No card
You also get rendered previews for Facebook or LinkedIn and X. No account or crawl is required.
The result reflects the HTML returned to the selected crawler. Tags injected with JavaScript may not appear in that response.
See the preview as you browse with the Sprout extension
The browser extension keeps social tag checks beside the page, removing the need to copy every URL into a separate tool.
Use the Sprout SEO extension guide to install it and open the Social tab. It reads the live DOM, including tags added after page load.
Sprout’s free SEO tools also cover canonical tags, hreflang, status codes, and broken links.
Once the checker identifies the failure, the repair should happen at its source.
How to fix a broken or missing social preview tag
Fix the source of the tag, deploy the change, and check the page again. Avoid patching one URL if the same template affects an entire content type.
1. Add the missing core tags
Output og:title, og:description, og:image, and og:url from the page template.
Populate each field with the value intended for that page, rather than leaving the same site-wide title or image on every URL.
2. Remove the duplicate source
Check whether the theme, page builder, and SEO plugin each output social tags.
Choose one system to control the metadata. Remove the duplicate call from the other source instead of hiding it with JavaScript.
3. Fix the image, then add twitter:card
Use an absolute image URL that loads without a login. The file should return an image such as JPEG, PNG, WebP, or GIF.
Add twitter:card after the image works. Use summary_large_image for a wide image or summary for a compact card.
Clear fields and a single source make it easier to distinguish social metadata from search metadata.
Open Graph vs. title tag vs. meta description
Search tags and social tags have separate jobs. One complete set does not replace the other.
| Signal | Primary reader | Typical use |
|---|---|---|
<title> and meta description |
Search engines and browsers | Search result and browser tab |
| Open Graph | Facebook, LinkedIn, and compatible apps | Shared title, description, image, and URL |
| Twitter Card tags | X | Card type and X-specific fields |
og:url |
Social platforms | URL associated with the share |
Write the search snippet for search results and the share card for the context in which people will post the page.
A strong <title> does not create an og:image. A complete Open Graph set does not create an X card without twitter:card.
Use the free Canonical Tag Checker when og:url and the canonical tag point to different URLs.
With those roles separated, tool comparisons become much clearer.
How this compares to other Open Graph tools
The key distinction is validation. A preview shows what might appear, while validation flags missing, conflicting, or broken inputs.
| Tool | Social preview coverage | Validation gap |
|---|---|---|
| Sprout web tool | Open Graph and Twitter Card previews | Checks one pasted URL |
| Sprout extension | Open Graph and Twitter Cards in the browser | Designed for page-by-page review |
| SEO Minion | Basic Open Graph | No Twitter Card validation |
| SEO Pro | Open Graph preview | No Twitter Card coverage |
| SEO META in 1 Click | Open Graph and Twitter previews | Does not flag missing, duplicate, or broken states |
| Detailed SEO Extension | No social preview feature | No Open Graph or Twitter Card review |
The SEO Minion comparison and the SEO Pro comparison both cover the same gap: a basic Open Graph preview shows a card exists, not whether X will build one.
The SEO META in 1 Click comparison separates preview support from active validation, and the Detailed SEO Extension comparison covers an extension with no social preview feature at all.
For one URL, use the web tool. For repeated reviews across a site, an in-browser check removes the paste-and-switch routine.
Check every page’s social tags as you browse (Chrome, Firefox, Edge)
Install Sprout SEO once, and each page’s social status stays one click away, with no separate paste-and-check step.
The Social tab, inline as you browse
Open the extension on the page you want to inspect. The tab reads the live DOM and reports the current social metadata.
The Social tab shows Complete, Partial, Duplicate, Broken image, and No card states. It updates as you browse.
The extension also supports canonical, hreflang, and broken link checks.
That puts the essential workflow into a short, repeatable process.
In short
Social previews break silently, but the fixes are concrete.
- Check the server HTML and preview for each platform.
- Fix missing core tags, conflicting values, and inaccessible images.
- Add
twitter:cardwhen X should build a card. - Recheck the URL after deployment.
- Use the extension to catch the same problems while browsing.
A few practical questions cover the remaining edge cases.
Check your social tags, then stop guessing on every share after this one
Broken social tags do not throw visible errors. They quietly weaken the link each time someone shares it.
Add Sprout SEO to Chrome to check Open Graph and Twitter Card tags on every page you browse. It is free and requires no crawl or account.
Sprout SEO also works in Firefox and Edge, so the check can follow your team’s browser workflow.