The Structure of a Post That Gets Read to the End

Jul 23, 2026 · 7 min read

AI disclosure: This article was drafted by an AI writing assistant from a brief set by the author, then reviewed and published by them.

Most people who click your post never finish it. Chartbeat analyzed two billion page visits and found that 55 percent of readers spent fewer than 15 seconds on the page. They did not leave because the writing was bad. They left before they could tell. That is a blog post structure problem, and you can fix it on your next draft.

If you publish regularly, you know the feeling. You spend three hours on a post. It goes out. The analytics show a stream of people arriving, skimming, gone. After enough of that, you start to suspect the whole game rewards clickbait, and that writing something honest and useful is a losing move.

The data says otherwise. Readers finish posts that are built to be finished. This is a how-to on that build: the lead, the promise, payoff spacing, subheads that work as rest stops, and a 40 percent rule for examples. By the end you will have a five part checklist you can run on tomorrow’s draft. None of it requires tricks. All of it is mechanical, which means you can do it on purpose instead of hoping.

What the reading data actually says

Two findings should sit behind every structural decision you make.

First, people scan. Nielsen Norman Group’s research on how users read on the web found that 79 percent of test users scanned any new page they came across. Only 16 percent read word by word. A later NN/g analysis, How Little Do Users Read?, estimated that on an average visit people read at most 28 percent of the words on a page, and 20 percent is more likely.

Second, attention is won in stages. The Chartbeat study behind that 55 percent figure, reported by the company’s CEO Tony Haile in Time, showed a cliff in the first 15 seconds. But readers who survive the cliff tend to stay a while. When Medium’s data team studied engagement on its own posts, total reading time peaked at a seven minute read, roughly 1,600 words. People will read long posts. They will not read long posts that fail them early.

So the job splits in two. Win the first 15 seconds. Then re-earn the reader every few hundred words after that. Each element below serves one of those two jobs.

The Structure of a Post That Gets Read to the End infographic

A blog post structure that matches how people read

The lead has one job

Your opening paragraph is a filter with a 15 second timer on it. The reader arrives asking one question: is this for me, and is it going anywhere? The lead answers that question or loses them.

A working lead does two things fast. It names the reader’s situation in concrete terms, and it signals that the post contains something they do not already have. Both in plain sentences, because a scanner only picks up plain sentences.

What kills leads is warming up. An opener about “today’s digital landscape.” A definition of a term your reader already knows. A story that takes four paragraphs to reach its point. If your first paragraph could open a hundred other posts, it opens none of them well.

The promise sets the contract

Within the first few paragraphs, tell the reader exactly what they will have by the end. A deliverable, stated plainly. “By the end you will have a five part checklist to run on tomorrow’s draft” is a promise. “Let’s explore the world of content” is a shrug.

The promise matters because it converts a scanner into a reader with a goal. NN/g’s work shows people hunt for specific information rather than absorb pages whole. A stated promise tells the hunter the prey is here. It also disciplines you as the writer: if you cannot state the deliverable in one sentence, the post is not ready to write.

Payoff spacing: deliver every 300 words

Here is where posts that start well fall apart. They front-load one insight, then pad. The reader hits a stretch with nothing usable in it, and the back button is one thumb away.

Treat 300 words as your maximum distance between payoffs. A payoff is anything the reader can take with them: a rule, a number, a template sentence, an example they can copy, a mistake they now know to avoid. Scroll through any 300 word window of your draft. If you find no payoff in that window, that window is where you are losing people.

This is why Medium’s seven minute peak makes sense. Length by itself does not push readers away. Empty stretches do. A 1,600 word post with a payoff every 300 words gets finished. An 800 word post with one payoff, stretched thin, does not.

Subheads are rest stops, not labels

Most writers treat subheads as filing. The section is about examples, so the subhead says “Examples.” Filing is for you. Rest stops are for the reader.

On a long drive, a rest stop lets you recover and tells you how far you have come and what is still ahead. Subheads should do the same work. A reader scrolling your post decides at each subhead whether to re-enter the text. So each subhead has to carry a payoff on its own. “The 40 percent rule for examples” makes a promise. “Examples” does not.

Run two tests on every subhead. The skim test: if someone reads only your subheads, do they get the argument in miniature? Since scanning is the default behavior, that skim version of your post is the version most visitors will read. Make it good. Then the re-entry test: does this subhead give a scanner a concrete reason to slow down and read the paragraph under it?

Spacing matters here too. A subhead every 200 to 350 words keeps the page from turning into a wall of text. Closer than that and the post feels chopped up. Farther apart and the scanner has no handholds.

If you want short daily reps on mechanics like this, The Daily Shortcut is one free marketing episode a day, and the archive is 166 episodes deep.

Empower Network sells the Blogging System and classic courses referenced on this page.

The 40 percent rule for examples

Here is the rule that does the most work in this whole system: in a how-to post, examples should take up about 40 percent of the words. Four out of every ten words showing the thing rather than describing it.

Why so much? Instruction tells the reader what to do. An example lets the reader check their own understanding against a worked case, and that check is itself a payoff. Which means examples are also your pacing tool. They are how you hit the 300 word spacing without padding.

Watch it work on the advice “make your promise concrete.” Weak version: “This post will help you improve your content.” Better version: “By the end you will have a five part checklist to run on tomorrow’s draft.” The rewrite is the payoff. The bare instruction was not.

To apply the rule, audit a finished draft. Mark every passage that shows something: a before and after, a template, a named number, a mistake reproduced on the page. If the marked share is under 40 percent, you have written a lecture. Trade abstract sentences for demonstrations until the balance shifts. The word count barely moves. The usefulness per screen does.

Structure is a practice

In 2009 I was living in a 1996 Dodge Caravan, and at the end of that year I started blogging into silence. Nobody was reading. That is where this obsession with structure comes from. When you have almost no readers, you cannot afford to waste the few who show up.

When Empower Network launched on Halloween 2011, beginners on the original network were getting comments in their first week. Some of that was the network putting readers in front of them. The rest was posts written for how people actually read. Today we publish daily on this network ourselves and show our work, and the same mechanics apply on the more than 750 member blogs live on the rebuilt network.

None of this is a template you apply once. The checklist below is a rep, and you run it on every draft.

The checklist

Run this before you hit publish.

Lead: Does the first paragraph name the reader’s situation and point at a specific payoff, inside 15 seconds of reading?
Promise: Is the deliverable stated in one plain sentence near the top?
Spacing: Does every 300 word window contain something the reader can take with them?
Subheads: Do the subheads alone tell the story, and does each one earn re-entry?
Examples: Do demonstrations make up at least 40 percent of the words?

If you want a place to run those reps where readers already are, that is what The Blogging System is for: your blog on the network, a list you own, one honest post a day. It is $25 a month or $197 a year, with a 30 day money back guarantee, and your list is exportable any time.