JSON-LD markup inspection
Structured Data / Schema Validator
Extract JSON-LD blocks, validate JSON syntax, inspect schema types, and flag missing recommended properties for common rich-result markup.
Tool guide
What is the Structured Data / Schema Validator?
The Structured Data / Schema Validator extracts JSON-LD blocks from a page or pasted HTML, checks JSON syntax, lists schema types, and flags missing recommended properties for several common markup patterns. Structured data helps machines understand entities and page content in a standardized format.
Valid JSON-LD does not guarantee a rich result. Search engines apply content policies, page-quality requirements, supported-feature rules, and their own eligibility decisions. The tool is useful for finding implementation errors before using official rich-result testing and search-console reports.
Audit coverage
What this SEO tool checks
JSON parsing and valid script blocks
Schema.org @context and @type values
Common required or recommended properties
Multiple entities and nested objects
Basic consistency between the markup and page purpose
Step-by-step
How to use the Structured Data / Schema Validator
- 1Enter a URL or paste HTML
Use pasted source for unpublished templates or generated markup.
- 2Run schema extraction
The tool finds application/ld+json scripts and parses each block.
- 3Review entity findings
Fix invalid JSON first, then missing properties and content mismatches.
- 4Validate in official tools
Test supported rich-result types and monitor enhancement reports after publishing.
Interpretation
How to understand the results
- A parse error means the JSON-LD block is not valid JSON and may be ignored.
- A missing property warning means the entity may be incomplete for its type or for a search feature.
- A valid schema block can still be ineligible if the visible page does not support the claims.
Practical advice
SEO best practices
- Mark up information that is visible and accurate on the page.
- Use specific schema types when they truthfully represent the content.
- Keep IDs and entity relationships consistent across related pages.
- Avoid fake reviews, invented ratings, misleading dates, or markup for content users cannot see.
- Retest after template changes because one syntax error can affect many pages.
Before you act
Limitations of this automated check
This validator provides rule-based checks and does not implement every Schema.org type or every search-engine feature. It cannot confirm rich-result eligibility, policy compliance, or the truthfulness of the data. Microdata and RDFa may require separate validation if they are not represented in JSON-LD.
Deeper explanation
Understand the decision behind the check
Use the practical guide below when you need context, common mistakes and a verification workflow instead of only a pass/fail result.
Common questions
Structured Data / Schema Validator FAQs
Does valid schema guarantee a rich snippet?
No. Valid markup is only one requirement. Search engines consider supported types, policies, page quality, and query context.
Should schema content be visible on the page?
Yes. Markup should represent content users can access and should not make hidden or misleading claims.
Can I use several JSON-LD blocks?
Yes. Multiple blocks are common, but their entities and identifiers should remain consistent.
Which format is recommended?
JSON-LD is widely used because it is easier to maintain separately from visible HTML, though other valid formats exist.
Continue your audit