Structured Data (Schema) Extractor
Pulls every JSON-LD block out of the page, catches syntax errors, and shows which schema types you use and whether the fields a rich result needs are filled in.
- Sign-in requiredMembership is free
- Open on the Pro plan100 runs a day
- Saved to your historyReachable from your account
What does this tool look at?
Everything that decides whether Google can crawl and index your page: tags, redirects, robots, sitemaps and server responses.
- Every JSON-LD block parsed, syntax errors caught
- List of the @type values found
- Required-field check for the common types
- Microdata and RDFa usage reported too
What this tool measures
Structured data is your page's information written a second time, in a form a machine can read. The line that says “Ahmet Yılmaz, 12 March 2026” on screen becomes the “author” and “datePublished” fields inside JSON-LD. A search engine reads instead of guessing, and star ratings, FAQ dropdowns and recipe cards all come out of that reading.
The tool extracts every <script type="application/ld+json"> block on the page, parses them one by one, and collects the @type values inside, including nested objects. If a block is malformed JSON it reports the error, and a malformed block is thrown away whole by a search engine.
Then it runs a required-field check on the common types: headline, datePublished and author for Article; name, image and offers for Product; name, address and telephone for LocalBusiness. A missing field cancels your claim to a rich result.
How to use it
- 1
Enter the address of a page you added markup to
An article, a product page or a page with an FAQ block gives you the most to look at.
- 2
Check the block count and the syntax line
If “valid JSON” is red, nothing else matters yet. Fix the syntax first.
- 3
Review the types found
If the type you expected is not listed, the markup was never printed to the page or it comes from a different template.
- 4
Close the required-field warnings
After filling the missing fields, confirm the output once more in Google's Rich Results Test.
When to use it
- After adding schema through a plugin, to see whether it actually reaches the page.
- To find which field is missing on a page that errors in the rich results report.
- To see which schema types a competitor uses on their page.
- After a site migration, to confirm the markup carried over to the new template.
Reading the result
No JSON-LD block at all
The page is not a candidate for any rich result. Start with the schema that matches the page: Article for a post, Service for a service page.
A block could not be parsed
Usually a quote character or a trailing comma. A malformed block is discarded along with everything inside it.
A required field is missing
The markup is valid but too thin for a rich result. Google ignores an incomplete record rather than reporting an error.
Unexpected types
The theme and a plugin may both be printing Organization. If two records of the same type carry conflicting data, merge them.
Microdata or RDFa in use
It works, but Google prefers JSON-LD. Rather than mixing old markup into the HTML, move it into a single JSON-LD block.
Questions about the Structured Data (Schema) Extractor
It is not a ranking factor. What it does is make your result bigger: stars, price, availability, an FAQ dropdown. A result that takes up more room at the same position gets clicked more, and that is where the gain comes from.
JSON-LD. Google recommends it outright, and the reason is practical: JSON-LD lives in one block, keeps the HTML clean and survives a redesign. Microdata spreads through the HTML as attributes, so a theme update can quietly erase your markup.
Do not. Google's structured data policy requires the marked-up information to be visible to the visitor too. An invisible star rating or an invented price can lead to a manual action removing your rich results.
It can, and usually should. A typical blog post carries Article, BreadcrumbList and Organization together. What matters is that they all tell the same story; two conflicting records of the same type cause trouble.
Use it alongside these
The other tools in the same category. Run them together and you see the whole picture.
The tool found the problem. Now for the fix
We run technical SEO, content and AI visibility work end to end. Let us review your site and come back with a clear list of what to do.
Monday – Saturday 09:00 – 18:00