How do you identify and remove thin pages?
Thin is about usefulness rather than word count — a 200-word page that answers the question completely is not thin. Combine three signals: Search Console pages with impressions and no clicks, analytics pages with immediate exits, and crawl data showing few inbound internal links. Then improve, merge, noindex or remove each.
Thin is about usefulness, not length
Word count is a proxy, and a bad one. A 200-word page that answers a specific question completely is not thin. A 1,200-word page of generic filler is.
The practical test: if someone landed here from a search, would they get what they came for, or would they leave and try the next result?
Find the candidates
Combine three signals rather than relying on one:
Search Console. Pages with impressions but almost no clicks, and pages with no impressions at all over a long window.
Analytics. Pages with entries but immediate exits and no onward engagement.
A crawl. Low word counts, missing meta descriptions, duplicate titles, few or no internal links pointing in.
A page that appears in all three is a confident candidate. A page in only one may just be seasonal or new.
The four outcomes
Every candidate ends up in one of four places, and deciding which is the whole job:
Improve it. The topic matters and the page is simply underdeveloped. This is the right answer for anything commercially relevant — service pages especially.
Merge it. Several thin pages circling one topic become one page that covers it properly, with the rest redirected in.
Noindex it. The page has to exist for visitors but has no business in search — thank-you pages, internal search results, utility pages.
Remove it. Genuinely obsolete. Redirect to the closest equivalent if there is one; return 410 if there is not.
Defaulting everything to deletion is a mistake. So is defaulting everything to expansion — padding a page that nobody needs produces a longer page nobody needs.
The usual offenders on a local business site
- Tag and category archives with one or two posts
- Author pages on a site with one author
- Paginated archive pages beyond the first
- Staff profile pages containing a name and a photograph
- Old event or seasonal promotion pages
- Location pages for areas you no longer serve
In The Woodlands, businesses serving a wide surrounding area often have a long tail of village and neighbourhood pages built years ago. Those deserve individual judgement rather than a blanket rule — a few are worth developing, most are not.
Work in commercial order
Start with pages that should be earning and are not. A thin service page is costing you money right now; a thin 2019 blog post is costing you very little. Fixing in traffic-and-revenue order means the effort shows up sooner.
Then stop producing them
The cleanup fails if the production process does not change. A simple rule works: nothing gets published unless someone can say what search it answers and what the reader does next. That single question kills most thin pages before they exist.
What to expect
The indexed page count will fall, sometimes substantially, and overall site performance often improves as a result. Track enquiries and rankings for commercially relevant terms, not the number of URLs.
Frequently asked questions
Is a short page automatically thin?
No. Word count is a weak proxy. A 200-word page that answers a specific question completely is useful; a 1,200-word page of generic filler is thin. The test is whether a searcher gets what they came for.
How do I identify thin pages?
Combine three signals: Search Console pages with impressions but no clicks or no impressions at all, analytics pages with entries and immediate exits, and crawl data showing low word counts and few inbound internal links.
What are my options for each page?
Improve it, merge it into a stronger page, noindex it if it must exist for visitors but not for search, or remove it with a redirect to the closest equivalent — or a 410 if nothing fits.
Which pages should I fix first?
Commercially important ones. A thin service page is costing money now; a thin blog post from years ago is costing very little. Working in revenue order makes the effort show up sooner.
How do I stop thin pages coming back?
Require that nothing is published unless someone can say what search it answers and what the reader does next. That one question prevents most thin pages from being created.