Google has no minimum word count. A page is thin when it doesn't fully answer its query. How to test that, then expand, merge or noindex it.
LLaunchScaler·Published ·9 min read
There is no word count below which content becomes thin, and Google says it has no preferred word count. A page is thin when it does not fully answer the query it targets: a 150-word page defining a term can be complete, while a 120-word page trying to explain a process leaves the reader searching again.
Word count is a symptom worth measuring, because very short pages are often incomplete. But the fix is never to add words for their own sake. The test is whether a searcher who lands on the page gets everything they came for, and the fix depends on the answer: expand the page, merge it into a stronger one, or keep it out of search.
Is word count a Google ranking factor?
No. Google's guidance on helpful content lists, as a warning sign, "Are you writing to a particular word count because you've heard or read that Google has a preferred word count?" and answers in the same line: "(No, we don't.)" Length is not measured for its own sake.
Correlation studies point the same way. Backlinko analysed 11.8 million Google results and found the average top-10 result runs 1,447 words, and also that there is "no direct relationship between word count and rankings." Long pages are common on page one because many queries need a long answer, not because length earns a position.
Read the average as a description of what ranks for broad informational queries, not as a target. A pricing page, a changelog entry or a definition does not need 1,447 words, and padding one to that length makes it worse. The same question for blog posts, with a way to set a length per query, is in how long a blog post should be.
What does Google count as thin content?
Google's manual action for "thin content with little or no added value" names the patterns it acts on: thin affiliate pages, content from other sources such as scraped content or low-quality guest posts, and doorway pages. All of them share one trait: they don't give users "substantially unique or valuable content."
The spam policies define each pattern more precisely:
Pattern
Questions, answered
What people ask about this
01
How many words is thin content?
There is no number. Google says it has no preferred word count. A page is thin when it does not fully answer the query it targets, so a 150-word definition can be complete while a 120-word page trying to explain a process is thin.
Pages "created to rank for specific, similar search queries" that lead users to "intermediate pages that aren't as useful as the final destination"
Fifty "invoicing software for [city]" pages with the same text and a city name swapped
Scaled content abuse
"Many pages are generated for the primary purpose of manipulating search rankings and not helping users," however they are created
Hundreds of AI-written glossary pages that restate the term and add nothing
Thin affiliation
Affiliate content where "product descriptions and reviews are copied directly from the original merchant without any original content or added value"
A "best tools" page that pastes each vendor's own blurb and an affiliate link
Scraped or stitched content
Republishing or "stitching or combining content from different web pages without adding value"
A roundup assembled from other sites' paragraphs
Incomplete page
Not a spam policy, but it fails Google's question about a "substantial, complete, or comprehensive description of the topic"
A how-to that lists three steps and stops, or an FAQ answer of one line
The first four are policy problems and can lead to a manual action. The last is a quality problem: nothing is penalised, but the page tends not to be indexed or not to rank, because something else answers the query better.
Google also says what makes affiliate pages good rather than thin: "additional information about price, original product reviews, rigorous testing and ratings, navigation of products or categories, and product comparisons." That list is a useful template for any page type. Thin means nothing on the page could not be found in the same form elsewhere.
How do you test whether a page is thin?
Write down the query the page targets, then read the page as the person who typed it. If they would need to search again to finish their task, the page is thin, whatever its length. Google puts it the same way: "Does your content leave readers feeling like they need to search again to get better information from other sources?"
Run the test in this order:
Name the single query the page should answer, in the searcher's words.
Search it and open the top three results. List what every one of them covers: the definition, the steps, the numbers, the examples, the edge cases.
Compare your page against that list. Every item the others cover and you don't is a gap.
Check for original value. Google asks whether the content provides "original information, reporting, research, or analysis." A page that only restates what the top results say adds nothing even when it covers all of it.
Check for duplication on your own site. If two of your pages answer the same query with overlapping text, at least one of them is thin by comparison.
Search Console can back this up with data. A page with impressions but no clicks for its target query, or a page stuck in the "Crawled - currently not indexed" state, is a candidate. That status means Google fetched the page and chose not to index it for now, and ruling out thin or near-duplicate content is the first check; Crawled - currently not indexed covers that status in full. A checklist of the questions Google asks is in the helpful content checklist.
How many words does each type of page need?
As many as the query's full answer takes, and no more. The type of query sets the floor. A definition query is answered in a paragraph and an example; a "how to" query needs every step; a comparison needs every option judged on the same criteria. About 120 words on an explainer page is almost always too few, because an explanation needs a definition, a mechanism and an example.
Query type
What a complete answer includes
Thin when
Definition ("what is X")
A one-sentence definition, how it works, one example, how it differs from the thing it is confused with
It stops at the definition
How to ("how to do X")
Every step in order, the exact settings or commands, what success looks like, the common failure
Steps are listed without the detail to do them
Comparison ("X vs Y")
Each option judged on the same criteria, with a verdict per situation
It describes each option separately and never compares
List ("best X for Y")
Criteria, each entry judged against them, facts verified per entry
Entries are vendor blurbs
Troubleshooting ("X not working")
Every common cause, how to confirm which one applies, the fix for each
It names one cause
Product or feature page
What it does, for whom, how it works, the price or how to get it, proof
It is a headline and a button
Treat word count as a flag, not a verdict. A page far shorter than the pages ranking for its query deserves a look for gaps, and one far longer deserves a look for padding. In both cases the table above decides, not the number.
Should you expand, merge or noindex a thin page?
Expand it when the page targets a query nobody else on your site answers and it can be made complete. Merge it when another page of yours already covers the same query better. Noindex it when the page is useful to visitors but has no search value of its own. Delete it only when it has no value, no traffic and no links.
Situation
Fix
How
Unique query, incomplete answer
Expand
Add the missing items from your gap list; keep the URL
Two or more pages compete for one query
Merge
Combine the best of both into one page, then 301 the others to it
Useful to visitors, not to searchers (tag archives, thin filter pages, internal notes)
Noindex
Add <meta name="robots" content="noindex"> and leave the page crawlable
No value, no traffic, no links
Remove
Return 404 or 410
For a merge, use a permanent redirect. Google says that with a 301 or 308, "Googlebot follows the redirect, and the indexing pipeline uses the redirect as a signal that the redirect target should be canonical," and recommends a permanent server-side redirect "whenever possible." Point internal links at the surviving URL too, and remove the merged URLs from your sitemap.
For a noindex, leave the page crawlable. Google drops a page from results once it crawls it and finds the rule, but "for the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file." A thin page blocked in robots.txt can still be indexed from links alone.
Expansion is the fix that most often gets skipped, because it takes the most work. It is also the one that turns a thin page into a page that can rank. Rewrite from the gap list, not from the old text, and keep the parts that were already specific. For pages that were complete once and have gone stale, a content refresh strategy covers when to update rather than rewrite.
Can a whole site be affected by thin pages?
Google's spam policies describe scaled content abuse as creating "large amounts of unoriginal content that provides little to no value to users, no matter how it's created," and tell sites hosting such content to "exclude it from Search." When thin content earns a manual action, Google's help describes the way back: remove or improve the pages, then send a reconsideration request with "examples of bad content that you removed and good content that you added."
Short of a manual action, the cost shows up page by page, as thin URLs that Google crawls and leaves out of the index. Thin pages usually come from a template (a city page, a tag archive, a generated glossary entry), so fix the template and every page it built improves at once. LaunchScaler's free scan flags a page whose main content is too thin for an informational topic, which is a quick way to catch the pattern on one template page before it spreads.
Plan fixes to thin pages alongside new articles
Fixing thin content is a planning problem as much as a writing one: you need to know which pages to expand, which to merge and which queries have no page at all. LaunchScaler's content engine plans a month of articles from your site's own Search Console queries, its readiness audit and keyword data, and each item in the plan is a move: a new page, or an improvement, retitle or consolidation of a page your site already has. It writes one article a day in your site's voice, thirty a month, and by default every draft waits for your review before it publishes. It costs $99/mo per website, with 3 days free, and publishes to WordPress, Webflow, Ghost, Shopify, Notion, Medium or a signed webhook. Start the engine to get a plan that treats your existing pages as part of the work.
No. Google's helpful content guidance asks whether you write to a word count because you heard Google prefers one, and answers 'No, we don't.' Backlinko's analysis of 11.8 million results found no direct relationship between word count and rankings.
03
What is an example of thin content?
Google's examples are thin affiliate pages that copy the merchant's descriptions, doorway pages built to rank for near-identical queries, scraped or stitched content, and pages generated at scale without adding value. A short explainer that leaves readers searching again is thin too.
04
Should I delete thin content?
Only if the page has no value and no traffic or links. Otherwise expand it to answer its query, merge it into a stronger page with a 301 redirect, or keep it for visitors and add a noindex rule so it stays out of search.
05
Does thin content cause 'Crawled - currently not indexed'?
It can. That status means Google fetched the page and chose not to index it for now. Checking that the page is not thin or a near copy of another URL, then making it substantially more useful, is the first thing to try.
Set twitter:card to summary_large_image, give X an image it can fetch, allow Twitterbot, then test in the post composer. X caches cards for up to 7 days.
