Free Structured Data / Schema Validator
One of the free tools from KinetixSEO, an SEO and AI-citation (GEO) checker. Check any page's JSON-LD, microdata and RDFa structured data for completeness, deprecated schema types, and common markup mistakes — the same check that runs inside KinetixSEO's full SEO/GEO audit, exposed here as a standalone tool. If you're looking to generate new schema instead of validating what's already there, use the JSON-LD Schema Generator.
What you'll get
Results for
https://example.com/guides/running-shoes-flat-feet
- JSON-LD blocks found
- 3
- Valid
- 2
- Invalid
- 1
Types found: WebPage, BreadcrumbList, HowTo
Schema completeness
- WebPageComplete
- BreadcrumbListComplete
- HowToMissing fields
Missing: step
Issues found
Deprecated schema types (no longer eligible for rich results)
- HowTo: removed from Google rich results as of 2023
Dangling @id references
- Unresolved reference: #breadcrumb-3
What the Free Structured Data / Schema Validator checks
- Every JSON-LD block on the page parses as valid JSON — malformed syntax is flagged with the parse error
- Each block declares a recognized schema.org @type and required @context
- Required properties for the detected type are present (e.g. Article needs headline/author/datePublished, Product needs name/offers)
- BreadcrumbList items are sequentially numbered and each has a name and item URL
- FAQPage mainEntity questions each have a matching acceptedAnswer
- Deprecated or unsupported types (like HowTo, removed from Google rich results) are flagged
- Duplicate or conflicting @id references across blocks on the same page
- Schema values are checked against visible page content where feasible, so markup can't silently contradict what a reader actually sees
Frequently asked questions
Why is one of my JSON-LD blocks flagged as invalid?
This tool parses every JSON-LD block on the page as JSON first — a block flagged invalid failed that basic parse, usually from a trailing comma, an unescaped quote inside a string value, or a mismatched brace, all common when JSON-LD is hand-edited or assembled by string concatenation in a template rather than generated from a proper data structure. A parse failure means the entire block is silently ignored by every crawler that reads it, search engines and AI systems alike — it's not partially read, it's discarded whole.
What does "deprecated schema type" mean, and why does it still show up in results?
A deprecated type is one Google has explicitly removed from eligibility for rich results in search — HowTo and FAQPage markup lost most of their rich-result eligibility in 2023, for example. This tool flags them separately from types that are simply unsupported, because a deprecated type isn't necessarily worthless: it may still be perfectly valid schema.org markup that AI answer engines read and use for citation context, even though it no longer earns a rich snippet in classic Google search. The two audiences (search rich results vs. AI citation) don't always agree on what's useful.
What are "dangling @id references" and why do they matter?
JSON-LD lets one schema block reference another by @id instead of repeating the full object — a Product block's review property, for example, can point at a Review block elsewhere on the page by its @id rather than nesting it inline. A dangling reference means the @id being pointed to doesn't actually exist anywhere in the page's structured data, which leaves that relationship broken from a parser's perspective — the reviewer can't resolve what's actually being reviewed. This is usually a copy-paste artifact from reusing a JSON-LD template without updating every @id consistently.
Does this tool check whether my schema markup matches what a reader actually sees on the page?
Where feasible, yes — this tool cross-checks schema property values against visible page content, so markup can't silently claim something the page doesn't actually show (a Product schema declaring a price the visible page never mentions, for example). This matters because search engines have explicit spam policies against structured data that misrepresents page content, and mismatched schema can trigger a manual action independent of how technically well-formed the JSON-LD itself is. This check isn't exhaustive for every property on every type, but it covers the common, high-risk mismatches.
My page has zero structured data — is that automatically a problem?
Not automatically — structured data is not a hard requirement for a page to rank, and plenty of well-ranking pages carry none. What it costs you is eligibility: no schema markup means no eligibility for rich results in search (breadcrumb trails, review stars, and similar), and it means AI answer engines have to infer your page's structure and identity from raw HTML instead of reading an explicit, unambiguous declaration of what the page is. Whether that gap is worth closing depends on the page — a high-traffic commercial or reference page benefits more than a low-priority blog post.
Related reading
Go deeper
This free check looks at one signal in isolation. KinetixSEO's paid report combines every signal below into one prioritised fix list and tracks it over time.
See the full paid report for this →This is one check from KinetixSEO's full SEO/GEO audit. Want the complete picture — Core Web Vitals, AI-citation readiness, technical SEO health, and tailored fixes? Run the free full checker.