How to find thin content on a WordPress site before it costs you rankings
A page doesn't need to be long to rank, but an informational page competing against 1,200-word results at 150 words is competing on substance it doesn't have. Here's how to find those pages before they quietly stop showing up.
Word count itself isn't something Google scores. Treating it as a proxy for substance is still useful, because a page that says less than the results it's competing against usually loses on merit, not on a technicality.
Thin content accumulates the same way orphan pages do: a post written to fill a content calendar slot, a category page auto-generated with no unique framing, a page that used to be longer before a redesign trimmed it.
Why word count works as a proxy
An informational query usually has an implicit bar for what a complete answer covers. A 1,500-word competing result probably addresses several sub-questions a searcher has; a 150-word page on the same topic almost certainly doesn't, regardless of how well it's written.
This doesn't mean longer always wins — a page that directly answers a narrow, specific query in 200 words can outperform a padded 2,000-word competitor. The floor exists for the broad, informational middle of most content, not for every query type.
Checking one page
There's no view-source trick for word count the way there is for a meta tag — you're estimating from the visible body text. Content Signal's free page checker fetches the page once and returns an approximate count, useful as a quick sanity check against a rough floor of roughly 300 words for informational content.
Treat that number as a signal to investigate, not a verdict. A 280-word page that fully answers a narrow question is fine. A 280-word page attempting a broad topic almost certainly isn't.
The honest fix isn't always "add more words"
Padding a thin page with restated sentences doesn't fix the underlying problem — Google's language understanding isn't fooled by volume without substance, and readers notice immediately.
Three real options exist for a genuinely thin page: expand it with content that actually adds coverage the topic needs, merge it into a stronger page that already covers the ground and redirect, or remove it if it serves no real purpose. Doing nothing is the only option that keeps the crawl cost without any of the benefit.
- Expand when the topic deserves standalone coverage and the gaps are addressable.
- Merge when a stronger page already covers the same ground — redirect the weaker one in.
- Remove when neither applies and the page has no search visibility to protect.
Finding thin pages across a whole site
A handful of thin pages found by spot-checking rarely represents the real scope. Content produced in a batch — a burst of short news posts, an auto-generated set of location or category pages, an early-stage content calendar before editorial standards tightened — tends to be thin as a group.
The free Content Signal WordPress plugin flags every published post and page under a configurable word-count floor, locally, across the whole site in bounded background batches, so the pattern is visible as a list instead of something you have to notice page by page.
Frequently asked questions
Is there a universal minimum word count for good SEO?
No. A reasonable floor for competitive informational content sits around 300 words, but transactional, reference, and narrowly-scoped pages can rank well far below that. Treat any specific number as a screening heuristic, not a rule.
Can a page be too long?
Length itself doesn't penalize a page, but padding a thin topic to hit a word count usually produces worse content — repeated points, diluted keyword relevance, and a slower page. The goal is matching depth to what the topic actually needs.
Does thin content get penalized, or does it just fail to rank?
For most pages it's the latter — it simply loses to more complete competitors rather than triggering an explicit penalty. The exception is content thin enough to look auto-generated or purely duplicative, which can draw closer scrutiny under Google's broader content-quality systems.
Check whether a single URL has this problem right now, free, at the page checker. To catch it across every published post and page, install the free plugin.