Thin content is a page that adds too little value to earn a place in search. It is rarely about word count alone. Here is what actually signals it, why a pile of thin pages drags down the pages you care about, and whether to improve, merge, or remove.
Thin content is a page that offers little unique value to the person who lands on it. Word count is one hint, but a 200-word answer that fully resolves a query is not thin, and a 2,000-word page that says nothing is.
Google's concern is value per page, not length. A page is thin when a searcher arrives, finds nothing they could not get faster elsewhere, and leaves. The classic cases are auto-generated pages, doorway pages built only to rank, near-empty category or tag pages, scraped or spun text, and pages that exist to hold an ad rather than to answer anything. What they share is that a real person gets little out of them.
Because "value" is hard to measure directly, an audit looks at the signals that tend to travel with thin pages, and flags a page when several stack up at once rather than relying on any single one. That is what the "thin content composite" finding is: not a word-count trip-wire, but a cluster of weak signals appearing together.
One of these alone is often fine. Several together is the pattern that flags a page.
Very little body text, or an "empty" page that returns 200 but has almost no words, so there is not enough substance to answer anything.
A long page with no structure: no headings breaking it into sections, which usually means it is not actually covering the subject in depth.
Content that skims the surface, thin paragraphs that raise a point and move on without developing it, so the page never resolves the query it targets.
The page follows a skeleton shared by many others with only a few words swapped in, so it is near-duplicate filler rather than a distinct answer.
The damage is not limited to the thin page itself.
A single thin page just does not rank, which on its own is harmless. The problem is scale. When a site has hundreds or thousands of thin, templated pages, Google's assessment of overall quality drops, and that can weigh on pages that are genuinely good. This is the core lesson behind the principle that one useful page beats a thousand near-empty ones: mass-produced thin content does not add a long tail of traffic, it adds a drag on the whole domain.
It also wastes crawl budget. Search engines spend a finite amount of effort crawling any site, and every thin page they fetch is effort not spent on the pages you want indexed and refreshed. Pruning thin content often improves how quickly your important pages get crawled and updated, an effect covered in the crawl budget guide.
Every thin page gets one of three decisions. Improve it if the topic deserves a page and you can genuinely make it the best answer: add depth, examples, structure. Merge it if it overlaps with a stronger page, combine them and 301-redirect the thin URL, so the surviving page inherits its signals. Remove it if the page has no reason to exist, return a 410 or redirect it to the most relevant page.
The wrong move is to leave a directory of thin pages sitting there "just in case". Doing nothing keeps the drag on site quality and the crawl-budget waste. Pick one of the three for each page and act on it.
Do not read a thin-content flag as "add more words". Padding a page to hit a word count makes it worse, not better: now it is thin and bloated. A concise page that completely answers its query is not thin, and no audit should push you to inflate it.
The fix for genuine thinness is added value, not added length: a real example, a comparison, a step someone can follow, a piece of information the reader could not easily find elsewhere. If a page cannot be given that, it is a candidate for merge or removal, not expansion.
It is rarely written deliberately. It accumulates: a programmatic page generator that spun up a URL per keyword, a CMS that publishes a page for every tag and filter combination, an old strategy of "more pages equals more traffic" that left a directory of near-empty stubs behind.
That is why the fix usually starts at the source, turning off the generator or noindexing the auto-created pattern, rather than editing pages one by one. An audit that groups the thin pages together shows you the pattern, so you can address the cause and then clean up what it already produced. Pages that are also duplicates are covered in the duplicate content guide.
Free to start. The audit stacks the weak-content signals and flags the pages where they cluster.
Start my free audit