She Knows SEO contains affiliate links and is a member of the Amazon Services LLC Associates Program. If you make a purchase using one of these Amazon links, we may receive compensation at no extra cost to you. See our Disclosure Policy for more information.

How to Write a Blog Post People Actually Want to Read

ByNina Clapperton

Writing a blog post is basically answering 1 person’s question, then organising your answer so they can use it.

I’ve written posts with an outline and without one, in stiff tech bro speak and in my actual voice, by typing and by talking into my computer when my arms won’t cooperate. The format changed. The basic job didn’t.

The easier way is to picture someone asking you the question at a party. Give them the short answer first. When they need more information, break the explanation into clear sections. Then end with what they need to do or understand next.

That’s the basic anatomy of a useful blog post: a title, an introduction that answers the question, a body that makes the answer easy to follow and a conclusion that moves the reader forward.

The words can be typed, written by hand or spoken into voice to text. What matters is helping a specific person get what they came to the post for.

Once you stop trying to sound impressive and start having that useful conversation instead, the blank page gets a lot less intimidating.

What Should a Blog Post Include?

Most blog posts have 5 basic pieces:

  1. A title that accurately tells the reader what the post delivers.
  2. An introduction that gives them the quick answer and a reason to trust the rest of it.
  3. A body that breaks the topic into useful sections with H2s and, where needed, H3s.
  4. A conclusion that gives the reader a relevant next step.
  5. Images, videos, tables or other media where they genuinely make the answer easier to understand or use.

That’s the physical shape of a blog post. It isn’t a fill in the blanks template that decides what every post has to say.

A tutorial, recipe, travel guide and affiliate post are all helping people do different things. Their headings and examples should reflect that. The structure supports the answer, not the other way around.

You also don’t have to create those pieces in the order the reader sees them. I normally write my title after the draft because I know what the post delivers by then. We will come back to that once the words exist.

Plan the Blog Post Before You Start Writing

Planning a blog post doesn’t mean deciding every sentence before you’re allowed to write. It means knowing who you’re helping, what you’re helping them do and the rough order they need the information in.

I didn’t always outline. I would start writing everything I knew about the topic and assume I could organise it later. Technically, I could. But it meant editing like freaking crazy because the useful answer was buried under repetition, detours and all the extra facts that happened to be in my brain that day.

Now I work out these pieces first:

  1. What specific question or topic is this post answering?
  2. Who needs this answer, and what do they already know?
  3. Where are they now?
  4. What should they understand, decide or be able to do after reading?
  5. What do I know, believe or have experience with that will make this answer mine?
  6. Where does this answer fit on my site and in the wider journey I’m creating for my audience?
  7. If I want the post found in search, what would this person actually type to find it?

The third and fourth questions give you the transformation from point A to point B.

For this post, point A is: I need to write a blog post, but I don’t really know what it should include or how to turn everything in my head into something useful.

Point B is: I understand the structure, I know how to plan the answer and I can create a draft that sounds like me instead of a school essay.

That transformation tells me what belongs here. It also tells me when to stop.

Once you know those pieces, turn the main answer into a rough list of sections. Start with your knowledge and your audience before reading a bunch of competing posts. It is very easy to accidentally copy the structure everyone else used, even when that structure doesn’t serve your people particularly well.

Research comes after I have my rough structure. I use it to check facts, fill real knowledge gaps and spot useful questions I may have missed. I don’t use it to replace my own experience or outsource my entire opinion to everyone who already wrote about the topic.

Your outline can change as you research and write. It is there to give you direction, not trap you.

How to Write a Blog Post Introduction

Your introduction should give the reader the quick answer immediately. It should NOT say: “So you want to know how to write a blog post?”

Obviously they do. That’s why they’re here.

It also should NOT say: “In this post, I’m going to tell you how to write a blog post.”

This isn’t an essay. You don’t need to announce what you’re about to prove. You need to show the reader that they’re in the right place, that you understand what they need and that you can help them.

