GitHub

Heading Hierarchy

Validates heading structure and hierarchy

Validates heading structure and hierarchy

Rule IDcontent/heading-hierarchy
CategoryContent
ScopePer-page
Severitywarning
Weight5/10

Solution

Proper heading structure (H1 → H2 → H3) helps users and search engines understand your content organization. Skipping levels (H1 → H3) creates confusion. Use headings in sequential order without skipping levels. Each section should use the next heading level down. Think of headings as an outline—they should make sense when read alone. Avoid empty headings or using headings purely for styling.

Enable / Disable

Disable this rule

squirrel.toml
toml
[rules]
disable = ["content/heading-hierarchy"]

Disable all Content rules

squirrel.toml
toml
[rules]
disable = ["content/*"]

Enable only this rule

squirrel.toml
toml
[rules]
enable = ["content/heading-hierarchy"]
disable = ["*"]

Type to search…

↑↓ navigate ↵ open esc close