Headings

03 / Structure

Heading tags divide a page into meaningful sections. The H1 names the main topic, H2 headings introduce major sections, and H3 through H6 organize progressively deeper subtopics, creating a content hierarchy that both visitors and search engines can follow.

Where the title tag names the page in search results and the meta description summarizes it, headings describe the structure of the visible content itself. A clear heading structure makes long pages easier to scan, supports screen reader navigation, and signals how topics and subtopics relate.

This lesson covers H1 tags, H2 to H6 headings, heading hierarchy, skipped heading levels, and the document outline. It also explains how to use SiteAuditLint to find missing, multiple, duplicate, empty, and out-of-order headings across a website.

1. Why headings matter

A well-structured page normally begins with an H1 for the main topic, followed by H2 headings for major sections. H3 headings then organize supporting topics underneath an H2.

2. H1 tags

The H1 is the primary heading of a page. It should clearly describe the main subject and give visitors an immediate understanding of what the page covers. A page will commonly have one main H1:

<h1>Technical SEO Audit</h1>

A missing H1 can make the page structure less clear, particularly when no other prominent heading identifies the primary topic.

The H1 should work with the page title and the visible content. It does not need to exactly match the title tag.

3. H2 to H6 headings

H2 through H6 headings create additional levels within the page structure. An H2 normally introduces a major section, and an H3 organizes a topic within that section:

<h2>Crawlability</h2>
<h3>Robots.txt</h3>

H4, H5, and H6 provide further levels when the content genuinely requires them:

Not every page needs all six heading levels. A short page may only need H1 and H2 headings. The goal is not to use as many levels as possible, but to create a logical structure that matches the content.

4. Heading hierarchy

Heading hierarchy shows how sections relate to one another. A logical hierarchy nests each level under the one above it:

H1
 ├── H2
 │    ├── H3
 │    └── H3
 ├── H2
 │    ├── H3
 │    │    └── H4
 │    └── H3
 └── H2

The structure should make sense when the heading text is read without the paragraphs underneath it. Each heading should describe the section that follows it. If the hierarchy becomes difficult to understand, the page structure may need to be reorganized.

Practical check

Ask one question: if the headings were the only text on the page, would a reader understand what the page covers and how its sections connect? If not, revise the headings or the structure.

5. Skipped heading levels

A skipped heading level occurs when the document jumps over a level without a clear structural reason.

6. Content outline

The headings on a page can be viewed as an outline of the content:

H1: Technical SEO Audit

H2: Crawlability
H3: Robots.txt
H3: XML Sitemaps

H2: Indexability
H3: Noindex
H3: Canonical URLs

H2: On-Page SEO
H3: Title Tags
H3: Meta Descriptions

This outline immediately communicates what the page covers and how the topics are organized. A useful test is to extract only the headings from a page and read them in sequence. If the outline is confusing, repetitive, or missing important sections, the underlying page structure may need improvement.

7. Common heading problems

A technical SEO crawl can identify several heading-related issues.

8. Headings and page relevance

Headings provide contextual information about the content that follows them. For example:

H2: Broken Links
H3: Internal Broken Links

This hierarchy communicates that internal broken links are a specific part of the broader broken-link topic. Descriptive subheadings also make pages easier to scan: someone looking for information about internal links can locate the relevant section without reading the entire page, and headings with id attributes can serve as jump link targets in a table of contents.

Headings should describe real content rather than be written primarily to insert keywords.

9. Checking headings with SiteAuditLint

A website crawler such as SiteAuditLint can inspect heading structures across every crawled URL and surface pages with structural problems.

1. Crawl the websiteCollect heading data for every URL.
2. Find missing and multiple H1sCheck that each important page has one clear primary heading.
3. Review duplicate headingsLook for repeated heading text that fails to distinguish pages or sections.
4. Check the hierarchyFlag skipped heading levels and headings out of logical order.
5. Remove empty headingsDelete empty elements or populate them with meaningful text.

10. Practical exercise: Review five heading structures

Choose five important pages from a website and record the heading structure for each page. For every page, check:

• Does the page have an H1, and does it describe the primary topic?
• Are major sections represented by H2 headings?
• Are H3 headings used for relevant subsections?
• Are heading levels skipped?
• Does the heading outline make sense when read by itself?
• Are there empty or repetitive headings?

Then compare the heading outline with the actual page content. A good heading structure should make the page easier to understand before the supporting paragraphs are even read.

11. Key takeaways

• The H1 identifies the primary topic of the page.
• H2 headings organize major sections.
• H3 through H6 can organize progressively deeper subsections.
• Heading hierarchy should reflect the relationship between sections.
• Skipped heading levels can make the content structure harder to follow, especially for screen reader users.
• A heading outline should make sense when read without the page copy.
• Headings should describe content rather than exist primarily for keyword placement.
• Crawling tools such as SiteAuditLint can reveal missing, duplicate, empty, and structurally inconsistent headings at scale.

Knowledge check

Ready to go further? Review the technical SEO checklist, or revisit how headings pair with page names in the Titles lesson.