AAAnow, 25 years of innovation
JSON-LD SCHEMA VALIDATOR

Primary sources:
each finding traced to a document

The validator holds no private opinion about correctness. This is the register of published material it treats as authority, with a link to each one.

DOCUMENT ID TOOL/2026/JSV/0005
PUBLISHED 23 August 2026
READ TIME 4 min
ADDRESS aaanow.ai/json-validator (live End Sept 2026)

The public methodology explains how to interpret the complete result, including its validation layers, authority precedence, severity, current bundle versions and source observation dates. It also records known limitations, robots handling, rendering conditions, privacy controls, correction policy and the relationship between those parts.

Individual findings link to authorities and primary sources. That transparency makes a conclusion reviewable without exposing proprietary rule implementation or the internal source-mapping methods that distinguish the product.

01How the register is used

The register below identifies the external authorities reflected in this document. Production rule bundles retain the precise source location, observation date and version metadata behind each rule; the register is the public orientation layer, not a substitute for that evidence. It gives external reviewers a direct route into the governing material cited throughout the finished operating product.

02The register

Internet standards

  1. RFC 8259: JSON Data Interchange Format Governs JSON grammar and duplicate-name interoperability handling.www.rfc-editor.org/rfc/rfc8259 (opens in a new tab)
  2. RFC 8785: JSON Canonicalization Scheme Supports deterministic post-parse content identity.www.rfc-editor.org/rfc/rfc8785 (opens in a new tab)
  3. RFC 6901: JSON Pointer Supplies source-value location syntax within result evidence.www.rfc-editor.org/rfc/rfc6901 (opens in a new tab)
  4. RFC 9309: Robots Exclusion Protocol Informs anonymous URL retrieval and crawl-policy evidence.www.rfc-editor.org/rfc/rfc9309 (opens in a new tab)
  5. RFC 9457: Problem Details for HTTP APIs Defines machine-readable service error envelopes.www.rfc-editor.org/rfc/rfc9457 (opens in a new tab)

W3C recommendations

  1. W3C JSON-LD 1.1 Governs JSON-LD syntax, data model, HTML embedding and security considerations.www.w3.org/TR/json-ld11/ (opens in a new tab)
  2. W3C JSON-LD 1.1 Processing Algorithms and API Governs expansion, document loading, extraction and normative processing errors.www.w3.org/TR/json-ld11-api/ (opens in a new tab)
  3. W3C SHACL Defines RDF graph validation against governed constraint shapes.www.w3.org/TR/shacl/ (opens in a new tab)
  4. W3C WCAG 2.2 Defines the public-interface accessibility assurance target.www.w3.org/TR/WCAG22/ (opens in a new tab)

Schema.org

  1. Schema.org data model Defines types, properties, hierarchy, domains, ranges and value multiplicity.schema.org/docs/datamodel.html (opens in a new tab)
  2. Schema.org developer documentation Supplies machine-readable release data and identifier guidance.schema.org/docs/developers.html (opens in a new tab)
  3. Schema.org releases Identifies release 30.0 and its publication date.schema.org/docs/releases.html (opens in a new tab)
  4. Schema.org working process Defines core, pending and release-status handling.schema.org/docs/howwework.html (opens in a new tab)

Google Search documentation

  1. Google structured-data testing guidance Separates generic Schema.org validation from Google rich-result testing.developers.google.com/search/docs/appearance/structured-data/rich-results-test (opens in a new tab)
  2. Google general structured-data policies Defines published technical and page-policy conditions.developers.google.com/search/docs/appearance/structured-data/sd-policies (opens in a new tab)
  3. Google Search Gallery Supplies the supported structured-data feature documentation set.developers.google.com/search/docs/appearance/structured-data/search-gallery (opens in a new tab)
  4. Google Search documentation updates Records continuing feature and property changes.developers.google.com/search/updates (opens in a new tab)
  5. Google JavaScript SEO guidance Supports raw and rendered comparison plus crawl findings.developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics (opens in a new tab)

Security guidance

  1. OWASP SSRF Prevention Cheat Sheet Supports layered public-URL destination controls.cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html (opens in a new tab)
  2. OWASP XSS Prevention Cheat Sheet Supports safe source display and output encoding controls.cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html (opens in a new tab)

Tooling and reporting

  1. Playwright container guidance Supports sandboxed, non-root handling of untrusted page rendering.playwright.dev/docs/docker (opens in a new tab)
  2. OASIS SARIF 2.1.0 Defines the standard used for static-analysis interchange.docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html (opens in a new tab)

03No artificial eligibility promise

A Google consumer result says whether the published technical requirements were met under the recorded rule bundle. It does not promise indexing, ranking or a rich-result appearance; Google’s own policies separate those outcomes from technical validation.

Questions of usefulness, reputation, deception and overall page quality still require human judgement. Where the available evidence cannot settle a policy question, the product says so. Absence of evidence becomes neither an invented failure nor an implied approval. The recorded boundary makes that limit explicit, preventing policy judgement from being mistaken for a machine-certified conclusion at any point in the result.