"Your content is thin" is the most common and most misunderstood diagnosis in SEO. It does not mean your article is under some magic word count. It means the page does not fully serve the searcher's need compared with what already ranks. This guide explains what thinness really is, how to audit your own pages for it, and how to fix it with substance rather than padding. It is part of our pillar diagnosis, why your articles aren't ranking.
- Thin means incomplete coverage, not short: a 400-word page that fully answers a narrow query can outrank a padded 2,000-word page.
- Judge thinness against the pages ranking above you — the gaps are the sub-questions, examples and evidence they include and you do not.
- The fix is substance, not padding: fill the genuine coverage gaps with specific, experience-based detail a content farm cannot copy.
- There is no magic word count. The right length is whatever complete coverage of the query takes.
Thin is a coverage problem, not a length problem
Google's own guidance frames the goal as helpful, reliable, people-first content, and its quality documentation has long treated "thin" as shorthand for pages with little added value. Two counterexamples make the point:
- A 350-word page answering "how many minutes in a fortnight" completely can satisfy a searcher fully. Nothing is missing, so nothing is thin.
- A 2,500-word "ultimate guide" that paraphrases the same three points, has no examples, no steps, and no original detail leaves the searcher needing another tab open. That is thin at any length.
The real test: after reading your page, does the searcher still need to go elsewhere to complete the task or answer the question? If yes, your page has gaps — and gaps are what "thin" means.
The four kinds of gaps
1. Missing sub-questions
Every topic has a natural set of follow-up questions — the ones in Google's "People Also Ask" boxes and in related searches. If the top results answer eight of them and you answer three, your coverage is thin by comparison. List the sub-questions before writing, not after.
2. No evidence of experience
Generic summaries of what everyone already says add nothing. Pages get stronger when they include what only someone who has done the thing would know: the step that usually goes wrong, the setting that matters, the mistake to avoid, the actual numbers from a real attempt. This is the practical meaning of the "experience" in E-E-A-T, and it is the hardest content for competitors to copy.
3. Structure that hides the answer
Some pages contain the information but bury it under a long preamble, so both readers and Google's systems judge the page as unhelpful. Put a direct answer near the top, then expand. A page can be "thin" in effect purely through poor organisation.
4. One format where the topic needs more
Some answers need a list, a comparison table, steps, or an example worked end-to-end. A wall of prose about a comparison topic is functionally thin because it does not give the searcher the comparison.
Audit your article against the results above it
- Open the top three ranking pages for your query.
- Write down every H2/H3 topic they cover.
- Mark which ones your page covers, covers better, or misses.
- For each miss, decide: genuine gap (add it), irrelevant tangent (skip), or something you can beat them on with real experience (add prominently).
- Also check the "People Also Ask" questions for your query and make sure the important ones are answered somewhere in your page.
This is a coverage audit, not an invitation to copy outlines blindly — ranking pages also contain fluff you should skip. The goal is no genuine gaps.
Fixing thin content without padding
- Add the missing sub-answers as proper H2 sections, each answering one sub-question completely.
- Add one worked example. A single concrete example usually adds more value than 500 words of generalisation.
- Add specifics: numbers, steps, settings, timeframes, costs where they are real and sourced.
- Add an FAQ section answering real follow-up questions (this article has one; so should yours).
- Cut and merge: sometimes two thin pages on the same topic should become one strong page — see keyword cannibalization for when merging beats expanding.
- Improve the top: a clear summary answer in the first screenful rescues pages whose depth was being missed.
How much content is enough?
Enough is when the coverage audit finds no genuine gaps and a reader could complete their task from your page alone. For competitive informational queries that often lands between 1,200 and 2,500 words; for narrow long-tail questions it may be 600. Write to the audit, not to a number. Our writing pillar guide builds this audit into the writing process itself, so pages are born complete instead of being repaired later.
Sources (5)
Google Search Central, "Creating helpful, reliable, people-first content" and the Search Quality Rater Guidelines' discussion of content quality, at developers.google.com/search/docs and guidelines.raterhub.com.
- Google Search Central — Creating helpful, reliable, people-first content
- Google Search Central — Google Search Essentials
- Google Search Central — SEO Starter Guide
- Google Search Central Blog — Google Search's guidance about AI-generated content
- Search Console Help — URL Inspection tool
Thin by duplication: the quiet variant
One more gap deserves naming: content can be "thin" relative to your own site. If three of your articles summarise the same topic at the same depth, each is effectively a third of a page as far as distinct value goes — and Google typically indexes and ranks one, holding the others back. This overlaps with cannibalization, but the root cause is coverage: none of the three adds anything the others lack. The audit question that exposes it: "if I deleted this page, what information would the site lose?" If the honest answer is "none", the page is duplication-thin regardless of its word count.
Thin content at site level
Individual thin pages are a quality problem; a pattern of them is a reputation problem. When a large share of a site's catalogue leaves searchers unsatisfied, the site's stronger pages can find the going harder too — Google's helpful-content system assesses sites partly as a whole. This is the strategic argument for the merge-and-delete end of the fix spectrum: ten strong pages do more for a small site's trajectory than forty thin ones, and pruning is not failure. It is editing, at catalogue scale.
An editor's shortcut
When time is short, one question performs most of the coverage audit's work: "what does the searcher still wonder after the best current answer?" Spend twenty minutes listing those residual wonders for your topic — the unpriced cost, the unmentioned exception, the step everyone glosses. An article built to answer the residue is rarely thin, because residue is where genuine gaps live.
Frequently asked questions
Is there a minimum word count to avoid thin content?
No official minimum exists. Coverage is the standard: if your page answers the query and its natural sub-questions as completely as the top results, length takes care of itself.
Can a page be too long?
Length alone does not hurt, but padding does — repeated points and off-topic sections dilute the page's focus and bore readers. Every section should earn its place in the coverage audit.
Should I expand thin pages or delete them?
Expand pages on topics worth owning; merge pages that overlap; delete only pages with no topic value at all. Our pillar guide's diagnosis order helps decide which case you have.
Does AI-written content count as thin?
Not automatically. Thinness is about value and completeness, not authorship. But unedited generated text often repeats generic points without experience detail — which is exactly the coverage gap described here.
How do I know if Google sees my page as thin?
There is no 'thin' flag in Search Console. The practical signals: indexed but near-zero impressions for months, or impressions for much narrower queries than you targeted.
Put your page beside the top three results, list what they cover that yours does not, and fill those gaps with detail only someone who has done the thing can supply. That list — not a word-count target — is your fix plan.
Which gap did you find first in your thinnest article: a missing sub-topic, missing examples, or missing proof?
