Schema Markup & JSON-LD Validator
Is your structured data good enough to earn a rich result, or is one broken block wasting it? This free JSON-LD validator checks the schema markup on any page in seconds and separates what is missing, what is merely nice to have, and what is simply broken.
This checked one URL, once.
VitalSentinel Inspector audits the whole page in one pass: this check plus every other technical SEO and performance issue on it, scored and ordered by what to fix first.
Free plan, no credit cardWhat it checks
- Checks every JSON-LD block separately, including entities nested inside one another or inside an @graph
- Points at the line and column a broken block fails on, and names the usual causes: a trailing comma, curly quotes, HTML entities
- Separates what Google requires from what it merely recommends, taken from Google's own tables for each type
- Flags values nothing can use: image URLs that are not absolute, dates that are not in ISO format, prices carrying a currency symbol
What it does not
- It reads the HTML your server sends. JSON-LD added by JavaScript is invisible to this check
- Property checks cover eight types: Article, Product, FAQPage, Recipe, Event, BreadcrumbList, LocalBusiness and Organization. Anything else is read and listed, not graded
- It does not grade microdata or RDFa. Both are reported when present, but only JSON-LD is graded
- It cannot tell whether your values are true, or whether they match what visitors see on the page, which is the most common reason valid markup earns no rich result
Questions
- My page has structured data, so why does the validator find none?
- This reads the HTML your server sends, before any JavaScript runs. JSON-LD written by a tag manager or by your front-end framework is not in there yet. Google renders pages and usually finds it, on its own schedule.
- Does valid markup guarantee a rich result?
- No. Having the documented properties is the entry ticket, not the prize. Google also weighs site quality, the query, whether the markup matches the visible page, and any manual actions.
- What is the difference between a required and a recommended property?
- A required property decides eligibility: without it, Google will not show that appearance at all. A recommended one only gives the result more to display. This tool keeps them apart, and takes both lists from Google's own tables for each type, so you are never sent chasing something that costs you nothing. Two of the eight types checked here, Article and Organization, have no required properties at all.
- Is this the same as Google's Rich Results Test?
- No, and they answer different questions. The Rich Results Test renders the page first, so it also sees JSON-LD written by JavaScript, and it tells you what Google considers eligible. This one reads the HTML your server sends, checks every block on its own so a single broken block does not hide the rest, and shows the exact line and column it breaks on. Use both.
More free tools
Fair use, and how to recognize us
5 per minute · 25 per hour · 100 per day per IP (per /64 for IPv6), plus a per-site limit
Every request these tools make sends this user agent, including the ones that load a page in a real browser. What a run records is set out in our privacy policy.
Mozilla/5.0 (compatible; VitalSentinel Free Tools Bot/1.0; +https://www.vitalsentinel.com/bot)
Stop checking by hand
Uptime, Core Web Vitals, indexing and robots.txt, monitored continuously. Start on the free plan and add your first domain in under a minute.