Blog / Digital growth /
How to write a blog post that ranks and still reads well
You’ve probably read a post that was clearly “written for SEO”. The keyword in every other sentence. A 300-word introduction before anything useful. Headings that read like a list of search terms. You found what you needed, eventually, and never came back.
Those posts used to rank. More and more, they don’t. The posts that do well now are the ones written for the reader first, with the SEO built in quietly underneath.
Here’s the process I use.
Key takeaways
- Choose a topic people actually search for, then work out exactly what they want from it.
- Answer the question early. Make the rest of the post earn the scroll.
- Use your keyword where it helps the reader understand the page: title, intro, a heading or two. Not everywhere.
- Add something only you can: an example, a result, a screenshot, an opinion.
- Edit for the reader last: shorter sentences, clear headings, a real ending.
1. Start with a search, not a topic
“I want to write about email marketing” is a topic. “How to grow an email list from zero for a small blog” is a search: something a real person types when they have a real problem.
Find searches with free tools (I listed my favourites in keyword research with no budget): Google’s autocomplete, “People also ask”, Search Console queries you already get impressions for, and the questions your customers ask you.
Pick one main search per post.
2. Work out what the searcher wants
Search the phrase yourself and study the first page:
- Are the results guides, lists, product pages or tools?
- Are they long or short?
- What do they all cover? What do they all miss?
That’s the search intent, and getting it wrong is the most common reason a good post doesn’t rank. If everyone ranking has a step-by-step guide and you write an opinion piece, you’re answering a different question.
3. Answer early
Readers decide in seconds whether they’re in the right place. So:
- Put the answer, or a clear promise of it, in the first few lines
- Skip the throat-clearing (“In today’s fast-paced world…”)
- Start with the problem, a short story, or the answer itself
A good intro makes the reader nod and keep going. It doesn’t need to be clever.
4. Outline with headings people would scan for
Write your H2s as if they were a table of contents for someone in a hurry. Each one should tell the reader what that section gives them.
Good: “How to set up your first automation”. Weak: “Automation considerations”.
Headings help Google understand the structure, too. But write them for people, and they’ll work for both.
5. Use the keyword where it makes sense
The keyword (and close variations) belongs in:
- the title
- the URL: short, using the main words
- the first paragraph, naturally
- one or two headings, if they genuinely fit
- the meta description
That’s it. Modern search understands synonyms and context. Repeating the exact phrase twenty times doesn’t help, and it makes the writing worse.
6. Add what only you have
This is the step most posts skip, and it’s the one that matters most now that anyone can generate competent, generic text.
Ask: what can I add that a reader can’t get from the other ten results?
- a real example from your own work
- a number: what changed, how long it took, what it cost
- a screenshot of the setting, the report, the before and after
- an opinion: “I’d skip this step, here’s why”
- a mistake you made, so they don’t have to
You don’t need all of them. One genuine detail is worth more than five paragraphs of general advice.
7. Make it easy to read
- Short paragraphs. Two to four lines on a phone.
- Lists for steps and options, tables for comparisons.
- Bold the phrases a scanner should catch.
- Plain words. If there’s a technical term, explain it the first time, with an example.
- Images only where they help: a screenshot beats a stock photo every time.
8. Link like a helpful friend
Link to your own related posts where a reader would genuinely want more (there’s a system for that in internal linking on WordPress). Link out to good sources when you mention a fact. Both help readers, and both help search engines understand where your post fits.
9. Write the title and description last
Once the post is written, you know what it actually delivers. Then write:
- a title that includes the main search and makes a clear promise, ideally under 60 characters so it isn’t cut off
- a meta description that sells the click: what will they get? (I use ChatGPT for first drafts of these, with some checks after.)
10. End properly
Don’t end by summarising what they’ve just read. End with something useful: a next step, a small task, a question. The reader should know what to do next.
Before you publish: a quick checklist
| Check | Done? |
|---|---|
| One main search, and the post matches its intent | |
| Answer or promise in the first few lines | |
| Headings make sense on their own | |
| Keyword in title, URL, intro and description | |
| At least one thing only you could add | |
| Links to related posts and to sources | |
| Read aloud once: does it sound like a person? |
FAQ
How long should a blog post be to rank?
As long as it needs to be to fully answer the search, and no longer. Look at what ranks: if the top results are 800 words, a 4,000-word post isn’t automatically better. It might just be slower to get to the point.
How often should I publish?
Consistently, at a pace you can keep up without the quality dropping. One good post a week beats five rushed ones.
Should I update old posts?
Yes. Updating a post that already has some traffic is often faster than writing a new one. Refresh the facts, add what you’ve learned since, and check it still matches what people are searching for.
Related reading
- Keyword research for a small website with no budget
- Search intent: why the same keyword needs different pages
- Internal linking on WordPress: a simple system
- Using ChatGPT to draft meta descriptions (and what to check after)
Take the last post you published and run it through the checklist above. Which row is empty? Start there.