How long should a blog post be for SEO? Forget 2,000 words

Somewhere along the way, 'long-form content' hardened into a rule: 2,000 words or don't bother. Businesses padded posts to hit it, writers billed to it, and a generation of bloated articles taught readers to skim. The rule was never real. Google has said so directly, the studies that seemed to support it say otherwise on close reading, and the industry's own behavior has quietly reversed. Here's the actual evidence, then a better way to size a post.

Google's position could not be plainer

Google's own guidance on creating helpful content includes, in its list of self-assessment questions, 'Are you writing to a particular word count because you've heard or read that Google has a preferred word count?' — and answers itself in parentheses: '(No, we don't.)' Google's John Mueller put it even more directly: 'the number of words on a page is not a quality factor, not a ranking factor', adding that 'just blindly adding more and more text to a page doesn't make it better.' And Danny Sullivan, Google's public Search Liaison, when asked on X for the best word count for search: it's 'not a thing! It doesn't exist. Write as long or short as needed for people who read your content.' This is one of the few SEO questions where the primary source has answered, repeatedly, on the record.

So why does everyone believe 2,000 words?

Because the correlation studies were real and the interpretation was wrong. Backlinko's analysis of 11.8 million search results found first-page content averaging around 1,400 words — and, in the authors' own words, no direct relationship between word count and rankings. Long pages rank more often because comprehensive pages tend to be long, and comprehensiveness — covering what searchers actually want, attracting links — is what ranks. Length is the shadow, not the cause. Writing 2,000 words to rank is copying the shadow: you can pad any post to any length without adding a gram of the coverage that did the work.

Long content ranks because complete answers are sometimes long. Padding copies the length and skips the completeness — the one part Google was rewarding.

The industry has already stopped

Orbit Media's long-running annual survey of bloggers (about 800 respondents) tracked average post length rising for a decade — roughly 800 words in 2014 to a peak around 1,430 in 2023 — and then falling for two consecutive years since, to about 1,330. Only 9% of bloggers still regularly publish 2,000+ word posts. Notably, those who do report better results than average — which sounds like a contradiction until you see it's the same finding as above: the minority still writing genuinely long pieces are the ones whose topics earn it. The era of length as strategy is ending; length as consequence is what's left.

Size the post to the query, not the counter

The practical rule: a post should be exactly long enough to fully answer its query for the person asking it. Since queries carry their intent in the words, they carry their size too:

• Specific factual questions — 'how much does a water heater cost in [city]' — deserve 500–800 words: the answer up top, the factors that move it, and done. Padding this to 2,000 words actively hurts; the answer your reader came for drowns.
• Comparisons and decisions — 'X vs Y', 'best X for Y' — genuinely need the middle range, often 1,000–1,800 words, because the job is covering criteria, differences, and situations. Completeness is the product.
• True pillar topics — 'the complete guide to X' — earn real length, 2,500+ words, but only a handful of topics per site are actually this. Most 'ultimate guides' are medium posts in a long costume.
• The universal test: read what currently ranks for your query and note what it covers, not how long it is. Match the coverage; let the count land where it lands.

Where the myth still bites

Two modern places. First, AI drafting made padding free — 2,000 hollow words now costs one prompt, which is how the content that gets demoted gets made; inflation is a spam signal now, not a strategy. Second, answer engines punished it retroactively: AI search extracts self-contained passages, and a direct 600-word answer is more quotable than the same answer buried in a wandering 2,400-word 'guide'. The tight post didn't just get easier to read — it got easier to cite.

If you've been writing to a word count, the correction is liberating: your specific posts get shorter and better, your genuinely big topics get the room they always needed, and the padding hours go into what actually moves rankings — publishing the next real answer instead of inflating the last one. Write until the question is answered. Then stop.