H1, H2, and H3 Hierarchy Best Practices for SEO

Header tags do more than make a page look organized - they give search engines a structural outline of your content and help readers scan a page to find the section relevant to them. Getting the hierarchy wrong doesn't just look messy, it can genuinely confuse both crawlers and visitors about what a page is actually about.

One H1 per page

Every page should have exactly one H1, and it should closely match (though not necessarily duplicate word-for-word) the page's main topic and, ideally, its title tag. Using multiple H1 tags on a single page is a common CMS default that undermines the clarity header tags are meant to provide.

H2s mark major sections, H3s mark subsections within them

Think of headers as a nested outline. H2s should represent the major distinct sections of your content - if you're writing a guide to email marketing, your H2s might be "Building Your List," "Writing Subject Lines," and "Measuring Performance." H3s then break those sections down further only when a section genuinely needs sub-points.

Don't skip levels

Jumping from an H1 straight to an H3, or from an H2 straight to an H4, breaks the logical outline structure that both accessibility tools and search engines rely on. Keep the hierarchy sequential: H1, then H2, then H3, without gaps.

Headers should describe content, not just contain keywords

A header like "SEO Tips" tells a reader almost nothing about what follows. "5 Technical SEO Tips for Faster Indexing" both describes the section's actual content and naturally incorporates relevant terms, which tends to perform better for both users and search visibility. For a deeper look at this, see our guide, Sitemaps, Robots.txt & Canonicalization.

Auditing your existing header structure

Use your browser's inspect tool or an SEO crawler like Screaming Frog to pull every page's header tags into a spreadsheet. This quickly surfaces pages with multiple H1s, empty headers, or skipped hierarchy levels that are otherwise invisible just by looking at the rendered page. For a deeper look at this, see our guide, How to Build and Optimize an XML Sitemap That Actually Helps Crawling.