Page word count

What this check does

Extracts the visible text content from the page body (ignoring nav, footer, scripts, styles, and image alts) and counts the words. Reports a single number and flags pages under roughly 300 words as thin.

Why it matters

Word count isn’t a ranking factor on its own — Google has said this directly — but it correlates strongly with topical depth, which is a factor. Pages under 300 words rarely cover their topic comprehensively enough to rank for competitive queries; Ahrefs and Backlinko’s regular crawl studies consistently show top-ranking pages cluster in the 1,500–2,500 word range for informational queries.

The helpful-content system was rolled out specifically to demote shallow pages — those written for ranking rather than for readers. Word count is one of the simpler proxies for that pattern.

How to fix it

Aim for at least 300 words of substantive copy on any page you expect to rank. Longer for informational queries; shorter is fine for navigational pages, product detail pages with rich structured data, or pages where the answer is genuinely short.

Add depth, not filler.

The wrong fix is to pad with paraphrased fluff. The right fix is to answer the next three questions a reader would ask:

- What is this thing?           ← what most thin pages cover
- When should I use it?         ← add this
- How does it compare to X?     ← add this
- Concrete example or recipe.   ← add this
- Common mistakes / FAQ.        ← add this

That structure naturally produces 800–1,500 words of useful content without padding.

Use sub-headings.

A 1,500-word page with three H2s reads like a wall. The same content with seven H2s reads like a structured guide. See the heading hierarchy check.

Mix in concrete material.

Code blocks, tables, screenshots, real numbers from your own data, and step-by-step recipes raise both word count and quality at once. Padding with synonyms raises only the first.

Don’t pad navigational pages.

Your /contact, /login, and category index pages don’t need 1,000-word essays. Block the rule for those templates or accept the soft warning — those pages don’t compete on informational queries anyway.

Pair with related checks:

• Content depth — covers topical breadth vs. raw length.
• Heading hierarchy — structures long content so it stays scannable.
• Internal linking strategy — connects thin pages to their cluster.

Frequently asked questions

Isn’t longer content always better?

No. Padding hurts. Google’s helpful-content guidance is specific: “Are you writing to a particular word count because you’ve heard or read that Google has a preferred word count?” is listed as a red flag. Length should follow the topic, not the other way around.

What about product pages with mostly structured data?

E-commerce product pages with thorough specs, reviews, and Q&A often rank fine at 200 words of prose, because the structured data carries the topical signal. The check still warns; that’s a judgment call to override on that template.

How does this differ from thin_prose and paragraph_length?

Word count is the gross total. Thin prose checks whether what’s there is substantive or boilerplate. Paragraph length measures structure rather than volume. All three can pass or fail independently.