Owned Content Hub is layer 2 of the Entity Architecture and Governance Framework (EP-9). It requires a dedicated URL for each entity, built on the 6-block structured template. It is mandatory: one dedicated page per entity.
What layer 2 covers
Layer 2 covers the page an entity owns. EP-9 requires a dedicated URL for each entity, structured with the 6-block template, so that the entity has one place where it is defined, explained, proven and connected to a next step. The framework's own master page, /en/ep9/, is an example.
Search engines read content before they read structured data. A schema declaration without a page behind it has nothing to confirm, which is why this layer comes before schema in the Trust Chain.
The six blocks of an entity page
The six blocks of an entity page are the definition, the scope, the criteria, the mistakes, the proof and the next step. Together they let one page serve two readers: a person deciding whether this entity is what they need, and a machine extracting a correct statement about it.
| Block | Block name | Required structural content and layout elements | AI and conversion function |
|---|---|---|---|
| Block 1 | H1 & Answer-First Definition | Exact entity name in H1 + direct 1-2 sentence canonical definition immediately following. | AI Featured Snippet & GEO Direct Answer |
| Block 2 | Context & Scope Boundaries | Detailed explanation of what the entity is, what it is NOT, and key application scenarios. | Semantic Disambiguation & Entity Bounds |
| Block 3 | Selection & Usage Criteria | Structured criteria, decision matrices, comparison tables, and execution conditions. | DLN Choose Stage (Solution Comparison) |
| Block 4 | Common Mistakes & Anti-Patterns | List of frequent execution errors, misconceptions, and anti-pattern warnings. | Risk Reduction & Trust Building |
| Block 5 | Proof Stack & Case Data | Verifiable implementation data, case study results, author bio, and ORCID/DOI citations. | E-E-A-T Verification & Proof Stacking |
| Block 6 | Next-Step DLN Link Rail | Contextual internal links leading to related Offer/Method entities or booking forms. | Conversion Pathway (DLN Rate -> Act) |
The definition directly under the H1
The definition directly under the H1 is the most important block on the page. The H1 carries the exact entity name, and the next element is a direct definition of one to two sentences. That position lets an answer engine take a complete statement without reading the rest of the page.
The same sentence is reused as the description in the schema of layer 4. Writing it once and copying it exactly is what makes the 100 percent text match of checkpoint CHK-EP-07 possible.
Can one page cover several entities?
No. Layer 2 asks for a dedicated page, one per entity. A page that defines two entities gives two answers to the question of what the page is about, and it cannot carry one canonical name in its title, H1 and schema as layer 1 requires.
Checkpoints for layer 2
The checkpoints for layer 2 confirm that the entity page exists at its canonical URL with all six blocks, and that its definition sits immediately under the H1 in the page text. They are taken from the 15-point EP-9 technical audit checklist and keep their original identifiers, so an audit report can cite each one directly.
| Checklist ID | Audit layer | Mandatory verification requirement | Tool and method |
|---|---|---|---|
| CHK-EP-02 | L2 Content | Dedicated Entity Page deployed with 6-block template at canonical URL. | URL Audit / CMS |
| CHK-EP-03 | L2 Answer-First | 1-2 sentence direct definition appears immediately under H1. | DOM Text Audit |
Check the page as it is served, not as it looks in an editor. A block that exists only in a draft or only after a click does not count toward either checkpoint.