How to fix content decay

Content decay is a lasting fall in the clicks a page earns from search. How to confirm it in Search Console, find the cause, and refresh, merge or let go.

Content decay is a lasting fall in the clicks a page earns from Google while the page itself stays the same. To fix it, first confirm that it is decay rather than seasonality, falling demand or a site-wide problem. Then find which searches the page lost and why, choose between refreshing, extending, merging or retiring it, and measure the result over the following weeks. Most of this can be done in Search Console's Performance report.

Is it decay, or something else?

A falling line can have several causes, and only some of them are fixed by editing the page. Google's guide to debugging traffic drops lists technical issues, security and spam problems, ranking updates, changes in what people search for, and site moves. Rule these out in order:

Seasonality. In the Performance report, use Compare and choose the last three months year over year, or look at the full 16 months for a yearly pattern. A garden-furniture guide that falls every autumn is not decaying.
A site-wide drop. If most pages fell in the same week, look at Page indexing, Manual actions and Security issues before blaming content. Decay is page by page and gradual.
Demand. If impressions fell while position held steady, fewer people are searching. Google suggests Google Trends to check whether a drop is part of a wider trend.
Measurement. If analytics shows a drop that Search Console does not, the problem is tracking, not search.

What remains is decay: people still search, Google still shows the page, but it ranks lower or gets picked less often than it used to.

Impressions	Position	CTR	Most likely cause	Response
Falling	Steady	Steady	Fewer searches	Wait it out, or widen the page to related searches
Steady or falling	Worse	Steady or falling	Newer or better pages overtook you	Refresh or extend (steps 4 and 5)
Steady	Steady	Falling	Something new sits above you on the results page, or your title or snippet changed	Look at the results page; see the CTR playbook
Steady or rising	Worse	Falling	Another of your own pages may be taking the search	Check the query's Pages tab; see cannibalisation

Step 1: find the pages that lost the most

Open Performance → Search results → Pages and compare the last 28 days with the 28 days before (or the same weeks last year for a seasonal site). Sort by the difference in clicks so the largest losses come first.

Rank by absolute loss rather than by percentage. A page that went from 900 to 600 clicks is a bigger problem than one that went from 12 to 3, even though the second lost three quarters of its traffic. Two reference points help when deciding what counts:

AutoPSEO's content engine refreshes its own articles when clicks in the last 28 days are at least 40% below the 28 days before, and only when the earlier window had 20 clicks or more.
AutoPSEO's Content Decay heatmap marks a page as severe when its latest month is at least 50% below its best month, and moderate at 25%.

Both are judgement calls. A short window catches decay early but is noisier; a monthly view is steadier but slower.

Step 2: find the searches that moved

Click the page to filter the report by it, switch to Queries, and keep the comparison. Sort by the difference in clicks. You will usually see one of three patterns:

One big search lost. The page fell several positions for its main query. Something specific overtook it.
Many small searches lost. The page's long tail is drying up, often because newer pages answer the details better.
No position change, fewer clicks. CTR fell. Something on the results page changed.

Write down the two or three searches that account for most of the loss, with their old and new positions.

Step 3: read today's results page

Search those queries in a private window, set to the country your audience is in, and note what now ranks above you. Look for:

Fresher pages. Google runs freshness systems designed to show fresher content for searches where people expect it (ranking systems guide). If the top results are all from this year and yours is three years old, that is your answer.
A different kind of page. Videos, tools, product pages or forum threads where articles used to be means the searcher's intent shifted.
Better answers. Competitors covering a step, a comparison or a question your page skips.

Step 4: refresh, extend, merge or let go

Situation	Choice
Same searches, same intent, your page is out of date	Refresh: update the facts and examples
The searches now include questions your page does not answer	Extend: add the missing sections
Another of your pages answers the same searches as well or better	Merge: move what is unique into the stronger page, then redirect
The product, event or topic is gone, and so is the demand	Let go: leave it, redirect it to a genuinely related page, or remove it

When you merge, redirect the old address permanently (301 or 308). Google treats a permanent redirect as a strong signal that the target should be the canonical (Redirects and Google Search). When you remove a page with no replacement, a 404 is fine; Google says that is not a problem for a page removed without a successor.

Step 5: refresh honestly

Keep the address. The page's history and links stay with it.
Keep what still works. Sections that hold their searches stay as they are.
Update the substance. Facts, prices, figures, screenshots, steps that changed, products that no longer exist.
Answer what people ask now. New searches in the page's Queries tab are the sections it is missing.
Do not just change the date. Google's helpful-content questions ask whether you change dates to look fresh when the content has not substantially changed. Change the date when the content changed.
Update <lastmod> in your sitemap to the date of the real update; Google uses it when it is consistently accurate.

Touch the title and description only if the searches the page wins have changed.

Step 6: tell Google and measure

For an important page, ask Google to crawl it once through URL Inspection; for the rest, the sitemap is enough. Add an annotation on the Performance chart on the day of the refresh and log the change. After four to eight weeks, compare equal windows before and after, query by query. If the page has not recovered, read the results page again: the searchers may now want a different kind of page, and merging or a new page may serve them better.

How AutoPSEO keeps its own articles fresh

For the articles its content engine manages, AutoPSEO runs this playbook every week without being asked (maintenance):

It compares each live article's last 28 days with the 28 before, with all language versions of a page counted together.
It queues a refresh when clicks fell by 40% or more from at least 20, largest loss first. The task carries its reason, for example that clicks fell from 120 to 64 and the average position slipped from 4.2 to 7.9.
It queues an optimisation when an article shows at positions 8 to 20 with at least 30 impressions but is clicked less than 60% as often as that position usually is. That task sharpens the title, the meta description and the direct answer.
It leaves young pages alone. Articles published or changed in the last 45 days are skipped, since search needs time to settle, and so are articles that already have a task open.
It limits itself to three refreshes and three optimisations per site per week.

Whoever takes the task, the platform's writer or your own AI through MCP, reads the article first and declines the task if its numbers have recovered or the article changed since the task was queued. When your site receives articles through the webhook, AutoPSEO reads the article again from your site before changing it, so an edit you made there is the version that gets updated. The new revision waits for review if your site requires it, then goes to your site as an update. When the platform's writer does the work, a refresh counts against your plan's monthly article allowance and an optimisation against a separate one; your own AI's work costs no allowance.

When two articles turn out to answer the same searches, they can be merged: one is taken down and your site is told to answer its old address with a 301 to the other.

For pages the engine does not manage, the Content Decay report shows your top pages month by month with a decay status, and Query Decay does the same for searches. Without an account, the free Content Decay Detector compares two exports.