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?

An Entity Map is the single record of who your organisation is to a machine. It lists every entity you want recognised: the organisation, its brands, products, locations and authors. For each entity it holds one identifier, the facts that describe it, and every profile and page where those facts must match. Structured data is how the map is published on your site.

The term has a second, narrower meaning: entitymap.json, a proposed open standard for publishing such a map as one file. We cover both below.

Why you need one

A model builds its picture of your brand from many places at once. Three things go wrong when those places disagree.

  • Disambiguation. Different spellings, old names and sister companies read as separate entities. Your authority is split across them.
  • Attribution. Your content informs the answer, but your name does not appear in it.
  • Relationships. Who owns whom, who works where and which product belongs to which brand stay implicit. The model guesses.

We have seen all three in audits. Answers about a Dutch retailer drew on a company with the same name in another country. A measurement tool resolved a brand name to an unrelated domain. If a specialised tool gets the entity wrong, the models do too.

The hierarchy: organisation, then authors

The map is a hierarchy, and the order matters.

  1. The organisation. One entity with one stable identifier. Legal name, trading names, former names, founding date, address, parent and subsidiaries.
  2. Brands, products and locations. Each linked to the organisation that owns it.
  3. Authors. The people who speak for the organisation, each linked to it as an employee, and each with their own author page and profiles.
  4. Published work. Articles, research and video, each linked to its author and to the organisation as publisher.

Most companies stop at level one. Levels three and four are where expertise becomes attributable. That is the subject of author enablement.

Six layers the map keeps aligned

Layer What must match
Domains One primary domain. Old domains redirected page by page.
Structured data Organization, Person, Product and Article markup with stable @id values.
Wikidata and Wikipedia Labels, descriptions, identifiers, ownership.
Profiles LinkedIn, YouTube, review platforms, app stores, Business Hub. Same name, same sentence.
Third parties Directories, comparison sites, partner pages, press boilerplate.
Content Your own pages, which state the identity sentence word for word.

How it is published

We publish the map as JSON-LD, in one connected graph. Every entity gets an @id that never changes. Other pages refer to that @id. They do not repeat the details.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.example.com/#organization",
      "name": "Example",
      "legalName": "Example B.V.",
      "url": "https://www.example.com/",
      "description": "Example is a planning platform that reschedules factory orders in minutes for mid-size manufacturers.",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q00000000",
        "https://www.linkedin.com/company/example/",
        "https://www.youtube.com/@example"
      ],
      "employee": [{ "@id": "https://www.example.com/team/jane-doe/#person" }]
    },
    {
      "@type": "Article",
      "@id": "https://www.example.com/research/disruption-index/#article",
      "headline": "Manufacturing Disruption Index, Q3",
      "datePublished": "2026-10-01",
      "dateModified": "2026-11-03",
      "author": { "@id": "https://www.example.com/team/jane-doe/#person" },
      "publisher": { "@id": "https://www.example.com/#organization" }
    }
  ]
}

The author's own entity lives on the author page. The author enablement page shows that markup.

The order of work: Organization with sameAs first. Then WebSite and breadcrumbs. Then Article with author and dates. Then FAQ, Product, Offer and Review where they apply.

Schema is packaging

Structured data states what a page already says. It does not add authority and it does not fix a vague page. Google documents that it uses structured data to understand content. The AI labs have published very little on how they use it. We treat markup as a way to remove ambiguity. We do not sell it as a ranking factor.

The same goes for the page itself. The author and the last-updated date must be visible on the page, and present in the markup too.

entitymap.json: early, cheap to test

entitymap.json is a proposed open standard from InLinks and Waikay, version 1.0, with its formal launch on 1 July 2026. One file at the root of your domain declares your entities, their relationships and the passages on your site that support each claim.

What we know so far:

  • No major AI lab has said it reads the file.
  • The published results are a handful of case studies on single sites, without control groups.
  • Once your Entity Map exists, generating the file costs little.

So we implement it as an experiment for clients who want it, and we measure it like any other change.

Who owns the map

One person on your side owns the map. We keep the change log. When a fact changes, such as a rebrand, a merger, a new product or a departing author, the map changes first. Every layer follows from it.

How we measure it

Four prompts, run on every engine: "What is {brand}?", "Is {brand} for {segment}?", "{Brand} versus {competitor}?", "Is {brand} reliable?" We score the answers for accuracy against the map and count wrong-entity answers. We also run a consistency check of all profiles against the map each quarter.

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.