intermediate7 min read·Foundations

Entity Basics for AEO

Entities are the named things - people, places, concepts, organizations - that Knowledge Graph and LLMs rely on to understand your content.

Level:

An entity is any real-world thing with a distinct identity: a person, company, product, place, or concept. Google does not just match keywords; it recognises entities and builds relationships between them in a Knowledge Graph. When your brand becomes a recognised entity, AI search can answer questions about you accurately. Read our Introduction to AEO to see where entities fit in the bigger picture.

How Google Builds an Entity Graph

Google does not store every statement on every page. It extracts and stores entity relationships that can then answer future queries without re-reading source content. The entity graph grows incrementally as Google reads more about your brand, products, and people across the web.

Entity Graph Visualisation

Watch how Google builds an entity graph from connected facts. Hit Play or step manually.

Isolated keyword:Without entity context, a keyword is ambiguous. 'Sage' could mean software, a herb, or a person.
1/5

Entity Types and Their AEO Relevance

Different entity types require different optimisation strategies. Select a type to see the specific AEO relevance, typical examples, and recommended schema markup.

Entity Types and AEO Relevance

Examples: Companies, NGOs, government bodies, educational institutions
AEO Relevance: Building brand entity recognition requires consistent NAP citations, Wikipedia presence, and structured mentions across authoritative sites.
Relevant Schema: Organization, LocalBusiness, Corporation

Entity-First vs. Keyword-First Search

The shift from keyword-matching to entity-understanding changes how you should write and structure content. The key differences:

Query handling

Keyword: Exact string match. 'Apple' returns results about the fruit AND the tech company.

Entity: Disambiguation. 'Apple' in a technology context is resolved to the Apple Inc. entity.

Variation tolerance

Keyword: Different keywords need separate optimisation. 'NYC' and 'New York City' are different targets.

Entity: All variants resolve to the same entity. One entity-strong page covers all query variants.

Cross-source synthesis

Keyword: Each page is evaluated independently.

Entity: Entity attributes from many pages are combined into a single entity profile used for AI answers.

Content requirement

Keyword: Target keyword must appear on the page.

Entity: Entity must be consistently referenced by canonical name and disambiguated by co-occurring entities (industry, location, category).

Entity Readiness Checklist

Work through this checklist to assess how well your brand, content, and structured data support entity recognition across Google's systems.

Entity Readiness Checklist

0/8

Frequently Asked Questions

Related Topics