Structured Data Checker
Check your page's JSON-LD structured data and Google rich result eligibility.
Sees what Google sees. This tool fetches your page's raw HTML, just like Googlebot's first crawl pass. JSON-LD that only exists after JavaScript renders won't show up here, and it may not show up for search engines either.
Why raw HTML matters for structured data
This tool fetches your page the same way Googlebot does on its first crawl pass: a single HTTP request that reads the raw HTML. No JavaScript is executed. That's intentional, because Google's structured data processing happens in two stages, and the first stage only sees the HTML source.
If your JSON-LD is injected by JavaScript after page load (common in React, Vue, and Angular SPAs without server-side rendering), it won't appear in these results. That's a real problem: Google may eventually render the page and find the schema, but there's no guarantee, and the delay can mean your rich results take days or weeks to appear instead of hours. If your structured data shows up here, it's in the HTML source and will be picked up immediately.
What structured data does for your pages
Structured data is machine-readable markup that tells search engines what your content is, not just what it says. When you add JSON-LD to a page, you're giving Google explicit signals about whether this is an article, a product, a recipe, an event, or a FAQ. Without it, Google has to guess.
The payoff is rich results. Pages with eligible structured data can appear with star ratings, FAQ dropdowns, recipe cards, event dates, and other enhanced formats in search results. These take up more visual space and consistently outperform plain blue links on click-through rate.
Schema types this tool detects
This checker extracts every JSON-LD block from your page, parses the schema.org types, and maps them to Google's rich result eligibility. Here are the types that can trigger enhanced search features:
| Schema Type | Rich Result |
|---|---|
| Article / NewsArticle / BlogPosting | Article rich result (headline, image, date) |
| FAQPage | FAQ dropdown directly in search results |
| HowTo | Step-by-step how-to display |
| Product | Product snippet with price and availability |
| BreadcrumbList | Breadcrumb trail in search results |
| VideoObject | Video thumbnail and duration |
| Recipe | Recipe card with ratings and cook time |
| Event | Event listing with dates and venue |
| Organization / Person | Knowledge panel eligibility |
JSON-LD vs Microdata vs RDFa
There are three ways to add structured data to a page. JSON-LD is a script block in your page head or body. Microdata is HTML attributes woven into your existing markup. RDFa is similar to Microdata but uses a different attribute set. Google recommends JSON-LD, and it's what this tool checks for.
The advantage of JSON-LD is separation: your structured data lives in a self-contained script tag, independent of your HTML structure. You can add, modify, or remove it without touching your templates. It's also easier to debug because the entire data object is visible in one place.
Frequently asked questions
Does structured data directly improve rankings?
Not directly. Structured data doesn't change your position in search results. But it can trigger rich results, which increase your click-through rate. A higher CTR on the same ranking position means more traffic from the same search visibility. Over time, strong engagement signals can indirectly support rankings.
What happens if my JSON-LD has errors?
Invalid JSON will be silently ignored by search engines. Missing required fields mean your page won't be eligible for the corresponding rich result, but it won't hurt your rankings. This tool flags both invalid JSON and missing recommended fields so you can fix them before Google has to deal with them.
Why doesn't my structured data show up in this tool?
This tool only detects JSON-LD (script tags with type application/ld+json). If your structured data uses Microdata or RDFa (HTML attributes), it won't appear here. Also, if your JSON-LD is injected by JavaScript after page load, the server-side fetch won't see it. Both are worth knowing about: if this tool can't find your schema, Googlebot's first crawl pass might miss it too.
Which pages should have structured data?
Start with pages that match a supported schema type and get meaningful search traffic. Blog posts benefit from Article schema. Product pages need Product schema. FAQ sections should use FAQPage. Every site should have Organization schema on the homepage and BreadcrumbList on content pages. Don't add schema types that don't match your content just to game the system. Google ignores mismatched markup and may issue manual actions for spam.