I call this my “Costco Free Sample Policy”. Costco doesn’t describe an egg roll while you stand there and they promise you may eventually discover whether it tastes good. They actually hand you the sample. Do that in your introduction.

Give the reader a useful taste of the real answer. At the beginning of this post, I told you to answer 1 person’s question, give them the short answer first, break the explanation into clear sections and end with the next thing they need. That answer can stand on its own. If it was literally all you needed, amazing. You can leave and write your post. If you need to know what belongs in each section, how to make the post sound like you or what to do after the draft, you can keep reading.

And please don’t worry about giving the milk away for free! People will need the cow unless all they ever wanted was a sip of milk. If they only wanted a sip, give them the sip. They were never going to buy the whole cow just because you hid the milk under all that throat clearing.

How to Organise the Body of a Blog Post

The body turns the main question into smaller questions, then answers them in the order the reader needs them. For “how to write a blog post,” you need to know what the post includes before I explain how to write each part. Then you need the writing process, followed by the things that make the draft easier to read and publish. Those are the big questions, so each one becomes a section.

Treat Each H2 Like Its Own Question

An H2 should answer a distinct question or help the reader complete 1 part of the bigger process. Give the direct answer first. Then explain what you mean and add the process, example, opinion or experience that helps the reader use it.

This section is answering, “How do I organise the body of a blog post?” The short answer is: break the big question into smaller questions and answer each one under a clear heading. Everything else in this section is helping you understand what that looks like in practice.

Use H3s When a Section Has Smaller Parts

Sometimes 1 section still contains a few separate ideas. That’s where H3s help.

This H2 is about organising the body. Under it, I’m explaining the job of an H2, when H3s make sense and how to write headings people can understand. Those pieces belong together, but they are not the same point, so they each get their own H3.

You don’t need to turn every tiny thought into a heading. Use one when the reader needs a clear signpost or the section has genuinely moved to a smaller question.

Make Your Headings Useful

Your headings should tell people what each section covers. Don’t get so clever or stylistic that someone has no clue what they’re about to read. If the headings in this post were “Breathe,” “Wind” and “Hurricane,” you would have no idea what the fuck any of it meant. And you would probably leave.

People are lazy. I’m lazy too. We want to look at a page and understand what is there without carefully reading every word first.

Clear headings let readers skim the post, find the part they need and understand the shape of your answer at a glance.

This is also why I hate the extra TLDR sections people keep adding to blog posts. Your introduction already gave the quick answer. Your table of contents is literally a list of your headings.

You don’t need to summarise the summary before people are finally permitted to read the post.

How to End a Blog Post

A blog post conclusion should give the reader their next step.

I changed the way I handle conclusions because the traditional version usually repeats the points the reader just finished reading under “Conclusion” or “Final thoughts.” The heading tells them nothing, the recap adds nothing and the useful next step disappears.

Think about the conversation again. You answered the question. The reader knows something they didn’t know before. What would they naturally ask next? Or what do they need to do now to use the answer?

A travel itinerary might end with where to stay. A recipe might end with how to store it. A tutorial might end with the next step in the process.

The exact ending depends on where this specific reader is after your specific post. But something should move.

If your conclusion only repeats everything and wanders away, the reader still doesn’t know what to do. It is usually boring writing too.

Write the First Draft Before You Edit It

Once you have an outline, you need to get the answer out of your head.

You can type it. You can write by hand. You can use voice to text. Whatever works for your brain and your body.

I use voice to text a lot because I have chronic pain and mobility issues in my arms. It also helps me keep my writing conversational because I am literally talking through the answer instead of trying to make every sentence sound impressive.

The source for this post started as a voice note. I talked through what I wanted to teach, corrected myself, doubled back, said “cut that bit” and generally produced the kind of word vomit that makes sense when you’re speaking and would be deeply annoying to read as a finished article.

Then comes the actual editing.

