Fact check: word count is not a ranking factor
Does word count decide rankings? We checked the claim that Google ranks longer posts higher. Our verdict is false, and here is the evidence.
No. Google does not rank a post higher because it is long. Its own guide to helpful content says plainly that it has no preferred word count. Long posts often do rank well, but that is because they tend to answer more questions and earn more links, not because of the length itself.
The claim we checked #
The claim turns up in briefs, agency pitches and tool reports. It usually reads like a rule: write a long post or do not bother. Some content tools score a draft by its word count against the pages that rank. Writers then pad a clear answer to hit the target.
We checked the claim in the form people make it: "Google ranks longer posts higher." That is a claim about cause. It says length itself moves a page up. To be true, a page would have to gain from the extra words alone, with nothing else changed.
What Google says about word count #
Google publishes a guide to creating helpful, reliable, people-first content. It lists questions to ask of your own pages. One of them asks whether you write to a set word count because you heard Google prefers one. Right beside the question, Google answers that it does not.
The guide puts that question in a list of warning signs. They are the habits of content made for search engines first and people second. So Google does more than say length is neutral. It treats writing to a target length as a sign that the writer has lost sight of the reader.
The claim against the evidence #
| What people say | What the evidence shows |
|---|---|
| Google rewards long posts | Google's own guide says it has no preferred length |
| The top results are long, so length must help | The top results also cover more questions and earn more links |
| A longer post looks more expert | Expertise shows in detail, sources and a named author, not in bulk |
| Adding words to an old post lifts it | Padding pushes the answer down and makes it harder to find |
The third row matters most for small teams. Google's idea of E-E-A-T (experience, expertise, authority and trust) is about who wrote a page and how they know. A real name, a first-hand example and a linked source show it. Extra words do not.
Why long posts often rank anyway #
Sort the results for a broad query by length and long pages often sit near the top. The pattern is real. It just does not show cause. Three things tend to travel with length, and each of them can help a page on its own.
- Wider coverage. A broad search hides many smaller questions. A guide that answers each of them matches more of what searchers want. The length is a side effect of the coverage.
- More links. Thorough guides are the pages other sites cite, so they earn more backlinks. Links help a page be found and trusted. The words do not earn them; the usefulness does.
- More care. Long guides are often a team's flagship pages. They get updated, linked from other posts and promoted. A short page with the same care would get much of the same lift.
Take those three away and the word count alone has nothing left to give. A short page that answers a narrow question well will beat a long page that buries the same answer under a history lesson.
When two things rise together, ask what else is rising with them before you credit either one.
What this means for your brief #
Drop the target word count from your briefs. Put a list of questions in its place. The post is done when it answers each of them clearly, once.
Start from the goal behind the search. Someone who asks how long a meta description should be wants a number and a reason, then wants to leave. Our meta description guide answers in two lines and stays short on purpose. Someone who asks how to plan a year of content wants a method, and that post will run long because the method has many parts.
Our full guide to writing posts that rank walks through the whole process, from the question to the final edit.
How to judge the right length #
You can find the right length without counting a single word.
- Read the results page. If the pages that rank all answer in a few lines, a long post will not beat them.
- List the questions. Write down each question a reader will have, in the order they will have it.
- Answer each one once. No section should say again what another already said.
- Cut what does not serve. Our checklist for the second draft shows where padding hides.
- Read it on a phone. A buried answer is easy to spot on a small screen.
How this page is marked up #
This page carries structured data for a fact check, known as ClaimReview: a short block of code that names the claim, our rating and who rated it. Fact-check tools can read the verdict without guessing. Khalid writes it from the post's settings, so the page and the code always agree.
How we check claims
Every fact check follows our editorial policy. We write the claim the way people make it, then look for the source best placed to know: the search engine's own documents, a standard, or a test we can repeat. We rate the claim on a five-point scale, from one for false up to five for true, and we give the verdict in words as well. A second editor reviews the evidence before we publish. If new evidence changes the verdict, we update the page and add a dated note that says what changed.
Signing up by email is not open on this site.
About the author
Research editor at Larkspur Studio
Experience MSc in Statistics, runs the yearly Larkspur content benchmark
Priya turns questions about content into numbers you can trust. She designs the yearly Larkspur content benchmark, checks every statistic we publish against its source, and writes about measuring what content earns and how AI search chooses what to quote.
Reviewed by
