Structured Summary: A schema governance policy for one centralized JSON-LD graph, typed primary entities, provenance, canonical IDs, and rendered-output validation.
Definition
Schema Governance defines which structured-data runtime is authoritative, how types are assigned, how relationships are mapped, and how duplicate or visible body schema is prevented.
Runtime Rule
Managed singular pages and posts use one JSON-LD graph in wp_head. JSON-LD must not appear as visible article content.
Type Rule
Schema types follow the actual content role. Dataset, Report, DefinedTerm, TechArticle, Organization, BlogPosting, CollectionPage, and WebPage are assigned through an explicit registry with conservative inference.
Validation Rule
Database checks are not sufficient. Representative rendered pages must return HTTP 200, contain exactly one managed schema script, and expose valid parseable JSON-LD.
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: GEO.or.id Governance
- Implemented By: Rendered Schema Validation Methodology
- Part Of: GEO.or.id Governance
- Supported By: Schema Type Registry
- Related To: Schema Intelligence
- Related To: Schema Intelligence System Index