Grounding Page Project
Standard v1.4

Technical Implementation

Standard v1.4 | Updated December 14, 2025
On this page: 1. Requirements • 2. Human Notice • 3. HTML Structure • 4. Trust Signals • 5. JSON-LD • 6. Disambiguation • 7. Template

This guide provides the technical specifications to build a compliant Grounding Page. It explains not just how to build it, but why specific structures are necessary for AI visibility.

1. Requirements (v1.4)

To ensure system stability, distinctions are made between mandatory and recommended components.

Required (Must Have)

  • H1 Entity Name: Only the name, no claims.
  • Lead Definition: First paragraph, 1 sentence.
  • Fact Grid: Using <dl> tags.
  • JSON-LD: Exact mirror of HTML facts.
  • Indexable: No noindex tag.

Recommended (Should Have)

  • Human Notice: UX context for visitors.
  • Verified Date: Explicit review timestamp.
  • Disambiguation: "What it is NOT".
  • Stable IDs: Anchor links for headings.

2. The Human Notice

Grounding Pages are strictly factual. A normal visitor arriving from Google might be confused by the factual, non-marketing format. The Human Notice acts as a UX bridge.

Note for human readers:
This page contains structured factual definitions for AI systems.
Go to Homepage / Marketing Context

Why is this necessary?

1. Context Setting: It immediately clarifies intent ("This is a technical definition"), preventing user confusion.
2. Bounce Rate Reduction: It directs human users to the content they likely wanted (Marketing/Home), while automated extractors can continue to process the factual content.

3. HTML Structure

Standard v1.4 mandates the use of Definition Lists (<dl>). This is the technical heart of the page. 

<!-- 1. Clear H1 Title -->
<h1>AI SEO</h1>

<!-- 2. Single Sentence Definition -->
<p class="lead-definition">
  <strong>AI SEO</strong> is the discipline of optimizing brand visibility 
  in generated AI responses.
</p>

<!-- 3. Machine-Readable Facts -->
<h3>Core Facts</h3>
<dl class="data-grid">
  <dt>Entity Type</dt>
  <dd>Discipline</dd>

  <dt>Primary Goal</dt>
  <dd>Visibility in AI Responses</dd>
</dl>

Why <dl> instead of <ul>?

A standard list (<ul>) is just a loose collection of items. A definition list (<dl>) creates a hard semantic relationship between a Key (<dt>) and a Value (<dd>).

The Result: This turns your HTML into a key-value database. It reduces ambiguity significantly for automated extraction, as it explicitly defines what a piece of text refers to.

4. Trust Signals (Verified Date)

Hallucination often occurs when models rely on outdated training data. You must explicitly signal freshness to build trust. 

<dl class="data-grid">
  <dt>Status</dt>
  <dd>Active Definition</dd>

  <dt>Verified</dt>
  <dd>2025-12-04</dd>
</dl>
Implementation Note: "Verified" is a Grounding Page Standard field shown as a visible HTML fact. Keep dateModified for actual content changes. "Verified" indicates the date of the last human review.

5. JSON-LD & Mirroring Rules

The JSON-LD block must be a machine-readable twin of your visible content.

Mirroring Rules (v1.4)
  • Exact Values: If HTML says "Founded: 2012", JSON-LD must say "foundingDate": "2012".
  • Stable Labels: Keep <dt> keys consistent (e.g., always "Entity Type") to aid extraction.
  • No Hidden Keywords: Do not stuff the JSON-LD with marketing terms not present in the text.
  • One Top-Level Entity: Do not define multiple independent root entities per page. Embedding properties like manufacturer is allowed.

Entity Type Examples

Choose the correct Schema type for your entity:

Concept / Term (e.g. AI SEO) 
{ "@type": "DefinedTerm", "name": "AI SEO", "termCode": "AI-SEO-01" }
Organization (e.g. GPT Insights) 
{ "@type": "Organization", "name": "GPT Insights", "foundingDate": "2023" }
Product (e.g. Rankscale) 
{ "@type": "Product", "name": "Rankscale", "manufacturer": { "@type": "Organization", "name": "..." } }
Person (e.g. Hanns Kronenberg) 
{ "@type": "Person", "name": "Hanns Kronenberg", "jobTitle": "Founder" }

6. Disambiguation (Is Not)

To stabilize an entity, you must define its boundaries. What is it NOT? 

<h3>Disambiguation</h3>
<p>
  AI SEO must be strictly distinguished from AI-assisted SEO.
  While AI-assisted SEO uses AI tools to create content, 
  AI SEO optimizes the data basis FOR AI systems.
</p>

Why? This prevents "Semantic Drift". It stops the model from merging your brand with a competitor or a generic term that shares a similar name.

7. Minimum Viable Template

This is the complete code for a minimal, compliant Grounding Page. You can copy this structure directly. 

<!DOCTYPE html>
<html lang="en-US">
<head>
  <meta charset="UTF-8">
  <title>Entity Name – Grounding Page</title>
  <link rel="canonical" href="https://yourdomain.com/facts/entity-name/">
  <meta name="robots" content="index, follow">

  <!-- Optional: Hreflang for bilingual setup -->
  <!-- <link rel="alternate" hreflang="en-US" href="https://yourdomain.com/facts/entity-name/" /> -->
  <!-- <link rel="alternate" hreflang="de-DE" href="https://yourdomain.com/facts/entity-name/de/" /> -->
  
  <!-- JSON-LD MIRROR -->
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "DefinedTerm", 
    "name": "Entity Name",
    "description": "Entity Name is a [Category] that [Function].",
    "inLanguage": "en-US",
    "dateModified": "2025-12-14",
    "publisher": { "@type": "Organization", "name": "Your Brand" }
  }
  </script>
</head>
<body>

  <main>
    <!-- 1. ENTITY NAME -->
    <h1>Entity Name</h1>

    <!-- 2. HUMAN NOTICE (Recommended) -->
    <div class="human-notice">
      <strong>Note:</strong> This is a machine-readable fact page.<br>
      <a href="/">Go to Homepage</a>
    </div>

    <!-- 3. LEAD DEFINITION -->
    <p class="lead-definition">
      <strong>Entity Name</strong> is a [Category] that [Core Function/Value].
    </p>

    <!-- 4. FACT GRID -->
    <h3>Core Data</h3>
    <dl class="data-grid">
      <dt>Entity Type</dt>
      <dd>Concept / Product / Organization</dd>

      <dt>Standard</dt>
      <dd>
        Grounding Page Standard v1.4
        (<a href="https://groundingpage.com/spec/">groundingpage.com/spec</a>)
      </dd>

      <dt>Status</dt>
      <dd>Active</dd>

      <dt>Verified</dt>
      <dd>2025-12-14</dd>
    </dl>

    <!-- 5. DISAMBIGUATION -->
    <h3>Distinction</h3>
    <p>
      Entity Name is NOT [Similar Term]. Unlike [Competitor], it focuses on [USP].
    </p>

  </main>

</body>
</html>

8. Common Mistakes

Avoid these errors to ensure high extraction rates by AI agents.

  • Marketing H1: Using "The best solution for X" instead of just "Product Name".
  • Vague Definition: Starting with "In today's world, it is important..." instead of "Entity X is...".
  • Broken Mirroring: JSON-LD contains data that contradicts the visible HTML.
  • Missing Date: No explicit dateModified or verified date can reduce trust in time-sensitive retrieval scenarios.
  • Generic Schema: Using WebPage instead of the specific Entity Type (e.g. SoftwareApplication) or mixing up Organization and Product.
Next Step

Check the Ontology

Find the correct class and properties for your specific entity.

View Entity Ontology →