Clear Identity Naming is layer 1 of the Entity Architecture and Governance Framework (EP-9). It requires one standardized, canonical name for each entity, without ambiguous acronyms. It is mandatory, and it is scored pass or fail.
What layer 1 covers
Layer 1 covers the name an entity is known by. EP-9 requires one standardized, canonical entity name, written the same way everywhere, with no ambiguous acronym standing in for it. Every later layer refers to the entity by this name, so an error here is copied into all of them.
The layer is scored pass or fail because a partial identity does not exist. If a brand appears under three spellings, a crawler and a language model see three candidates and have to guess which one the page means.
Choosing the canonical name
Choosing the canonical name starts with the entity group it belongs to: an offer, a problem, a method or a trust entity. The name should say what the entity is in words a reader would search for, and any acronym should appear together with its full form, as in Decision Ladder Navigation (DLN).
An acronym on its own is ambiguous by default. EP9, for example, is also the name of an electric car, which is why this framework's own pages always write it as EP-9 next to its full name.
Where the name must match
The name must match in three places that machines read first: the page title, the H1 and the schema. Checkpoint CHK-EP-01 verifies exactly these three by DOM inspection, and the first domain of the Definition of Done awards 20 points when the name is standardized and the title and H1 are aligned.
Variants and synonyms still have a place, but not here. They are recorded in layer 5, where each one is mapped back to the same canonical URL.
What should happen to the other names an entity already uses?
The other names become synonyms, not rivals. Layer 1 fixes one canonical name, and layer 5 then maps three to five alternative names back to it in the page text. That way readers who search an older or shorter name still arrive at the same entity.
Checkpoints for layer 1
The checkpoint for layer 1 is a direct comparison of the entity name across the title, the H1 and the structured data of the entity page. It is inspected in the rendered DOM rather than in a template file. 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-01 | L1 Identity | Exact canonical entity name used across Title, H1, and Schema. | DOM Inspection |
A page passes when all three strings are identical. Record every difference you find, including capitalization and punctuation, because each one is a separate spelling to a machine.
DefinitionClear Identity Naming is layer 1 of EP-9 that fixes one standardized, canonical entity name without ambiguous acronyms, helping crawlers and language models match the title, the H1 and the schema to one entity.
How to apply one canonical entity name under EP-9 layer 1
These steps help you pick one canonical name for an entity and make the title, the H1 and the schema use exactly the same string so machines see one entity.
- Identify the entity groupDecide whether the entity is an offer, a problem, a method or a trust entity, because choosing the canonical name starts with that group.
- Write the name in searchable wordsChoose a name that says what the entity is in words a reader would search for, and write any acronym together with its full form, as in Decision Ladder Navigation (DLN).
- Match the title, H1 and schemaPut the exact same canonical name in the page title, the H1 and the structured data, since these are the three places machines read first.
- Move other names to layer 5Keep older or shorter names as synonyms, which layer 5 maps back to the same canonical URL, so readers searching those names still reach the same entity.
FAQ about Clear Identity Naming
Direct answers to frequently asked questions about Clear Identity Naming, based on real-world implementation data, systematic technical audits, and verified production performance.
Is a short acronym enough to name an entity under EP-9?
No. An acronym on its own is ambiguous by default, so it should appear together with its full form, as in Decision Ladder Navigation (DLN). EP9, for example, is also the name of an electric car, which is why the framework is always written as EP-9 next to its full name.
Which three places must show the same canonical entity name?
The page title, the H1 and the schema must show the same canonical entity name. These are the three places machines read first, and checkpoint CHK-EP-01 verifies exactly these three by DOM inspection, looking at the rendered DOM and not at a template file.
What is Clear Identity Naming in EP-9?
Clear Identity Naming is layer 1 of the Entity Architecture and Governance Framework (EP-9). Clear Identity Naming requires one standardized, canonical name for each entity, without ambiguous acronyms, used the same way in the page title, the H1 and the schema. The layer is mandatory and scored pass or fail.
How is a canonical entity name different from its synonyms and variants?
A canonical entity name is the one standardized name fixed in EP-9 layer 1 and used identically in the title, the H1 and the schema. Synonyms and variants are alternative names recorded in layer 5, where each one is mapped back to the same canonical URL so every name points to one entity.