The one structure that makes a blog post answer its question, survive being scanned, and get read again — demonstrated on the post itself.
A blog post needs a question it answers, an answer up front, and every section serving that answer — and, if it is worth writing, a structure that still works when it is read again later. Everything else — the hook, the formatting, the tone — follows from those things. This post explains the structure, and it applies the rules to itself as it goes. Each section demonstrates the point it makes.
Before writing a word, decide the single question the post must answer. Not the topic — the question. "How to write a blog post" is a topic; "what structure makes a post answer its question and get read again?" is a question. The difference decides everything you write.
The thesis is the interpretation of the question. The Writing Center at UNC states it plainly: a thesis "directly answers the question asked of you." If you can write your answer in one sentence, you have a contract with the reader. The rest of the post either honors that contract or breaks it.
The question for this post is: what structure does a blog post actually need? The answer, stated now so we are clear: a question, an answer up front, and sections that each serve that answer — in a shape that survives being scanned now and re-read later.
Put the answer first, details after. This is the inverted pyramid, and it is not a style choice — it is a response to how people read.
Attention collapses fast. Nielsen Norman Group measured that 81% of readers look at the first paragraph, but only 32% make it to the fourth. If your conclusion sits at the bottom, most readers never see it. Put it at the top, and every reader leaves with the point even if they stop at paragraph two.
This post did it. You read the whole answer in the opening paragraph. Everything below is the why and the how, in decreasing order of importance.
The same rule applies inside each section. First sentence: the point. Following sentences: the support. Readers scan first sentences — the F-pattern means the left edge and the early words get the most attention.
Most readers do not read; they scan. NN/g has measured this for two decades: 79% of users scan, and only 16% read word by word. You cannot change that, but you can structure for it.
Three formatting choices do most of the work:
Keep the bold under 30% of the text. Bold is for the critical phrases, not for emphasis. Over-formatting is as bad as none.
For a post over a thousand words, add a short summary at the top. The reader decides in seconds whether to continue; the summary gives them the map.
Concrete examples before abstract rules. A reader who sees the pattern in action understands it faster than one who reads a description of it.
This post is its own example. Every section here shows the rule it describes, so the structure is not a claim — it is a demonstration. That is the worked-example effect: seeing one solved problem teaches more than instructions alone.
There is a limit, and it matters for a technical blog. Storytelling helps novices, but it can slow experts down — the expertise reversal effect. A reader who already knows the field wants the lesson, not the setup. Resolve it this way: keep the conclusion up front, and put the story or example after it, as the "how." Experts can skip it; novices get it.
Narrative does one thing well: it makes ideas stick. Curiosity improves memory — the higher the curiosity before an answer, the better the recall weeks later. A hook that opens a question and closes it later is not decoration; it is a memory aid. But the hook must be honest. A promise the post does not keep destroys trust, and readers who are deceived once do not come back.
If you cite research, report how confident the evidence is. This separates a post you can trust from one you cannot.
Two axes matter, and they are different: the strength of the evidence, and the size of the effect. Strong evidence can point to a small effect. Weak evidence can point to a large one. Conflating them is the most common error in science writing. The distinction is clearer as a table than as prose — which is the point:
| Strong evidence | Weak evidence | |
|---|---|---|
| Large effect | Best case: trust it, act on it | Promising: worth a cautious trial |
| Small effect | Real but modest: report it honestly | Unverified: label it speculative |
When you give a number, give the uncertainty around it. An effect size without a confidence interval is a headline, not a measurement. Example: guided discovery has an effect of d = 0.30, with a 95% confidence interval from 0.23 to 0.36 — the interval tells you the finding is real, not just nonzero. And translate it: a "d of 0.3" means nothing to most readers; "a learner using the method would outperform another roughly 58% of the time" means something.
Use a consistent scale for certainty: established, very likely, probable, speculative, inconclusive. It takes one sentence, and it lets you re-read your own post without second-guessing it.
For health-adjacent topics, this matters more. The SMOG readability score exists for health content, and it correlates strongly with comprehension. Plain language is not dumbing down; NN/g found that even experts prefer short, clear text. Nobody has ever complained that a text was too easy to understand.
The structure above makes a post answer its question and survive the scan. The third thing — getting read again — is mostly a matter of what the question was in the first place. Ask: will this question still be worth answering in a year? A post about a durable problem (how to learn Rust, how to structure a post) gets re-read because the question persists. A post about a trend or a version number does not, no matter how well it is structured.
Two choices make rereading more likely, and both are structural:
The scan structure you already have does the rest: a reader can reopen the post, find the section they need, and leave. That is rereading, and it works only because the headings are scannable and the sections stand alone.
Every section must serve the question. If it does not, cut it — no matter how interesting it is.
The reverse outline finds the problem: after drafting, summarize each section in one line, in order. Then test each line against the question. Sections that drift off-topic are the scope creep that sinks posts. You are covering the topic instead of answering the question.
There is a test for this. Ask of every paragraph: so what? If the reader cannot say why it matters to the question, the paragraph does not belong. It is a hard thing to do with your own writing. The UNC guide puts it bluntly: omit evidence that does not serve the question.
An article I admire, this-blog-is-a-notebook, had this problem — it said the same thing four times. Cutting the repetition made it stronger. The first draft had more; the published version says it once.
The conclusion must answer the opening question explicitly. The reader who skips straight from title to conclusion should be able to reconstruct the full answer.
This is the test: write the question, write the conclusion, and read them together. If the conclusion does not respond to the question, the post has not closed its loop.
The University of Wisconsin writing handbook describes the good conclusion as one that "revisits your main idea with new insight." It is not a summary, but a return to the question that adds something. And if you opened with a question, close it. An open loop that never closes is a broken promise.
Different blogs, different structures, one shared habit: they write for themselves first and get read for it.
What these have in common: they answer a real question, they structure for the scanner, and they are honest about what they know. The structures differ; the habit is the same.
Every rule in this post serves one habit: decide what question you are answering, then make every sentence pull toward that answer.
Structure is not a template. It is the visible shape of a single decision. A post that knows its question writes itself; a post that does not cannot be saved by formatting.
This post asked one question and answered it. You can verify the structure worked: read the opening paragraph, read the conclusion. Both give the same answer — a question, an answer up front, sections that serve it, and a shape that still works when read again. That is the test. If your post can survive reading only its start and end — now and in a year — the structure held.