Browser tool
Validation & Markup Workbench
Paste or load JSON-LD, then check it against a local checklist of syntax rules, Schema.org basics and notes from Google's structured data documentation. Everything runs in your browser.
Markup workbench
A learning tool that runs in your browser. It is not Google's Rich Results Test or the Schema Markup Validator, and it cannot tell you whether Google will show a rich result. Nothing you paste leaves this page.
Example loaded. Edit it or paste your own JSON-LD, then check.
| Type | Google Search feature | What the checklist does |
|---|---|---|
| Organization | Logo and administrative details; no required properties | Asks for name, url and logo; notes sameAs; warns on self-serving ratings |
| WebSite | Site names (home page only). Sitelinks search box retired in November 2024 | Requires name and url; notes SearchAction is unused |
| Article | Article understanding; no required properties | Asks for headline, author, datePublished; notes time zones and images |
| BreadcrumbList | Breadcrumb trail, desktop results only | Requires two or more ListItems with position, name and item |
| FAQPage | No longer shown since May 7, 2026 | Adds a note; checks Question and Answer structure |
| Review, AggregateRating | Review snippets for supported item types; self-serving reviews excluded | Asks for author, rating and item; counts for aggregates |
| Person, ContactPoint | Used inside other markup, such as article authors and organization contacts | Asks for name and a link; a contact channel |
| SiteNavigationElement | No documented Google feature | Adds a note |
Sources: Google Search Central structured data documentation and the Search Central documentation updates log, both read on October 26, 2026. See Google structured data changes, 2023 to 2026.
| Type | Name | @id | Path |
|---|---|---|---|
| Organization | Verdant Crown Casino | https://verdantcrown.example/#org | (top level) |
| ContactPoint | contactPoint |
References by @id
- None in this markup.
Draw these links as a diagram in the entity map.
- Trailing comma or missing quote. JSON does not allow comments, trailing commas or single quotes. The checker reports the line and column.
- Wrong script type. JSON-LD must sit in
<script type="application/ld+json">. - Misspelled or British-spelled type.
Organisationis not a Schema.org type;Organizationis. - Relative or http URLs. Use the full https address the page or image is served from.
- Breadcrumb gaps. Missing position or item values break the trail.
- Self-serving ratings. Stars on a brand's own Organization markup are not eligible for Google review snippets.
- Markup that is not on the page. Google asks that structured data describe content readers can see.
More detail in structured data validation errors.
Sample: Organization (casino brand)
Checklist results (local, not Google)
0 errors, 0 warnings, 0 notes
- JSON parsesOne JSON-LD block read.
- No checklist problemsThis local checklist found no errors or warnings. Google may still show no rich result.
Detected entities
- Organization1
- WebSite0
- WebPage0
- Article0
- BreadcrumbList0
- FAQPage0
- Review0
- Person0
What the checklist does
- Parses JSON or a
<script type="application/ld+json">block and reports the line and column of the first syntax error. - Checks
@contextand@type, flags type names it does not recognize, and lists every typed entity and every@idreference. - Applies 43 rules for Organization, WebSite, WebPage, Article, BreadcrumbList, FAQPage, Review, AggregateRating, Person, ContactPoint and SiteNavigationElement, based on Google Search Central documentation read on October 26, 2026.
- Flags absolute URL problems, dates without time zones, self-serving ratings and markup for retired Google features.
What it does not do
- It does not fetch pages, contact Google or send your markup anywhere.
- It does not check every Schema.org type or property. Use the Schema Markup Validator for full vocabulary checks.
- It does not test Google feature eligibility. Use Google's Rich Results Test, ideally with the page URL.
- It cannot tell whether markup is true. Only comparing it with the visible page can.
Using it
- Choose an example and press Load example, or paste your own markup.
- Press Check markup, or Ctrl+Enter in the editor.
- Read errors first, then warnings. Notes explain Google documentation changes and are not problems.
- Use the Entity review tab to see which entities and references were found, and the entity map to draw them.
Error explanations are in structured data validation errors.