Field notes

When a machine confuses you with a company you have never heard of

Entity confusion is rarely caused by one bad page. It comes from a business describing itself three different ways across places nobody has audited together.

The complaint arrives in a recognisable form: someone asked an AI assistant about the company and got details belonging to a different business, or a mixture of two. Usually there is no single broken page to point at. The cause is distributed, and it accumulated over years.

How the confusion forms

A machine establishing what an organisation is draws on whatever it can find and looks for agreement. Confusion sets in when the available evidence disagrees. Typical sources of disagreement:

  • The homepage describes the company one way; the About page, written three years earlier, describes it differently
  • Structured data carries a legal entity name nobody uses in practice
  • An old directory listing has a previous address or a disconnected phone number
  • A social profile from an abandoned campaign describes a discontinued product line
  • The company rebranded and the old name still appears in several places
  • A similarly named business in an adjacent sector is described more consistently than you are

Individually, each is trivial. Collectively they mean there is no single coherent story, so a coherent-sounding wrong one may win.

The audit worth doing once

This is dull work with unusually good returns, because most competitors have not done it. Collect how your organisation is described in every place you control or can correct:

  1. Homepage — the visible name, description, and any contact details
  2. About page — the same, which frequently disagrees with the homepage
  3. Structured data — what your Organization markup actually asserts today
  4. Footer and contact page — address, phone, email
  5. Every external profile you can find: directories, industry listings, review sites, social accounts, old press releases

Put them in a table. The disagreements are usually obvious and often surprising — teams routinely discover addresses they left years ago, and descriptions of products they no longer sell, still live.

Resolving it

Decide the canonical version once: one name as you actually use it publicly, one description, one address, one primary contact. Then propagate it, starting with the sources you control fully and working outward.

When the name genuinely collides

Sometimes a larger or better-established company shares your name. You will not out-rank them on the name alone, and trying is a poor use of effort.

What works is being unambiguous about the qualifiers that distinguish you: sector, location, what you actually do. If your description is 'a leading provider of innovative solutions', you have supplied nothing to distinguish you from anyone. If it is 'a Bengaluru-based accessibility testing firm for financial services', a system has clear grounds to separate you from a same-named company in another field.

Keeping it true

Entity descriptions drift because nobody owns them. The cheap prevention is a short checklist attached to events that cause drift — rebrands, address changes, product launches and retirements, domain migrations. A list of every place your organisation describes itself, revisited when those happen, prevents most of the accumulation.

Sources

Check your own site

Run the audit described in these notes against your own website. No signup, evidence included for every check.

Run a free audit