Free tool
Schema markup validator
Paste a JSON-LD block. The checker parses it, walks any graph, reports the types it finds, and flags missing required properties for the common types. It runs in your browser and keeps nothing.
Findings
Results appear here. The checker reads structure and required properties. It does not guarantee a rich result, because eligibility also depends on content quality and on what the page actually renders.
What does a schema validator actually tell you?
It tells you whether your markup parses, which types are declared, and whether the properties those types require are present. It cannot tell you whether a search engine will show a rich result, because that also depends on content quality and policy.
- Valid markup that contradicts the visible page is a liability, not a win.
- One connected graph with @id references beats several unrelated blocks.
- Structured data helps machines confirm what the page says. It does not replace saying it.
Scope
What this checker does not do
It does not fetch your page, so it cannot compare markup to rendered content. It does not know which rich results you qualify for. It checks a short list of common types against the properties we consider mandatory in production, which is stricter than the bare minimum in some places and lighter in others.
Use it as a fast structural pass while you write. Then confirm against the official testing tools before you ship, and confirm again after deploy, because a build step that strips or escapes a script tag will break markup that validated fine locally.
Related
Go deeper
Want structured data generated, not maintained by hand
We build schema from a typed component library so every page emits a consistent graph.