Website Word Count — Paste Text or Raw HTML

A website word count tool solves a very specific, very common headache: you have a chunk of page content — sometimes clean text, sometimes raw HTML copied straight from "View Source" or a browser inspector — and you need the real, visible word count, not the count of every div, class name, and script tag mixed in with it. This tool handles both. Paste plain text and it counts instantly. Paste raw HTML, flip the "Strip HTML tags" toggle, and it strips out every tag, script, and style block first, then counts only the words a real visitor would actually read.

It also estimates two different kinds of time: reading time, for anyone judging how long a page takes to consume, and speaking time, for anyone turning that same content into a video script or voiceover — a need that a standard word counter rarely accounts for. Everything runs locally in your browser as you type or paste.

What This Website Word Count Tool Does

Paste your content into the box. If it's plain visible text, leave the toggle off and the tool counts it directly. If it's raw HTML — the kind you'd get from right-click "View Source," a browser's Inspect panel, or an exported page file — switch on "Strip HTML tags" and the tool removes all markup, script content, and style blocks before counting, leaving only the text a visitor would actually see and read on the page. Either way, you get a live word count, character counts both with and without spaces, a sentence count, a paragraph count, and estimated reading and speaking times, all updating as you type or paste.

How to Use It

1. Copy the content you want to measure. This can be your own draft, a live page's visible text, or its full HTML source.
2. Paste it into the box. Counts appear immediately for plain text.
3. If you pasted HTML source, check "Strip HTML tags" so script code, style rules, and markup don't inflate your word count.
4. Read the word count and reading time to judge how substantial the visible content really is.
5. Check the speaking time if you're repurposing the content into a video script, podcast segment, or voiceover — it's paced differently than reading time.

The Formula: How Each Metric Is Calculated

Word count comes from splitting the text on whitespace after trimming extra blank lines and, when the strip option is on, removing everything between angle brackets along with the contents of any <script> or <style> block, since those contain code rather than visible text. Character counts are reported both including and excluding whitespace, since different platforms and fields measure differently. Sentences are estimated by counting terminal punctuation — periods, question marks, and exclamation points — and paragraphs are estimated by counting blocks of text separated by line breaks. Reading time uses roughly 220 words per minute, a commonly cited average for adult silent reading; speaking time uses roughly 130 words per minute, in line with typical conversational and presentation pacing guidance from public-speaking resources such as Toastmasters International's public speaking guidance, which places comfortable spoken delivery meaningfully slower than silent reading speed.

Why Visible Text and Source Code Word Counts Diverge So Much

This is the gap that trips up almost everyone auditing a page for the first time, especially when sizing up a competitor. Open "View Source" on any reasonably built modern page and you'll see enormous amounts of text that a visitor never reads at all: navigation menu labels repeated in mobile and desktop markup, hidden accordion content, script variables, JSON-LD structured data, comment blocks, and CSS class names, all mixed directly into the raw character stream alongside the actual paragraph text. Running a naive word count on that raw source can easily double or triple the number a person would actually encounter scrolling the page. This tool's "Strip HTML tags" option exists specifically to remove that noise — script and style block contents are dropped entirely, tags are removed, and what's left is a much closer approximation of the words a reader genuinely sees.

This distinction matters for two very different jobs. If you're auditing your own site's content depth for SEO, you want the visible-text count, since that's what corresponds to the "How Users Read on the Web" research from usability groups like the Nielsen Norman Group, which studies how people actually scan and consume on-page text — not how much raw markup ships with the page. If you're sizing up a competitor's real content investment on a page, the same visible-text number tells you what they actually wrote for humans, versus what their page template happens to generate.

Reading Time vs. Speaking Time — Why Both Matter

A word count alone doesn't tell you how long content takes to consume, and "how long" means different things depending on the medium. Reading time, calculated here at roughly 220 words per minute, estimates how long a visitor spends silently reading a page — useful for judging whether a blog post or article is appropriately paced for its topic. Speaking time is a completely different calculation, estimated at roughly 130 words per minute, reflecting how much slower comfortable spoken delivery is compared to silent reading. This number matters most when the exact same block of text is being repurposed into something spoken aloud: a video script, a podcast segment, a voiceover for an explainer video, or a webinar talk track.

A script that reads as a "3-minute read" in text form can easily run 5 minutes once it's actually spoken at a natural, unrushed pace — a gap that catches people off guard when a script written to hit a target video length runs long once recorded. Checking both numbers before recording anything saves a re-write after the fact.

Common Mistakes to Avoid

• Counting raw HTML as if it were visible text. Without stripping tags first, script code and markup inflate the count far beyond what a reader actually sees.
• Forgetting hidden content. Accordion panels, tabs, and mobile-only menus often contain text that's technically on the page but not always visible to every visitor — decide deliberately whether to include it in your audit.
• Using reading time to estimate speaking time. The two paces are meaningfully different; a script written to a reading-time target usually runs long once actually spoken aloud.
• Comparing your visible-text count to a competitor's raw source count. Always compare like with like — strip both, or strip neither, or the comparison is meaningless.
• Ignoring paragraph and sentence structure. A high word count spread across very few, very long paragraphs often signals a readability problem the word count alone won't reveal.

Related Free Tools From Arb Digital

For a quick plain-text count without the HTML-stripping or speaking-time features, use our word counter. To benchmark a draft's length against real SEO ranking data by content type, try the SEO content length checker, and check readability with our readability checker. Once your content length is solid, tighten the on-page tags with the title tag length checker and meta description length checker. Browse everything at our free online tools hub.

How Word Count Actually Relates to Ranking

Word count is a symptom, not a cause. Google has said plainly that there is no minimum word count and that length is not a ranking factor — yet longer pages do correlate with better rankings in study after study, and both facts are true at once. The reason is coverage: a query like "how to file taxes" simply cannot be answered thoroughly in 300 words, so the pages that satisfy it tend to be long because they are thorough, not because length itself earns anything. Padding a thin page to 2,000 words of filler does nothing but waste the reader's time and dilute the terms that matter.

Use this counter as a coverage check, then judge the number against intent. A definition or a store's contact page is complete at 150 words and adding more would hurt it. A pillar guide competing with established sites usually needs 1,500–3,000 to cover the subtopics, questions and examples the reader expects. The honest test is never "did I hit a word target" but "did I answer the question more completely than the pages currently ranking" — open the top three results, list what they cover, and make sure yours covers it and then some.

Counting a Whole Site vs a Single Page

There are two very different reasons to count words. Auditing a single page tells you whether a specific article has the depth to compete for its keyword. Auditing a whole site's word count — total words across every URL — tells you something else entirely: whether you have enough indexable content for Google to understand your topical authority at all. A ten-page site with 120 words per page has roughly 1,200 words of substance for the entire domain, which is why it struggles to rank for anything competitive no matter how good the design is.

When you scale this up, watch for the opposite problem too: thin, near-duplicate pages (location pages that differ only by city name, tag archives, boilerplate product variants) inflate your total word count while adding no unique value, and at volume they can trigger a thin-content or doorway assessment. More words are only ever an asset when each block earns its place; the goal is depth per topic, not tonnage per domain.

Frequently Asked Questions