Guide No. 7
How Long Should a Blog Post Be?
Typical lengths for different kinds of posts, what Google says about word count, and how to tell whether a draft is too long or too short.
Short answer
As long as it takes to answer the question fully and no longer. For a personal blog that usually means 600 to 1,500 words for most posts, 300 to 600 for quick updates, and 1,500 words or more only for detailed guides. Google says it has no preferred word count.
Key takeaways
- Length should follow the job the post does, not a target number.
- Google's own guidance on helpful content says it has no preferred word count.
- Most useful personal blog posts land between 600 and 1,500 words.
- Cut anything a reader would skip; add only what they would otherwise go and search for.
In this guide
"How long should my post be?" is one of the first questions new bloggers ask, usually right after they've written 400 words and wondered whether that counts. The honest answer is that length comes out of the post, not the other way round. That's not much help on its own, so here are the ranges that tend to work and a way to judge your own drafts.
Is there an ideal word count for a blog post?
No single number is ideal; the right length is whatever fully answers what the reader came for, without padding.
You'll find articles claiming that the perfect post is 1,600 words, or 2,100, or 7 minutes of reading time. Those figures come from studies of what ranked or got shared at one point, on certain kinds of sites. They describe averages, and averages hide everything that matters about your post.
Google's own guidance on helpful content is direct about this. In its self-assessment questions for writers, it asks whether you're writing to a particular word count because you heard Google prefers one, and answers that it doesn't. Search engines care whether the page satisfies the person searching, and length is only a side effect of that.
How long are different kinds of posts?
Most personal blog posts work at 600 to 1,500 words, with quick notes shorter and in-depth guides longer.
| Type of post | Typical length | What decides it |
|---|---|---|
| Quick note or update | 300 to 600 words | One point, made once |
| Opinion or reflection | 600 to 1,200 words | The argument and one or two examples |
| How-to for one task | 700 to 1,500 words | The number of steps and the likely problems |
| Review of a book, tool or place | 800 to 1,500 words | What you'd want to know before buying or going |
| Detailed guide | 1,500 to 3,000 words | How many related questions it has to answer |
| List of resources | Any length | The number of items worth including |
Treat these as signals rather than rules. If your how-to is 400 words and complete, publish it. If your opinion piece is 2,000 words and every paragraph earns its place, publish that too.
How do you know when a post is too long?
A post is too long when parts of it could be removed without the reader missing them.
Read your draft as a stranger would and look for these:
- An opening that takes three paragraphs to get to the point. Start with the point.
- Background the reader already knows ("Blogging has become very popular...").
- The same idea said twice in different words, often at the end of a section.
- A section that answers a different question from the one in your title. That's often a second post.
- A long conclusion that repeats the post. One or two sentences are enough.
Cutting is the fastest way to improve most drafts. It's common to remove a fifth of a first draft and end up with a better post.
How do you know when a post is too short?
A post is too short when a reader finishes it and still needs to search for something you could have explained.
Signs to look for:
- You say what to do but not how. "Set up an RSS feed" is a step; telling people where the setting lives is the help.
- You skip the obvious next question. If you recommend a platform, readers will ask what it costs and how hard it is to leave.
- There's no example. One concrete case is often worth a page of explanation.
- You assume knowledge your readers may not have.
Adding these usually makes a post longer, and that's fine. Length that answers questions is the good kind.
Does word count affect search traffic?
Only indirectly: a post that answers a question completely tends to do better, and complete answers to bigger questions are naturally longer.
A short post can rank well for a narrow question, such as how to change one setting. Broad topics need more space because there are more sub-questions to cover. What hurts is stretching a narrow answer into a long post. Readers scroll past the filler, and the part they wanted is harder to find.
Our guide to basic SEO for a personal blog covers titles, headings and links, which matter more than length.
How should you plan the length before writing?
List the questions a reader would have, then write until each one is answered once.
- Write the title as a question or a promise.
- Under it, jot the three to six questions a reader would ask next.
- Turn each question into a section heading.
- Write each section until the question is answered, then move on.
- Cut anything that doesn't serve one of those questions.
This gives you a natural length and a clear structure in one go. If you're planning several posts at once, the first 10 posts planner suggests a mix of short and long ideas so you're not writing a 2,000-word guide every week. For a first post specifically, see how to write your first blog post.
What about reading time?
Most adults read prose at roughly 200 to 250 words a minute, so a 1,000-word post takes about four or five minutes.
Some blog themes show reading time at the top of each post. It sets expectations, and people seem more willing to start a post when they know it's five minutes rather than an unknown length. Don't let it push you to trim a post that needs its length. A clear structure with headings matters more, because readers who skim can still find the part they need.
Questions
- Is a 500-word blog post too short?
- Not if it answers the question. A short post about one specific fix, a book you finished or a quick opinion can be complete at 500 words. It's too short only if readers finish it with the question they came with still unanswered.
- Do longer posts rank better on Google?
- Not because of length. Longer posts often cover a topic more completely, which can help, but Google states that it doesn't prefer any word count. A padded 3,000-word post can do worse than a focused 900-word one.
- How long should a newsletter issue be?
- Shorter than a blog post, as a rule. Many personal newsletters work well at 300 to 800 words because people read them in an inbox, often on a phone. Link to a longer blog post when a topic needs more room.
- How many words can I write in an hour?
- It varies a lot. Many people manage a rough draft of 500 to 1,000 words in an hour once they know what they want to say, but editing usually takes as long again.