Loading…
Paste your JSON-LD or test a live URL. Get instant errors for missing required properties, warnings for recommended ones, and plain-English explanations — mapped to Google's rich result requirements.
First, syntax: broken JSON is the most common structured data bug, and the validator reports the exact line and column of the first parse error. Second, structure: every entity needs an @context pointing at schema.org and an @type. Third, completeness: for ten common types (Product, Review, AggregateRating, Organization, LocalBusiness, FAQPage, Article, BreadcrumbList, SoftwareApplication, WebSite) it knows which properties Google requires and which it recommends, and flags each one that's missing.
It also sanity-checks values: ratingValue must be numeric and inside the declared rating range, review counts must be whole numbers, dates should be ISO 8601, and URL-ish properties should be absolute http(s) URLs. Documents with multiple entities — arrays or @graph structures — are validated entity by entity.
Structured data is unforgiving: one missing required property and Google silently drops the rich result. There is no error page, no ranking penalty to notice — your competitors simply show stars and FAQ dropdowns while you show a plain blue link. Because failure is invisible, teams routinely ship broken markup and never find out.
The highest-stakes case for SaaS is review markup. A Product or SoftwareApplication entity with a valid AggregateRating is what puts star ratings under your result. If maintaining that markup by hand feels fragile, TWR generates it automatically from verified user reviews on your public review page — that is the product behind this free tool. You can create markup from scratch with the schema generator and inspect complex documents in the visualizer.
<script> tag — the validator unwraps it. Click Validate.application/ld+json block, and validate each one separately.Errors are missing required properties or invalid values — they typically make the entity ineligible for rich results. Warnings are missing recommended properties: the markup still works, but adding them improves eligibility and how much information Google can show.
Google's official test renders the page with a real crawler and is the final word on eligibility. This validator is faster for iteration: it checks raw JSON-LD instantly in the browser, pinpoints JSON syntax errors with line numbers, and explains each missing property in plain language. Use both — this one while writing, Google's before shipping.
The URL tester fetches the server-rendered HTML. If your site injects JSON-LD with client-side JavaScript (some SPA setups do), it won't appear in the fetched markup — and Google may also struggle with it. Prefer rendering structured data into the initial HTML.
It has encoded rules for Product, Review, AggregateRating, Organization, LocalBusiness, FAQPage, Article, BreadcrumbList, SoftwareApplication, and WebSite — plus type checks for ratings, dates, counts, and URLs on any entity. Unknown types still get syntax, @context, and @type checks.
By default schema.org ratings run from 1 to 5. If your scale differs, declare bestRating and worstRating explicitly; otherwise Google assumes the 5-point scale and ignores values outside it.
TWR adds AggregateRating schema to your public review page automatically — free. Collect verified reviews inside your app and let us handle the structured data.