Structured Summary: A repeatable validation method for HTTP status, canonical output, one managed JSON-LD graph, parseability, provenance, and typed relations.
Database Checks
Confirm schema type, node ID, managed flag, canonical URL, relationship metadata, and absence of JSON-LD embedded in post content.
Rendered Checks
Request representative public URLs, verify HTTP 200, count the managed schema script, decode its JSON, and confirm WebSite, Organization, WebPage, primary node, and breadcrumb IDs.
Acceptance Criteria
Exactly one managed schema script on each sampled singular page, valid JSON, self-referencing canonical IDs, publisher and date provenance, and no duplicate body schema.
Limitation
Hosting loopback restrictions may prevent automatic requests. In that case the report marks rendered validation as unknown rather than passing it by assumption.
Governance Note
This document is versioned and should be revised when production architecture, source specifications, or validation evidence changes. It does not guarantee ranking, citation, recommendation, or business outcome.
Version: 1.0 | Published: 28 July 2026 | Owner: GEO.or.id
Knowledge Relationships
This asset is connected to canonical nodes through typed relationships maintained in the GEO.or.id knowledge registry.
- Is Part Of: Methodology
- Implements: Schema Governance
- Implements: Schema Type Registry
- Part Of: Methodology
- Related To: Schema Intelligence
- Related To: Schema Validation Dataset