Find the issue. See the code. Know what to fix. — 2-UA
Inspect JSON-LD with source line numbers, entity navigation and copyable fix examples. Test your changes before publishing.
Enter a public URL or paste your HTML / JSON-LD directly. We extract every application/ld+json block
with its original source lines. Explore nested entities, understand missing fields
and test fixes in the code editor below.
No registration required.
Code checks run in your browser. Examples contain placeholders: replace them with true, visible page content. Examples do not replace your existing markup automatically.
Works on Articles, Products, BreadcrumbList, FAQ, HowTo, LocalBusiness, Recipe, Event, Video, JobPosting, Organization and more.
Structured data workbench
Inspect original source lines, follow entities and copy concrete fix examples. Test changes here before updating your website.
What is checked — and what is not?
JSON syntax, Schema.org V30.1 type/property names and property domains, entity detection, in-document @id references and selected completeness checks for common types. Every member of a repeated property is checked. Suggestions are not universal Schema.org requirements or a complete Google eligibility test.
Only JSON-LD in fetched HTML is inspected. JavaScript is not rendered. Microdata, RDFa, remote or aliased contexts, property value/range validation, Google policies and indexing are not checked. A recognized type without a completeness checklist is detected, not rejected. External @id references are not fetched.
Google no longer shows FAQ, HowTo or sitelinks search box rich results. Valid markup can still describe your content. Google Search updates · Full Schema.org vocabulary validator · Google Rich Results Test
Vocabulary data derived from Schema.org V30.1 (2026-09-16), by the Schema.org sponsors, under CC BY-SA 3.0. Adapted to type inheritance and property domains.