Structured Data Validator
Paste JSON-LD or point this at a URL. It parses every structured-data block, reports syntax errors with the exact character position, and checks each node's required and recommended fields against schema.org and Google's guidance for its type.
Structured data is how you turn prose into facts a search engine can use for rich results and AI answers. But a single trailing comma or an unescaped quote makes a whole JSON-LD block invalid, and search engines then ignore it entirely — usually without telling you.
This validator catches both failure modes: broken JSON, pinpointed to the character, and valid JSON that is missing the fields Google needs for a given type, such as an Article without a headline or a Product without an offer.
How markup is validated
Given pasted content, we accept either raw JSON-LD or a full HTML document, from which we extract every <script type="application/ld+json"> block. Given a URL, we fetch the page and do the same. Each block is parsed and, on a syntax error, we report the message and the character offset so you can jump straight to the problem.
For each valid node we read its @type and look it up in our schema guide, derived from schema.org and Google's structured-data documentation. We then check the required fields (without which the rich result will not show) and the recommended fields (which strengthen it), and list exactly what is missing per node.
The tool handles @graph and nested nodes, and reports the types it found so you can confirm the page is describing what you intended — an Article, an FAQPage, a Product, a LocalBusiness, and so on.
| Check | What it means and the exact threshold |
|---|---|
| JSON-LD syntax | Each block parses as valid JSON; errors are reported with character position. |
| Type detection | The @type of every node, including those inside an @graph, is identified. |
| Required fields | Fields Google requires for the type's rich result, flagged when missing. |
| Recommended fields | Fields that strengthen the result but are not strictly required. |
| Block extraction | All JSON-LD script blocks are found in a full HTML document or pasted markup. |
Limits and honest caveats
- This is not a substitute for Google's Rich Results Test, which is the authoritative check for rich-result eligibility.
- We validate JSON-LD; Microdata and RDFa are not parsed.
- Field guidance covers common types; very niche or custom types may not have a rich-result mapping.
- Valid markup makes a page eligible for a rich result but does not guarantee Google shows one.
Frequently asked questions
- Is this the same as Google's Rich Results Test?
- No, and it is not a substitute. This tool catches syntax errors and missing fields quickly during authoring; Google's Rich Results Test is the authoritative check for whether a specific rich result is eligible.
- Why is my valid JSON still flagged?
- The JSON parses, but the node is missing a field Google requires for that type — for example, an Article without a headline or a Product without an offer. Add the listed fields to become eligible.
- Which schema type should I use?
- Match the page: Article or BlogPosting for posts, FAQPage for Q&A, Product with Offer for shop pages, LocalBusiness for a location, plus a site-wide Organization. Our GEO audit rewards valid JSON-LD.
- Can I validate markup before it's live?
- Yes. Paste the JSON-LD or the full HTML to validate offline, then re-check by URL once it is deployed to confirm it renders in the page.
- Does structured data help with AI answers?
- It helps. Valid, specific JSON-LD makes your facts unambiguous, which is why answer engines and our GEO audit both reward it. It is a core GEO signal.
Stop checking by hand. Put SEO on autopilot.
Autoranko researches keywords, writes expert articles in your language, publishes them, and tracks whether AI assistants cite you — on a free plan to start.
In the glossary
Related tools
GEO Readiness Audit
Score how ready a page is to be found, read and quoted by AI answer engines.
Open toolMeta Tags Checker
Inspect title, description, canonical, Open Graph and Twitter tags on any page.
Open toolSERP Snippet Preview
Preview your Google result in pixels and see where the title and description get cut.
Open tool