Ask five content experts how long a blog post should be and you will get six answers, most of them confident, few of them consistent. The question itself is the problem. A blog post on a small business website is not one thing — an answer post that resolves a pricing question has almost nothing in common with a case study that walks a real project from brief to result, and treating them to the same word count wrecks one or the other. This article gives you the useful version of the question: how long should each kind of post be, for the job it actually has to do on your site? The ranges below are working ranges, not laws — they come from what posts need in order to satisfy a searching reader and earn a place in search results, and they assume the writing stays concrete the whole way through. They pair naturally with a sustainable choosing a blog cadence a small business can actually keep, and they apply just as much when you run an older draft through the refresh check before publishing an old draft before republishing it. Where a post needs more room — especially service case study posts — we will say so explicitly, because padding those is just as costly as starving them.
One principle governs every range that follows: length is a cost the reader pays, so the post must repay it. A post earns extra words only by doing extra work.
Why There Is No Magic Number
The internet’s favorite answer — “long posts rank better” — confuses correlation with instruction. Long posts often rank because they were written to cover a subject completely, by people with real expertise and something specific to say, and completeness is what both readers and search engines reward. Chasing the length without the completeness produces the worst of both worlds: a thin idea wearing a thick coat, padded with throat-clearing and restated conclusions. Search engines have spent years learning to recognize when a post satisfies the reader’s question quickly, and readers vote with their backs — a post that answers in 500 words and stops has a better chance of being read, shared, and linked than an 1,800-word post that answers the same question at word 300 and then wanders. Long-running content analyses, like those published on the Moz blog, keep arriving at the same correlation: coverage and usefulness, not raw length, travel together with rankings. For a small business site, there is a second constraint the big publishers do not face: your posts compete on usefulness, not on publishing volume. Every post is a small piece of sales collateral. A reader who finds your 450-word answer post genuinely helpful trusts you more than one who bounces off your 2,000-word epic at the second scroll. The right framing is not “how long should posts be” but “how long does this post’s job take” — which is a question with a real answer.
Length By Job: Working Ranges For Common Post Types
The table below maps the five post types a small business blog actually publishes to the length each job typically requires. The ranges assume the writing is concrete throughout — examples, numbers, specific steps — because vague writing at any length satisfies nobody.
Notice the design logic hiding in the ranges. Answer posts are short because their job is to end the search; every extra paragraph past the answer is reader-tax with no return. How-to guides earn their length from steps and decision points, not from explanation of why the task matters. The comparison post needs enough room to be fair to both sides — shorter reads as a hatchet job. The case study is the one type where longer consistently wins, because its entire value is the specific arc of a real project. And the opinion post breaks the pattern on purpose: its job is voice, and voice dies under padding. If you find yourself stretching any of these ranges, the post usually has the wrong job — it is pretending to be a guide when it is really an answer post, or a case study wearing a guide’s clothes. Retitle it instead of padding it.
The Signals That A Post Is The Wrong Length
Length problems announce themselves in recognizable ways, and they run in both directions. A post that is too long shows the same three symptoms almost every time: a conclusion that restates the introduction almost verbatim, a middle section that explains why the topic matters at a point where the reader already agrees, and hedged summary paragraphs that say nothing the reader can use. Cut all three and the post usually finds its natural length on its own. A post that is too short shows different symptoms: questions a reader would obviously ask next that the post never addresses, steps that assume knowledge the reader may not have, and a call to action that arrives before the post has earned it. The fix is not uniformly “add words” — it is “close the open loops.” Sometimes that takes 200 words; sometimes it reveals the post should have been two posts. One diagnostic worth building into your review habit: read the post aloud and mark every paragraph where your attention drifts. The drift points are almost never in the first half. Posts are rarely too long throughout; they are too long after they have finished their job.
How Length Interacts With Your Publishing Schedule
Length and cadence trade against each other, and small business blogs go wrong by ignoring the trade. A site committed to one substantial post a month can afford 1,200-word pieces with real reporting in them. A site trying to post weekly on the same budget produces four thin posts a month, and thin posts compound badly — they train readers that the blog is skippable and train search engines that the site rarely satisfies. This is where choosing a blog cadence a small business can actually keep becomes the real decision: pick the length you can sustain at quality, then derive the cadence from it, not the reverse. For most small service businesses, that lands somewhere between a short answer post every week and a deep piece every two weeks. There is also a maintenance angle: older long posts deserve a periodic trim, because standards of tightness rise and a post that felt complete two years ago may now read as padded. Trimming a live post is one of the highest-value edits available — you keep the accumulated search equity while improving the reader’s odds of actually finishing, which is a signal worth chasing in its own right.
A Worked Example: One Topic, Three Honest Lengths
Watch the same topic take three defensible shapes. Take the question “should a bakery’s website have a blog?” — a real search a real owner makes. As an answer post, it needs about 450 words: a direct answer up top (usually yes, if you can sustain it, with one exception), the exception explained, and a link onward. As a how-to guide, it needs about 1,100 words: the answer plus a step-by-step of the first six posts a bakery could realistically write, with topics pulled from customer questions. As a case study, it needs 1,500 or more: the story of one bakery, the posts it published, the traffic and orders that resulted, and the owner quotes that make it believable. None of these is “the right length.” Each is right for its job, and a site that tried to make the answer post stretch to case-study length would lose readers the moment the padding started. When you sit down to plan a post, the most productive first question is not “what should I write about” but “which of these three jobs is this post doing” — the length then mostly decides itself, and the writing gets easier because it has a shape.
The table in this article is the planning tool: name the job before you write the outline, pick the range, and hold the post to it. Posts that know their job feel finished at their natural length — whatever that number turns out to be.