Entity is the second pillar of the Website Growth System™. It answers a question the reader never asks and the machine always does: who are you, what do you do, and which of these pages is the real one. When the answer is consistent, search engines pick the right primary page and generative systems quote you in the right context. When it is not, good content sits unquoted.
What Entity means in the Website Growth System
Entity in the Website Growth System is the identity a machine can resolve: the brand, the services, the place, the expertise, and the relationships between the concepts on the site. It is treated as an engineering property rather than a branding one, because the failure it prevents is mechanical. An unresolved entity means a system cannot decide which page speaks for a topic.
The pillar is not about being described flatteringly. It is about being described identically in every place a machine looks, which is a lower bar and a much harder one to hold across a site that several people write.
The three layers where an entity is normalised
An entity is normalised at three layers, and skipping any one of them leaves the other two contradicted. The prose layer fixes what things are called, the technical layer declares it in structured data, and the link layer proves it through the anchors used across the site. Machines cross-check the three, which is why a declaration that the prose disagrees with is worse than no declaration.
- Prose layer: one name per thing used throughout, each important term defined at first use, and conclusions stated before explanations so a short passage can be quoted correctly.
- Technical layer: structured data declared at the correct scope per page type, so that a page claims what it is and nothing more.
- Link layer: internal link anchors that use the entity's actual name rather than whatever phrase fits the sentence.
The entity signals that have to be consistent
The entity signals that matter are unglamorous and finite, which is the good news about this pillar: the work ends. The list below is the whole of it for most sites, and each item is a place where two pages on the same site commonly disagree with each other without anyone noticing.
- Brand name: written the same way everywhere, with no alternate capitalisation and no abbreviation that appears without being introduced.
- An author and contact surface: a real about page, a real contact page and a real author identity, which is the cheapest credibility signal a site has.
- Term definitions in the body: so a retrieval system reading one section knows what the words mean without the rest of the page.
- Structured data with one organisation: declared fully once, referenced by identifier elsewhere, so the site is not read as several separate organisations.
- Anchor text that names the entity: consistent anchors teach a machine which page a concept belongs to.
One Organization node, referenced everywhere else
Declaring the organisation once and referencing it by identifier elsewhere is the specific technical rule in this pillar that is most often got wrong, and its failure mode is expensive. When every page declares a full organisation of its own, a crawler has grounds to read them as distinct entities, and the authority that should accumulate on one identity is split across many.
The correct shape is a single full declaration at one canonical location, with every other page pointing at that declaration by identifier. This is also the reason the technical layer is described here as fix-once work: it is cheap to do once, and it breaks broadly when it is done wrong, so it is verified before it ships rather than after.
Writing so that a single section can be quoted
Writing so a single section can be quoted is what connects this pillar to being cited by generative systems. A retrieval system usually takes a passage, not a page. If the conclusion of a section arrives in its final sentence, the passage that gets extracted is the setup rather than the answer, and the quote misrepresents the position.
The rule is therefore mechanical: the sentences immediately after a heading state the conclusion. Everything after that explains, qualifies or evidences it. This also happens to be how a hurried human reads, so the two audiences want the same structure.
The metric for the Entity pillar
The metric for the Entity pillar is whether machines quote you and whether they name you consistently when they do. It is a coarser measurement than the other three pillars allow, and this specification states that limitation rather than inventing precision: there is no clean per-URL counter for being included in a generated answer.
What can be tracked is directional and still useful. Whether the intended page is the one surfaced for the entity's own name, whether the brand is referred to by one form or several, and whether the definitions on the site are the ones that come back when the terms are queried.
What the Entity pillar hands to the conversion pillar
The Entity pillar hands the conversion pillar something specific: a reader who believes the page is written by someone identifiable and consistent. Trust is a precondition for action, and the third pillar cannot manufacture it at the point of the call to action if the preceding pages were vague about who was speaking.
Continue to pillar three, Conversion Rate Optimization, which turns that trust into a next step the reader is ready to take.