Thin content: how 200-word pages drag down your whole site

Every site accumulates them: the service page that is a heading and two sentences, the "news" section with one post from 2023, the tag archives WordPress generates for every label anyone ever typed. Each page looks harmless. Together they are a quality signal, and it points down.

Why thin pages are a sitewide problem

Search engines evaluate sites as wholes. When a large share of your indexed pages offer nothing to answer, the site-level judgment gets dragged toward "mostly not useful", and even your strong pages feel it. Crawl budget is finite too: time spent crawling empty archives is time not spent noticing your updated money pages.

What counts as thin

• Under roughly 300 words of actual content, template text excluded.
• Auto-generated archives: tags, date pages, empty categories, attachment pages.
• Near-duplicates: five city pages with the same paragraph and a swapped place name.
• Placeholders that shipped with the theme and never got written.

Expand, merge, or remove

Sort every thin page into one of three buckets. Expand pages that target a question a customer actually asks; give them the answer-shaped treatment. Merge near-duplicates into one strong page with a redirect. Remove or noindex the structural leftovers: WordPress attachment pages, empty tags, and date archives should generally not be in the index at all.

The goal is not more words. Padding a 200-word page to 800 with filler makes it worse. The goal is that every indexed URL either answers something or stops being indexed.

Our scan flags thin content per crawled page and pairs it with the internal-link check, because thin pages and orphan pages usually travel together: the site's forgotten tail. Clearing that tail is one of the least glamorous and most reliable score improvements there is.

Quick answers

What counts as thin content?

Pages with too little substantive text to answer any question, typically under about 300 words of actual content. Templates, tag archives, and placeholder pages are the usual suspects.

Should I delete thin pages or expand them?

Expand pages that target a real customer question. Delete or noindex pages that exist only for structure, like empty tag archives. Every indexed page should earn its place.