01 · Syntax
Can the JSON be read?
Look for broken quotes, missing separators and duplicate members. Start here before interpreting the entities in a block.
Look beneath the page
Understand the markup you already have.
See which entities a page declares, how they connect and where the JSON breaks. Start with a URL or paste JSON-LD for an immediate inspection in your browser.
Inspect your markup
Schema Viewer & Validator
Read the page, or bring the code.
URL mode inspects inline JSON-LD from the fetched HTML. Paste mode checks a JSON object or array in your browser. Use Load example if you want to explore the report first.
02 / Read the structure
Your schema report
Enter a URL or paste JSON-LD to inspect it.
Plain-text report
For broader checks, use the Schema.org validator or Google Rich Results Test. Your data is not sent to them automatically.
AI schema recommendations
Plain-text recommendations
Put it to work
Three questions. Three levels of checking.
Passing a syntax check is useful. It is only the first part of reviewing structured data.
02 · Structure
What does this code declare?
Review the listed types, IDs and graph nodes. These basic checks do not validate every Schema.org property or its expected value.
03 · Eligibility
Does it meet the relevant search requirements?
Use broader vocabulary validation and the relevant Google test. This inspector does not establish rich-result eligibility or guarantee a search appearance.
Illustrative example
One publisher. Connected references.
This deliberately small example connects a website to an organisation through a shared @id. It explains the relationship; it is not a complete implementation for your business.
Organisation
https://example.com/#organisationThe identity being referenced.
Website publisher
https://example.com/#organisationThe same ID connects the website to that organisation.
Inspect the example JSON-LD
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://example.com/#organisation",
"name": "Example Studio"
},
{
"@type": "WebSite",
"@id": "https://example.com/#website",
"url": "https://example.com/",
"publisher": {
"@id": "https://example.com/#organisation"
}
}
]
}Before adding another block, inspect what your theme and plugins already emit. Reusing a stable ID can help describe the same entity consistently.
Before you move on
Choose the next check that answers your question.
Fix syntax and inspect the graph
Review each block and its declared entities. Copy the report to keep the finding alongside your implementation notes.
Validate the vocabulary and relevant feature
Use Schema.org’s validator for broader markup checks and Google’s Rich Results Test for supported search features.
Treat AI advice as a separate review
When available, AI recommendations send a bounded public-page excerpt, metadata and existing JSON-LD to OpenAI on request. Review the evidence and suggestions; nothing is installed automatically.
Your questions
Know the scope of the inspection.
Does paste mode upload my JSON-LD?
No. The regular paste inspection runs in your browser. Paste one JSON object or array without script tags, up to 256 KiB. The optional AI page review is a separate action with its own disclosure.
Does “no blocks found” mean there is no structured data?
No. URL mode looks for inline JSON-LD in fetched HTML. It does not execute JavaScript or inspect Microdata and RDFa as structured-data graphs.
What does the validator actually validate?
JSON syntax and basic JSON-LD shapes, including literal @type, @id and @graph fields. It does not resolve remote contexts, validate the full Schema.org vocabulary or determine Google rich-result eligibility.
Not sure which system owns the markup?
Send us a page and the report. We can help trace overlapping theme and plugin output, identify inconsistencies and plan a cleaner implementation.
Send an enquiry