Structured-data markup linter
Check pasted JSON-LD for syntax and common field inconsistencies.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Parse JSON-LD-shaped JSON and report missing contexts/types, selected nonabsolute URL values and minimal LocalBusiness name/address issues without fetching contexts.
Read the source reference ↗A few things to know
A limited local linter, not a JSON-LD processor, Schema.org ontology validator or Google Rich Results Test. Valid JSON can still be semantically incorrect; duplicate JSON keys keep the last value.
When to use this tool
Separate JSON syntax from selected structured-data checks. This linter identifies common omissions while stating where semantic validation still needs another tool.
- Find missing types.
- Review a JSON-LD draft.
- Separate syntax and eligibility checks.
How to use structured-data markup linter
Prepare the inputs
Paste or upload the requested source or crawl-export columns.
Choose the settings
Run the local check; no remote website requests are made.
Review and export
Review flagged rows and confirm them against the actual site.
Try the supplied example
Inputs
json: {"@context":"https://schema.org","@type":"LocalBusiness","name":"Example Studio","address":{"@type":"PostalAddress","streetAddress":"123 Example Street","addressLocality":"Example City","addressCountry":"US"}}
Result
The example parses one LocalBusiness node with context, name and address.
What it means
A zero-finding result does not establish Schema.org correctness or rich-result eligibility.
Common mistakes to avoid
A limited linter is not semantic certification
A limited linter is not semantic certification.
Duplicate JSON keys can hide earlier values
Duplicate JSON keys can hide earlier values.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
Does this fetch @context?
No. All checks happen locally.
Is this a full JSON-LD processor?
No. It does not expand contexts or resolve vocabularies.
Can I paste an @graph?
Yes, or a top-level object or array of objects.
Which business fields are checked?
Minimal LocalBusiness name and address presence plus common context/type/URL shapes.
Are relative IDs always invalid?
No. They can be context-dependent; the tool asks you to review them rather than claiming invalidity.
Does valid JSON imply a rich result?
No. Use the relevant platform test and verify policy eligibility.
Are my inputs uploaded or stored?
Processing happens locally in your browser. This tool does not upload inputs. Downloads stay on your device; sharing or opening them in another service is your choice.
What should I check before using the output?
A limited local linter, not a JSON-LD processor, Schema.org ontology validator or Google Rich Results Test. Valid JSON can still be semantically incorrect; duplicate JSON keys keep the last value.
Explore the topic in the blog
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.