Skip to content 
There's no single ideal blog length, but UK data points to roughly 1,200–1,600 words for most small-business topics, stretching to 1,500–2,300 words for competitive informational guides and shrinking to 600–1,000 words for narrow questions. The right length is the amount of content needed to satisfy the searcher, not a number chosen to keep Google's imaginary word-count bouncer happy.
That challenges the most popular advice about how long should a blog post be. A fixed target sounds wonderfully tidy, especially when you're a plumber, solicitor or electrician with a blank document open and a cup of tea going cold beside it. But a 1,500-word guide about boiler servicing and a 1,500-word announcement about a legal change don't have the same job.
I reverse-engineer search results for service businesses regularly, and the pattern is clear. Intent, result type and coverage matter more than length alone. This guide gives you a practical way to choose the scope before you write, avoid grey-hat padding and build posts that help both readers and search engines.
Table of Contents
- Why There Is No Magic Word Count
- What the Data Says About Post Length
- Matching Length to Your Goal and Search Intent
- Short Posts Versus Long Posts and When to Use Each
- Three Blog Post Templates You Can Use Today
- Why Depth Beats Padding Every Time
- Your Next Steps and a Pre-Publish Checklist
Why There Is No Magic Word Count
A word-count target can make a service-business article worse. The useful question is not “How long should this post be?” but “What must this page help the reader decide or do?” A plumber's guide to boiler servicing and a solicitor's short legal update may both rank as blog content, yet they need different levels of explanation.
For many UK small-business subjects, 1,200–1,600 words is a sensible working range. A competitive informational guide may need 1,500–2,300 words, while a narrow question can be answered properly in 600–1,000 words, according to UK small-business blog length guidance. Use those ranges to plan scope, not to manufacture paragraphs.
The blank-page problem
A local roofer searching “how often should roof tiles be replaced?” might worry that a short answer looks weak to Google. A solicitor preparing a legal update can make the same mistake. Both are choosing a word count before identifying the reader's task.
The roofer may need to cover warning signs, inspection steps, material differences, weather exposure and when to request an assessment. The solicitor may only need to explain what changed, who it affects and what the reader should do next. A long history of roofing or legislation would add bulk without improving either result.
Reader behaviour also pulls in different directions. 75% of readers prefer articles under 1,000 words, while the same source gives an optimal blog length of about a 7-minute read, roughly 1,750 words. The figures support a practical trade-off rather than a universal target. A reader checking one symptom wants a clear answer. Someone comparing roof repairs, legal options or a local service needs enough evidence to trust the recommendation. The UK blogging statistics summary sets out that context.
Practical rule: List the questions your customer needs answered first. Count the words afterwards.
Search intent and the result type should set the brief. Informational queries often need explanation and examples. Local searches need service-area relevance, qualifications and a clear next step. Transactional searches usually benefit from concise decision support rather than a padded essay.
Stop when the page has answered the query, handled reasonable follow-up questions and made the next action clear. Chasing a larger number after that is grey-hat padding, even if the prose wears a respectable SEO hat.
What the Data Says About Post Length
UK publishing data points to a clear shift away from the very short posts once treated as sufficient. A widely cited 2025 content-marketing round-up reports an average blog post length of 1,427 words, up 77% compared with ten years earlier. Only 3% of blogs exceed 2,000 words, and most published posts fall between 500 and 1,500 words. The UK content-marketing statistics round-up provides the underlying figures.
An average is a description, not an instruction. A post of exactly 1,427 words will not automatically outrank a shorter answer that resolves the query cleanly, or a longer guide that provides the evidence a customer needs. For a local roofer, forcing every article to the same length is less an SEO strategy than spreadsheet theatre.
Page-one figures need careful handling
A UK-focused analysis of several SEO studies reports that page-one posts average about 1,447 words, while a practical target for many SEO-led articles is 1,500–2,500 words. It also summarises SEMrush figures placing top-performing posts at around 1,152 words, compared with 668 words for low-performing posts. These figures support depth and completeness, but they do not create a ranking rule. The UK SEO content-length analysis makes that distinction clear.
The historical change still matters. Advice that once treated 300–500 words as adequate has shifted towards satisfying intent, answering related questions and showing topical understanding. That does not justify padding every page. A post should earn its length by helping the reader reach a decision.
For a local service business, the numbers provide a starting point for competitor research, not a copying brief. A guide on preparing a house for an electrical inspection may need several connected explanations. A post answering whether an inspection is needed before selling can be much tighter.
What the numbers leave out
Averages hide the shape of the search results. They do not show whether ranking pages are service pages, category pages, quick answers, comparison articles or detailed guides. They also miss local entities, customer objections and practical steps that may separate a useful page from a padded one.
Use the figures to avoid wafer-thin content by default. Then inspect the result type and produce the shortest answer that fully resolves the searcher's question.
Matching Length to Your Goal and Search Intent
Start with the searcher's job. Length follows intent, never the other way round. Classify the query as informational, local, commercial or transactional, then decide what evidence and explanation someone needs before taking action.
Informational searches need room to teach
An informational searcher wants understanding, not a sales slogan. Someone asking “how often should a boiler be serviced?” may need the recommended process, warning signs, safety context, preparation advice and a plain-English explanation of what a service includes. A plumber could reasonably develop that into a 1,200–1,600-word local authority post, provided the answer appears near the top rather than after a ceremonial march through filler.
Useful sections might cover:
- What servicing involves: Explain the inspection and testing process in plain English.
- Signs of trouble: Help readers separate routine servicing from an urgent repair.
- Local relevance: Mention property types, weather conditions or housing stock only where they change the advice.
- Next action: Give readers a sensible way to book an assessment or ask a question.
A solicitor covering a narrow law update has a different job. 600–1,000 words may be enough for a focused update. State what changed, who may be affected, what remains uncertain and what readers should check. Someone trying to understand a rule that changed this morning does not need a grand tour of legal history.
Local and commercial searches require proof
A local searcher may want to know whether an electrician serves their area, handles a particular job and appears trustworthy. A blog post supporting that decision might sit around 1,200–1,600 words, but each section should earn its place through process detail, qualifications, service boundaries, common questions and a clear enquiry route.
Comparison content sits between education and conversion. A post such as “repair or replace a faulty consumer unit?” needs decision criteria, likely scenarios, safety considerations and a recommendation framework. It should not become a disguised sales pitch. White-hat SEO answers the question directly. Grey-hat content buries the answer beneath repeated location names and padded calls to action. Black-hat tactics may create a short-term impression of relevance, but they do not make unsafe electrical advice useful.
The same keyword can need a short answer, a step-by-step guide or proof of local expertise. The search result tells you which one.
For a broader property example, this 2026 real estate SEO guide reinforces the need to match content planning to topic, audience and competitive context rather than applying one generic blog length.
Use this decision sequence:
- Identify what the searcher wants to know or do.
- Check whether results are mainly guides, service pages, category pages or quick answers.
- List the follow-up questions a competent customer would ask.
- Write until those questions are answered clearly.
- Remove anything that does not help the reader understand or decide.
Ranges such as 1,200–2,500 words or a 1,400–1,500-word sweet spot are starting points, not instructions. A local service or conversion-supporting post may need less copy than an informational guide. UK guidance on blog posts, pillar pages and landing pages correctly puts the emphasis on intent. Write enough to resolve the query, then stop.
Short Posts Versus Long Posts and When to Use Each
Short posts win when the reader wants a fast, specific answer. Long posts win when the reader needs a complete explanation before contacting a business. Neither format wins because it has more words. It wins because it removes the right uncertainty.
A short post under 1,000 words suits a focused law update, a seasonal reminder about frozen pipes or a direct answer about an electrical certificate. It respects a busy reader and can perform well when the topic has a narrow scope. A long post over 1,000 words suits a detailed guide, a complex comparison or an educational article designed to build authority around a service.
The important counterweight is that local and transactional pages often need much less copy than informational blogs. UK eCommerce category research found top-ranked pages averaged only 310 words of unique text, with 66% under 400 words. The category-page content research shows why page type and intent matter more than a blanket long-form rule.
A quick decision table
| Content Goal | Recommended Length | Best-Fit Example |
|---|---|---|
| Narrow question | 600–1,000 words | A solicitor explaining a specific law update |
| Local authority article | 1,200–1,600 words | A plumber explaining boiler servicing for homeowners |
| Competitive informational guide | 1,500–2,300 words | An electrician's guide to preparing for an inspection |
| Transactional support | Keep it concise and complete | A service page explaining an emergency call-out |
| Comparison article | Usually substantial, based on decision complexity | Repair or replace a consumer unit |
The table gives you a starting point, not permission to hit a number and go home. If a 700-word post answers the question fully, extending it to 1,500 words may make it worse. If a 1,500-word article leaves out safety considerations, cost factors or next steps, it may need more work rather than more padding.
My plain recommendation is this: use short posts for narrow intent and long posts for complex intent. For most UK small-business blog topics, start around 1,200–1,600 words, then move down or up according to the questions, result type and competitive depth.
Three Blog Post Templates You Can Use Today
A template stops two problems before they reach publication: a thin answer that leaves a reader stranded, and a long article repeating itself in three different jumpers. Match the structure to the searcher's task, then add your own trade knowledge. Word count follows the job, not the other way round.
The quick-answer template
Use this for a narrow query, a law update or a time-sensitive local question. Aim for 600–1,000 words, a practical range supported by earlier UK small-business guidance.
Suggested structure:
- Direct answer, about 60–100 words: Give the conclusion first.
- Essential explanation, about 150–250 words: Define the issue and stay on point.
- Practical implications, about 200–300 words: Explain what a homeowner or business owner should check.
- Common questions, about 150–250 words: Resolve obvious follow-ups.
- Call to action, about 50–100 words: Invite the reader to request relevant help.
A solicitor explaining a legal update should put the effective date, affected groups and recommended next step near the top. A plumber answering whether a boiler needs servicing can use the same approach, covering the warning signs and the sensible next action without writing a small book. Lawyers have enough paperwork already.
The local authority template
For a local service topic, 1,200–1,600 words gives room to answer the question and show useful local knowledge. Mention the relevant area where it helps, rather than scattering place names like confetti.
Use this structure:
- The answer and why it matters, about 100–150 words.
- The process explained, about 300–400 words.
- Local considerations, about 200–300 words.
- Warning signs or decision points, about 200–300 words.
- Frequently asked questions, about 200–300 words.
- Trust signals and next action, about 100–150 words.
An electrician could apply it to “how to prepare for an electrical inspection”. Cover what the customer can safely do beforehand, what the electrician checks and when a repair may be needed. Put the enquiry prompt after the main answer and at the end, keeping both relevant. A guidance-seeking reader should not be ambushed by a sales brochure.
The comprehensive guide template
Competitive informational subjects usually need 1,500–2,300 words, the range identified in UK analysis of commercially competitive informational posts. The discussion of longer blog posts and topical completeness is useful because it connects length with coverage of entities and subtopics, rather than treating word count as a ranking trophy.
Build the guide around:
- A concise answer, about 100–150 words.
- Core concepts, about 300–400 words.
- Step-by-step method, about 400–600 words.
- Scenarios and exceptions, about 300–400 words.
- Related questions, about 250–350 words.
- Decision and call to action, about 100–150 words.
Before publishing, read the piece aloud. If you run out of breath, the reader probably will too.
Why Depth Beats Padding Every Time
Word count is a depth proxy, not a ranking target. Two posts can contain the same number of words, yet only one may answer the searcher's question, cover related concerns and explain the relevant entities. The other circles the subject like a lost delivery driver.
Commercially competitive informational posts often need substantial coverage, but the useful test is whether each section helps the reader understand an issue or make a decision. A post about preparing for an electrical inspection, for example, should explain safe preparation, the checks an electrician carries out, warning signs and when repairs may be needed. Adding another paragraph about why inspections matter achieves very little.
What padding looks like
Grey-hat padding often arrives disguised as optimisation:
- Repeated introductions: The same promise appears in several forms.
- Keyword reshuffling: “Boiler servicing in Leeds” replaces natural wording throughout the page.
- Obvious filler: A sentence announces what the next section will discuss instead of discussing it.
- Thin FAQs: Headings multiply, while the answers repeat earlier paragraphs.
A padded sentence might read: “Boiler servicing is an important service for your boiler because servicing your boiler helps ensure that your boiler remains serviced and ready to provide boiler service when needed.” It has the nutritional value of a damp biscuit.
A useful rewrite is: “Annual servicing helps identify faults early and confirms that the boiler is operating safely.” The sentence does the job. The repetition belongs in the bin.
White-hat standard: Add a section only when it improves understanding, supports a decision or answers a genuine follow-up question.
Black-hat tactics are easier to recognise. Spun text, automatically generated bulk pages without knowledgeable review, and copied material presented as local expertise create volume without trust. A service business can end up publishing content that sounds confident about checks nobody has made.
Software can help with outlines or research, but it cannot replace trade knowledge and editorial judgement. Businesses considering practical uses can read AI insights for business, focusing on tools that support thinking rather than manufacture empty pages.
DigiVisi Ltd's SEO copywriting service reflects the same principle: match coverage to intent instead of chasing an arbitrary length. Length helps only when it buys topical depth. When extra words add no explanation, evidence or useful next step, they are padding, however polished the formatting looks.
Your Next Steps and a Pre-Publish Checklist
Choose length from the query, not a superstition about word counts. For many UK small-business topics, 1,200–1,600 words is a sensible starting range. A competitive informational guide may need 1,500–2,300 words, while a narrow question can work in 600–1,000 words if it resolves the issue properly. Page-one posts average about 1,447 words, but that is a benchmark, not a publishing quota, as noted earlier.
Before publishing, check:
- Intent: Does the post answer the searcher's actual question?
- Coverage: Have you handled the obvious follow-up questions?
- Local proof: Where relevant, does it show genuine knowledge of the area, property type or customer situation?
- Structure: Can readers scan the headings and find the answer quickly?
- Conversion: Is the next action clear without making the article read like a billboard?
- Editing: Have you removed repetition, waffle and location stuffing?
For example, a boiler engineer is better served by one clear guide for homeowners or landlords than a calendar of thin posts built around a quota. Match the article to the result type, then publish only what earns its place. Grey-hat padding may increase the count, but it does not improve trust or enquiries.
Software can support research and outlines. It cannot replace trade knowledge or editorial judgement. DigiVisi Ltd's SEO copywriting service follows the same principle, matching coverage to intent instead of chasing arbitrary length.
DigiVisi Ltd helps UK service businesses with competitor analysis, keyword research, SEO copywriting and content optimisation. Visit DigiVisi Ltd to discuss a practical content plan for turning useful visibility into calls and enquiries.
