The Encyclopedia Mistake in Subheadings: Turning H3s into Micro-Action Prompts

In my early years at the writing desk, I used to measure the depth of my technical guides by the sheer weight of their subheadings. I assumed that the more academic, the more encyclopedic my breakdown of a topic was, the more authoritative I would appear. I would write subheads like "The Importance of Image Optimization", "The Keyword Research Process", or "Designing Meta Descriptions", and pack everything beneath them with theoretical exposition. Time-on-page metrics were decent; I would glance at the analytics dashboard with pride. But one day I faced the bitter truth: readers weren't patiently reading these pieces—they were merely scanning them, and worse yet, leaving the page without implementing a single one of the detailed steps I laid out. Because my subheadings weren't road signs; they were library index cards.

I made this mistake for years. Research by Nielsen Norman Group shows that 79% of web users scan any new page they encounter rather than reading it word-for-word. What's more, only about 20% of the text on an average web page is actually read. This data clearly reveals the modern screen reader's impatience and scanning reflex. Yet we writers continue to craft text as if we are speaking to a scholar reverently turning the pages of a printed encyclopedia. When we turn H3 subheadings into a conceptual glossary, all we do is compound the reader's cognitive load.

I remember a guide I wrote under the old habit. My subheading was: "Image Alt Tags (Alt Text)". Beneath it sat three dense paragraphs of theory explaining why alt tags are critical for SEO. When a reader sees this subhead, here is what happens in their mind: "Okay, I get what an alt tag is; it's important." But in that moment, they have no idea what to do. Now, I rewrite that heading using the approach I run in my workshop: "Add a 3-Word Descriptive Alt Tag to Images".

The first heading is a static noun phrase that leaves the reader as a passive recipient. The second acts like a UX-driven UI component—an explicit call to action. As the reader scans the page in an F-pattern, the second they hit this subhead, they immediately grasp what to do, how to do it, and its concrete boundary (3 words). Subheadings are not cold walls meant to classify topics; they are micro-action instructions that take the reader by the hand and guide them to the next step.

Of course, turning every subheading into an aggressive imperative carries risks. A relentless tone that constantly shouts "do this" or "optimize that" triggers cognitive fatigue and cheapens the piece into a pushy marketing brochure. The craft lies in striking the balance: instead of forcing every subhead into an imperative command, framing the action itself or guiding with clear constraints gets the job done.

Here is the foundational rule you can apply in your own workshop today to transform your writing from an information dump into a living guide:

The Craftsman's Transferable Rule: Inspect every H3 subheading you write. If it consists solely of nouns or passive nominal phrases, scrap it immediately. In its place, write a single-step micro-instruction equipped with an active verb and a constraining metric that the reader can execute at their desk right then and there.

Now let's ask ourselves this honest question: Do our subheadings simply tell the reader what the topic is, or do they tell them exactly what to do right now?