A page can run past two thousand words and still be thin content in Google's eyes. A page can run under 100 words and be exactly what the searcher needed. Word count was never the real test, even though a lot of advice still treats it that way.
This guide cross-checks Google's own guidance on thin content against the statuses you actually see in Search Console, then reconciles the usual conflicting advice (expand it, delete it, noindex it) into one framework you can apply page by page.
You'll get a plain-language definition, six concrete types of thin content, a Search Console status table that tells you which flagged pages are actually thin, and a five-option fix framework so you're not guessing. Here's where to start.
What Is Thin Content?
Google defines thin content as pages that offer little or no added value to the person reading them, regardless of how those pages were produced. That includes auto-generated text, thin affiliate pages, scraped content, and doorway pages built mainly to funnel traffic elsewhere.
The term became common shorthand after Google's Panda update in February 2011, which targeted sites built around low-value, keyword-stuffed pages. Panda is old news at this point, but the underlying standard hasn't changed: does this page actually help the person who searched for it?
That standard has nothing to do with length. A page can run 2,000 words and still be thin if none of those words answer the question. A page can run 80 words and be complete.
The Word-Count Myth
A lot of SEO advice still repeats some version of "keep pages above 300 words to avoid thin content." That advice is incomplete, and following it on its own won't fix anything.
Word count is a symptom you might notice, not the cause you're trying to fix. A short FAQ answer that fully resolves the question isn't thin. A long product page that copies the manufacturer's spec sheet and adds nothing else is thin no matter how many words it runs.
The real question for any page: if you removed everything a competitor already says better, is there anything left? If the answer is no, length won't save it.
6 Types of Thin Content (With Examples)
Most guides on this topic list anywhere from four to eight overlapping categories. Here are the six that actually show up in practice, with the difference between them made concrete.
| Type | What it looks like | Example |
|---|---|---|
| Auto-generated content | Text produced by AI or a template with no original analysis or checking | An AI-written "best productivity apps" listicle with no first-hand testing, generic descriptions pulled from app store copy |
| Thin affiliate pages | Product info copied from the manufacturer, no hands-on use | A headphone review that repeats spec-sheet numbers but never says how the headphones actually sound |
| Doorway pages | Near-identical pages built to rank for local or variant keywords, all pushing to the same destination | "Best dog food in Austin," "Best dog food in Houston," and "Best dog food in Dallas" that are the same page with the city name swapped |
| Scraped or syndicated content | Content copied from elsewhere with no canonical tag or attribution | A "news roundup" page that republishes other outlets' articles in full |
| Internal duplicate content | Two or more of your own pages targeting the same intent with near-identical content | A blog post and a landing page that both explain the same concept, word for word, under different URLs |
| Boilerplate pages that scale unintentionally | Auto-created pages from a CMS template that never got individual attention | Empty tag archive pages, thin attribute pages on an ecommerce catalog (e.g. "Blue widgets," "Red widgets" with no unique copy) |
The first three are usually intentional (someone built them to game rankings). The last three usually aren't. They accumulate quietly as a site scales, which is why they're the hardest type to catch with a manual read-through.
Why Thin Content Hurts Your SEO
Thin content doesn't just fail to rank. It actively works against the rest of your site in a few specific ways.
Higher bounce rates. Visitors who land on a page that doesn't answer their question leave immediately. What counts as "high" varies a lot by page type: a 90%+ bounce rate is normal for a single-answer blog post, while the same number on an ecommerce category page usually signals a real problem. Don't compare your bounce rate to a single universal number; compare it against similar pages on your own site.
Wasted crawl budget and index bloat. On larger sites, Googlebot spends time crawling thousands of thin pages instead of your pages that matter. That slows down how quickly new or updated content gets indexed.
Keyword cannibalization. When two or more thin pages target the same query, they split ranking signals instead of combining them, and neither ranks as well as one consolidated page would.
Manual action risk. Widespread, clearly manipulative thin content (doorway pages, scraped content at scale) can trigger a manual action, not just a ranking drop. Check Security & Manual Actions in Search Console if you suspect this.
How to Find Thin Content on Your Site (Using Search Console)
Most guides on this topic stop at "run a site audit" or "review your content manually." Neither tells you where to actually look first. In practice, thin content usually shows up as an indexing status or an engagement problem in Search Console before you'd ever spot it by reading through pages one by one.
Here's the workflow:
- Pull the Pages report. In Search Console, go to Indexing → Pages, and scroll to "Why pages aren't indexed."
- Cross-reference against the Performance report. For any URL flagged in that report, check whether it also shows near-zero clicks and impressions over the last 90 days in Performance. Pages that are both excluded from the index and getting no search visibility are your highest-priority candidates.
- Triage by pattern, not URL by URL. Group flagged pages by section or template (tag archives, old blog posts, product variants) instead of investigating one at a time. If 200 flagged URLs all come from the same tag-archive template, that's one fix, not 200.
Manually exporting both reports and cross-referencing them by hand works fine for a few dozen URLs. Past that, it turns into a spreadsheet exercise nobody wants to repeat every month. Visualizing your Search Console data (with a tool like SEO Heatmap) surfaces the same low-performing, thin-content-prone pages without the manual export step, which makes the audit something you can actually run on a recurring basis instead of once a year.
In practice: thin content rarely spreads evenly across a site. It clusters in specific sections: old tag archives, thin location pages, abandoned product variants, or a blog category nobody's updated in years. Once you find one cluster, check whether the same template produced others.
GSC Status → Thin Content Diagnostic Table
Search Console already tells you which pages have a problem. It just doesn't tell you whether that problem is thin content or something else. This table closes that gap.
| GSC status | What it usually means | Is it thin content? | What to do |
|---|---|---|---|
| Crawled – currently not indexed | Google crawled the page but chose not to index it | Often, yes, if the page doesn't clearly add anything beyond what's already indexed | Expand, consolidate, or remove depending on demand. See our full guide |
| Discovered – currently not indexed | Google found the URL (via sitemap or links) but hasn't crawled it yet | Sometimes: can also be a pure crawl-budget or crawl-queue issue unrelated to content quality | Check crawl priority first, then content quality. See our full guide |
| Duplicate without user-selected canonical | Google sees this page as equivalent to another and picked its own canonical | Often, yes, if the "duplicate" is actually a near-identical internal page | Consolidate or add a canonical tag. See our full guide |
| Soft 404 | Google thinks the page's content resembles an error or empty page, even though it returns a 200 | Frequently, yes: empty category pages, out-of-stock products, or thin location pages commonly trigger this | Add real content or return a real 404/410. See our full guide |
| Excluded by noindex tag | You (or your CMS) told Google not to index this page | Not a problem by itself: this is the correct outcome for pages you deliberately kept thin (see "Noindex it" below) | No action needed if intentional |
| Indexed, but near-zero clicks/impressions over 90+ days | The page is in the index but isn't earning any visibility | Worth checking manually: not every low-traffic page is thin, but this is where to look next | Manual review against the typology above |
How to Fix Thin Content: 5 Options (and When to Use Each)
Guides on this topic tend to default to one of two answers: "expand it or delete it," or "noindex it instead." Both are right some of the time and wrong the rest of the time. The actual answer depends on three questions:
- Does the page have backlinks or organic traffic worth preserving?
- Does it need to stay live for users even if it shouldn't rank (checkout, thank-you, internal search)?
- Does the topic have real search demand that justifies the investment?
Answer those three questions and you land on one of five outcomes.
Expand It
Use this when the topic has real demand and the page just doesn't deliver yet. Add original analysis, first-hand examples, or data that isn't already sitting on the top-ranking pages for the same query. Confirm the demand exists before investing the time. Padding an existing page with more words that don't add anything just produces a longer thin page.
Consolidate It
Use this when several of your own pages compete for the same intent. Merge them into one page that actually covers the topic, then 301 the merged URLs to the survivor. Watch for the early symptom first: multiple similar pages on your site ranking for the same query and swapping positions in Search Console's Performance report over time.
Redirect It
Use this when the page has no standalone value left but does have backlinks or history worth preserving. 301 it to the closest genuinely relevant, stronger page on your site. Don't redirect it to something unrelated just to keep the link; that confuses users and doesn't pass much value anyway.
Noindex It
Use this when the page has to exist for users but was never meant to rank: checkout pages, thank-you pages, internal search results, thin filtered or faceted URLs. Keep the page live, keep it out of the index. This is the option most "expand or delete" advice skips.
Delete It
Use this when the page has no traffic, no backlinks, and no realistic path to becoming useful. Check first that nothing on your site still links to it internally. Let it return a real 404 or 410 rather than redirecting it somewhere unrelated just to avoid an error.
Quick reference:
| Has traffic/backlinks? | Must stay live for users? | Real search demand? | Fix |
|---|---|---|---|
| Yes | No | Yes | Expand |
| Yes | No | Overlaps another page | Consolidate |
| Yes | No | No | Redirect |
| No/Yes | Yes | N/A | Noindex |
| No | No | No | Delete |
How to Prevent Thin Content From Piling Back Up
Cleaning up existing thin content is a one-time project. Keeping it from coming back is an ongoing habit.
- Add a gate before publishing near-duplicate topics. Before a new page goes live, check whether it says anything the top-ranking pages for that query don't already say. If not, don't publish it as a standalone page.
- Audit new page templates before they scale. Tag pages, location pages, and attribute pages look harmless as a single example. Check what 50 or 500 of them will look like before the template goes live sitewide.
- Refresh on a schedule, not just after a traffic drop. A rough rule of thumb: spend about a quarter of your content time updating existing pages instead of only publishing new ones.
- Recheck the Page Indexing report on a set cadence. Monthly works for most sites. New thin content tends to appear right after a CMS migration, a new template rollout, or a content import, and catching it early is much cheaper than cleaning it up a year later.
Thin content audit worksheet:
| URL | GSC status | Traffic (90d) | Backlinks? | Fix chosen | Date fixed | Verified? |
|---|---|---|---|---|---|---|
| /example-page-a | Crawled – not indexed | 0 clicks | No | Delete | 2026-07-21 | Yes |
| /example-page-b | Soft 404 | 3 clicks | Yes | Redirect | 2026-07-21 | Pending |
| /example-page-c | Duplicate, no canonical | 12 clicks | No | Consolidate | 2026-07-21 | Yes |
If you're auditing a site with a lot of pages, spotting these clusters by scanning a spreadsheet gets old fast. SEO Heatmap turns your Search Console data into a visual map, so the pages worth triaging stand out instead of getting lost in an export.
Frequently asked questions
Is there a minimum word count that counts as thin content?
No. Google's guidance on thin content is about whether a page adds real value, not how many words it contains. A short page that fully answers the question isn't thin, and a long page that pads itself out without answering the question still is. Judge each page by whether it says something the top-ranking pages for that query don't already say.
Can a short page rank well without being thin content?
Yes. FAQ answers, definitions, and single-purpose pages can run under 100 words and still fully satisfy the intent behind a search. What matters is completeness, not length. If a reader gets exactly what they came for and doesn't need to leave the page, it isn't thin.
How long does it take to see ranking changes after fixing thin content?
There's no fixed timeline. Search Console's Page Indexing report reflects Google's most recent crawl, which can lag by days to weeks after you make a change. Give a fix at least two to four weeks before checking whether the page's status or performance improved, then keep monitoring monthly.
What's the difference between thin content and duplicate content?
Thin content lacks value regardless of whether it's unique, while duplicate content is identical or near-identical to another page, whether or not either version is thin. The two overlap often: two duplicate pages that both add nothing are thin and duplicate at the same time. A page can also be duplicate without being thin (a well-written syndicated article) or thin without being duplicate (an original page that's simply underdeveloped).
Should I delete thin content or noindex it instead?
It depends on whether the page needs to stay live for users. Delete pages with no traffic, no backlinks, and no path to becoming useful. Noindex pages that have to exist for people, like checkout pages, thank-you pages, or internal search results, but were never meant to rank.
How do I find thin content without reading every page manually?
Start with the Pages report in Search Console instead of a manual read-through. Cross-reference pages excluded from the index against the Performance report for near-zero clicks and impressions, then group the results by template or section instead of checking one URL at a time. A tool like SEO Heatmap can visualize that same Search Console data so the low-performing clusters stand out without exporting and merging reports by hand.
Can thin content trigger a Google manual action?
Yes, if it's widespread and clearly built to manipulate rankings. Doorway pages, scraped content at scale, and auto-generated pages with no original value are the types most likely to trigger action, not one thin page here and there. Check Security & Manual Actions in Search Console if you suspect this, since a manual action needs a reconsideration request after the fix, not just a content update.
What should I do first if I think my site has thin content?
Pull the Pages report in Search Console and check what's excluded from the index before doing anything else. That report tells you where to look, so you fix pages that are an actual problem instead of guessing. From there, sort flagged pages into five fix options (expand, consolidate, redirect, noindex, delete) based on traffic, backlinks, and whether the page has to stay live.
If thin content is the kind of issue you'd rather catch early instead of during a yearly cleanup, SEO Heatmap is built to make Search Console data easy to scan at a glance. Give it a try, it's free.