I remove the ums, ahs, repeated ideas and spoken instructions. I move ideas into the section where the reader needs them. I rewrite anything that is confusing, weak or still sounds like raw dictation.

Writing the way you talk doesn’t mean publishing a transcript.

Your first draft only needs to exist. Once it does, you can turn it into something another person can easily understand.

Write Like Yourself, Not Like a Person Writing a Blog Post

When I started She Knows SEO, I thought I needed to use the formal, businessy style I saw tech bro SEOs using.

I published about 4 posts like that. I hated writing them so much that I stopped for a while.

It wasn’t only miserable for me. That stiff tech speak wasn’t particularly useful for the people I wanted to help, who were already confused by stiff tech speak. They didn’t need more tech speak. They needed someone to explain what the thing meant and what to do with it.

Writing became much easier when I let myself use plain English, actual opinions, weird analogies and the words I would use if the person was sitting beside me on the couch.

That is what “write the way you talk” means.

It doesn’t mean keeping every pause, filler word and unfinished thought from the way you physically speak. It means keeping your explanation, perspective and personality while editing the words so another person can follow them.

A blog post is not Wikipedia. Someone looking for Rome travel tips doesn’t need the full history of Rome before they’re allowed to see your tips. Someone searching for a competitive analysis tutorial doesn’t need you to spend half the post defining the term they just searched.

Give them your answer. Use your experience. Let yourself have an opinion.

Your audience should be able to feel that the post came from you. If someone copied it, they should recognise whose thinking and explanation it was.

Keep the Post Focused on the Reader

A blog post isn’t a diary. It is not “welcome to my website, here are all the thoughts currently wandering around my brain.”

It should help the reader do, learn, understand, decide or experience something.

That reader arrived with intention. They searched for this answer. You aren’t interrupting them on social media while they’re trying to watch funny cat fails and take a shit at work. They chose your post because they want something from it.

Give them that thing.

This is why the point A to point B transformation matters so much. It helps you decide what serves the reader and what is only related because the information happened to be in your head.

I have absolutely written content because I thought the keyword looked useful without properly asking whether the post belonged in my ecosystem. That is how I ended up writing a beach packing list when I don’t even like the beach.

Technically, I could write it. But it didn’t connect to the person I was trying to help or what I wanted my site to do. It was a post I could write, not a post I should write.

Focus applies inside the post too. Don’t add every related thing you know just because it could technically connect.

If “how to write a blog post” is becoming a 100 page ebook on everything vaguely related to blogging, you are probably answering more than 1 question. You may have 12 focused posts hiding inside the giant one.

Those posts can have different jobs. A post intended to help someone choose or buy something needs to help them make that decision without turning into a weird sales pitch. That is a different job from this post, so you don’t need all of that strategy crammed in here too.

Answer the question they asked. Then let them ask the next one.

Make Your Blog Post Easy to Read

A useful answer can still become unusable if you put it inside 1 giant grey wall of text.

Make the post easy to follow at a glance with:

  • Clear H2s and H3s
  • Short paragraphs
  • Lists when they make steps or examples easier to scan
  • Tables when someone needs to compare information
  • Images or videos when they explain or demonstrate something useful
  • White space
  • A table of contents for longer posts

If your theme doesn’t create the shortcuts automatically, you can make the table of contents clickable when you upload the post. That is an upload problem, not something you need to derail your writing session to solve.

I usually keep paragraphs to about 1 to 3 sentences. That doesn’t mean every sentence needs its own paragraph. It means the reader isn’t digging through a giant block of text to find the point.

Formatting should always have a job.

Don’t bold random sentences because the page looks boring. Don’t add an image at some arbitrary fixed interval. Ask whether the choice helps the reader understand the answer, find the information or use the post.

And remember that readable and accessible are connected, but they are not exactly the same thing. Once the post is formatted, check that the headings, links, images and other pieces work for more than the person who created them.

How Long Should a Blog Post Be?

