Testing and validating structured data
By Abhijay Tondak, Founder · Updated July 1, 2026 · 5 min read
Testing and validating structured data means checking your schema for syntax errors, required-property gaps, and mismatches with the visible page - because invalid markup simply won't be used, and mismatched markup can be ignored or penalized. Use structured-data validation tools to confirm the JSON-LD parses and meets each type's requirements, then verify manually that every value matches what's actually on the page before shipping.
Key takeaways
- Invalid schema won't be used - validation is not optional.
- Use structured-data testing/validation tools to catch syntax and required-property errors.
- Beyond validity, verify every value matches the visible page - mismatches get ignored or penalized.
- Check required vs. recommended properties for each type.
- Re-test after content or template changes, which silently break markup.
Why validation is mandatory
Structured data only helps if engines can parse and trust it. A single syntax error, a missing required property, or a wrong type can make the whole block unusable - and you'd never know without testing, because there's no visible error on the page. Validation is the difference between schema that works and schema that's silently ignored.
What to check
Validation has two layers - technical validity and honesty:
- Syntax: the JSON-LD parses without errors.
- Required properties: each type's mandatory fields are present and correctly typed.
- Recommended properties: the fields that make the markup more useful are included.
- Page match: every value corresponds to something actually visible on the page.
The mismatch trap
A block can be technically valid and still fail, because the values don't match the visible page - a price, rating, or date in the markup that isn't shown to users. Validators catch syntax and structure, but you must manually verify honesty: the markup and the page must tell the same story. Mismatches are a top reason valid-looking schema gets ignored or penalized.
Re-test after changes
Structured data breaks silently when templates, CMS fields, or content change - a redesign drops a property, a migration alters values, a plugin update changes output. Re-test after any change that could affect markup, and spot-check periodically. Treat structured-data validation as an ongoing check, not a one-time setup, so your schema keeps working as the site evolves.
Frequently asked questions
How do I validate structured data?
Use a structured-data testing/validation tool to confirm the JSON-LD parses and meets each type's required properties, then manually verify every value matches the visible page. Both layers matter - technical validity and page-match honesty.
Why isn't my valid schema working?
Often a mismatch - the markup is technically valid but its values (price, rating, date) don't match what's shown on the page. Validators catch syntax and structure; you must manually confirm the markup and page tell the same story.
How often should I re-test structured data?
After any change that could affect markup - redesigns, migrations, CMS/plugin updates - since schema breaks silently. Spot-check periodically too; treat validation as ongoing, not one-time.
What happens if my schema is invalid?
It simply won't be used - engines can't parse it, and there's no visible error on the page to warn you. That's why validation is mandatory before shipping any structured data.
Put this into practice — free.
Get your free AI-visibility audit and see where engines find you today.
More from this topic
Keep building your expertise with related GEO content in the same cluster.
Structured data (JSON-LD) for AI search
Structured data helps AI engines understand and cite your pages. Here are the JSON-LD schema types that matter for AI search and how to implement them.
ReadHow to write a TL;DR that gets cited
A citable TL;DR answers the page's core question in 1-3 self-contained sentences at the top. Here's how to write one AI answer engines will lift verbatim.
ReadWhy original data and statistics win AI citations
Original statistics and data give AI answer engines something concrete and attributable to cite. Here's why proprietary data outperforms recycled claims in GEO.
Read