Subheadings that actually subdivide

Subheadings do three jobs

A subheading that works tells you what the section covers, how it fits into the whole, and whether you need to read it. Most fail at two of those three.

Bad subheading: "Benefits"

Better: "Why this matters for small catalogs"

The first is a label. The second is a claim you can evaluate before you commit.

Test: cover everything above it

Put your hand over the page content up to the subheading. Can someone who just scrolled down still understand what the section is about? If the subheading only makes sense after reading three paragraphs of setup, it's decorative.

Subheadings should function as a structural outline if you read them in isolation. Someone skimming should be able to reconstruct your argument from headings alone.

Parallel structure makes the pattern obvious

If your first subheading is "How to audit your taxonomy" and your second is "Mistakes," you've broken the pattern. Readers have to re-orient. They can't skim efficiently.

Commit to a structure:

• All questions: "What counts as duplicate content?" / "When does Google actually penalize you?"
• All imperatives: "Run the crawler" / "Tag the orphans" / "Redirect or consolidate"
• All outcome-based: "Faster builds" / "Fewer support requests" / "Easier onboarding"

Pick one and stay in it. Switching mid-page makes your structure invisible.

Avoid the "more about" trap

Subheading: "More about image formats"

That's not a subheading. That's you admitting you don't know what the section does. "More" is never the organizing idea.

Instead: "When WebP isn't worth the hassle" or "JPEG quality settings that matter" or "Formats for transparency: PNG vs. SVG."

Be specific about what the section delivers. Vague subheadings make readers work harder than they should.

Use subheadings to preview effort

"Install the plugin" signals a five-minute section. "Migrate your existing URLs" signals you're asking for an afternoon. Subheadings set expectations about scope.

If a section is long, the subheading should acknowledge it. If it's short, don't oversell. Readers notice when effort and framing don't match.

One idea per section

If your subheading tries to cover two things—"Planning your categories and managing redirects"—split it. One subheading, one idea. Readers should never wonder which part of the heading the paragraph is addressing.

Subheadings are navigation. Treat them like signage, not decoration.