Schema.org MainEntity

mainEntity acts as the ultimate tie-breaker when other on-page signals contradict each other. It establishes a strict hierarchy for topical authority.

• Override Mechanism: If a page's <title> is broad but the mainEntity specifies a specific Product, the structured data takes precedence for entity extraction.
• Canonical Conflict Prevention: Ensures that a page about a specific entity model does not get indexed as a generic category page.
• Crawl Budget Efficiency: By immediately signaling the page's exact purpose, it prevents search bots from misinterpreting and wasting crawl budget on misclassified content.

The owl:sameAs property asserts that two different URIs refer to the identical real-world entity. When combined with MainEntity, it provides a machine-readable equivalence map across knowledge bases.

• Links a page's primary entity to external authorities like Wikidata Q-IDs or DBpedia
• Resolves identity fragmentation when an organization has multiple web presences
• Critical for entity reconciliation in Google's Knowledge Graph

Example: A company page with MainEntity pointing to its local schema can use sameAs to link to its Wikidata entry, confirming both describe the same organization.

The computational process of identifying and merging disparate records that refer to the same real-world entity. MainEntity provides the explicit signal that simplifies this otherwise probabilistic task.

• Eliminates ambiguity when a page mentions multiple entities
• Uses techniques like fuzzy matching and transitive closure to cluster references
• Reduces the need for coreference resolution by declaring the primary subject upfront

Without MainEntity, search engines must infer the page's topic from context, risking misattribution of authority signals to secondary entities mentioned in body text.

A persistent, non-ambiguous identifier—such as a Wikidata Q-ID or Google Knowledge Graph MID—that serves as the canonical reference for an entity across all semantic systems.

• MainEntity acts as the bridge between a webpage and its corresponding graph node
• Enables graph merging by providing a stable anchor point for identity alignment
• Prevents canonical conflict where multiple URLs claim to represent the same entity

Best practice: Pair MainEntity with an @id attribute using a stable URI that matches your organization's entry in authoritative knowledge bases.

The single, authoritative version of an entity's data created after deduplication and conflict resolution. MainEntity designates which page-level representation should be treated as the golden record for search indexing.

• Applies survivorship rules to select the best values from conflicting sources
• Consolidates link equity and authority signals to one definitive URL
• Prevents dilution of ranking power across duplicate or near-duplicate pages

When multiple pages describe the same entity, the one with properly implemented MainEntity markup signals to crawlers that it is the preferred canonical source for knowledge extraction.

The NLP task of identifying all expressions in a text that refer to the same entity—such as pronouns, acronyms, and aliases. MainEntity pre-resolves the primary referent, reducing the computational burden on parsers.

• Explicitly declares 'this page is about X' before any linguistic analysis begins
• Prevents confusion when an entity is referenced by multiple names in body content
• Improves accuracy of information extraction pipelines that populate knowledge graphs

Example: A page about 'International Business Machines' can use MainEntity to clarify that mentions of 'IBM' and 'Big Blue' all refer to the same canonical organization.

A controlled vocabulary of preferred names and identifiers used by libraries and databases to ensure consistent entity representation. MainEntity functions as a web-scale authority file declaration embedded directly in page markup.

• Mirrors the function of Library of Congress Authority Records for the open web
• Establishes a single canonical heading for entities with multiple name variants
• Supports Unicode normalization by linking all orthographic variations to one identifier

Implementing MainEntity with a stable, resolvable URI creates a self-maintaining authority record that search engines can reference for disambiguation across the entire crawl corpus.