content-hierarchy

What this datapoint measures

Use of heading structure that reflects actual content organization. Whether h1-h6 elements are used to convey content structure or whether they are used inconsistently, decoratively, or skipped.

What high looks like

• Single h1 per page reflecting the page’s primary topic
• h2 elements for major sections
• h3-h6 used in proper hierarchy (h3 nested under h2, etc.)
• Heading text accurately summarizes the section that follows
• No skipped levels (h2 then h4 with no h3)
• No multiple h1 elements per page

What low looks like

• Multiple h1 elements per page
• Heading levels used for visual styling rather than structural meaning
• Skipped heading levels
• Generic heading text that doesn’t summarize content (“Section 1,” “Topic 2”)

What at floor looks like

A brand at floor on content-hierarchy has heading structure that doesn’t reflect content organization. AI systems parsing the page cannot use heading structure to understand content sections; they must infer structure from prose, which is less reliable.

This pattern is common in brands using visual page builders that generate headings for visual emphasis rather than structural meaning, in brands with content authored without editorial discipline, and in brands with templates that produce structural inconsistencies.

What affects this datapoint

• Single h1 per page
• Proper h2-h6 hierarchy
• Headings reflecting actual content structure
• Heading text accurately summarizing sections
• No skipped levels

OMG actions that influence this datapoint

Action	Influence
O-4 Technical Infrastructure, Performance & International Foundation	Substantial. Template-level work corrects structural heading issues.
M-2 Answer-First Content Architecture	Substantial. Answer-first content explicitly uses heading structure to reflect Q-and-A organization.
O-6 Content Audit & Baseline Optimization	Substantial. Audit surfaces hierarchy violations.

Multilingual considerations

Content hierarchy is language-neutral in markup. Heading text in non-Latin scripts requires standard handling. Consideration:

• Heading length conventions vary by language. Japanese and Korean headings tend to be shorter than English equivalents; this is conventional and not a quality issue.
• Heading-text translation should preserve structural intent; literal translation may produce headings that don’t read naturally in the target language.

Common failure modes

• Visual page builders generating multiple h1 elements per page
• Heading levels chosen for visual size rather than structural depth
• Heading-only content (sections that are headings without body content)
• Auto-generated heading text from CMS that’s generic (“Untitled,” “Section”)

Diagnostic interpretation

Content-hierarchy at floor with semantic-html (V1.1) at low indicates broad template-level engineering work needed. The two datapoints frequently move together.

Content-hierarchy at low with content-depth (V2.1) at high indicates substantial content with poor structure. Editorial restructuring lifts the datapoint without requiring new content.

---