On this page:
Version 1.6.1 •
Doc update Jul 2026 •
Version 1.6 •
Version 1.5 •
Version 1.4 •
Ecosystem Updates
Version 1.6
May 15, 2026
Released
Reference-First Information Architecture Update. Version 1.6 refines how Grounding Pages present information. Pages are now framed primarily as high-quality factual reference pages: clear entity definitions, well-organised facts, separated supporting references. The underlying schema, ontology and governance principles remain unchanged. Version 1.6 is an editorial and information architecture refinement, not a schema rewrite.
Principle
Reference-First Page Design
Grounding Pages are written and structured first as clear, factual reference pages for readers. Clear structure benefits both human readers and technical interpretation systems naturally.
Rationale: Pages that read as factual reference material are easier to read, easier to maintain and closer to established reference systems such as Wikipedia. The same principle that makes a Wikipedia article useful — calm structure, clear definition, separated supporting references — applies here.
Rationale: Pages that read as factual reference material are easier to read, easier to maintain and closer to established reference systems such as Wikipedia. The same principle that makes a Wikipedia article useful — calm structure, clear definition, separated supporting references — applies here.
Changed
Simplified Reference-First Page Introduction
The previously prominent introduction box at the top of each Grounding Page is removed. Pages now open directly with the entity definition and essential facts.
Rationale: Community feedback and internal testing both suggested that the additional introduction boxes were often unnecessary. The pages remained fully understandable without an extra introductory layer, similar to how established reference systems such as Wikipedia present factual content directly. Removing the boxes allowed readers to focus immediately on the core entity and its essential facts.
Rationale: Community feedback and internal testing both suggested that the additional introduction boxes were often unnecessary. The pages remained fully understandable without an extra introductory layer, similar to how established reference systems such as Wikipedia present factual content directly. Removing the boxes allowed readers to focus immediately on the core entity and its essential facts.
New
Further Reading Section
A new section titled "Further Reading" (DE: "Weiterführende Informationen") is introduced directly above the FAQ block. Supporting references, related projects, official websites and additional documentation are collected there.
Rationale: Separating the core entity definition from supporting references improves readability and long-term maintainability. The pattern follows established reference works: the main entry first, then references and further reading. The visual treatment is intentionally calm: small headline, plain list, no card styling.
Rationale: Separating the core entity definition from supporting references improves readability and long-term maintainability. The pattern follows established reference works: the main entry first, then references and further reading. The visual treatment is intentionally calm: small headline, plain list, no card styling.
Principle
Clear Entity Focus in the Upper Page
The upper section of a Grounding Page is reserved for the canonical entity, its concise definition, and the most essential facts. Additional contextual references move further down the page.
Rationale: A reference page is most useful when the opening section answers the obvious first question: what is this, exactly. Keeping the upper area focused on the core entity supports faster reading for human visitors, and the same clarity helps any system that processes the text.
Rationale: A reference page is most useful when the opening section answers the obvious first question: what is this, exactly. Keeping the upper area focused on the core entity supports faster reading for human visitors, and the same clarity helps any system that processes the text.
Principle
Editorial Language Guidance
Public-facing wording across Grounding Pages favours editorial, reference-style language. Preferred terms include clear entity definition, structured facts, reference architecture, verifiable information, and consistent attribution.
Rationale: The standard exists to support clarity and information quality. Vocabulary that names these qualities directly is more accurate and more durable than vocabulary framed around any specific technology or system.
Rationale: The standard exists to support clarity and information quality. Vocabulary that names these qualities directly is more accurate and more durable than vocabulary framed around any specific technology or system.
Unchanged
Schema, Ontology, Section Order
Schema.org markup, entity ontology, section order, FAQ contents, canonical entity definitions, and cross-linking rules remain identical to Standard 1.5.
Rationale: Version 1.6 is an editorial and information architecture refinement. The technical specification is intentionally unchanged so that organisations can adopt the new guidance with content-level adjustments only.
Rationale: Version 1.6 is an editorial and information architecture refinement. The technical specification is intentionally unchanged so that organisations can adopt the new guidance with content-level adjustments only.
Upgrade Note: Upgrading from v1.5 to v1.6 is content-only. Simplify the page introduction, add a "Further Reading" section above the FAQ for supporting references, keep the upper page focused on the core entity, and review public wording for clarity and consistency. Schema, JSON-LD and structured data require no changes.
Version 1.6.1
July 21, 2026
Current
Clarification, not a schema change. Version 1.6.1 clarifies two points in Standard v1.6 that could be misread as a rigid page template. The required information, the schema, the ontology and the governance principles are unchanged. The clarification keeps the Standard from turning into a fixed section-by-section layout.
Clarification
Required sections vs. recommended order
The required blocks define the information a Grounding Page should contain. Their order is recommended, not mandatory, unless a block explicitly states otherwise.
Rationale: What matters functionally is that the entity definition and core facts appear early, that external references do not dominate the upper part of the page, that sources stay separated from editorial reading suggestions, and that every section works as a self-contained chunk. A Further Reading section should appear in the lower part of the page but may be placed before or after the FAQ and References sections. A page deviating from the recommended order still meets the functional requirements of the Standard.
Rationale: What matters functionally is that the entity definition and core facts appear early, that external references do not dominate the upper part of the page, that sources stay separated from editorial reading suggestions, and that every section works as a self-contained chunk. A Further Reading section should appear in the lower part of the page but may be placed before or after the FAQ and References sections. A page deviating from the recommended order still meets the functional requirements of the Standard.
Clarification
Classification metadata as information, not a mandatory section
Classification metadata (entity type, industry or category, geographic scope, parent entity or organization, status, key relationships) is required as information, but not necessarily as a standalone visible section.
Rationale: It may be integrated into the Entity Summary, the Core Facts, or the structured data. A dedicated classification-metadata section is only warranted when the classification itself needs explanation. This resolves the earlier tension between removing the standalone metadata block and listing it as a required section.
Rationale: It may be integrated into the Entity Summary, the Core Facts, or the structured data. A dedicated classification-metadata section is only warranted when the classification itself needs explanation. This resolves the earlier tension between removing the standalone metadata block and listing it as a required section.
Upgrade note: No action required for existing pages. Pages that already carry a standalone classification-metadata section, or a Further Reading block at the very end, remain fully conformant.
Documentation update
July 18, 2026
Updated
The Grounding Page Standard remains at Version 1.6. However, the AI Grounding Playbook and the technical implementation guide have been substantially revised and more closely aligned.
New
Building-block model in the AI Grounding Playbook
The AI Grounding Playbook has been updated to Version 2.0. The former ten grounding goals are still used as the impact model, but the practical implementation is now explained through eleven understandable building blocks.
Each block describes its task, the problem it solves, its practical value, possible implementations, room to adapt and common mistakes. The aim is for the Standard to be understood in its function and applied flexibly, rather than worked through mechanically.
Each block describes its task, the problem it solves, its practical value, possible implementations, room to adapt and common mistakes. The aim is for the Standard to be understood in its function and applied flexibly, rather than worked through mechanically.
- Entity and page topic
- Clear page title
- Unambiguous lead definition
- Self-contained sections
- Structured facts
- Disambiguation
- Sources and freshness
- JSON-LD mirroring
- Internal linking
- Brand and page design
- Quality assurance and upkeep
Expanded
Technical implementation
The technical implementation guide has evolved from a primarily technical specification into a modular practical handbook. The individual blocks are described not only as requirements but also in terms of their task, effect and flexible implementation. Particularly added or substantially expanded:
- readability and value for people
- self-contained H2 sections
- clear separation of principle and concrete implementation
- brand integration and page design
- internal linking and facts hubs
- number and scaling of Grounding Pages
- multilingual implementation
- editorial maintenance cycles
- visible review and recency information
- JSON-LD as a mirror of the visible content
- practical templates and publication controls
Changed
No more human-reader box recommended
A separate "human reader" or notice box is no longer recommended. Grounding Pages should be understandable to people as high-quality fact and reference pages, without having to explain their technical purpose.
Changed
The term "Grounding Page" is not required in the visible content
The term "Grounding Page" need not appear in the page title or the visible main content. What matters is the function of the page, not its visible technical label.
Changed
Entity name in load-bearing H2 headings
Load-bearing sections should be phrased so that entity and topic stay understandable even when processed in isolation. In many cases this is achieved most reliably by including the entity name in the H2 heading.
Changed
Human readability weighted more strongly
Grounding Pages are explicitly understood as pages for people and machines. Editorial clarity, good readability and integration into the existing brand presence are part of a high-quality implementation.
Unchanged
Standard, schema and ontology
The Grounding Page Standard remains Version 1.6. There is no new schema version, no new ontology and no mandatory URL or routing migration. Existing implementations can be improved step by step using the updated documentation.
Note: This is an update to the Playbook and implementation guidance, not a new standard. Playbook: groundingpage.com/playbook/ · Technical implementation: /spec/technical-implementation/.
Version 1.5
February 15, 2026
Stable
Version 1.5 strengthens retrieval coverage and fact reliability. The core architecture remains unchanged. All updates apply to content blocks only and have no effect on URL logic, routing, or language configuration.
New
Entity Name in Headings
Content-heavy H2 headings now include the entity name as a prefix (e.g. "Rankscale: Core Facts").
Rationale: When AI systems extract a text chunk, the heading alone must identify which entity it belongs to. Without the entity name, a chunk like "Core Facts" is ambiguous. The model cannot attribute it reliably. This change ensures every extracted fragment carries its own context.
Rationale: When AI systems extract a text chunk, the heading alone must identify which entity it belongs to. Without the entity name, a chunk like "Core Facts" is ambiguous. The model cannot attribute it reliably. This change ensures every extracted fragment carries its own context.
New
FAQ Section
A new recommended element: Grounding Pages can now include a FAQ block answering the most common questions about the entity.
Rationale: Grounding Pages that answer frequent questions are more likely to be retrieved as a source. Not just for the definition question ("What is X?") but also for related queries ("What should I consider when choosing X?"). This expands retrieval coverage beyond the core definition.
Rationale: Grounding Pages that answer frequent questions are more likely to be retrieved as a source. Not just for the definition question ("What is X?") but also for related queries ("What should I consider when choosing X?"). This expands retrieval coverage beyond the core definition.
New
Segment Assignment
The lead section now includes an explicit segment classification (e.g. "Rankscale is a tool in the AI Visibility Tools segment").
Rationale: AI systems build meaning through relationships. An entity that is explicitly assigned to a market segment has a stronger semantic anchor than one that must be inferred from context. This small addition significantly strengthens the link between entity and category.
Rationale: AI systems build meaning through relationships. An entity that is explicitly assigned to a market segment has a stronger semantic anchor than one that must be inferred from context. This small addition significantly strengthens the link between entity and category.
New
Volatile Fact Hygiene
Facts that change frequently (pricing, feature lists, supported systems) must now include a date stamp and a link to the primary source.
Rationale: AI systems cannot distinguish current from outdated facts unless the page signals it. A price listed without a date risks being reproduced as current even months later. This rule reduces the risk of AI answers containing outdated information.
Rationale: AI systems cannot distinguish current from outdated facts unless the page signals it. A price listed without a date risks being reproduced as current even months later. This rule reduces the risk of AI answers containing outdated information.
Principle
Content-Only Scope
Standard updates are explicitly limited to content blocks. Routing, canonicals, hreflang, and language logic remain untouched across all versions.
Rationale: Version upgrades should be low-risk and predictable. By guaranteeing that no URL or routing changes are required, organizations can upgrade existing Grounding Pages without coordination with IT or DevOps teams. This lowers the adoption barrier significantly.
Rationale: Version upgrades should be low-risk and predictable. By guaranteeing that no URL or routing changes are required, organizations can upgrade existing Grounding Pages without coordination with IT or DevOps teams. This lowers the adoption barrier significantly.
Upgrade Note: Upgrading from v1.4 to v1.5 requires only content-level changes. No URL migrations, no redirects, no routing changes. Review your existing Grounding Pages and add the new elements (entity name in headings, FAQ section, segment assignment, volatile fact dates) where applicable. See the Technical Implementation Guide for the full specification.
Version 1.4
November 2025
Initial Release
Version 1.4 is the initial public release of the Grounding Page Standard. It establishes the core architecture for machine-readable entity definitions.
New
Core Architecture
Defines the three foundational elements: Stable Definition, Clear Distinction, and Consistent Structure. Every Grounding Page must contain a verifiable entity definition, a disambiguation statement, and a uniform format.
Rationale: AI systems reconstruct entities from probabilities. Without a clear definition and explicit boundaries, models fill gaps with plausible but incorrect information. The three-element architecture provides the minimum structure needed for reliable interpretation.
Rationale: AI systems reconstruct entities from probabilities. Without a clear definition and explicit boundaries, models fill gaps with plausible but incorrect information. The three-element architecture provides the minimum structure needed for reliable interpretation.
New
HTML + JSON-LD Mirroring
Every fact visible in HTML must have an identical structured representation in JSON-LD. The visible text is the primary source; JSON-LD provides the machine-readable layer.
Rationale: AI systems use multiple extraction paths. Some parse HTML, others rely on structured data. Mirroring ensures consistency regardless of extraction method and prevents contradictions between visible and structured content.
Rationale: AI systems use multiple extraction paths. Some parse HTML, others rely on structured data. Mirroring ensures consistency regardless of extraction method and prevents contradictions between visible and structured content.
New
Quality Principles
No adjectives, one fact per sentence, visible timestamps (Created, Updated, Verified). Marketing language is explicitly prohibited.
Rationale: AI systems select sources based on semantic similarity and factual density. Marketing language ("innovative", "leading") reduces citability because it is not verifiable. Factual discipline maximizes the probability of being selected as a source.
Rationale: AI systems select sources based on semantic similarity and factual density. Marketing language ("innovative", "leading") reduces citability because it is not verifiable. Factual discipline maximizes the probability of being selected as a source.
New
Human Notice
A recommended UX element that gives human visitors immediate context when landing on a fact-oriented page.
Rationale: Grounding Pages prioritize machine-readable facts. Human visitors expecting marketing content may find the format unusual. The Human Notice bridges this gap by explaining the page's purpose upfront.
Rationale: Grounding Pages prioritize machine-readable facts. Human visitors expecting marketing content may find the format unusual. The Human Notice bridges this gap by explaining the page's purpose upfront.
New
Entity Ontology (18 Classes)
Defines 18 entity classes (Organization, Product, Person, Tool, Field of Knowledge, etc.) with decision rules for consistent classification.
Rationale: Without a fixed classification framework, every organization would invent its own categories. This creates inconsistency across implementations. The ontology provides a shared vocabulary so entities can be categorized consistently across all Grounding Pages.
Rationale: Without a fixed classification framework, every organization would invent its own categories. This creates inconsistency across implementations. The ontology provides a shared vocabulary so entities can be categorized consistently across all Grounding Pages.
New
Footer Link Strategy
Grounding Pages should be linked in the website footer, similar to an imprint or privacy page.
Rationale: Sitewide footer links signal high relevance to both crawlers and AI systems. The position communicates: "This is an authoritative, permanent resource", comparable to how an imprint signals legal identity.
Rationale: Sitewide footer links signal high relevance to both crawlers and AI systems. The position communicates: "This is an authoritative, permanent resource", comparable to how an imprint signals legal identity.
Ecosystem Updates
Tools, playbooks and applications built on the Grounding Page Standard.
This section covers tools and applications built on the standard. For specification changes, see the version history above.
Entity Decoder released
Multi-pass analysis tool for grounding readiness, entity reconstruction and source attribution.
February 15, 2026
Grounding Playbook published
Practical implementation guide for teams building AI-readable content.
April 26, 2026
Grounding Check launched
Lightweight scan to evaluate entity activation and citation strength in any content.
May 5, 2026
Bookmarklet released
Run the Grounding Check directly from the browser DOM, including SPAs and protected pages.
May 5, 2026
Grounding Page Generator announced
Upcoming tool to create standard-compliant grounding pages.
May 5, 2026