What Is Entity SEO? Making Your Brand Machine-Readable

Entity SEO is identity work, not keyword work, and the useful way to think about it is this: your own markup is a claim, and everything that makes the claim credible sits on sites you do not control. Google's word for what it does with your Organization markup is disambiguate — and you cannot disambiguate yourself from your own site alone, any more than you can prove who you are by writing your name on a piece of paper.

This guide covers what Google documents that it actually uses, what it says you cannot do, and which parts of this are worth an afternoon rather than a retainer.

What Google says the markup is for

Google's organization structured data documentation, last updated 8 September 2026, states the purpose directly:

"Adding organization structured data to your home page can help Google better understand your organization's administrative details and disambiguate your organization in search results."

Two words are doing the work. Administrative details — the boring facts: legal name, address, contact, identifiers. And disambiguate — separate you from other things with your name. Neither is about ranking a page, which is why entity work belongs in a different budget line from content and links.

The same page is unusually relaxed about what you must include:

"There are no required properties; instead, add the properties that apply to your organization."

So the question is not "have I got all the fields" but "which of these actually pin down who we are".

The properties most sites skip, and why they are the good ones

The list Google supports includes the obvious — name, url, logo, description, address, contactPoint, email, telephone, foundingDate, numberOfEmployees, sameAs — and a second set that almost nobody uses:

legalName, alternateName, duns, leiCode, vatID, taxID, naics, iso6523Code, globalLocationNumber.

That second set is where disambiguation actually happens, because those values are unique by construction. Two companies can share a trading name. They cannot share a VAT number or a D-U-N-S number. If your brand name is common, or you operate under a trading name that differs from your registered one, legalName plus one registry identifier does more for identity than any amount of prose.

This is also the cheapest thing on the list. You already have these numbers; they are on your invoices.

sameAs is a pointer, not a declaration

Google defines it as:

"The URL of a page on another website with additional information about your organization, if applicable. For example, a URL to your organization's profile page on a social media or review site."

Read it as a citation. The value is entirely in the destination existing, being about you, and agreeing with what your site says. A sameAs that resolves to a 404 asserts an identity nobody can check — which is worse than leaving the property out, because the property exists to be followed.

We found exactly that on our own site during an audit: three social URLs in our Organization node, all returning 404 because the accounts had not been created. They came out. They go back the day the accounts exist, and not before.

The practical rule: every sameAs should be a URL you would be happy for a journalist to open.

What you cannot do

This is the part that gets sold and should not be. Google states:

"Knowledge panels are automatically generated, and information that appears in a knowledge panel comes from various sources across the web."

You cannot create one. If a panel already exists and you are the official representative of the entity, you can claim it and suggest changes. A Google Business Profile is a separate product that looks similar and applies to businesses serving customers at a location or within a service area — which is a real and claimable thing, and the subject of our local SEO guide.

So when a proposal offers to "get you a knowledge panel", the honest translation is: produce enough corroborated, consistent information across the web that Google's systems form one. That is a communications outcome with an SEO component, not a markup task, and nobody can promise the date.

The consistency job nobody itemises

Because the evidence lives off your site, the highest-value work is unglamorous: making every mention of you agree.

• One legal name, spelled one way, everywhere it appears — your site, your invoices, your registry entry, your profiles.
• One address format. "8 The Green, Suite A" and "8 The Green Ste A" are the same place to a person and two strings to a machine.
• One canonical URL for the brand, with the rest redirecting to it.
• One description that says the same thing in the same order, so three sources reinforce rather than compete.
• Profiles that exist and are filled in, because an empty profile is a weak citation and a missing one is none.

None of this needs a developer. All of it is the difference between a system that can resolve you confidently and one that has to guess — and a system that guesses sometimes guesses a competitor.

Where this sits relative to AI answers

Entity clarity is frequently sold as the way into AI answers, so it is worth being precise. Google's own generative AI guidance says structured data is not required for generative AI search and there is no special schema.org markup to add. We went through that claim in detail in our llms.txt guide.

What entity work does do is narrower and still worth having: it reduces the chance that an answer about your field attributes your work, your numbers or your position to a company with a similar name. That is an attribution problem rather than a visibility problem, and attribution is the part of generative engine optimization that is actually within your control.

Where we say no

We do not sell knowledge panels, and we will say why in one sentence rather than quoting for it.

We do not add sameAs entries for accounts that do not exist yet, including our own — we removed ours rather than leave three dead URLs asserting identities nobody could verify.

And we do not treat entity markup as a substitute for the thing it describes. Person markup around a byline with no history describes a byline with no history, which is the same point we made about what Google actually rewards.

An afternoon's version

1. Put one Organization node on the home page or the about page, not fifteen copies. Google recommends "your home page, or a single page that describes your organization."
2. Add legalName and one registry identifier. VAT, D-U-N-S or the local equivalent. Unique by construction, and already on your invoices.
3. Open every sameAs URL. Anything that 404s comes out today.
4. Fix the name and address spelling across your site, your profiles and your registry entry until all three match character for character.
5. Claim what is claimable. A Business Profile if you serve a location; an existing knowledge panel if one already exists.

If you want this checked against what Google currently documents rather than against a checklist someone wrote in 2021, send us the domain and we will tell you which of the five is actually missing.