Thin Content: How to Spot It and What to Do With Your Old Posts

Old blog posts do not age gracefully. Somewhere on your site there is probably a 300-word update from 2019, a news announcement about an event that has long since happened, or a hastily written "5 tips" post that says nothing your competitors have not said better. In thin content SEO terms, these pages are not neutral. They sit in Google's index representing your business, and a graveyard of weak pages can quietly hold back the good ones.

The fix is not to delete everything in a panic, and it is not to leave it all alone because touching old posts feels risky. It is a triage: look at each page, put it in one of four buckets, and act. Done properly, you can get through twenty old posts in about an hour.

What thin content actually means in SEO

Thin content is any page that offers little or no value to the person who lands on it. Google's own guidelines use the term for pages with scant original substance: a few hundred generic words, content copied or lightly rewritten from elsewhere, doorway pages that exist only to catch a keyword, or posts so out of date they now mislead.

Length alone is not the test. A 250-word page that fully answers a specific question, such as your opening hours over Christmas or how to reset a specific device, is not thin. A 1,500-word post that circles a topic without ever answering anything is. The question to ask of every old post is simple: if a genuine prospect landed here from Google today, would they be glad they clicked?

Two things follow from that definition. First, most small business blogs have some thin content, because early posts were written quickly and standards rise over time. Second, this is rarely a penalty situation. Google does not usually punish a site for a handful of weak posts; it just stops sending them traffic, and it may trust the site a little less overall. The cost is opportunity, not punishment.

Gather the evidence first: ten minutes in Search Console

Before deciding anything, you need to know which old posts still earn their keep. Guessing from memory gets this wrong surprisingly often, because pages you have forgotten about sometimes pull steady traffic.

1. Open Google Search Console and go to the Performance report. If you have never set it up, this walkthrough covers the setup and the four reports that matter.
2. Set the date range to the last twelve months.
3. Switch to the Pages tab and export or scan the list. Note which old posts get clicks, which get impressions but no clicks, and which get nothing at all.
4. Check whether any other pages on your site link to each old post. Your platform's search or a quick site:yourdomain.com "post title" search will surface most of them.

That is your evidence. A post with steady clicks is an asset, whatever its word count. A post with zero impressions in a year is invisible, and you can act on it without fear of losing anything.

The four options: improve, merge, redirect or delete

Every old post goes in one of four buckets. Here is how to choose, in the order you should consider them.

Improve: the post covers a topic you still want to win

If the topic is still relevant to what you sell and the post gets any impressions at all, improving it is usually the best return on your time. Google already knows the page exists and has some history with it, which a brand new URL does not. Keep the URL, keep the title where it still fits the search, and rewrite the body: answer the question properly, add the detail the original skipped, update anything that has changed, and cut the padding. Then update the published or modified date honestly, because you have genuinely revised it.

Merge: several weak posts circle the same topic

Blogs written in bursts often have three or four short posts on near-identical subjects: "backup tips", "why backups matter", "backup mistakes". Individually they are thin; together they are one decent article. Pick the strongest URL, combine the useful material into a single thorough post, and redirect the others to it. This also fixes the problem of your own pages competing with each other for the same search.

Redirect: the post is dead but the URL has value

If a post has inbound links from other sites, or still gets clicks, but the content itself is beyond saving, set up a 301 redirect, the instruction that permanently sends visitors and search engines to a new address. Point it at the closest relevant page: a better post, a service page, or your blog home as a last resort. A redirect to something irrelevant helps nobody, so only redirect where a genuinely related destination exists.

Delete: nothing to save, nowhere to send it

If a post gets no traffic, has no links, and covers a topic with no connection to what you sell, delete it and let it return a 404 or, better, a 410, the status code that tells Google the page is gone deliberately. Deleting feels drastic, but a dead announcement from 2019 does you no favours sitting in the index. Fewer, stronger pages beat a long tail of dross.

Triage twenty posts in an hour

With the Search Console data in front of you, the actual decisions are quick. Aim for two to three minutes per post.

• Open the post and skim it for thirty seconds. Ask the one question: would a prospect be glad they landed here?
• Check its clicks and impressions from your Search Console list.
• Assign a bucket and write it next to the URL in a simple spreadsheet: improve, merge (with what), redirect (to where), or delete.
• Do not fix anything yet. Triage first, act later. Mixing the two turns an hour's job into a lost afternoon.

When the list is done, schedule the work. Deletions and redirects take minutes. Merges and improvements take longer, so spread them over a few weeks, starting with the posts that already get impressions, because those are closest to paying off. If this exercise is part of a wider health check, it slots neatly alongside a thirty-minute audit of the rest of your site.

Why refreshing often beats writing new

There is a strong pull towards writing new posts because new feels like progress. But an existing page with age, a few impressions and perhaps a link or two starts from a better position than a blank URL. Google has already crawled it, filed it and formed a view of it. Rewriting it properly tends to move rankings faster than publishing the same material at a new address.

That does not mean you should stop publishing new content. It means the sensible order for a site with a backlog is: triage the old posts first, rescue the ones with potential, clear out the dead weight, and then add new articles on topics you have not yet covered. A tidy foundation makes every new post work a little harder.

A blog is judged by its average page, not its best one.

Where Helio SEO fits in

Helio SEO writes and publishes new articles; it does not go back and rewrite your 2019 archive, so the triage above is a job worth doing yourself, and it only takes an hour. Where we help is with everything after the clear-out: a steady stream of properly researched, full-length articles so the thin content problem does not simply grow back.