Entity-based SEO is the discipline of optimising content around the things a piece of content is about – the people, places, organisations, products, concepts, and events that search engines and AI systems recognise as discrete identifiable nodes – rather than the keywords used to describe them. Where classical SEO treated the query string and its synonyms as the unit of optimisation, entity-based SEO treats the underlying real-world thing as the unit and asks how clearly the content connects to that thing in machine-readable form. This shift has been underway since Google’s Knowledge Graph launched in 2012 and accelerated through the 2020s as AI-powered ranking and answer systems became increasingly entity-aware.<\/p>\n
This article walks through what an entity is in the SEO sense, why search and answer engines moved toward entity-based understanding, what role Wikipedia, Wikidata, and the sameAs property play, and what entity-based optimisation looks like in practice. The framing is definitional – the goal is to give a reader a working mental model of what entity-based SEO means and how it differs from keyword-centric SEO.<\/p>\n<\/p>\n
An entity, in the SEO and information-retrieval sense, is a uniquely identifiable thing that exists in the world and can be referred to. The classic definition from Google’s early Knowledge Graph documentation describes entities as ‘people, places, things, and concepts’ – the named nouns that search queries and content are usually about. What makes an entity distinct from a keyword is identity: ‘apple’ as a string is ambiguous, but the entity ‘Apple Inc. (the technology company headquartered in Cupertino)’ has a single identity, a stable Wikidata QID (Q312), and a Knowledge Graph machine ID. The entity is the thing; the keyword is one of many strings that might refer to the thing.<\/p>\n
Entities have properties (founding date, headquarters location, founders, products) and relationships to other entities (Steve Jobs is a founder of Apple Inc.; Apple Inc. is the parent of Apple Music). These properties and relationships form a knowledge graph – a structured representation of how things in the world connect. Search engines and AI systems use these graphs to disambiguate queries, to enrich answers, and to verify that a candidate source is actually about the entity the query is asking about. A page that talks about ‘apple’ without any signal indicating which apple – the company, the fruit, or the record label – is structurally weaker as a candidate for citation than a page that makes the entity explicit.<\/p>\n<\/p>\n
The motivation for the shift from keyword-centric to entity-centric understanding is disambiguation and depth. Keyword matching, the foundation of classical search, is brittle in the face of synonyms, paraphrases, multilingual variants, and ambiguity. A query for ‘Singapore best hawker food’ and a page titled ‘Top hawker dishes in Singapore’ are about the same thing but match poorly on string overlap; a page about ‘apple’ could be about the company, the fruit, or the band. Entity-based understanding solves both problems at once – the query and the page are mapped to the underlying entities they are about, and the match is made at the entity level rather than the string level.<\/p>\n
The historical milestones are well-documented. Google launched the Knowledge Graph in May 2012 with the explicit framing of ‘things, not strings’. The Hummingbird algorithm update in 2013 deepened the use of entity understanding for query interpretation. RankBrain in 2015 and BERT in 2019 added neural-network-based language understanding that reinforced entity-aware retrieval. By the time AI Overviews and AI answer engines became prominent in 2024-2026, the underlying retrieval stack was entity-aware end-to-end. The implication for SEO is that pages whose entity signals are explicit and consistent are easier for these systems to match, retrieve, and cite than pages that rely on string matching alone.<\/p>\n<\/p>\n
Three external knowledge bases anchor most of the entity work that matters for SEO: Wikipedia, Wikidata, and Google’s own Knowledge Graph. Wikipedia is the most visible – the canonical encyclopaedic article about an entity in human-readable form, with a stable URL that often serves as the de facto identifier. Wikidata is the structured-data sibling of Wikipedia, holding the same entities as machine-readable items with QIDs, properties, and relationships. The Google Knowledge Graph draws on Wikipedia and Wikidata heavily, alongside other curated sources, to populate Knowledge Panels and to inform entity-aware ranking.<\/p>\n
The schema.org sameAs property is the primary mechanism through which a website asserts the identity of itself or a subject it describes by linking to authoritative external references. An Organization schema block on a company website includes a sameAs array linking to the company’s Wikipedia page, Wikidata item, LinkedIn page, Crunchbase profile, and other canonical references. This explicit linking tells search engines and AI systems ‘this website is the entity at these external identifiers’ and resolves the ambiguity that string-based matching alone cannot. The same mechanism applies to Person entities (linking authors to their professional profiles, Wikipedia pages, Wikidata items where they exist) and to Product, Place, and Event entities.<\/p>\n<\/p>\n
AI answer engines extract entities from two places: the user’s query and the candidate sources retrieved for that query. On the query side, the engine parses the query to identify the entities being asked about – ‘who founded SpaceX’ resolves to the entity SpaceX and the relationship founded-by, ‘best hawker centres in Singapore’ resolves to the entity Singapore and the concept hawker centre. On the source side, the engine extracts the entities each candidate page is about and matches them to the query entities. A source whose entity signals are explicit and unambiguous is easier to match; a source whose entities are implicit, ambiguous, or inconsistent is harder.<\/p>\n
The practical consequence is that entity signals influence both retrieval and citation. Retrieval – whether a page is among the candidates the engine considers for a query – depends partly on whether the engine can identify the page as being about the relevant entities. Citation – whether the engine actually quotes or attributes to the page in its answer – depends partly on whether the page’s entity claims are verifiable against the engine’s knowledge graph. A site whose Organization schema, sameAs links, author entities, and on-page entity references are coherent and verifiable performs better on both dimensions than a site whose entity signals are weak or contradictory. Entity-based SEO is the discipline of making those signals coherent.<\/p>\n<\/p>\n
Practical entity-based SEO begins with an inventory: identify the entities the site is associated with – the publishing organisation itself, the authors who write for it, the products or services it describes, the places it operates in, the topical concepts it claims expertise on. For each entity, ask whether it exists in Wikidata or a comparable knowledge base, whether the site’s references to that entity are consistent, and whether the schema markup on the site links the entity to its external identifiers via sameAs.<\/p>\n
The most common workstreams are Organization-level (Organization schema with sameAs to LinkedIn, Crunchbase, Wikipedia\/Wikidata where applicable, and consistent NAP across the web), Person-level (Person schema for authors with sameAs to their professional profiles, author bios that establish credibility, consistent author identity across platforms), and topical-entity-level (on-page entity references that are explicit and disambiguating, internal linking that reinforces topical entity associations, content that demonstrably covers the entity’s properties and relationships rather than just mentioning the keyword). For organisations notable enough to warrant Wikipedia entries but not yet covered, the path involves earning the kind of independent press and authoritative reference that Wikipedia editors require – not direct page creation, which violates conflict-of-interest policy. For organisations not yet notable enough for Wikipedia, Wikidata items can be created independently and are a useful first step. The thread connecting all of these workstreams is the same: make the entity identity of the site, the authors, and the subjects explicit and verifiable, so that entity-aware search and AI systems can recognise, trust, and cite the content.<\/p>\n<\/p>\n
Entity-based SEO is the practice of optimising content around the things it is about rather than around the keyword strings used to describe them. It rests on the recognition that search engines and AI answer engines have moved from string-matching to entity-aware retrieval, that the disambiguation and verification of entities materially affects which sources are retrieved and cited, and that the mechanisms for asserting entity identity (Wikipedia, Wikidata, schema sameAs links, consistent on-page references) are publicly available to any site willing to invest in the work.<\/p>\n
The framing to take away is that entity-based SEO is not a replacement for keyword-aware content – it is an additional layer that makes the entity identity of the site, the authors, and the subjects explicit and verifiable. Sites whose entity signals are coherent are easier for entity-aware systems to recognise, trust, and cite. The practical investment is moderate, the conceptual shift is meaningful, and the trajectory of search and AI retrieval points firmly in the direction of entity-aware understanding becoming the default. Optimising for entities is increasingly the same thing as optimising for visibility.<\/p>\n<\/p>\n
The terms overlap heavily and are often used interchangeably. Semantic SEO is the broader umbrella – optimising content for meaning rather than for keyword strings, which includes entity understanding, topical depth, related-concept coverage, and natural-language structure. Entity-based SEO is the specific subset focused on the entity layer – identifying the things a piece of content is about, connecting them to known entities, and reinforcing those connections through schema and consistent references. Most semantic SEO programmes include entity work as a core component; most entity-based SEO programmes operate within a semantic SEO framing.<\/p>\n<\/div>\n<\/details>\n No, although a Wikipedia entry materially strengthens the entity profile of an organisation or person notable enough to warrant one. For organisations not yet notable enough for Wikipedia, the practical path involves Wikidata (which has a lower notability threshold), consistent Organization schema with sameAs links to authoritative external profiles (LinkedIn, Crunchbase, industry directories), and the kind of independent third-party coverage that builds the entity’s verifiability over time. Entity-based SEO is meaningful at every level of brand maturity; Wikipedia is one signal among many, not a prerequisite.<\/p>\n<\/div>\n<\/details>\n sameAs is a schema.org property used inside an entity’s structured data to link to external pages that represent the same entity. For an Organization, sameAs typically points to the organisation’s Wikipedia page, Wikidata item, LinkedIn company page, Crunchbase profile, and other canonical external references. The property tells search engines and AI systems that the entity described in the schema is the same entity as the one at the linked URLs, which reinforces the entity identity and improves the chance of correct disambiguation in entity-aware retrieval and answer systems.<\/p>\n<\/div>\n<\/details>\n The starting points are the obvious ones – the publishing organisation, the named authors, the products or services described, the locations served. Beyond those, the topical entities can be identified by analysing the content itself for the named concepts that recur (industries, technologies, methodologies, named frameworks) and by examining how search engines currently associate the site with topical entities through tools that surface entity-level data. The Knowledge Graph API, third-party entity-extraction tools, and manual review of how Google’s Knowledge Panel and AI Overview surfaces treat the site are all useful inputs to building an entity inventory.<\/p>\n<\/div>\n<\/details>\n No – it reframes it. Keyword research remains useful as a way to understand the language users actually employ when looking for the entities and concepts a site covers. What changes is that the keyword is treated as a signal of the underlying entity or intent, not as the unit of optimisation in itself. A site doing entity-based SEO still researches what users search for; it then maps those queries to the underlying entities and optimises content around the entities, with the keyword strings serving as the natural-language surface that humans use to express the entity-level intent.<\/p>\n<\/div>\n<\/details>\n If you want to map the entity landscape around your brand and identify where the most important entity work would sit, we are glad to talk it through. Enquire now<\/a> for an entity-SEO conversation.<\/p>\n<\/div>\nDo I need a Wikipedia page to do entity-based SEO?<\/summary>\n
What is the schema.org sameAs property?<\/summary>\n
How do I know what entities are associated with my site?<\/summary>\n
Does entity-based SEO replace keyword research?<\/summary>\n