Entity consistency
Entity consistency is the property of a brand being described the same way everywhere it appears, so that a model resolves every mention to one entity instead of several similar ones.
Same name, same description, same identifiers, on your own site and on every third-party profile. It sounds like housekeeping and it is the layer that decides whether a model can say who you are with enough confidence to name you.
Why does a model need entity consistency?
To cite you, a model has to be reasonably sure that the company on your homepage, the one on your LinkedIn page and the one in a directory listing are the same company. It has no registry to check against. All it has is whether the descriptions agree.
When they disagree, the mentions do not add up: they split across two or three weak entities instead of accumulating into one solid one. Nothing breaks and nothing shows an error. You simply stop being the obvious answer to a question you should own.
This is also where the one measured finding in the field lands: the GEO study saw up to 40% more visibility for content that cites sources and can be attributed to someone specific. Attribution is entity work, and it is the half most sites never do.
What breaks entity consistency?
Almost always small things, introduced one at a time by people who had no way of knowing they mattered.
- A legal name in one place and a trading name in another, with no statement that they are the same.
- A description rewritten for each channel, so no two say the same thing.
- Structured data that declares one organisation while the visible page describes another.
- Profiles left behind on platforms nobody updated, still describing what the company did three years ago.
How is entity consistency declared?
With schema.org, an Organization block carrying a stable identifier, the name, one description and the links to the profiles you recognise as yours. The identifier is what lets every page point at the same entity instead of repeating a copy of it.
The rule that makes it work is dull and absolute: the description is written once and reproduced word for word. Rewriting it per channel feels like better copy and costs you the thing the block exists to build.
What is this based on?
Two pieces of the schema.org vocabulary and one measured study. All three are public and free to read in full.
- schema.org
The vocabulary structured data is validated against: which types exist and which fields each one marks as required.
- schema.org/Organization
The specific type used to declare a company as an entity, with the fields that carry identity: name, legal name, description, identifiers and recognised profiles.
- GEO: Generative Engine Optimization
Measures what makes a source more visible inside generated answers, including the effect of content that can be attributed to someone specific.
Frequently asked questions about Entity consistency
Is entity consistency the same as NAP in local SEO?
- Entity consistency comes from the same instinct and goes further. NAP keeps a name, address and phone number identical across directories, for a search engine. Entity consistency extends that to the description, the identifiers and the recognised profiles, because a model reads meaning and not only contact fields.
Do I need a Wikipedia page to be an entity?
- No. A Wikipedia entry helps because it is heavily cited, and it is not a requirement. What a model needs is agreement between the sources that already mention you, and that you can fix this week without anybody's permission.