Definition · published
What is Schema?
Structured data vocabulary used to describe entities and page content in a machine-readable form.
Structured data vocabulary used to describe entities and page content in a machine-readable form. Learn how VOID applies the term, what evidence to inspect, and where the definition stops.
Reviewed 2026-07-20 · National guidance, Austin proofThe task and the failure mode
Built for: Owners, operators, marketers, and technical teams who need a shared working definition of Schema.
The term “Schema” is often used without a testable boundary. That makes briefs, audits, vendor comparisons, and performance reviews harder to evaluate.
Workflow
- 01Use the definition to state what Schema includes in the current project.
- 02Name the evidence that would show whether the Schema requirement is met.
- 03Record important exclusions, dependencies, and unknowns before implementation.
- 04Assign an accountable owner and a review date.
- 05Measure the operational or search outcome separately from completion of the task.
Evidence to retain
- Structured data should describe visible truth. It must not invent proof, services, reviews, locations, authorship, or credentials.
- A project-specific acceptance test for Schema.
- A visible source, artifact, or observation that another reviewer can inspect.
Release checklist
- Define Schema in the project brief.
- Identify the affected routes or workflow.
- Separate verified facts from assumptions.
- Link the governing source.
- Document exceptions and risks.
- Set a review date.
Boundaries and caveats
This is VOID’s practical working definition of Schema, not a guarantee of search or business outcomes.
Platform terminology and behavior can change; verify current primary documentation before a high-impact decision.
Primary sources
- Schema: primary referencedevelopers.google.com
- Google Search Central: Creating helpful, reliable, people-first contentdevelopers.google.com