Entity
A canonical concept in your model (e.g. a problem, use case, persona, integration) that many pages and systems reference — the unit that keeps narrative, links, and signals consistent.
Last updated: December 12, 2025
Definition
A canonical concept in your model (e.g. a problem, use case, persona, integration) that many pages and systems reference — the unit that keeps narrative, links, and signals consistent.
In practice
- Use entity IDs as the backbone: pages, analytics events, and traits reference the same entity.
- Link across page types (glossary → use case → KB → tool) using the same entity language.
Common mistakes
- Treating the URL slug or keyword as the entity (slugs change; entity meaning should not).
- Allowing duplicate entities for the same concept (“churn reduction” vs “reduce churn”) without a merge rule.
Related terms
- Entity model — A small, stable set of entities (problems, use cases, roles/personas, industries, etc.) and their fields/relationships that power content, analytics, automation, and LLM retrieval.
- Canonical page / canonical link — The single page you want threads, content, ambassadors, and internal tools to link to for a topic — so knowledge compacts instead of fragmenting across repeated answers.
- Traits — Machine-readable tags derived from page views and behavior (tied to entities) that feed analytics, automation, and CRM without manual interpretation.
- Template spine — A consistent page structure for each page type (use case, glossary, KB, etc.) so users and machines know where to find definitions, steps, mistakes, and related links.