Schema Validator
Paste JSON-LD or fetch from any URL. Validates against Google's required fields, checks dates, URLs, and nested objects.
Generate Schema from Page Content
Analyze any URL and let AI generate the ideal JSON-LD structured data. Use Auto-detect to let AI pick the best type(s) — it will combine multiple schemas via @graph when appropriate (e.g. Article + FAQPage + BreadcrumbList).
Generate Schema for Multiple URLs
Paste up to 5 URLs and the AI generates the ideal JSON-LD for each page in one run.
How this JSON-LD validator works
Google's Rich Results Test tells you if your schema is valid. It doesn't tell you if it's good. Missing recommended fields, sloppy date formats, and broken author objects won't throw errors, but they'll cost you rich snippets. This schema validator validates against Google's actual documentation, beyond what the spec requires.
Paste JSON-LD or fetch it from any live URL (JS-heavy sites get headless rendering automatically). The tool covers 15 schema types and checks every required and recommended field. Hit "AI Fix" and it rewrites your schema with all issues resolved, ready to paste back into your page.
How does a schema validator work?
A validator parses your JSON-LD block and cross-references every field against the Schema.org definition for that type. If the type is "Article", it looks for a headline, an author, a datePublished, and an image. If any required field is missing or malformed, you get a flag. Good validators also warn about recommended fields that aren't required by the spec but are required by Google to earn a rich result.
Schema validator vs. Google Rich Results Test
When it comes to rich results, Google's Rich Results Test is the official tool. It tells you whether your schema qualifies for a specific rich result in search. It's the final check before you ship. A general schema validator (like this one) catches issues across all fields, not just the ones Google cares about for rich results. Use both: validator first to clean up, Rich Results Test last to confirm eligibility.
Common structured data errors
The same errors keep showing up. Dates in the wrong ISO format (2026/04/10 instead of 2026-04-10). Nested objects where the @type is missing and Google can't figure out what the field is. Price values as strings with currency symbols baked in ("$29.99") instead of separate "price" and "priceCurrency" fields. Image URLs that are relative instead of absolute, so Google's crawler can't fetch them. And the most common: using "Product" schema on category pages that don't have a single product.
Explore more tools
SERP Preview
Google snippet preview with pixel counter.
Meta Tag Analyzer
Analyze all SEO meta tags for any URL.
llms.txt Generator
Create AI crawler guides.
Heading Checker
Analyze H1-H6 heading hierarchy.
OG Preview
Preview social cards for Facebook and LinkedIn.
FAQ
The Lumina Chrome Extension runs FAQ cross-check, pixel-accurate meta validation, and full schema audits on every page you visit, automatically.
Add Lumina to Chrome — Free