EP-9 Spec

L2 Owned Content Hub: one dedicated entity page

Layer 2 of EP-9 gives every entity one dedicated URL built on the 6-block template, with a one to two sentence definition directly under the H1.

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.

Specification: EP-9 (layer 2 of 9) Source: section 3 of the deposited specification Next: layer 3

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.

The 6-Block Entity Page Template.
BlockBlock nameRequired structural content and layout elementsAI and conversion function
Block 1H1 & Answer-First DefinitionExact entity name in H1 + direct 1-2 sentence canonical definition immediately following.AI Featured Snippet & GEO Direct Answer
Block 2Context & Scope BoundariesDetailed explanation of what the entity is, what it is NOT, and key application scenarios.Semantic Disambiguation & Entity Bounds
Block 3Selection & Usage CriteriaStructured criteria, decision matrices, comparison tables, and execution conditions.DLN Choose Stage (Solution Comparison)
Block 4Common Mistakes & Anti-PatternsList of frequent execution errors, misconceptions, and anti-pattern warnings.Risk Reduction & Trust Building
Block 5Proof Stack & Case DataVerifiable implementation data, case study results, author bio, and ORCID/DOI citations.E-E-A-T Verification & Proof Stacking
Block 6Next-Step DLN Link RailContextual 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.

Checkpoints for layer 2, from the 15-point EP-9 audit checklist.
Checklist IDAudit layerMandatory verification requirementTool and method
CHK-EP-02L2 ContentDedicated Entity Page deployed with 6-block template at canonical URL.URL Audit / CMS
CHK-EP-03L2 Answer-First1-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.

DefinitionOwned Content Hub is layer 2 of EP-9 that gives every entity one dedicated URL built on the 6-block template, helping search engines and readers find one place where the entity is defined.

How to build a dedicated entity page for layer 2

These steps help you give each entity one dedicated URL with all six blocks and a definition directly under the H1, so the page passes checkpoints CHK-EP-02 and CHK-EP-03.

  1. Assign one URL per entityGive each entity its own dedicated page at its canonical URL. Never define two entities on one page, because it cannot carry one canonical name in title, H1 and schema.
  2. Place the exact name in H1Put the exact entity name in the H1, then place a direct definition of one to two sentences as the very next element on the page.
  3. Define context and scopeExplain what the entity is, what it is not, and its key application scenarios, so the entity has clear bounds for readers and machines.
  4. Check the served pageAudit the page as it is served and confirm all six blocks and the definition under the H1 appear in the page text. Blocks found only in a draft or after a click do not count.

FAQ about Owned Content Hub

Why does a schema declaration fail without a dedicated entity page behind it?

A schema declaration without a page behind it has nothing to confirm. Search engines read content before they read structured data, so they look for the page first. That is why layer 2 comes before schema in the Trust Chain, and why each entity needs its own dedicated URL built on the 6-block template.

What is the difference between Block 2 and Block 3 on an entity page?

Block 2 sets context and scope boundaries, explaining what the entity is, what it is not, and its key application scenarios. Block 3 gives selection and usage criteria, such as decision matrices, comparison tables and execution conditions. Block 2 helps a reader understand the entity, and Block 3 helps the reader choose.

What is the Owned Content Hub in the EP-9 framework?

The Owned Content Hub is layer 2 of the Entity Architecture and Governance Framework, known as EP-9. The Owned Content Hub requires one dedicated URL for each entity, built on the 6-block template, with a one to two sentence definition directly under the H1. The rule is mandatory: one dedicated page per entity.

How is the Owned Content Hub different from the schema layer in EP-9?

The Owned Content Hub is layer 2 of EP-9 and covers the visible page an entity owns, while schema arrives in layer 4. The Owned Content Hub comes before schema in the Trust Chain because search engines read content before structured data, and a schema declaration without a page behind it has nothing to confirm.

Menu

Add to Home Screen

  1. 1 Tap Share in Safari toolbar
  2. 2 Scroll down, select Add to Home Screen
  3. 3 Tap Add in top right corner

These steps are for Safari on iOS. If viewing inside another app, open in Safari first.