Heading structure gives a page an outline. It helps readers scan, helps assistive technology navigate, and gives search systems clearer clues about how sections relate to the page’s main purpose.
A good heading audit does not force every page into a rigid sequence for its own sake. It asks whether the hierarchy communicates meaning when the visual styling is removed.
Use this checklist for articles, landing pages, product pages, documentation, dashboards, and reusable CMS templates.
Identify the page’s main heading
The H1 should usually describe the main purpose of the page. It should be visible, specific, and consistent with the title tag and opening content.
Check that:
- the page has a meaningful H1;
- the H1 is not an empty logo, icon, or hidden accessibility workaround;
- the wording matches what the page actually delivers;
- repeated template elements do not create several competing H1s;
- the title tag and H1 reinforce the same topic without needing to be identical.
Multiple H1 elements are valid in HTML, but most production pages are easier to audit and maintain with one clear primary H1. If several H1s exist, verify that the structure is intentional and understandable rather than assuming the markup is automatically wrong.
Read the outline without the design
List the H1-H6 elements in document order and read them as a table of contents.
The outline should answer:
- What is this page about?
- What are the major sections?
- Which subsections belong to each major section?
- Does the order match the visible reading flow?
- Would a screen-reader user understand where each section begins?
If the outline contains navigation labels, button text, modal headings, and repeated card titles before the actual H1, the component structure may be adding noise.
Check hierarchy, not typography
Heading levels express relationships. Font size and visual weight do not.
Use H2 for major sections under the H1, H3 for subsections within an H2, and deeper levels only when the content genuinely needs them. Avoid choosing H4 simply because its browser style looks smaller.
A skipped level, such as H2 directly to H4, is often a sign that styles and semantics became mixed. It is not always catastrophic, but it deserves review because assistive navigation and automated outlines rely on the markup.
Find missing and decorative headings
Common template problems include:
- important sections built with styled div or paragraph elements instead of headings;
- empty heading tags used for spacing;
- headings containing only an icon or badge;
- visually hidden headings that do not help navigation;
- card titles marked as headings even when they do not introduce sections;
- footer or sidebar headings appearing in the outline before the main content.
Fix the component or template when the same issue appears across many pages. Editing individual pages only hides a systemic problem.
Review repeated headings
Repeated text can be legitimate for consistent card patterns, but it can also make the outline ambiguous.
Look for repeated headings such as “Features,” “Learn more,” “Overview,” or “Details” that provide little context. A person navigating by headings should be able to predict what comes next.
Prefer descriptive labels such as:
- “Technical SEO checks” instead of “Features”;
- “Canonical and robots review” instead of “Details”;
- “Export the audit report” instead of “Learn more.”
Do not add keywords to every heading. Clarity and section identity matter more than repeating the primary phrase.
Check dynamic and hidden content
Modern pages often render headings inside accordions, tabs, dialogs, carousels, and client-side components.
Review whether:
- headings exist in the DOM before users open the component;
- hidden sections create a confusing outline;
- tab panels use the right accessible relationships;
- modal headings are correctly associated with the dialog;
- loading states temporarily produce empty or duplicated headings;
- mobile and desktop layouts preserve a coherent order.
The correct implementation depends on the interaction. The audit goal is to ensure that the heading remains meaningful in both visual and accessibility contexts.
Align headings with content intent
Headings should help a reader decide whether a section answers their question. They can naturally include relevant terminology, but they should not become a list of keyword variants.
Compare each major heading with the text that follows it:
- Does the section answer what the heading promises?
- Is the heading too broad for the content?
- Are two sections competing to answer the same question?
- Could one long section be divided into clearer subsections?
- Does a thin section exist only to place another keyword on the page?
If a heading has no substantial content beneath it, improve the section or remove the heading.
Heading structure checklist
- The page has a clear, visible H1.
- The H1 matches the page purpose and supports the title tag.
- Major sections use descriptive H2 headings.
- H3-H6 levels represent real nested subsections.
- Heading levels are not selected only for visual styling.
- Empty and decorative headings are removed.
- Important section labels are semantic headings, not styled divs.
- Repeated headings remain understandable out of context.
- Navigation, cards, footers, and sidebars do not overwhelm the main outline.
- Dynamic and hidden content preserves an accessible hierarchy.
- Headings accurately describe the content below them.
- The outline remains useful on mobile and desktop.
How Crowra supports heading review
Crowra extracts the active page’s heading hierarchy, flags missing or suspicious structure, and can mark visible headings directly on the page. This makes it easier to connect an outline problem with the component that produced it.
Use the SEO and Accessibility views together: the SEO view provides page-structure context, while accessibility evidence helps identify navigation and semantic problems. Export the heading findings when the underlying fix belongs to a shared template or design system.
Crowra can show the hierarchy and evidence, but it cannot decide the best editorial structure for every page. That still requires understanding the audience, page purpose, and content relationships.