• Understand the internal structure of a page.
• Assign intent, description, and metadata at a more granular level.
• Anchor interpretations to specific subsections rather than the entire page.
• Navigate content more efficiently for instruction following or summarization.

Sections enable precise semantic targeting—critical for AEO/AIO optimization.

• Belong to exactly one page (via the parent term).
• Have a unique section-level id.
• Represent a semantically coherent block of content.
• Be addressable — either via anchor or structural identification.

Sections are not standalone pages unless explicitly promoted to page-level status.

• id — stable identifier for the section.

Recommended metadata fields include:

• name — title of the section.
• description — summary of content within the section.
• intent — purpose behind the section.
• interpretiveFrame — local context or assumptions.
• parent — ID of the page containing the section.
• order — optional numeric order for rendering and navigation.

Sections MAY contain nested subsections if the hierarchy remains unambiguous.

• AI agents MUST treat sections as semantically distinct units.
• Section-level metadata SHOULD override page-level metadata when more specific.
• AI SHOULD use section ids to target answers to precise content areas.
• Missing section metadata SHOULD trigger fallback to page-level context.
• Conflicting metadata across sections MUST be treated as structural anomalies.

Sections provide fine-grained interpretive fidelity, especially for long-form content.

• page — the parent container for all sections.
• parent — links sections to their page.
• name / description / intent — define the semantics of each section.
• interpretiveFrame — contextualizes how the section should be understood.
• id — uniquely identifies each section.

{
  "section": {
    "id": "introduction"
  }
}

Section with expanded metadata:

{
  "section": {
    "id": "lighting-basics",
    "name": "Lighting Basics",
    "description": "Introduction to natural and artificial lighting principles.",
    "intent": "Provide foundational understanding for new photographers.",
    "parent": { "id": "lighting-guide" },
    "order": 1
  }
}

Nested subsections example:

{
  "sections": [
    {
      "id": "studio-lighting",
      "name": "Studio Lighting",
      "parent": { "id": "lighting-guide" }
    },
    {
      "id": "studio-modifiers",
      "name": "Lighting Modifiers",
      "parent": { "id": "studio-lighting" }
    }
  ]
}

• Each section includes a stable, unique identifier.
• Sections clearly belong to a single page.
• Section metadata is coherent and non-conflicting.
• The structure maintains clear semantic boundaries.
• All normative rules for section semantics are followed.