JSON-LD schema audit lab
Extract JSON-LD from a URL or pasted markup, parse every block, inspect graph nodes and nested types, review property coverage for common schema patterns, and keep a readable report before structured data reaches production templates.
URL extraction checks JSON-LD script blocks. Paste mode is useful for drafts, plugin output, isolated schema snippets and pages that block browser fetches.
Valid JSON is only the first schema check
A JSON-LD block can parse perfectly and still be weak structured data. The page may use the wrong type, omit the property that explains the entity, mark up content visitors cannot see, or ship a graph where identifiers and nested objects are hard to maintain. That is why a useful schema markup validator should show syntax, graph shape and practical content coverage together.
This tool reads JSON-LD from public HTML or from pasted markup. It lists each block, walks arrays and @graph nodes, records nested @type values, and reviews common schema families such as Article, FAQPage, BreadcrumbList, Product, SoftwareApplication, Organization, WebSite and WebPage. The checks are deliberately readable. They are a review aid, not a replacement for Google feature documentation or the Schema.org vocabulary.
What to review before publishing structured data
- Syntax: every JSON-LD block should parse without hidden copy-paste damage.
- Type fit: the schema type should describe the real visible page and entity.
- Coverage: important fields such as headline, itemListElement, acceptedAnswer or publisher should not vanish from a template.
- Graph shape:
@idreferences and nested nodes should stay understandable when reused site-wide. - Policy fit: markup should not promise content or reviews the visitor cannot actually find.
A practical schema workflow
- Extract the live URL after WordPress, SEO plugin or theme changes.
- Open the graph node table and confirm the main page entities are present.
- Read the property coverage tab for the page type you care about.
- Paste a draft snippet when you want to test markup before it reaches the template.
- Run the official rich-result or Schema.org tools when eligibility and vocabulary validation matter.
Common questions
Does valid schema guarantee a rich result?
No. Structured data can make a page eligible for features when the markup and content meet current requirements, but display still depends on search systems and feature-specific rules.
Why does this tool focus on JSON-LD?
JSON-LD is common in modern CMS and SEO plugin output, and it is easy to inspect without mixing annotations into visible HTML. Microdata and RDFa still exist, but they are outside this JSON-LD-focused audit.
Should every page use as many schema types as possible?
No. A smaller graph that accurately describes the page is easier to maintain than a crowded graph assembled only to chase features.
