Google has no preferred word count. Stop writing to one.

A post should be as long as the question it answers, and no longer. That sounds too obvious to argue, yet briefs still arrive asking for 2,000 words because someone read that long posts rank. Google has said plainly that it has no preferred length. Word count is a symptom of a post that did its job, and treating it as a target produces the opposite.

Google answered this in its own guidance

Google's page on creating helpful, reliable, people-first content contains a list of warning signs, questions that suggest you are writing for search engines rather than for people. One of them asks whether you are writing to a particular word count because you have heard or read that Google has a preferred one. The answer is printed right after the question, in brackets: no, it doesn't.

That is unusually direct for a company that rarely confirms or denies anything about ranking. It sits in the same list as writing about trending subjects your audience never asked about, and leaving readers feeling they need to search again. The common thread is effort spent on how a page looks to a ranking system rather than on what it gives the person reading it. We made the broader case in our post on how Google treats AI content: what gets demoted is content nobody needed, whoever wrote it. A target length is one of the quieter ways of producing exactly that.

Length is what the question costs to answer

The belief that long posts win is not invented from nothing. Long pages often do rank well. But length usually travels with the things that actually help, such as covering the follow-up questions a reader was about to search for, or being thorough enough to earn links from other sites. Those causes produce length as a by-product. Copying the by-product does not bring the causes with it.

Some questions are expensive to answer. Explaining what a second language really costs to maintain takes a thousand words because there are several separate costs and each needs an example. Other questions are cheap. How to find your post ids in an admin panel is a paragraph and a screenshot. Stretch the cheap answer to a thousand words and you have not made it more helpful. You have hidden the paragraph inside nine hundred words the reader has to wade through to find it.

Padding is the machine's cheapest failure

This matters more now than it did when every word cost a writer an hour. A language model asked for 1,500 words will deliver 1,500 words whether the subject holds them or not. It will restate the introduction as a conclusion, add a section on "why this matters", and define terms the reader already knew. None of it is false, which is what makes it hard to catch. It is simply empty, and the reader pays for it in scrolling.

The reader who pays most is the one who arrives from an AI summary. As we argued in arriving from an AI summary, that reader already has the gist and clicked for the particulars. Every padded paragraph between them and the particulars is a reason to leave. So when an engine writes to a length, it tends to fail in the one direction that is hardest to spot in review and most costly on the page.

Why our own blog still has a word range

Here we have to be honest about ourselves. The script that publishes this blog refuses any English post under 700 words or over 1,050, and any Finnish post outside 430 to 800. That looks like exactly what we have just argued against.

The difference is what the range is for. It is a format, in the way a newspaper column has a length. It exists so that a reader who comes to this blog knows roughly what they are getting: one argument, made properly, in a sitting. It is also a failure detector. A post that comes out at 300 words has usually been truncated, and one at 2,500 has usually lost the thread. The Finnish bounds are lower because Finnish carries the same content in fewer, longer words, and a single range would force the Finnish to pad.

What the range must never do is decide how a subject is treated. When a subject cannot fill the format honestly, the correct response is to put it somewhere else, on a documentation page or a product page, as we argued in not every subject is a post. When a subject needs more than the format allows, it becomes two posts, each with its own claim. The range chooses the format. It does not stretch the argument to fit it.

Ask what the reader leaves with

If you brief an engine or a writer, drop the word count and state the question instead, along with who is asking it and what they should be able to do afterwards. Length will follow from that, and it will vary, which is the correct outcome. When you review a draft, ask whether any paragraph could be deleted without the reader losing something. If it could, delete it, even if that takes the post below the number you had in mind. The number was never what Google was measuring, and it was never what your reader came for.