What is an H4 Tag?

H4 tag: granular structure beneath H3

The H4 tag (<h4>) is where many marketing pages stop descending the heading ladder—but documentation, API references, legal agreements, and enterprise comparison matrices often need a fourth tier. H4 labels subtopics that live entirely inside one H3 block without meriting promotion to H3.

Think of H4 as footnotes in the outline: necessary for precision, invisible on a landing page with three short sections.

Four-level outline example

H1  API authentication guide
├── H2  OAuth 2.0 flows
│   ├── H3  Authorization code flow
│   │   ├── H4  PKCE requirements
│   │   └── H4  Refresh token rotation
│   └── H3  Client credentials flow
├── H2  API keys (legacy)
│   └── H3  Key rotation policy
└── H2  Error codes
    ├── H3  401 Unauthorized
    └── H3  403 Forbidden

Without H4, PKCE and refresh rotation would compete as H3 peers with entire OAuth flows—misrepresenting relationships.

When H4 is appropriate

When H4 is overkill

• Short blog posts under 1,000 words
• Single-offer landing pages
• Product pages with only three tabs
• Pages where H4 would label one sentence

If your CMS default template injects H4 for widget titles, demote decorative labels to <p> or <strong>.

H4 vs bold labels

Designers sometimes bold a line instead of marking H4:

<!-- Weak for outline -->
<p><strong>Rate limits</strong></p>

<!-- Stronger -->
<h4>Rate limits</h4>

Semantic H4 enables screen reader heading navigation; bold alone does not.

H4 in policy and compliance content

Privacy policies and terms of service benefit from deep headings for user trust and CTRL+F discoverability:

<h2>Data we collect</h2>
<h3>Account information</h3>
<h4>Email address</h4>
<h4>Payment method tokens</h4>
<h3>Usage analytics</h3>
<h4>Page views and referrers</h4>

Search engines may not rank these pages competitively, but clear H4 structure reduces support tickets and supports regulatory readability expectations.

H4 in technical documentation SEO

Developer content targets long-tail queries ("OAuth PKCE SPA redirect URI"). H4 strings that match precise concepts can align with niche searches when surrounded by explanatory body copy.

Avoid:

• Auto-generated H4 from code symbol names without context
• H4 per enum value when a table communicates better

H4 styling and components

Component libraries rarely ship variant="h4". Document rules:

• Sidebar widgets: not H4 unless doc TOC
• Card grids under H2 Features: card titles as H3, bullet labels not H4 unless long descriptions follow
• Code sample titles: <h4> or <figcaption> inside <figure>

Hierarchy validation

Automated checks:

FOR each h4 ON page:
  REQUIRE preceding h3 in ancestor outline path
  WARN if h2-to-h4 skip with no intervening h3

Manual review questions:

1. If I promote this H4 to H3, does the outline become clearer? → promote
2. If I demote H4 to paragraph lead-in, is anything lost? → demote

H4 mistakes

• Footer column headings as H4 on every page (outline pollution)
• H4 duplicated across locale templates with only city name swapped
• Using H4 because CSS class .h4 exists, not because outline needs level 4
• Twenty H4s with no H2/H3 parents on single-page app routes

H4 and on-page SEO impact

H4 is a supporting actor:

• Improves comprehensiveness signals on deep URLs
• Helps internal glossary and docs cross-link to specific anchors
• Reduces bounce when users land on long pages and need quick orientation

It will not rescue thin content. Depth must follow headings.

Anchor links and H4

Deep docs benefit from stable id attributes on H4 for support links:

<h4 id="pkce-requirements">PKCE requirements</h4>

Support teams can link https://docs.example.com/auth#pkce-requirements. Stable anchors are an underrated on-page UX and SEO hygiene practice.

Measuring H4 usage

Relationship to H5 and H6

Most sites rarely need H5 or H6 tags. If you reach for H5, confirm H4 sections are not already too shallow. Split into separate URLs when outlines exceed four meaningful levels routinely.

How Crawlox helps with H4 tags

Crawlox records full heading depth per URL, flagging unusual H4-heavy templates, skipped heading levels, and duplicate H4 strings introduced by CMS widgets. Use exports to clean up documentation and policy templates where fourth-level headings should clarify detail—not add noise to every page sitewide.