SEOLivly
Menu
Home Tools Blog Services Contact Run the free scan

Word count is not a ranking factor, but it matters

By Derek Murphy  · 

Word count is not a ranking factor. Google has said so, and the evidence on real sites supports it: short pages beat long pages when the short page answers the query. But word count still matters, for three reasons that have nothing to do with a magic number.

First, it is a proxy for coverage. A page cannot answer a complex query in 200 words unless the answer is genuinely simple. Second, it affects how the page looks in the SERP and how long it takes to read. Third, it is a production decision: how much time a page gets before it ships.

The three jobs of a word count

  • Coverage. Does the page contain the sections a searcher expects: the answer, the steps, the exceptions, the cost, the alternatives?
  • Fit. Does the length match the intent? A recipe-style answer wants 400 words. A comparison wants 1,500. A definition wants 150.
  • Production. A brief with a word count is a way to stop a writer padding and a way to stop them leaving out the difficult section.

None of those is "longer ranks better". A 3,000-word page with 1,000 words of template is worse than a 900-word page with a real answer, because the template dilutes the signal and bores the reader.

What the top results are actually doing

When people say "the top results are 2,000 words", they are observing a correlation. Complex queries attract long pages because the answer is long, and long pages rank because they answer. The length is a by-product of the intent, not the cause of the ranking.

Look at what the top results contain rather than how many words they use. Do they have a table? A step list? A video? A calculator? That is the format the searcher wants, and format beats length every time.

How to use a word count without padding

  1. Set a range, not a target. "800 to 1,100 words" is a range that allows a real answer. "Exactly 1,500" invites filler.
  2. Write the answer first. The first 60 words should satisfy the query. Then add the sections that make the answer useful.
  3. Count sections, not words. A page with five useful sections at 200 words each is a better 1,000 than a page with ten thin sections.
  4. Cut before you add. When a draft is over, remove the paragraph that repeats the intro and the conclusion that repeats the body. The word count usually lands where it should.

The word and character counter gives you words, characters, sentences, paragraphs and reading time as you type. The useful part is the table of real platform limits: X at 280 characters, meta descriptions around 155, titles around 60, KDP blurbs around 4,000. Those are hard limits, not ranking targets.

The pages where length matters most

Roundups and comparisons need to be long enough to justify the claim in the title. A "best tools" page with three sentences per tool is a page that has not done the work. A tutorial needs to be long enough to get someone to the end of the task, and no longer.

Product and service pages need to be long enough to answer objections: price, scope, timeline, what happens next. If a buyer has to email to ask what the price is, the page is missing words, not ranks.

What to check instead of length

Read the page out loud. Does it answer the title? Does it have the example, the table or the step list a searcher expects? Does it link to the next thing the reader needs? Those questions predict performance better than a word count.

How to brief a word count

When someone else writes the page, the brief should give a range and the sections, not a target and a vibe.

For a fix page: "900 to 1,200 words. They need the answer in the first 60 words, a step list, one worked example, the two mistakes to avoid, and a link to the tool." That brief tells the writer what the words are for.

For a comparison page: "1,200 to 1,800 words. A table with every option, a verdict paragraph per option, a section on when to choose none of them, and a clearly labelled disclosure if there are affiliate links."

For a definition page: "300 to 500 words. Define it, give one example, say what it is not, link to the next page." A brief that asks for 1,500 words here produces padding, and the reader leaves.

The range is a budget, not a target. If the writer finishes at the bottom of the range and every section does its job, the page is done. If they hit the top and the sections are thin, the word count lied. Read the sections, not the number.

A final sanity check: compare the finished page with the top three results for the query. If they answer in 600 words and yours takes 2,000 to reach the same point, the word count is hiding the problem. Cut until the answer arrives sooner.

The only word count that matters is the one that gets the answer into the first screen. Check that, then stop counting.

If you want the objective checks around a page, run the website auditor for title, description, headings and links, and the keyword density checker to see whether the page is actually about its subject. The tools hub has both. The number you should care about is whether the page does its job, and that number is usually one.

Check your own page

The free website auditor runs forty checks on one URL and lists the worst problems first. No signup. If you would rather hand the list to somebody, the fix service has the prices on the page.

Run the free scan

Keep reading