# Content Hierarchy

Content hierarchy orders and signals information by importance and relationship so users can scan, understand, and act efficiently.

- Type: principle
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/content-hierarchy/>)

## What it means

Content hierarchy is the structural ranking of information within a page, screen, document, or flow. It uses sequence, headings, grouping, labels, and visual emphasis to show what is primary, what supports it, and how sections relate. Semantic structure and visual styling should reinforce each other rather than creating an appearance that assistive technologies cannot interpret.

## Why it matters

A clear hierarchy helps users identify the page purpose, jump to relevant sections, and understand which information belongs together. It reduces the need to read every word and provides a navigable outline for screen-reader users. For teams, it also exposes when several messages are competing for the same level of importance.

## When to use it

Use content hierarchy whenever information exceeds a single short statement, especially on guidance pages, dashboards, forms, product detail pages, and mobile screens. Rework it when headings are generic, several calls to action appear equally dominant, or visual order differs from reading and focus order.

## How it works

1. Name the page’s primary purpose and rank the questions, decisions, and actions users need to address.
2. Group related material and arrange it in a task-appropriate sequence rather than following the order in which the organization supplied it.
3. Create a logical heading outline with descriptive labels and avoid skipping levels for visual effect.
4. Align typography, spacing, component emphasis, DOM order, and focus order with the intended structure.
5. Test scanning, heading navigation, zoom, reflow, and comprehension with representative content and assistive technologies.

## A practical example

A loan application page begins with the amount and repayment summary, followed by a primary “Review and apply” action. Eligibility, fees, and required documents have descriptive second-level headings; detailed definitions sit beneath the relevant section. The DOM and visual order match, so keyboard and screen-reader navigation follow the same logic.

## Where it breaks

Hierarchy is contextual and cannot be solved by font size alone. Excessive levels create complexity, while flattening everything removes relationships. A visually elegant hierarchy may still fail when headings are semantically incorrect or focus order is different. Mobile reflow can also change perceived priority and must be checked separately.

## Common mistakes

- Using bold text as a heading without semantic heading markup.
- Choosing heading levels for appearance rather than document structure.
- Giving several messages and actions equal visual priority.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/content-hierarchy/#visualization-content-hierarchy>)

## Sources

1. [Headings](<https://www.w3.org/WAI/tutorials/page-structure/headings/>) — W3C Web Accessibility Initiative · Accessibility tutorial
2. [Understanding Success Criterion 2.4.6: Headings and Labels](<https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html>) — World Wide Web Consortium · WCAG guidance
3. [Create a Clear Structure for Your Content](<https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-structure/>) — Government Digital Service · Government guidance

## Related topics

- [Plain Language](<https://wiki.soroush.uk/topic/plain-language/>)
- [Progressive Disclosure](<https://wiki.soroush.uk/topic/progressive-disclosure/>)
- [Information Scent](<https://wiki.soroush.uk/topic/information-scent/>)
