Entity
Updated 2026-09-15
An entity is a specific, identifiable thing — a company, a person, a product, a place — that a search or answer system can recognise and attach facts to. AI answers are assembled around entities, not keywords, which is why brand visibility work is entity work.
What makes an entity legible
Three signals do most of the work. A stable identifier: the same name, the same URL, the same markup identifier used consistently everywhere. Clear attributes: what it is, what it does, who built it, where it operates, stated in text rather than implied by design. And corroboration: independent sources that describe the entity the same way. When those disagree, engines hedge or blend — which is exactly how brands get described as something they are not.
Illustrative check (example, not a customer measurement)
An organisation node is declared once with a fixed identifier and referenced from every page; the founder is a person node linked to it; the same two sentences describing the product appear on the about page and in external profiles. An engine asked "what is <brand>" now has one consistent story to compress instead of three partial ones.
Common mistakes
- Describing the product differently on every page, which gives engines several competing versions to choose from.
- Listing profile links that do not exist or are abandoned — unverifiable identity signals are worse than none.
- Assuming a logo and a tagline convey what the product does. Engines read text, not design.
Frequently asked questions
- Does a brand need a Wikipedia page to be an entity?
- No. Consistency and corroboration matter more than any single source: a clear entity page, matching profiles, and third parties describing the brand the same way are enough for engines to treat it as one thing.
- What is the fastest entity fix?
- One page that answers "what is this, who built it, what does it do, what does it not do" in plain sentences, referenced from the rest of the site and matched by the external profiles you actually control.
