What is an H3 Tag?

H3 tag: subsections inside H2 chapters

The H3 tag (<h3>) drills one level deeper than H2 tags. Where H2 splits a guide into chapters, H3 splits chapters into scenes: individual steps, feature bullets expanded into mini-sections, or FAQ questions grouped under a parent FAQ heading.

H3s shine on long URLs targeting broad queries—"technical SEO checklist," "migrate WordPress to headless," "compare project management tools"—where one H2 section needs internal structure.

Outline example

H1  Migrate WordPress to a headless CMS
├── H2  Prerequisites
│   ├── H3  Export content and media
│   └── H3  Map URL redirects
├── H2  Choose your frontend stack
│   ├── H3  Static site generators
│   └── H3  SSR frameworks
└── H2  Post-launch validation
    ├── H3  Crawl for 404s
    └── H3  Monitor index coverage

Each H3 should belong to exactly one parent H2. If an H3 feels orphaned, promote it to H2 or merge sections.

H3 vs H2 decision matrix

H3 in FAQ and how-to content

FAQ blocks

<h2>Frequently asked questions</h2>

<h3>How long does a crawl take?</h3>
<p>Duration depends on site size and rate limits...</p>

<h3>Can I crawl staging environments?</h3>
<p>Only authorized domains you configure...</p>

Pair with valid FAQ structured data when content is visible on-page—markup alone without matching H3/pattern confuses quality checks.

Step sequences under one H2

<h2>Configure DNS records</h2>
<h3>Step 1: Add TXT verification</h3>
<h3>Step 2: Point CNAME to CDN</h3>

For purely sequential short steps, an <ol> may suffice without H3 per step—choose based on length and anchor-link needs.

H3 on product and spec pages

Under H2 Specifications:

Spec H3s surface long-tail queries ("45L backpack dimensions") when copy is real, not placeholder.

H3 density and thin sections

SEO audits flag "heading bloat" when:

• H3 introduces one sentence then next H3 appears
• H3 text duplicates H2 meaning (H2 Pricing → H3 Pricing details with no new info)
• Auto-generated H3s from TOC plugins split paragraphs artificially

Rule of thumb: if removing the H3 loses no information, it was unnecessary.

H3 styling in design systems

Cards and accordions often misuse heading levels:

Document which components emit H3 so content editors do not accidentally stack four H3s before the first H2.

H3 and keyword targeting

H3 is not a license to repeat primary keywords. Instead:

• Mirror natural sub-questions from People Also Ask
• Use entity names (tools, standards, regulations)
• Prefer clarity over synonym stuffing

Example for a cybersecurity guide:

<h2>Harden authentication</h2>
<h3>Enforce multi-factor authentication</h3>
<h3>Rotate API keys after employee offboarding</h3>

H3 accessibility considerations

• Navigate by heading level: users expect H3 after H2 in same branch
• If accordion panels hide content, ensure expand/collapse is keyboard accessible
• Visible focus styles on accordion buttons inside headings

Common H3 mistakes

• Using H3 for sidebar "Popular posts" on every article (template noise)
• Identical H3 labels across thousands of location pages
• H3 in comments widgets (Leave a reply) polluting outline
• Skipping H2 entirely—H1 followed by ten H3s with no grouping

Auditing H3 structure

Crawl-derived checks:

1. URLs with H3 count > 0 but H2 count = 0 (likely hierarchy skip)
2. Duplicate H3 strings site-wide (template issue)
3. Average words between H3 headings < 40 (possible thin sections)
4. Compare H3 list to Search Console query variants for same URL

H3 in documentation sites

Docs platforms (ReadMe, GitBook, Docusaurus) generate deep H3–H4 trees. SEO implications:

• Each doc URL should still have one H1
• H3 pages within single-page docs may use in-page anchors instead of separate URLs—choose URL strategy deliberately
• Versioned docs need canonical discipline so H3-heavy duplicates do not index

How Crawlox helps with H3 tags

Crawlox captures full heading trees per crawled URL, making it easy to find pages that skip H2, overuse identical H3 boilerplate, or carry deep heading stacks with thin intervening copy. Refine long guides and documentation templates where H3 structure shapes both user comprehension and subtopic coverage.