Entity HTML: How to Become a Machine-Readable Brand (Knowledge Graph, sameAs & the Entitymap)

The web spent twenty years optimising strings, keywords, phrases, exact-match text. Search engines and AI assistants now think in things: people, companies, products, places, and the relationships between them. If a machine can't resolve your brand to a confident, well-connected entity, you are a string it has to guess about, and in an AI answer, guessing means citing someone else.

This is the complete reference for entity HTML: how to make your brand a machine-readable thing, where those signals must physically live in your markup, and how to build the kind of entity confidence that earns Knowledge Panels and AI citations. It's the structural companion to The Forgotten HTML, because none of this matters if it isn't in the HTML the crawler actually renders.

🧩 Strings vs things: what an entity actually is

Google announced the shift in 2012 with the Knowledge Graph and the phrase "things, not strings." A string is text, the characters a-p-p-l-e. A thing is a uniquely identified concept, Apple the company, distinct from apple the fruit, with attributes (founded 1976, HQ Cupertino) and relationships (founded by Steve Jobs). Each entity has a stable internal ID, and the Knowledge Graph stores what's true about it and how it connects to everything else.

Why this matters more every quarter: being a confident entity is now the prerequisite for the surfaces that are eating clicks. Knowledge Panels, AI Overviews, AI Mode, and Gemini answers all draw on entity understanding to choose who to feature. If Google isn't sure who you are, you are not a candidate, no amount of keyword optimisation fixes an identity problem.

🗺️ The entitymap: a useful way to picture it

Waikay's EntityMap case study (April 2026) frames this cleanly. In their words, "an entitymap tells AI models what your brand means, what it does, and how its parts relate to each other." It's the same idea as a Knowledge-Graph node for your brand, made deliberate: a structured description of your entity and its relationships, published where machines read it.

Their reported result is a useful illustration of the mechanism, credited, with the caveat that it's a single vendor case study, not independent research: after deploying an entitymap, they observed "AI Knowledge Scores improved by up to 26 points in 48 hours," and the entitymap was "cited 2.2, 3.0× more often than the site's own About page." Treat the exact numbers as directional; the direction, clearer entity, more citations, is what's worth internalising.

⚙️ How entity confidence is actually built

Machines don't trust a single self-declaration. Entity confidence comes from independent sources agreeing about who you are. The mechanism:

🔩 The building blocks (where the signals live in your HTML)

• The entity home. One canonical URL that is your entity, usually your homepage or /about. Everything else points back to it. Pick one and be consistent; a split identity confuses the graph.
• Organization (or Person) schema. JSON-LD that states your name, logo, URL, and, critically, sameAs. This is the machine-readable declaration of identity.
• sameAs corroboration. An array of URLs to other authoritative profiles of the same entity: Wikidata, Wikipedia, LinkedIn, Crunchbase, official social. Wikidata is the highest-leverage target because it feeds the Knowledge Graph directly. More agreeing identifiers = higher confidence.
• Consistent naming (NAP). Identical name, address, and phone everywhere. Inconsistency reads as two different entities.
• Entity linking in content. When you mention your brand, people, or products, link them to their entity home; reference well-known entities (and their Wikipedia pages) to place yourself in the right neighbourhood of the graph.
• Author entities. Real Person schema for authors, with their own sameAs, the backbone of E-E-A-T and a signal AI Mode uses when picking expert sources.

🧱 A correct Organization + sameAs block

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "Organization",
 "name": "Acme Analytics",
 "url": "https://acme.example",
 "logo": "https://acme.example/logo.png",
 "sameAs": [
 "https://www.wikidata.org/wiki/Q000000",
 "https://en.wikipedia.org/wiki/Acme_Analytics",
 "https://www.linkedin.com/company/acme-analytics",
 "https://www.crunchbase.com/organization/acme-analytics"
 ]
}
</script>

Every URL in sameAs must genuinely describe the same entity and should, ideally, link back to you, corroboration is mutual.

🗺️ What an entitymap actually looks like

This stays abstract until you see one, so here is a worked example for a fictional company, "Acme Analytics." An entitymap is just a structured statement of the entity, its core attributes, the relationships it has to other entities, and the independent sources that confirm all of it.

That same map, expressed as the JSON-LD you publish on your entity home, with the founder modelled as a linked Person entity:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Analytics",
  "url": "https://acme.example",
  "foundingDate": "2017",
  "location": { "@type": "Place", "address": "Austin, TX" },
  "founder": {
    "@type": "Person",
    "name": "Jane Doe",
    "sameAs": [
      "https://www.linkedin.com/in/janedoe",
      "https://www.wikidata.org/wiki/Q999999"
    ]
  },
  "sameAs": [
    "https://www.wikidata.org/wiki/Q123456",
    "https://en.wikipedia.org/wiki/Acme_Analytics",
    "https://www.linkedin.com/company/acme-analytics",
    "https://www.crunchbase.com/organization/acme-analytics"
  ]
}
</script>

How to create your entitymap, step by step

1. Name the entity precisely. The exact, consistent name you want machines to recognise. One name, used everywhere.
2. List the stable attributes. Founding date, location, industry, and a one-line statement of what you actually do. Facts, not adjectives.
3. Map the relationships. Founders, key people, parent or subsidiary companies, and flagship products. Each important one should ideally be its own entity with its own sameAs.
4. Gather corroborating sources. Create or correct your Wikidata item, claim your LinkedIn and Crunchbase profiles, and make sure they all state the same facts. Agreement is what builds confidence.
5. Express it as JSON-LD on your entity home. Organization (or Person) with sameAs and linked entities, published on the one canonical URL that defines you.
6. Keep it consistent everywhere. Same name, same facts, in your footer, your About page, your profiles, and your markup. Contradictions lower confidence.

What to add, and what to leave out

🎯 The priority order most brands should follow

Entity work has a sequence. Doing it out of order wastes effort:

1. Entity home, pick and harden the one canonical URL that defines you.
2. Wikidata entry, create or correct it; it's the most direct Knowledge-Graph input and is openly editable (with sources).
3. sameAs schema, wire the corroboration links from your entity home.
4. Entity linking, connect mentions across your content to entity homes.
5. Mentions & PR, earn references on sources Google already trusts. This is where the brand-mention signal compounds.

🚧 What entity HTML does not do

Measured expectations, because this is a confidence game, not a switch:

• Schema alone won't manufacture an entity. Declaring Organization with no corroboration is a claim with no witnesses. Without independent agreement, confidence stays low.
• It won't conjure a Knowledge Panel on demand. Panels appear when Google is confident enough, markup helps, but notability and corroboration drive it, and it takes time.
• Faking sameAs backfires. Linking to profiles that aren't really you, or that contradict your other data, lowers confidence instead of raising it.
• It's not instant, and it's not a ranking cheat. Entity confidence accrues as sources align over weeks and months. Treat it as foundational infrastructure, not a campaign.

🔎 How to check your entity

1. Search your brand and see whether a Knowledge Panel appears, that's Google showing you it has a confident entity.
2. Look yourself up on Wikidata. No entry, or a thin/incorrect one, is a direct gap in the Knowledge Graph's primary feed.
3. Validate your schema with the Schema.org validator and Google's Rich Results Test, confirm Organization/Person and sameAs parse.
4. Ask an AI assistant who you are. If it's vague, contradictory, or wrong, your entity isn't resolving cleanly, exactly the gap this work closes.

❓ Entity SEO FAQ