SEO Tools
Structured Data / JSON-LD Checker
Inspect JSON-LD syntax, supported structured-data fields, node identifiers, and supplied references. Markup and reports stay in your browser.
Your structured data
Paste JSON-LD or supplied HTML. Checks update automatically; no page or context is fetched.
Used only as the base for relative URLs and node IDs. Cross-block references are compared as data from one supplied page. URLs are never visited.
Limits: 512 KiB UTF-8, 20,000 source lines, 100 script blocks, 20,000 values per block, 5,000 JSON objects, 2,000 typed entities, and 128 nesting levels. HTML is limited to 10,000 elements.
JSON blocks parsed
Profile checks
Issues
Review notes
A supported static check, not full JSON-LD expansion, Schema.org validation, or Google Rich Results testing. Invalid blocks are skipped while other blocks are inspected.
Inspect an extracted JSON block
Diagnostic line and column numbers refer to this extracted JSON text, not the original HTML. The viewer is read-only; edit the source above.
Findings and recommendations
Detected typed entities
| Location | Types | @id | Checks applied |
|---|
Understand the checker’s coverage
Which structured-data types are checked?
Bundled field profiles cover Article, BlogPosting, NewsArticle, Organization, BreadcrumbList, and LocalBusiness plus Store, Restaurant, CafeOrCoffeeShop, Hotel, ProfessionalService, Dentist, HairSalon, and RealEstateAgent. Supporting objects are inspected within those profiles. Other types are listed without complete field checks. Unknown properties are not treated as errors solely because they are outside the bundled rules.
How are issues different from recommendations?
Issues identify syntax problems, ambiguous duplicate JSON keys, invalid checked values, or missing requirements in a supported Google profile. Article and Organization have no universally required Google properties; missing suggested fields receive review notes. LocalBusiness checks name/address; BreadcrumbList checks its trail and items. These profiles do not cover every Google feature, policy, or subtype.
How are contexts and references handled?
Type-specific checks require a plain http://schema.org or https://schema.org context with short property names. Context objects, arrays, aliases, custom vocabularies, expanded properties, and advanced context behavior are not expanded; affected checks are skipped. Pure @id reference objects can resolve to a unique supplied definition. Missing references receive review notes because external definitions can be valid. Repeated @id definitions can merge in JSON-LD; this checker reports them and skips their field profiles rather than guessing a merge.
What does passing these checks mean?
It means no issue was found within the supported static checks. It does not verify actual page content, image dimensions, accessibility, crawlability, live URLs, canonicals, indexing, search-engine eligibility, ratings policies, rich results, rankings, or AI citations. Review the current official guidelines and test deployed pages separately.
Is my markup private?
Inputs stay in this tab. HTML is parsed in an inert template; scripts are never executed or attached to the page. Remote contexts, script sources, URLs, and images are never fetched. File reads, analysis, clipboard copies, and reports run locally without a processing endpoint or browser storage.
Bundled rules reviewed 2 November 2026. References: Article · Organization · LocalBusiness · BreadcrumbList.
