Structured data testing tool
Read JSON-LD from a public page or paste it here. We check the schema type, field values, and JSON structure, then point to each problem.
Structured data result
Choose a public page or paste JSON-LD to see types, fields, errors, warnings, and evidence.
This is an independent Schema.org structure checker. It is not an official Google tool and it does not guarantee rich results or rankings.
What this structured data tester checks
JSON-LD extraction
Finds JSON-LD blocks from a public HTML response or parses the code you paste, then returns copyable valid JSON for one or multiple blocks.
Vocabulary and shape
Confirms JSON structure, Schema.org context and types, arrays and objects, and sensible non-empty field values without inventing universal required fields.
Problems by field
Shows the path, value found, severity, and suggested fix. Syntax errors stay separate from optional profile suggestions.
Fix the field that failed
Read the field
Start with the parsed type and error list. Open the evidence for the exact field or path rather than changing every property at once.
Correct the markup
Correct invalid JSON or context values first. Then resolve type and field warnings only when the field describes the visible page and its vocabulary.
Run it again
Retest the same URL or pasted block and copy the normalized JSON if you need to hand the exact payload to an engineer.
Where Schema checks stop
- This is an independent Schema.org structure checker, not Google's official Rich Results Test.
- A structurally valid graph does not guarantee rich-result eligibility, indexing, ranking, or AI citation.
- Profile suggestions come from this checker's rules. Schema.org does not make every suggested field universally required.
Structured data questions
Does a missing URL always make Organization invalid?
No. The tool treats profile suggestions such as URL as warnings unless the JSON or vocabulary structure itself is invalid.
Why is false not accepted as a field value?
Boolean false is a value in JSON, but it is not a usable value for fields that need a non-empty name, URL, person, or other structured object.
Does this test Google's rich results?
No. It explicitly separates Schema.org parsing and field checks from Google's changing feature-specific eligibility rules.
Related checks and guides
Robots.txt checker
Confirm the crawler and path can reach the page before interpreting its markup.
Check robots.txtGenerative engine optimization
Place structured data in a broader page and information architecture workflow.
Read the guideFull page audit
Review the surrounding content, access, and publisher details in one public URL.
Check a URL