1. Definition
Within Advanced Schema.org implementation for Generative Engine Optimization (GEO), the correct usage of the mentions and about properties is critical for defining Entity Relationships and signaling factual authority to Large Language Models (LLMs). These properties tell the LLM exactly what the content is truly about and which other entities are simply referenced or cited.
| Property | Definition for GEO | LLM Interpretation |
about Property | Defines the primary, central Entity or topic of the page. | “This document is an authoritative source on X.” (High Information Gain and Topical Authority signal). |
mentions Property | Defines secondary Entities that are referenced, cited, or related, but are not the main focus. | “This document cites Y but is not an authoritative source on it.” (Low Authority signal; context only). |
2. The Mechanics: Entity Resolution and Signal Weighting
The correct use of about vs. mentions prevents the Retrieval-Augmented Generation (RAG) system from confusing a tangential reference with the page’s core subject matter.
Entity Resolution for about
When an LLM sees a Schema.org block defining an article or WebPage with an about property, it assigns a high weighting to the facts presented regarding that entity.
- Example: On a page reviewing the “Tesla Model 3,” the Schema block should use
about:Productfor “Tesla Model 3.” - LLM Action: The LLM uses this page to ground facts about the “Tesla Model 3.”
Entity Resolution for mentions
When an LLM sees a mentions property, it treats the entity as part of the supporting evidence or comparative context.
- Example: On the same “Tesla Model 3” review page, competitors like the “Hyundai Ioniq 6” should be defined with the
mentionsproperty. - LLM Action: The LLM knows the page discusses the “Hyundai Ioniq 6” but will rely on other pages defined with
aboutfor authoritative facts about the Hyundai.
Consequences of Misuse
If a page primarily about the “Tesla Model 3” incorrectly uses about for the “Hyundai Ioniq 6” as well, the LLM’s Topical Authority score for the primary page is diluted, confusing its entity-mapping.
3. Implementation Strategy for GEO
GEO requires a strict, one-to-one relationship between the page’s primary focus and its about property.
Focus 1: Single Primary Entity
- Rule: A high-authority, citable page should generally define only one primary entity using the
aboutproperty. - Action: If a page discusses two equal-priority entities (e.g., a “Product Comparison” page), the
aboutproperty should be assigned to the concept or category itself (e.g.,about:Categoryorabout:Comparison), and the individual products should be relegated tomentions.
Focus 2: Citing External Authorities
When citing external sources, competitors, or third-party organizations, these entities should almost always be marked with the mentions property.
- Rationale: This signals to the LLM that the brand is aware of the external entity, but the brand’s page is not an authoritative source for the external entity’s facts. This preserves the brand’s Citation Trust Score for its own claims.
Focus 3: The mainEntity Attribute
In complex Schema implementations, the mainEntity attribute (which should only be used once per page) is often used in conjunction with about to clearly identify the single, most important entity on the page, reinforcing the LLM’s high-confidence scoring.
Best Practice Summary:
$$\text{Schema.org `about`} \implies \text{This is my source of truth.}$$
$$\text{Schema.org `mentions`} \implies \text{This is supporting context.}$$
By accurately defining this relationship, AppearMore ensures that clients’ content is correctly mapped to their core entities, maximizing their Topical Authority in the generative index.