FIRST — WHAT IS AN ENTITY?
An entity is a distinct, identifiable thing. A person, an organisation, a place, a product, a book, an event, a concept — anything that can be pointed at and named as a specific, well-defined "it."
- Person — Ricky Whiting
- Organisation — Webstudio.Marketing
- Place — Brighton, UK
- Product — a specific book or service
- Book — a published title
- Event — a conference or keynote
- Concept — a topic like "local search" or "content authority"
The reason this matters: modern search increasingly works at the level of entities, not just the words on a page. A search system is trying to understand what a page is about — the actual thing — not just which words appear how many times.
KEYWORDS VS ENTITIES
This is the distinction at the heart of entity SEO, and it is worth making sharply.
- A keyword is a word or phrase that appears on a page. It is a string of characters.
- An entity is the actual, identifiable thing those words refer to. It is a concept with a real-world referent.
A page can use the word "apple" ten times. That tells a search engine the string "apple" is present. It does not, by itself, tell the engine whether the page is about the fruit or the company. Meaning depends on context.
What modern search systems do — and what AI systems do — is use surrounding context and relationships to disambiguate. If the page links to a page about iPhones, mentions Tim Cook, and sits on a domain about technology, the system has good reason to decide "apple" means the company. If it links to recipes and mentions orchards, it has good reason to decide it means the fruit.
That process — using context and relationships to pin down meaning — is exactly what entity SEO is trying to make easier. You are giving the machine less work to do, and fewer chances to get it wrong.
WHY DO ENTITIES MATTER TO SEARCH?
Several reasons, and I want to be careful not to overclaim on any of them:
- Understanding. Entities help a search system understand what a page is actually about, beyond surface keywords.
- Disambiguation. They let the system tell apart things that share a name — a person, a place, a brand.
- Relationships. Entities can be connected: a person founded a company, an author wrote a book, an organisation serves a location. Those relationships carry meaning.
- Knowledge graphs. Many search systems build structured representations of entities and their relationships. Being a clear, well-connected entity increases the chance of being understood correctly.
- Context. Entities place a page within a broader topic and set of relationships, which helps relevance.
- Authority. Being recognised as a credible, well-referenced entity for a topic is a form of authority — and it is increasingly how authority is assessed.
I am not saying entities cause rankings in a simple, direct way. I am saying the work of being clear about your entities makes it more likely a search or AI system understands you correctly — which is the precondition for being surfaced at all.
A REAL ENTITY SEO EXAMPLE
This is where it helps to use an actual site rather than a hypothetical. Let's use this one.
RickyWhiting.com has a defined, canonical entity architecture. The central Person entity — me — lives at a specific, stable identifier:
Canonical Person:
https://www.rickywhiting.com/#person
From that one node, a set of real, verifiable relationships extend:
- Ricky Whiting → founder of → Webstudio.Marketing
- Ricky Whiting → author of → Books
- Ricky Whiting → author of → Articles (this one included)
- Ricky Whiting → speaker at → Speaking events
- Ricky Whiting → sameAs → verified public profiles (LinkedIn, Amazon author pages, and others that genuinely represent the same person)
These are not invented relationships. They are real, and they are corroborated: the site states them, the structured data describes them, and the external profiles confirm them. That corroboration — the same facts appearing in more than one trustworthy place — is what makes entity information credible rather than just asserted.
The principle generalises. Whatever your business is, the same logic applies: identify the core entities, state the real relationships between them, and make sure those statements are consistent and corroborated across your site and the wider web.
WHAT ROLE DOES SCHEMA MARKUP PLAY?
Schema markup (structured data) is a way of making explicit statements about entities and their relationships. A Person schema can say this is a person, here is their name, their job, and the organisation they founded. An Organization schema can describe a business. A Book schema can describe a published title.
That is genuinely useful. It reduces the guesswork a machine has to do, and it states relationships in a machine-readable format.
But here is the principle I keep coming back to:
Schema doesn't create authority. It helps describe it.
If the schema accurately reflects a real, corroborated, well-referenced entity, it helps. If the schema claims relationships the content and the wider web don't support — if it invents expertise or manufactures connections — it doesn't help, and it can undermine trust. Schema should describe reality, not manufacture it.
The same applies to entity SEO more broadly: it is about making real things clearer, not about inventing signals.
Person
RICKY WHITING
WEBSTUDIO.MARKETING
Organisation
BOOKS
Authored works
ARTICLES
Authored content
SPEAKING
Speaker events
VERIFIED PROFILES
sameAs
An educational diagram of real, verifiable relationships on this site — the same principle applies to your business, people and products.
WHAT IS A KNOWLEDGE GRAPH?
A knowledge graph is a structured representation of entities and the relationships between them. Think of it as a web of nodes (the entities) connected by edges (the relationships), where the meaning lives in the connections.
Search engines build their own knowledge graphs to organise what they know about the world. AI systems draw on similar structured representations to reason about entities and context.
Here is what I am not claiming: I am not claiming that by adding schema you control Google's Knowledge Graph, or that you can "get into" a knowledge graph on demand. You can't. What you can do is make your entities clear, consistent and corroborated enough that the systems building those graphs are more likely to understand you correctly.
Entity SEO is the work of being understood. The knowledge graph is where that understanding, when it succeeds, gets represented.
DOES ENTITY SEO HELP WITH AI SEARCH?
Yes, probably — with the usual caveats.
Clear, consistent entity information can make it easier for machine systems — including AI search — to understand who and what your content refers to, and how it connects. That is a real benefit. If an AI system can correctly identify your business, its people and its expertise, it is more likely to represent you accurately when it answers.
But clear entities do not guarantee:
- AI citation (being named in an answer)
- AI inclusion (being part of a summary at all)
- A specific ranking
- A Knowledge Panel appearing for your brand
These things depend on the platform, the query, the retrieval, and factors outside any site owner's control. What entity SEO does is improve the conditions for being understood correctly — which is the best lever available, even if it isn't a guarantee.
For the broader picture, see what is AI SEO?
HOW TO IMPROVE ENTITY CLARITY
This is the practical part. Here is what genuinely helps:
- Consistent identity. Use the same name, role and description across your site and the web.
- Clear About information. An About page that actually says who you are and what you do — not a press release.
- Structured data. Accurate schema (Person, Organization, Article) that reflects reality.
- Author information. Attach real authors to articles, with their own credible presence.
- Organisation relationships. Make the relationships between people, brands and entities explicit.
- Verified profiles. Link to genuine, controlled profiles (LinkedIn, etc.) — not random mentions.
- Consistent references. Use the same descriptions and identifiers where you can.
- Relevant external mentions. Be referenced credibly elsewhere on the web.
- Clear topical expertise. Build genuine, useful coverage of the topics you want to be known for.
- Internal linking. Connect related content so the relationships are visible to crawlers.
What does not help — and I would actively avoid — is spammy entity stacking: dumping every possible entity and relationship into schema in the hope something sticks. If it doesn't reflect reality, it is noise at best and a trust signal at worst.
ENTITY SEO CHECKLIST
A short, honest version:
- [ ] Is there a clear, central entity (person or organisation) the site is about?
- [ ] Is that entity described consistently on the site and across the web?
- [ ] Does structured data accurately describe the entity and its relationships?
- [ ] Are the relationships (founder, author, serves, sameAs) real and verifiable?
- [ ] Are external profiles genuine and controlled by the entity?
- [ ] Is the entity's expertise demonstrated through real, useful content?
- [ ] Is related content internally linked so relationships are discoverable?
- [ ] Would a machine reading the site understand who you are without guessing?
If you can answer those honestly, you have a clearer picture of your entity SEO than most keyword-stuffing tools will give you.
How clearly does your website explain who you are?
Enter your site and I'll review how clearly it communicates its expertise, entities, content and search foundations — and where I'd look first.


