MainEntity

The core function of mainEntity is to resolve ambiguity. On a page containing multiple entities (e.g., a blog post reviewing a Product that also mentions the Organization that makes it), this property identifies the single most prominent subject. This prevents AI models from confusing a supporting mention with the page's actual topic, ensuring the correct entity is indexed and cited in generative overviews.

mainEntity does not define a new entity; it points to an existing one defined elsewhere in the JSON-LD graph. It expects a reference to a full entity node that already has an @type (e.g., Product, Article) and a unique @id.

• Syntax: "mainEntity": {"@id": "#primary-product"}
• Mechanism: This creates a directional link from the WebPage node to the subject node, establishing a clear parent-child relationship in the knowledge graph.

Generative engines use mainEntity to select the definitive source for entity extraction. When an AI model synthesizes an answer, it prioritizes data anchored to the mainEntity of a page.

• Factual Grounding: The property acts as a confidence signal, telling the model that the information within the mainEntity node is the page's authoritative claim.
• Citation Integrity: It reduces the risk of the AI citing a tangential entity mentioned in a sidebar or footer, preserving brand attribution accuracy.

mainEntity is a property of the WebPage type and its subtypes. Its usage is most critical on ItemPage, a schema type specifically designed for pages focused on a single entity.

• WebPage: Use when the page has a primary topic but isn't exclusively about it.
• ItemPage: The strongest signal that the page is entirely dedicated to the mainEntity. This combination is highly effective for product detail pages, recipe pages, and individual event listings.

Schema.org provides a spectrum of properties to define a page's relationship to entities, each with a different semantic weight:

• mainEntity: The primary, most prominent entity.
• about: The general subject matter; less specific and can be a broader topic.
• mentions: A secondary or incidental reference to an entity. Using mainEntity instead of about for the central topic provides a much stronger, machine-readable declaration of focus, directly influencing how knowledge graph nodes are connected.

To ensure correct implementation, validate your structured data using the Schema Markup Validator and Rich Results Test. Key checks include:

• The mainEntity property must reference a valid @id that exists within the same @graph block.
• The referenced entity must have a valid @type.
• A page should have only one mainEntity to avoid confusing parsers.
• Test in Google Search Console to confirm the page is being indexed as the correct entity type.