What thin content means
Thin content is a page that does not do enough for the person who landed on it. Word count is a symptom rather than the definition: a short page that answers one question completely is not thin, and a long page assembled from padding, restated definitions and filler is.
In practice it shows up as pages with little more than a heading and a paragraph, near-identical location or service pages built from a template with the name swapped, copied or spun text, and product pages carrying the manufacturer’s description that every other shop also carries. What they have in common is that the visitor could have got the same thing anywhere, or got nothing at all.
Why thin content matters
Search engines have to decide which pages deserve a place in the index, and pages with nothing distinctive on them are the easiest to leave out. A site full of them also spends its crawl allowance on pages that will never rank and spreads its internal links across material that cannot repay them.
The commercial cost is more immediate. A visitor who arrives on a page that does not answer them returns to the results and picks a competitor, and if you paid for that click you paid twice — once for the visit and once for the impression you left behind.
Common mistakes with thin content
The usual response is to add words. Padding a page towards a length target changes nothing that matters, because the page was never too short, it was empty. The fix is substance: an answer, an example, a photograph, a realistic price range, a specific only you can supply.
The second mistake is deleting everything at once. Some weak pages still earn links or rank for a small query, and removing them costs more than leaving them alone. Others should be merged into a stronger page and redirected, and only a few genuinely deserve to disappear. Deciding case by case is exactly what a content audit is for.
How to act on it
List the pages that get almost nothing from search and offer a visitor nothing to act on. For each one choose a route: improve it into a page that answers something, merge it into a page that already does and redirect the old address, or remove it and let the URL return the correct status code.
Where the pages are near-duplicates — a location page per suburb, a service page per keyword variant — the honest fix is to write fewer of them properly. One page with real detail about how you work in a place beats a set of templates with the place name substituted. If a query genuinely needs a page of its own, give it something local and true: a photograph, a delivery time, a named contact, an example of work done there. That is the difference between a template and writing built to answer a query.
