This post may contain affiliate links. If you buy through one, we may earn a commission at no extra cost to you. See our Affiliate Disclosure for details.
Somewhere on a small blog there is a post from 2024 that used to bring in a hundred visitors a week. Nobody touched it. Nothing broke. This month it brought in thirty. The writer, who is also the designer, the support desk and the accountant, hasn't noticed yet, because the site total looks fine — a couple of newer posts are covering the gap. That slow, silent slide is content decay, and on a one-person blog it is the biggest source of lost traffic that nobody is measuring.
Content decay is the gradual loss of search traffic to a post that once ranked, usually because competitors published fresher pages, the question people ask has shifted, or the facts in the post went stale. Find it by comparing the last three months against the same three months a year earlier in Google Search Console, sorted by the drop in clicks. Then make one of three calls per page: refresh it properly (new facts, new sections, tighter answer), merge it into a stronger post with a redirect, or leave it alone if the topic itself has died. A quarterly afternoon covers a blog of fifty posts.
Why a post that ranked stops ranking
Nothing has to go wrong on your site for a post to decay. Three things happen on their own.
Competitors ship. A post that was the clearest answer to a question in 2024 is now one of forty, and several of the newer ones cite this year's numbers. Google's own guidance on creating helpful content leans on whether a page gives a satisfying, current answer, and a two-year-old page with a two-year-old screenshot rarely does.
The question drifts. "Best invoicing app" in 2024 and "best invoicing app" in 2026 are the same words with a different set of tools behind them. Search engines notice when clicks move to pages that talk about the new set, and the old page slides even if its writing is better.
The facts expire. Pricing tables, feature lists, "as of" dates, links to pages that have since moved. A reader who lands on stale facts leaves quickly, and enough of that shows up as a page that no longer satisfies the query.
None of this is a penalty. There is no alert, no email, no red flag in the dashboard. That is what makes it dangerous for a blog with one person on it.
Finding the pages that slipped
The Search Console Performance report keeps up to 16 months of data, which is enough for a proper year-over-year comparison. The routine takes about ten minutes once you've done it twice.
Open Performance, set the date filter to Compare, and choose the last three months against the same three months a year earlier. Switch to the Pages tab. Sort by the difference column for clicks, with the biggest negative numbers at the top. That list is your decay report.
Two checks before acting on it.
Impressions versus clicks. A page whose impressions held steady but whose clicks fell is still being shown and no longer chosen — the title or snippet lost a fight with a newer result, or the query behind it changed meaning. A page whose impressions fell too has slipped out of the results altogether, which usually points at content rather than packaging.
Seasonality. A post about year-end tax filing will look like it is dying every spring. Comparing against the same period a year earlier handles most of this, but look at the 16-month line for anything that swings.
The Compare view in Search Console is the whole detection system. Photo via Pexels.
For a second opinion from outside Google's own data, Ahrefs Webmaster Tools offers a free tier for verified site owners with page-level organic traffic estimates. It is an estimate, not a measurement, so use it to confirm what Search Console shows rather than to replace it. A rank tracker does the same job for a handful of chosen keywords, if you already run one.
Refresh, merge, or let it go
Not every declining page deserves the afternoon. The decision comes down to two questions: does anyone still ask this, and is this the best page on your site to answer it?
Refresh when the topic is alive and the page is your only real answer to it. This is the majority case on a small blog. The page has history, inbound links and an established URL; a rewrite on a new URL throws that away.
Merge when two or three of your posts answer near-identical questions and are splitting the traffic between them. Fold the weaker ones into the strongest, then point the old URLs at it with a permanent redirect. Google's redirect documentation covers which redirect type to use and why a 301 is the one for a permanent move. This tends to produce a bigger lift than any individual refresh, and it is the step solo bloggers skip most often, because deleting a post feels like losing work.
Leave it when the question has genuinely gone away — a tool that shut down, a feature that no longer exists, a platform nobody uses. A short note at the top saying the post is kept for reference costs nothing and stops the page from misleading the few people who still land on it.
The temptation with all three is to keep adding rather than deciding. A blog with two hundred posts of which sixty quietly compete with each other is heavier to maintain and weaker in search than the same blog at one hundred and forty.
What a refresh actually changes
A refresh is not a date bump. Editing the publish date without changing the page is the one move that reliably does nothing, and the one people reach for first.
Start with the "as of" lines. Any sentence that states a price, a plan limit, a feature or a number needs re-checking against the vendor's page and a fresh date. If the number moved, update it; if you can't confirm it, replace the number with a link to the page that has it. This blog runs on that rule for good reason — prices in a two-year-old post are wrong more often than they are right.
Then look at what the newer competing pages answer that yours doesn't. Open the top three results for the page's main query and note the sections they have in common that you lack. Those are the questions the query grew to include. Add a section for each, written from your own angle, and skip anything that is padding on their side too.
Tighten the opening. The first two paragraphs of a post written when the topic was new usually spend their time explaining that the topic exists. Two years on, the reader already knows; cut to the answer. The same logic behind which pages get cited in AI answers applies here — a clear answer near the top is what both search engines and readers reward.
Fix the links. Outbound links to pages that have moved get updated or removed. Inbound links from your own newer posts get added, since a post published last month almost never links back to one from two years ago on its own. The internal linking pass for a small blog is the same exercise, applied to one page at a time.
Optional: run the draft through an on-page editor. Surfer SEO scores a draft against the current top-ranking pages for a keyword and lists the terms and headings those pages share, which is a faster version of the manual comparison above. As of September 2026, Surfer's pricing page lists several tiers with different monthly article limits; the numbers change often enough that the page itself is the only reliable source. For a blog refreshing three or four posts a quarter, the free comparison in a browser tab does most of the same work, and the content optimization tools covered earlier on this site fill in the rest.
An archive is only useful if someone re-shelves it now and then. Photo via Pexels.
A quarterly routine that fits in one afternoon
| Step | Tool | Time |
|---|---|---|
| Compare last 3 months vs. same period a year earlier, Pages tab, sort by click difference | Search Console | 10 min |
| Mark each of the top 10 decliners as refresh, merge, or leave | A spreadsheet | 15 min |
| Refresh the top 2 or 3: facts, new sections, opening, links | Editor of choice | 2–3 hours |
| Merge one cluster if there is one, with 301 redirects | Site CMS | 30 min |
| Note the date and the pages touched, so next quarter's compare is readable | Same spreadsheet | 5 min |
Four of these a year keeps a fifty-post blog from quietly shrinking. The spreadsheet matters more than it looks: without a record of what was refreshed when, next quarter's comparison can't tell a page that recovered from one that was never touched.
Pick one post this week
Open Search Console, set Compare to the last three months against the same three months last year, switch to Pages, and sort by the click difference. Take the single page at the top of the list — the one that lost the most — and read it as if you had just found it in a search result. Fix its dates and numbers, add the one section the competing pages have that it lacks, and link to it from your newest post.
One page, one week. Content decay is not solved in a sprint; it is held off by a habit, and the habit starts with the page that is losing the most right now.
저는 한국에서 직원 없이 혼자서 두 개의 소규모 사업체를 운영하고 있습니다. 견적, 회계, 마케팅, 웹사이트 관리까지 모두 제가 직접 하고 있습니다. 개발자는 아니지만, 이 사이트의 자동화 시스템은 AI 코딩 도우미를 활용하여 밤늦게까지 오랜 시간 공들여 구축했고, 모든 콘텐츠 관리 및 게시도 제가 직접 담당하고 있습니다.