Skip to main content

Word Count

What it does

The Word Count tool counts words, sentences, paragraphs, characters (with and without spaces), the longest word, average sentence length, and reading time at a configurable words-per-minute rate. It accepts plain text or HTML — the HTML-stripping option pulls out the rendered text so the count reflects what readers see, not what the markup contains.

Common situations

You have just written a long-form article and want to know whether it crosses the threshold for “long-form” by SEO conventions (usually 1,500-2,000+ words). The tool gives you the count plus the reading time, which is the more meaningful number for content planning.

A blog post has been written by a freelancer to a 1,200-word brief and you want to verify the count without wading through the doc. Paste the content, get the count, decide whether to send back for expansion or accept.

You are auditing a content set to identify pages that are likely thin (under 300 words) — Google’s helpful-content updates have made thin content increasingly visible as a ranking penalty. Run important pages through the counter; pages well under 300 words are candidates for expansion or consolidation.

A piece of marketing copy has a strict word limit (a meta description, a tweet, a paid ad headline) and you need to know whether it fits. Paste, count, edit, repeat.

You are evaluating a competitor’s content depth — their long-form articles vs yours. Drop their content into the counter; the relative word count tells you whether the gap in performance is content depth or other factors.

What you need to know

Word count is one of the simpler signals in SEO, often misunderstood. The honest framing: word count is correlated with ranking but not causal. Pages that rank well tend to be longer because longer content covers more search intent, has more opportunity for internal linking, and demonstrates more topical depth. But adding words to a thin page rarely improves its rank — what improves rank is improving the content’s depth, breadth, and topical authority, which usually (but not always) results in more words.

The pragmatic targets:

  • Under 300 words — likely thin content territory. Pages this short usually need expansion to rank competitively unless the topic genuinely resolves in a few sentences (a definition, a single fact, a contact page).
  • 300-800 words — standard short-form. Appropriate for news posts, brief explanations, FAQ entries, glossary terms.
  • 800-1,500 words — standard long-form. The default for substantive blog posts and content marketing articles.
  • 1,500-3,000 words — pillar content. Long-form posts targeting competitive keywords. The depth that ranking requires for non-trivial topics.
  • 3,000+ words — comprehensive guides, definitive resources. Signal: this page covers everything someone could want to know about the topic.

What the counts include and exclude:

Words: split on whitespace. Hyphenated compounds (well-known) count as one word; numbers count as words.

Sentences: split on ., !, ? followed by whitespace or end of text. Imperfect — abbreviations like “Dr.” and “U.S.” can fool the splitter. The count is approximate but consistent.

Paragraphs: split on double newlines. HTML paragraphs after stripping use the rendered structure.

Characters: with and without spaces. Useful for length-constrained writing (tweets, meta descriptions).

Reading time: words divided by reading speed (default 220 wpm). 220 is the average for adult silent reading; comprehension reading is slower (180-200), skim reading is faster (300+). Adjust the wpm slider to match the audience.

The HTML-strip option uses DOM parsing to extract body.textContent — what users see, not what’s in the markup. This is the right number for “how much content does this page actually have for the reader” rather than counting markup tokens or invisible elements.

Frequently asked questions

Does word count affect SEO rankings?

Indirectly. Longer pages tend to cover more search intent and rank better, but the causation runs through content depth, not word count itself. Adding 1,000 words of fluff to a 500-word page makes it 1,500 words but worse, not better. Add words only when there is more useful content to add.

What’s a good word count for a blog post?

Depends on the topic and intent. Definitional content (glossary terms): 200-400 words. Standard articles: 800-1,500. Pillar guides: 2,000+. The honest answer: write the content the topic actually warrants, not to a target. Pages that rank do so because they cover the topic well, not because they hit a word count.

How does the tool count “well-known” — one word or two?

One word — hyphenated compounds count as one. Most word-count algorithms split on whitespace, which treats hyphens as part of the word. If you want hyphens treated as separators, add spaces manually.

What about plain numbers (e.g. “404”)?

Numbers are counted as words. “404 errors” is two words.

Does the reading time take comprehension into account?

The default 220 wpm is silent comprehension reading for an adult reader on familiar topic. Technical or unfamiliar content reads slower (150-180). Adjust the wpm to match.

Can I exclude HTML tags from the count?

Yes — the “Strip HTML” toggle pulls out the rendered text via DOM parsing. The counter reads only the visible text.

What’s the longest-word number useful for?

Long words (15+ characters) are usually compound terms, technical jargon, or accidental run-on words from copy-paste. The counter surfaces them so you can spot accidentally-merged words or decide whether a piece of jargon is too dense for the audience.

Why does my count differ from Microsoft Word’s count?

Word counters use slightly different rules. Word splits on whitespace and punctuation; some other tools split only on whitespace. The differences are small (a few percent) and not meaningful for SEO purposes.

Common problems

Problem: Word count differs from what the CMS reports.

CMSes have their own count logic — some include alt text, some count meta fields, some count differently depending on language. The tool’s count is the rendered body text. If you need to match the CMS’s count, paste the content the CMS reports rather than the rendered HTML.

Problem: Reading time looks too fast.

The default 220 wpm is silent comprehension reading. For technical content, drop to 180 or 150. The tool is giving you the maths; you set the wpm to match the audience.

Problem: Sentence count seems wrong.

Abbreviations confuse the splitter — “Dr.”, “Mr.”, “etc.” are read as sentence endings. The count is approximate by design; treating it as exact is overstating the precision the tool offers.

Problem: Paragraph count is 1 even though the content has multiple paragraphs.

Plain text needs double newlines between paragraphs to split correctly. HTML uses <p> tags. If neither is present (single block of prose with single newlines), the splitter sees one paragraph. Add line breaks or wrap in HTML.

Problem: Word count is 1,500 but the article still feels thin.

Word count and content depth are different things. A 1,500-word article that meanders, repeats, and hedges is thinner than a 700-word article that says something specific and useful. Use word count as one signal, not as the definition of quality.

Tips

  • Don’t pad pages to hit a target. Write to the topic; the count follows.
  • Reading time is more useful than raw word count for content planning. “5-minute read” sets reader expectations better than “1,200 words”.
  • For competitor analysis, run the same word counter on their content as on yours — different counters will give different numbers.
  • Track word count by intent type: glossary terms shouldn’t be 1,500 words; pillar pages shouldn’t be 400.
  • Use the longest-word indicator as a quick check for accidental copy-paste errors (run-on words from formatting issues).

Related tools in this suite

The Keyword Density Checker is the natural companion — the word count tells you length; the density checker tells you what the content is about. The AEO Content Scorer goes deeper into content shape, scoring extractability for AI search engines.

What this looks like at scale

For a single page, the counter is fine. For a content site, word count should be tracked as a content-set metric — distribution across short, standard, and long-form, identification of unexpectedly thin pages. The WP Beacon Plugin reports word count distributions across an entire site, surfacing pages that are surprisingly short or surprisingly long for their template.

Take it further

If a content set you have inherited has many thin pages, the right scope is consolidation (merging thin pages into pillar pages with redirects) and expansion (filling out genuinely under-developed pages). Talk through what’s there and the appropriate response.