The Entity Map. One identity, stated the same way everywhere.
Authority · Entity Map
Press, reviews, profiles and Wikidata only add up when they describe the same company. The Entity Map is the record that keeps them aligned, and structured data is how we publish it.
What is an Entity Map?
Why you need one
The hierarchy: organisation, then authors
Six layers the map keeps aligned
How it is published
Schema is packaging
entitymap.json: early, cheap to test
Who owns the map
How we measure it
Is an Entity Map the same as schema markup?
No. The Entity Map is the record: which entities, which facts, which profiles. Schema markup is one way of publishing it, on your own site. The map also governs Wikidata, your profiles and the wording third parties use.
Do AI assistants read structured data?
Google says it uses structured data to understand pages. Other providers have said little. We see markup help most with disambiguation: telling a machine that two names are one company, or that an author works for you.
What is entitymap.json?
A proposed open standard for publishing your entities, their relationships and supporting evidence in one file. It is new and unproven. No major AI lab has committed to it. It is cheap to add once the map exists, so we test it and measure.
When do we need an Entity Map most?
After a rebrand or a merger. When you operate in several countries under one name. When your name resembles another company's. And when AI answers state basic facts about you wrongly.
See which sources carry your category
The GEO baseline shows which pages the engines cite for your prompts, and where your brand is missing.