A blog post should be as long as this reader needs it to be.

I know people want an exact number. There isn’t one.

The useful length depends on the question, what the reader already knows and how much information they need to get from point A to point B.

If you have to add a pile of irrelevant bullshit to hit a word count, the post didn’t need those words.

If the answer is becoming enormous, look for the moment where you quietly started answering a new question. That section may need its own post.

The time it takes isn’t universal either. I’ve written some posts in 45 minutes and had others take 2 weeks, so the time your blog post takes isn’t a useful way to decide whether you’re doing it right. The topic, research, format and your actual life all affect the process.

Common Blog Writing Mistakes

Most blog writing mistakes come from forgetting the person and performing what you think a blog post is supposed to be instead.

So please don’t:

  • Write it like a school essay
  • Make the whole post about you instead of using your experience to help the reader
  • Hide the answer under a long introduction
  • Copy someone else’s structure before thinking through your own answer
  • Use headings that explain nothing
  • Publish the entire post as 1 giant paragraph
  • Ramble into every vaguely related topic
  • Call separate posts “Part 1” and “Part 2” when neither one answers a complete question by itself
  • Make up facts, examples, experience or results
  • Leave the useful draft sitting in Google Docs forever because it isn’t “good enough” yet

Done is better than good!!

I like that better than “done is better than perfect” because nothing is ever perfect. But your version of good is probably miles beyond what your audience needs before the post can help them.

Your audience is helped most when the useful content is available to them.

They’re helped least when it lives in your Google Docs folder while you promise yourself you will publish it eventually.

Examples of Well Written Blog Posts

There isn’t 1 exact formula every blog post needs to follow. The structure should fit the question, the niche and the reader.

These posts from Profitable Part-Time Blogger students show what that looks like in different niches.

What to Do After Writing a Blog Post

Writing the words isn’t the final step.

Once the draft exists:

  1. Edit it for the answer, order, repetition and anything the reader doesn’t actually need.
  2. Write the title.
  3. Upload the post to your site if you wrote it somewhere else.
  4. Format the headings, paragraphs, lists and tables.
  5. Add the images or videos that genuinely help.
  6. Add alt text that describes what each image shows and why it matters for anyone who cannot see it.
  7. Add the internal and external links that help the reader. Internal links should move people into the related answers on your site, not sit there because you were trying to hit a number.
  8. Preview the post on desktop and mobile.
  9. Publish it, then check the live version to make sure everything worked.
  10. Promote it.
  11. Update it when new information, experience or examples give you a real reason to improve it.

A blog post is never done forever. You can make it better later. But the useful version on your site can help someone today, and the better version you’re still editing in Google Docs cannot.

I normally write the title after I finish the draft because then I know what the post became. I can make sure the title represents the answer instead of forcing the answer to match a title I chose before I knew where I was going.

Once your draft tells you what it genuinely delivers, turn that answer into a title your audience will understand and want to click.

Like this post? Share it with others!

Nina Clapperton is the founder of She Knows SEO.

She started blogging in 2018 and spent years doing everything “right” while earning $0. Then she stopped guessing and learned how search actually works. She rebuilt her travel site around audience intent and structure and grew to 50,000 sessions in 6 months. Within a year, the blog was bringing in $30,000 months and later crossed 243,000 pageviews.

She took the same audience first SEO approach and built her education business into multiple $100,000 months.

Now Nina teaches bloggers and online business owners how to build search powered businesses grounded in strong positioning, clear structure, and monetisation that actually supports their audience. She covers traditional SEO and AI driven search without the tech bro noise, and she’s known for explaining complex strategy with analogies you won’t forget.

Want to organize your SEO strategy?

Get My SEO Spreadsheets

10 Spreadsheets for Bloggers

OOO, TELL ME MORE 👀
SEO Spreadsheets for Bloggers - mock up on a laptop of the spreadsheets with a button saying "Only $9!" on the corner.