Definition: What is an entity?
In the SEO and information-retrieval context, an entity is a uniquely identifiable unit that exists as a standalone node inside a knowledge graph. It carries an identifier (URI, Wikidata Q-ID, Schema.org @id), properties (name, type, founding date, industry) and relations to other entities (founder, location, products). The entity perspective displaces the classical document perspective: search engines no longer primarily manage pages but units - and pages are only one of several representations of an entity.
The transition to entity SEO began with Google's Knowledge Graph in 2012 and has become the strategic core topic in the LLM era. Schema.org, launched in 2011 by Google, Microsoft, Yahoo and Yandex, supplies the vocabulary: Organization, Person, Product, Event, Article and hundreds more types. Wikidata provides the structured, open data base from which Google and LLMs seed their initial entity profiles.
LLMs see entities, not pages
Without an anchored entity identity, a brand remains a text fragment. Clean entity signals are the prerequisite for any sustainable GEO strategy and for any Knowledge Panel.
The three pillars of entity anchoring
1. Schema.org markup on your own domain
Structured JSON-LD markup in the <head> of the homepage and the core profile pages is the self-declaration. A brand declares itself as Organization or LocalBusiness with name, URL, logo, founder, contact information and - critically - with a stable @id referenced consistently across all schema blocks on the site. This @id is the internal entity anchor.
2. Wikidata entry as the external anchor
Wikidata is the open knowledge base behind Wikipedia. Every entity there carries a Q-ID (e.g. Q95 for Google LLC). That Q-ID is the most universal entity address in the public web. Google, ChatGPT, Claude and Perplexity all use Wikidata as a training and retrieval source. A Wikidata entry requires notability and external references - promotional entries get deleted. For established companies, authors and subject-matter experts the entry is achievable.
3. sameAs - the cross-reference
The Schema.org property sameAs connects your own entity declaration with external representations: Wikipedia article, Wikidata Q-ID, LinkedIn company page, Crunchbase profile, GitHub organization, official social profiles. Every sameAs link stabilizes attribution and reduces the risk that Google or an LLM treats two related profiles as separate entities. A solid B2B brand typically carries 8-12 sameAs entries.
Example: Organization markup with entity anchors
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example GmbH",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.svg",
"foundingDate": "2008-03-14",
"sameAs": [
"https://en.wikipedia.org/wiki/Example_GmbH",
"https://www.wikidata.org/wiki/Q12345678",
"https://www.linkedin.com/company/example-gmbh/",
"https://www.crunchbase.com/organization/example-gmbh"
]
}
The @id is the central address. Every other schema object on the domain references it: author schema binds publisher to this @id, breadcrumb schema points to the same domain, E-E-A-T signals aggregate onto a consolidated entity.
Measuring and auditing entity health
Entity health is quantitatively measurable. The relevant metrics:
- MSA - Multi-Source Agreement. Share of external sources (Wikipedia, Wikidata, LinkedIn, Crunchbase) that consistently report identical core facts. Target: > 85 percent.
- Knowledge graph presence. Does the entity appear in the Google Knowledge Graph? Test via the Knowledge Graph Search API or branded SERP analysis.
- Knowledge panel. Does a Knowledge Panel show up on a brand search? If yes, the entity is established. If no, Wikidata anchoring or
sameAsdensity is usually missing. - sameAs depth. Number of consistent external profiles that link back to the main domain.
Audit tools: Screaming Frog (extracts schema blocks), Schema.org Validator, Google Rich Results Test, Wikidata's Query Service for consistency checks. For enterprise setups, WordLift and InLinks provide entity-level monitoring.
Typical mistakes in entity strategies
- No stable @id anchor. Each page declares a new
Organizationwithout a shared@id. Consequence: schema fragmentation, no consolidation. A unified@idpattern (/#organization,/#person) is mandatory. - sameAs pointing at dead profiles. Old Xing pages, stale Crunchbase drafts, deleted Facebook pages. Google follows the links and devalues inconsistent references. Quarterly audit of the sameAs list.
- Inconsistent name spellings. "Example GmbH" on the website, "Example GmbH & Co. KG" in the imprint, "ExampleGmbH" on LinkedIn. Divergence weakens MSA.
- Wikidata entry without references. Creating an entry without external secondary sources leads to deletion. Before creating the Wikidata entry, secure at least three independent editorial sources.
- Markup without external endorsement. Self-declaration alone does not produce an entity. Without PR, trade citations and authoritative co-occurrence, the profile remains weak.
Related terms
Entity SEO is tightly linked with Knowledge Graph, Knowledge Panel, sameAs, Wikidata and Schema.org. For AI visibility, the entity base is the prerequisite for any GEO and LLM SEO strategy. E-E-A-T signals aggregate onto a clearly anchored entity.
FAQ on Entity (Schema.org)
What is an entity in the SEO sense? ▾
An entity is a uniquely identifiable unit - a person, organization, place, product or concept. In the SEO context this means: a resource that Google and other systems recognize as a standalone unit, not just a text fragment. Representation happens through Schema.org markup, Wikidata entries and consistent sameAs links.
Why is entity SEO critical for LLMs? ▾
LLMs and retrieval systems operate at the entity level, not at the page level. A clearly anchored entity is referenced reliably during semantic search and generation. Without anchoring, the brand remains a text fragment that is not consistently identified at inference time.
How do I create a Wikidata entry? ▾
Wikidata is an open wiki. Registered users can create entries as long as the entity meets the relevance criteria (external sources, secondary literature). For companies: commercial registry entry, press releases, trade articles. The entry must be supported by references, otherwise it gets deleted.
What does sameAs actually achieve? ▾
sameAs is a Schema.org property that connects an entity to its external representations - Wikipedia, Wikidata, LinkedIn, Crunchbase, MusicBrainz, GitHub. This cross-reference helps search engines reconcile divergent profiles of the same entity and stabilize its position in the entity graph.
Is Schema.org markup alone enough? ▾
No. Markup is necessary but not sufficient. Without external endorsement (Wikidata, PR, authoritative citations) the entity remains a self-claim. Google weights independent sources more than self-declarations. Trust density emerges from external endorsement, not from markup alone.