In one sentence: an entity is the model's stable idea of who you are, and it is built from consistent naming, a machine-readable identity block, and corroborating references you do not control — in that order of cost and that order of importance.
Why this comes before content
A model naming a brand in an answer is making a claim it has to stand behind. If your name is spelled three ways across your own site, collides with an unrelated company, or has no consistent description anywhere, there is no stable thing to name. Writing more pages does not fix ambiguity; it multiplies it.
Layer 1 — Consistency you control
- One canonical name, used identically in the title tag, the H1, the footer, the schema and the social profiles. Decide whether the legal suffix is part of it and then never vary.
- One canonical description. A single sentence saying what you do and who for, repeated verbatim across your own properties. Variation reads as uncertainty.
- One canonical domain form. www or not, trailing slash or not, enforced in code — we had 46 pages indexed under two URL forms each, splitting roughly 1,980 impressions between twins, before we enforced it.
Layer 2 — The identity block
An Organization block with name, URL, logo, founding date, location and — the field that matters most — sameAs. This is the cheapest way to state identity facts in a form that does not depend on prose parsing.
An Organization block with an empty sameAs is an assertion with no corroboration. It says who you claim to be and nothing about whether anyone else agrees.Layer 3 — Corroboration you don't control
This is the slow layer and the one that decides outcomes. The goal is that the claims in your identity block appear, independently, somewhere you do not own:
| Surface | What it corroborates |
|---|---|
| Structured knowledge bases | That the entity exists and is distinct |
| Software directories with real fields filled in | Category, pricing shape, who it's for |
| Comparison pages you did not write | Where you sit relative to named alternatives |
| Community threads | That real people use it, in their own words |
| Documentation written by customers | Concrete capability claims |
How to check where you stand
Search your exact brand name and read what comes back as if you had never heard of the company. Then ask an engine to describe you and read the sources it cites. If every source is your own domain, you have layers one and two and none of layer three — which is precisely the state where a brand is mentioned but never recommended.
The disambiguation case
If your name collides with a larger entity, none of the above is enough on its own; you need the qualifier to appear consistently everywhere — the category, the location, or the sector, attached to the name in the same form each time. It is tedious and it is the only thing that works.