Nayan Dhumal
Most blog posts are opened, skimmed for a few seconds and closed. The writing is rarely the problem. The structure is. This guide shows you how to plan, write and edit a post so that a reader who arrives from Google stays until the last line.
Think about the last article you gave up on. You probably did not leave because of a spelling mistake. You left because the intro took too long, or the page was a wall of text, or you could not tell whether your question would ever be answered.
Your readers behave the same way. They arrive with one question, give you a few seconds to prove you can answer it, and then decide. Everything in this guide is about winning that decision again and again as they move down the page.
None of this needs talent. It needs a repeatable process, and that is what you will have by the end.
Key takeaways
- Readers decide in the first few lines. Answer the main question early, then earn the rest of their time.
- Plan before you write: one reader, one question, one promise and a clear outline.
- Write the way you speak. Short sentences, short paragraphs and plain words beat clever ones.
- Make the post easy to scan with honest subheadings, lists, tables and examples.
- Editing is where a post becomes readable. Cut first, polish second.
- A post is finished when the reader knows exactly what to do next.
Why readers leave before the end
Before fixing anything, it helps to know what actually sends people away. In almost every post that loses its readers, you will find one of these five problems.
- The intro delays the answer. Three paragraphs about the history of the topic, and the reader still does not know if the page is for them.
- The post is a wall of text. Long paragraphs with no subheadings look like work, and people do not come to a blog to work.
- It is written for everyone. A post that tries to serve beginners and experts at once ends up being too slow for one group and too confusing for the other.
- It says things without showing them. Advice like “write engaging content” gives the reader nothing to do. An example does.
- It has no direction. The sections could be shuffled and nobody would notice. Without a sense of progress, there is no reason to keep scrolling.
Notice that none of these are about vocabulary or grammar. They are planning problems. That is good news, because planning is easy to learn.
Before you write: plan the post
A readable post is mostly decided before the first sentence is written. Ten minutes of planning saves an hour of rewriting. Work through these four steps in order.
Pick one reader and one question
Write down who the post is for and the single question they typed into Google. Be specific. “People interested in blogging” is not a reader. “Someone who started a blog last month and has published three posts that nobody read” is.
Then write their question in their own words, the way they would say it to a friend. If you cannot fit the question into one sentence, the post is trying to do too much and should be split into two.
Check what the reader expects to find
Search for your topic and look at the first page of results. You are not copying anybody. You are learning the shape of the answer people want.
Are the top results step-by-step tutorials, lists, comparisons or opinion pieces? How long are they? Which questions appear in the “People also ask” box? If every result is a step-by-step guide and you write an essay, you are answering a different question from the one being asked.
Once your blog has some traffic, your own data becomes even more useful. The Performance report in Search Console shows the exact searches that bring people to your pages. If you have not set it up yet, follow my Google Search Console guide for beginners.
Write the promise in one sentence
Finish this sentence: “After reading this post, you will be able to …” That is your promise. It keeps you honest while you write, because every section either helps the reader get there or it does not belong.
A weak promise sounds like “you will know more about email marketing”. A strong one sounds like “you will be able to write a welcome email and schedule it today”.
Outline with subheadings first
Now write only the subheadings. Each one should be a step toward the promise, and together they should read like a short summary of the whole post. A good test: if a stranger read only your subheadings, would they understand what the post teaches?
Put the sections in the order the reader needs them, not the order you thought of them. For a tutorial that is usually the order in which things are done. For an explanation it is usually simple ideas first, then the details.
Pro tip
Under each subheading, write one line that says what the section must deliver. For example: “Explain why short paragraphs are easier on a phone, with a before and after.” When you sit down to write, you are no longer facing a blank page. You are filling in answers.
Write a headline that makes an honest promise
The headline has one job: to get the right person to click and to tell them truthfully what they will get. A clever headline that hides the topic loses to a clear one every time.
A few patterns work for almost any post:
- How to + result. “How to Write a Blog Post People Actually Finish Reading”.
- Number + thing + benefit. “9 Ways to Monetize a Blog With Under 1,000 Visitors”.
- Topic + for whom. “Keyword Research for Complete Beginners”.
- Question the reader is asking. “Is Shared Hosting Good Enough for a New Blog?”
Put the main topic near the start, keep the headline short enough to be read at a glance, and never promise more than the post delivers. A reader who feels tricked by the headline does not finish the article, and does not come back.
Open with a hook, not a warm-up
The introduction is the most-read part of your post and the place where most readers are lost. It does not need to be long. It needs to do three things quickly.
- Show the reader you understand the problem. Describe their situation in a sentence or two, in words they would use themselves.
- Promise the result. Tell them what they will be able to do by the end.
- Give them a reason to trust the page. This can be as simple as saying what the guide covers and how it is organised.
Then stop and start the first section. Compare these two openings for a post about fixing a slow website.
| Weak opening | Strong opening |
|---|---|
| “In today’s digital world, website speed is more important than ever. Since the early days of the internet, people have wanted pages to load quickly.” | “Your blog takes six seconds to load and you do not know why. This guide walks you through the five checks that find the cause, in the order you should do them.” |
| Talks about the topic in general | Talks about the reader’s problem |
| Could be the start of any article | Could only be the start of this one |
| Delays the answer | Promises the answer and says how it is organised |
If your post answers a direct question, such as “how long should a blog post be?”, give the short answer in the first few lines and use the rest of the post to explain it. Some writers worry that readers will leave once they have the answer. In practice the opposite happens. A reader who gets a straight answer trusts you, and trust is what keeps people reading.
Make the post easy to scan
Almost nobody reads a web page from the first word to the last. People scan first, decide whether the page is worth their time, and then read the parts they need. Your job is to make scanning easy, so that the decision goes your way.
Use subheadings that carry meaning
A subheading such as “Step 2” or “More tips” tells the reader nothing. “Compress your images before you upload them” tells them what the section contains and what to do. Write subheadings as small promises.
Keep paragraphs short
On a phone screen, a five-line paragraph on your laptop becomes a block that fills the display. Aim for two to four sentences per paragraph. A single-sentence paragraph is fine when you want an idea to stand out.
Turn lists into lists
If a sentence contains three or more items separated by commas, it probably wants to be a bullet list. If the order matters, make it a numbered list. Lists are easy to scan and easy to follow while doing a task.
Use tables for comparisons
When you are comparing options across the same points, a table does in ten seconds what three paragraphs cannot. Use it for prices you have checked, features, pros and cons, or before and after examples.
Bold the few things that matter
Bold text pulls the eye, which is exactly why it must be used sparingly. Bold the key phrase of a list item or one important warning. If everything is bold, nothing is.
Add images that explain
A screenshot that shows where to click, or a simple diagram, is worth including. A stock photo of a person smiling at a laptop is not. Every image should help the reader understand something faster than words would.
Here is a quick checklist to run on any draft:
- A subheading appears at least every 200 to 300 words.
- No paragraph is longer than four sentences.
- Steps are numbered, and options are in bullets or a table.
- Each section could be understood by someone who skipped the one before it.
- The most important sentence of the post is impossible to miss.
Write the way you speak
The easiest posts to read sound like a knowledgeable friend explaining something across a table. You get there with a few habits.
- Use “you” and “I”. You are talking to one person, not addressing a crowd.
- Choose the plain word. “Use” instead of “utilise”, “help” instead of “facilitate”, “about” instead of “regarding”.
- Keep sentences short. If a sentence needs to be read twice, split it in two.
- Prefer the active voice. “Install the plugin” is clearer than “the plugin should be installed”.
- Explain a term the first time you use it. One short clause is enough, and experienced readers will not mind.
- Cut filler. Words like “very”, “really”, “basically” and “in order to” can almost always go.
A simple test is to read your draft aloud. Wherever you stumble, run out of breath or feel bored, your reader will too. Mark those places and rewrite them.
Good to know
Writing simply is not the same as writing for beginners. Experts also prefer clear sentences, because they are faster to read. You can discuss an advanced topic in plain language. What you should never do is make an easy topic sound difficult.
Show, do not just tell
General advice slides off the reader. Specific examples stick. Whenever you make a claim or give an instruction, ask yourself what it would look like in practice and show that.
- Give an example. Do not only say “write a specific headline”. Show a vague one and the improved version next to it.
- Use numbers you can stand behind. “Aim for two to four sentences per paragraph” is more useful than “keep paragraphs short”.
- Walk through a real case. A short story about how a post was fixed teaches more than a list of principles.
- Show the screen. In a tutorial, a screenshot of the exact setting removes all doubt.
Only use facts and figures you have checked, and say where they come from. An invented statistic may sound impressive, but one reader who knows better is enough to damage your credibility for the whole post.
Edit in three passes
First drafts are for getting ideas down. Readable posts are made in the edit. Do not try to fix everything at once. Go through the draft three times, each time with a different job.
- Pass 1: Cut Read the whole post and remove anything that does not serve the promise. Delete the warm-up at the start, the side stories and the points you made twice. Most drafts get better when they lose a tenth of their words.
- Pass 2: Clarify Go through sentence by sentence. Split long sentences, swap complicated words for plain ones, and add an example wherever the advice is abstract. Check that every subheading says what its section delivers.
- Pass 3: Check Read it aloud, or have your device read it to you. Fix spelling and grammar, test every link, confirm every fact and number, and look at the post on your phone.
If you can, leave a gap between writing and editing. Even a few hours helps. You will come back seeing the post the way a reader does, not the way its writer does.
Watch out
Do not edit while you write. Stopping after every sentence to polish it breaks your train of thought and can turn a one-hour draft into a full day. Write the whole draft badly first. Then fix it.
End with a clear next step
Many posts simply stop, or finish with “I hope this helped”. That wastes the moment when your reader is most willing to act.
A good ending does two things. It reminds the reader of the main points in a few lines, so the post feels complete. Then it gives one clear next step: try the method on a draft, read a related guide, download a checklist or leave a question in the comments. Offer one action, not five. People who are given too many choices often take none.
Checklist before you hit publish
Run through this list once for every post. It takes five minutes and catches most of the problems that make readers leave.
- The headline says clearly what the post delivers.
- The first three sentences name the reader’s problem and promise a result.
- The main question is answered early.
- Every subheading describes what its section contains.
- Paragraphs are short and steps are numbered.
- Each piece of advice has an example or a reason.
- Every fact, number and link has been checked.
- The post has been read aloud once.
- It looks right on a phone.
- The ending gives one clear next step.
If you have not published anything yet, start with my step-by-step guide on how to start a blog, and come back here when you are ready to write your first post.
Ready to write your next post?
Pick a topic your readers are already searching for, then use the outline in this guide. If you do not have a topic yet, these niche ideas are a good place to start.
Frequently asked questions
How long should a blog post be?
As long as it takes to answer the reader’s question fully, and no longer. A simple question may need 600 words. A complete tutorial may need 2,500 or more. Look at the pages that already rank for your topic to see how much depth readers expect, then cover the subject properly without padding.
How long does it take to write a good blog post?
It varies with the topic and your experience. For a detailed guide, expect to spend time on research and planning, a first draft, and editing. Many bloggers find that planning and editing together take as long as the writing itself. The process gets faster once you have a template you reuse.
Should I give the answer at the start of the post?
Yes, when the reader is asking a direct question. Give the short answer first and use the rest of the post for the explanation, examples and details. Readers trust a page that respects their time, and they are more likely to keep reading.
How many subheadings should a post have?
There is no fixed number. A useful rule is one subheading every 200 to 300 words, or whenever the topic changes. Use H2 headings for the main sections and H3 headings for points inside a section.
Does making a post easy to read help with SEO?
It helps indirectly. Search engines try to show pages that satisfy the searcher. A post that answers the question clearly, is well structured and keeps readers on the page is more likely to do that than one people leave after a few seconds. Clear headings also help search engines understand what each part of your page covers.
Can I use AI tools to write my blog posts?
You can use them for help with outlines, ideas and editing. Do not publish their output unchecked. AI tools can state things that are wrong with great confidence, and they cannot add your own experience or examples. Treat the result as a draft that you fact-check, rewrite in your own voice and improve.