How to Write a Blog Post People Read to the End
Most blog posts lose readers in the first few lines, not the last few. Someone lands from Google with a question, scrolls past three paragraphs of warm-up, doesn't see their answer and hits the back button. The post might have been excellent from paragraph four onwards. Nobody found out.
Writing a post people finish isn't about talent. It's a handful of habits, and you can use every one of them on your next post.
Start with the reader's question, not your topic
"Sourdough" is a topic. "Why is my sourdough so dense?" is a question, and it's the one somebody actually typed into a search box at eleven at night with a flat loaf in front of them.
Before you write a word, finish this sentence: The reader wants to know... If you can't finish it in one line, you're not ready to write yet. Pick a narrower angle.
Questions give you three things a topic doesn't:
- A clear test for every paragraph (does this help answer it?)
- An obvious opening, because you can answer it straight away
- A natural ending: once it's answered and the reader knows what to do next, you stop
If you're not sure which questions your readers are asking, the search suggestions under Google's search box and the "People also ask" boxes are a free starting point. Our guide to planning your first 30 posts goes further on turning those into a list.
Write a headline that promises something specific
A headline is a promise. Vague promises don't get clicked, and broken ones get abandoned.
| Weak | Stronger |
|---|---|
| Sourdough Tips | Why Your Sourdough Is Dense (and 6 Fixes That Work) |
| Thoughts on Budgeting | How to Cut £100 a Month From Your Food Shop |
| My Garden Update | What I'd Plant in a North-Facing Garden Next Spring |
The stronger versions name the problem, hint at the payoff and often include a number or a clear scope. Don't overreach, though. If the headline says "6 fixes", give six good ones, not four and two fillers. Readers notice.
Write the headline first as a working title, then rewrite it once the post is done. You'll know far better by then what the post actually delivers.
Get to the point in two or three sentences
Your opening has one job: show the reader they're in the right place and that the answer is coming. The fastest way is to give them part of the answer immediately.
Compare these two openings for a post about dense sourdough:
Baking bread is one of life's great pleasures. There's nothing quite like the smell of a fresh loaf coming out of the oven. But sometimes things don't go to plan...
A dense sourdough loaf is nearly always one of three things: a weak starter, too little proving time or dough that's too wet to hold its shape. Here's how to tell which one is yours, and how to fix it.
The first could open any baking post ever written. The second tells the reader exactly what they'll get, and many will keep reading because they now want to know which of the three it is.
Write your opening last if it helps. It's much easier to summarise something that exists.
Use subheadings that say something
Most readers scan before they read. They jump through the subheadings to see if the post covers their situation. Make those subheadings do real work.
"Introduction", "Step 2" and "Other things" tell the scanner nothing. "Check your starter is active before you mix" tells them exactly what the section covers, and if that's their problem, they'll stop and read.
A good test: read only your subheadings, top to bottom. Do they make sense as a rough summary of the post? If yes, the structure is sound. If they read like a list of vague labels, rewrite them.
Keep paragraphs short
On a phone, a five-sentence paragraph fills the screen. It looks like hard work before anyone has read a word.
Aim for one to three sentences most of the time. Mix in the occasional longer one when an idea needs room, and the occasional one-liner when something deserves emphasis.
Like this.
Short paragraphs don't mean shallow writing. They just give the eye places to rest.
Be specific
Generic advice is the main reason people stop reading. They've seen "make sure your starter is healthy" a dozen times. What they haven't seen is a clear check they can do right now.
Swap vague for concrete wherever you can:
- "Feed it regularly" becomes "feed it at the same time every day for a week before baking"
- "Prove it long enough" becomes "it should have grown by about half and spring back slowly when you press it"
- "Use the right flour" becomes "use strong bread flour, not plain flour"
Examples, numbers, named tools, before-and-after comparisons and your own results all do this. If a sentence could appear unchanged in any post on the subject, it's probably not pulling its weight.
Use lists and tables where they help
Lists are good for steps in order, sets of options and checklists. Tables are good for comparing things side by side: prices, features, pros and cons.
They're not good for everything. An argument, an explanation of why something works or a story reads better as normal prose. A post that's nothing but bullet points feels like notes, not writing. Use a list when the content is genuinely list-shaped.
Edit it hard
Your first draft is for getting ideas down. Your second pass is where the post gets good. Two habits make the biggest difference.
Cut about 20%. Go through line by line and remove anything that repeats a point, warms up before the point or hedges it into mush. Phrases like "it could be said that", "in many cases" and "basically" can usually go. Whole paragraphs often can too. The post will feel faster and more confident.
Read it aloud. Your ear catches what your eye skips: sentences that run out of breath, words repeated three times in a paragraph, places where you'd never talk like that. If you stumble reading it, a reader will stumble too.
Then check the basics: is every fact right, does every link work, and does the post deliver what the headline promised?
A simple post template
When you're staring at a blank page, this outline gets most how-to and advice posts written:
- Headline that names the problem and the payoff.
- Opening of two or three sentences that starts answering the question.
- A short section on the quickest fix or the most common answer.
- Three to six sections, each with a descriptive subheading, covering the details, options or steps.
- Specific examples, numbers or a comparison table in at least one of those sections.
- A section on common mistakes or what to do if it still isn't working.
- A clear next step: what to try, read or do now.
It won't fit every post. Opinion pieces and personal stories need a looser shape. But for answering questions, which is most of what a new blog should be doing, it works.
Mistakes that make people leave
Throat-clearing intros. Background, history, a definition nobody needed, "In this post I'll cover...". Cut it and start with the answer.
Walls of text. Long paragraphs, no subheadings, no breaks. Even good content gets skipped when it looks like homework.
Burying the answer. If the one thing the reader came for is in paragraph twelve, many will never get there. Put it near the top, then explain.
Padding to hit a word count. A 900-word post that fully answers the question beats a 2,500-word one stretched to look thorough. Length should come from usefulness, not the other way round.
No clear next step. The reader finishes and... nothing. Tell them what to do now: try the fix, read a related post, download the checklist, sign up for updates. A post that ends with direction feels finished.
Never reading it back. Typos and clumsy sentences tell readers you didn't care much. One proper read-through catches most of them.
Your next post
Take the post you're writing now, or the next one on your list, and do three things before you publish: write down the reader's question in one sentence, rewrite the opening so it starts answering that question within three lines, and cut a fifth of the words. That alone will put it ahead of most posts on the same topic.
When you're ready to get those posts found, SEO for new blogs covers what matters most in your first year.
