Content SEO
Content Decay: When to Update, Rewrite, Merge, Remove or Leave a Page
A page that slowly loses clicks isn't always decaying, and a new date rarely fixes it. Here's how to confirm the decline, rule out other causes, and decide whether to update, rewrite, merge or leave the page alone.
On this page
- What content decay is, and what it isn't
- Step 1: confirm the decline
- Step 2: rule out causes that only look like decay
- Step 3: leave, update, rewrite, merge or remove
- Step 4: change the date only when the page changed
- Step 5: measure the result
- How DeepSpider.ai fits in
- Frequently asked questions
- The short version
- Sources
A cycling site has a buying guide called "Best gravel bikes 2024". It brought steady search traffic for two years, but its Search Console line has sloped down for twelve months. Someone suggests the quick fix: change "2024" to "2026", set the date to today and move on.
That skips the real question: why is the page losing visibility? Outdated models, a newer page on the same site chasing the same searches, or results that now answer the question directly each need a different response, and a new date fixes none of them.
In short
Content decay is a slow loss of search visibility, and age alone doesn't cause it. Confirm the decline, rule out seasonality, search result changes and your own technical slips, then update, rewrite, merge, remove or leave the page. Change the date only when the content really changed.
What content decay is, and what it isn't
Ahrefs' Louise Linehan defines content decay as "the gradual decline in a page's organic traffic and rankings over time". A cliff on one day usually has another cause, though a slow slope doesn't prove decay either. Positions move, Google's debugging guide notes, because the web itself keeps changing.
Age isn't the problem. In a 2025 Ahrefs study of 1.3 million random US keywords, Patrick Stox found that 72.9% of pages in Google's top 10 were more than three years old, counted from when Ahrefs first saw the URL. On Google's Search Off the Record podcast, John Mueller noted that reference material is "kind of by definition old" yet still useful.
Step 1: confirm the decline
Start in Search Console's Performance report. Google's debugging guide suggests a routine:
- Choose Last 16 months to see whether the drop happens every year.
- Compare the last three months with the previous period or the previous year.
- On the Pages tab, sort by Clicks Difference to find the pages that lost most.
- Check whether the whole site, one section or one page is affected.
Then open a slipping page's Queries tab with the same comparison. If the main query lost positions, look at what now ranks above you. If impressions moved to other queries, the search itself may have changed.
| Pattern | Likely explanation | Check next |
|---|---|---|
| Clicks and impressions both slide over months | Lost positions, less demand or stronger pages | Google Trends, the pages now above you |
| Impressions steady, clicks falling | The page shows but is chosen less | Your title and snippet, rich results, AI answers |
| Sharp drop on one date | A site change or a ranking update | Your change log, Page indexing, Manual actions, Security issues, ranking updates |
When impressions hold and clicks fall, Google points to your title and snippet or a better rich result elsewhere; Linehan calls this a SERP feature problem rather than decay. Search Console's Generative AI performance report shows AI Overview and AI Mode impressions, but no clicks. Bing makes the same point for its own results, Copilot included: "A decline in clicks does not always indicate a loss of visibility."
Step 2: rule out causes that only look like decay
Linehan separates two cases: traffic that fell while the page stayed the same is classic decay, while a fall right after an edit suggests you broke something, so compare the versions. Check technical changes too: a noindex, a canonical pointing elsewhere, a new redirect or robots.txt rule, or internal links lost as newer posts pushed the page deeper (how deep a page sits is worth checking). A gentle slope doesn't rule these out: Google notes that a misplaced noindex takes effect only as pages are recrawled.
Then look at the results. Glenn Gabe describes intent shifts, where Google "decides to show different types of content for the queries you once ranked for", and notes that site owners have little control over them. If the results now favour comparison tables and you have an essay, a new date won't help.
If the drop lines up with a ranking update, Google says "there might not be anything fundamentally wrong with your content."
Step 3: leave, update, rewrite, merge or remove
Leave it
For small position drops, Google is direct: "we recommend avoiding making radical changes if your page is already performing well." Keep pages with archival value, such as announcements, case studies and release notes.
When to leave it alone
The drop is seasonal, demand is falling, or the page is still correct and still matches what the results show. Note it, check again next quarter and move on.
Update or rewrite
An update fixes what has aged: facts, prices, models, steps, screenshots and links that now redirect. Check that the title and introduction still match the page's current queries. Adam Riemer warns that material which doesn't fit an existing section can take the page off-topic; a separate, linked page may serve readers better.
A rewrite is for when the search moved and the page didn't, or the page was weak from the start. Note the format of today's top results and the questions they answer first, keep the sections that still earn queries and rebuild the rest. If you use AI for this, our guide to AI-generated content and AI slop covers how to avoid publishing unchecked text.
Merge or remove
Merge only when two pages serve the same need. As Google's John Mueller put it in remarks quoted by Search Engine Journal, "pages aren't duplicates just because they happen to appear in the same search results page." If they do overlap, keep the URL with more clicks and links, move the best of the other page into it and 301-redirect the other URL there. Link straight to the final URL in one consistent trailing-slash form, then add links from related posts, as our guide to pages with too few internal links explains.
To remove a page with nothing worth keeping, return a 404 or 410 (Bing's guidelines ask for a 404). If a related page replaces it, redirect there, but not to the homepage, which Linehan says passes little value. Noindex suits pages people need but search doesn't, and she adds that "Noindex is reversible if you change your mind; deletion is not."
Step 4: change the date only when the page changed
Google lists this among its warning signs: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" On the same podcast episode, Mueller called pages "updated for 2024" that still carry "the same list of fax machines as you had ten years ago" misleading. Yoast says it removed its current month and year title variables partly to stop fake refreshes. Lily Ray counts artificial refreshing among the most common patterns she has seen on sites hit by algorithm updates, an observation rather than a measured ranking effect.
The tactic survives because it has seemed to work. In a small 2015 test written up on the Moz blog, Anthony D. Nelson changed only the dates of 16 posts on one blog; organic visits in the next four weeks were 66% higher, and the lift lasted about two months. He leaned towards freshness but called it a small test, not a trick for sustained growth, and it predates Google's current guidance.
| Change | New "Last updated" date | Sitemap lastmod |
|---|---|---|
| Replaced outdated models, prices and steps | Yes | Yes |
| Merged another guide into this page | Yes, on the surviving page | Yes |
| Changed "2024" to "2026" in the title only | No | No |
| New copyright year in the footer | No | No |
When you change the date, change it everywhere. Google's byline guidance asks for a labelled date such as "Last updated" that matches the structured date, and its sitemap guidance says lastmod should reflect the last significant update. Bing's guidelines also ask for accurate lastmod values.
For a meaningful addition that doesn't warrant a new post, Google's Search Central blog keeps the original date and adds a dated note, as Lizzi Sassman described on the podcast.
Step 5: measure the result
Add a Search Console annotation on the day you change the page, then wait. Google suggests a few weeks before analysing again, with no guarantee of an effect. Compare the same queries before and after, alongside the page total. Riemer suggests leaving a couple of comparable pages untouched as a control group for a few months.
How DeepSpider.ai fits in
DeepSpider doesn't chart Search Console trends or compare periods. Its Search Console data is one snapshot: the last 90 days from a Google sync, or your export's period from an upload. Spot the decline in Search Console, then use DeepSpider to check the causes an audit can see.
Pages with impressions but no clicks lists indexable audited pages with at least 100 impressions, no clicks and an average position of 10 or better. These are DeepSpider's review thresholds, not Google's rules, so pages still getting a few clicks won't appear. Its How to fix it guidance asks you to search the main queries first, since an AI Overview or another result may already answer them, and otherwise to rewrite the title and description. Uploaded interface exports stop at 1,000 rows, so on larger sites pages without clicks are often missing; the Google sync reads up to 200,000 page rows.
| Step | Report or check | What it can't tell you |
|---|---|---|
| Your own changes | Compare Audits → Important changes | Traffic, or anything before your oldest saved audit |
| Technical slips | Non-indexable pages shown in Google | Whether the page changed during the period |
| Lost links | Few internal links to this page, Orphan page candidates, High crawl/click depth | Why the links went |
| Merging | Queries where several of your pages compete, Near-duplicate main content | Whether the intent is the same |
| After a merge | Internal links to redirects | Whether the target is the right page |
| Dates | Content freshness signals, Schema date inconsistencies, Invalid or suspicious lastmod | Whether a date matches a real change |
| Real updates | Compare Audits → Content changes | What changed; it measures length |
Search Console reports sit outside Website Health Score, while audit checks such as Internal links to redirects are Warnings that count towards it.
DeepSpider can't judge whether content is accurate, current or matches search intent, and it can't detect a date-only update. Invalid or suspicious lastmod flags malformed or future dates, but not a sitemap that stamps today's date on every URL. Content freshness signals lists each page's declared dates for you to compare.
Frequently asked questions
How often should I update old content?
There's no fixed rule. Update when the facts, products or searches change. A fixed schedule invites cosmetic edits.
Should I delete old posts so my site looks fresher?
Not because of their age. Google's helpful content guidance asks whether you are "removing a lot of older content primarily because you believe it will help your search rankings" and answers "No, it won't". Mueller called content decay "more of a strategic thing" than "a direct SEO factor": what your site wants to be known for, whether that matches what people look for, and whether the information is still correct.
Should I change a URL that contains a year?
Usually not. Keep the URL and update the title and content: a new URL needs a 301 redirect, updated internal links and time to settle, and Bing's guidelines advise against unnecessary URL changes. Leave years out of new slugs for pages you plan to keep current.
Do AI answers prefer recently updated pages?
The evidence conflicts. Ryan Law's 2025 Ahrefs study of about 17 million citations found that AI assistants cited somewhat newer URLs than Google's organic results, but AI Overviews didn't. A 2025 Seer Interactive study of log files and citation data found AI Overviews citing mostly recent content. Both are correlations, so neither shows that a new date earns citations.
The short version
A slow loss of clicks is a reason to investigate. Find the cause, then update, rewrite, merge, remove or leave the page, and change the date only when the page substantially changed.
Sources
- Google Search Central: Debugging drops in Google Search traffic
- Google Search Central: Creating helpful, reliable, people-first content
- Google Search Central: Influence your byline dates in Google Search
- Google Search Central: Build and submit a sitemap
- Google Search Console Help: Generative AI performance report (Search)
- Google Search Off the Record (John Mueller, Lizzi Sassman): Let's talk content decay
- Microsoft Bing: Bing Webmaster Guidelines
- Ahrefs (Louise Linehan): What is content decay? (And how to fix it before it tanks your traffic)
- Ahrefs (Patrick Stox): How long does it take to rank in Google? And how old are top ranking pages?
- Ahrefs (Ryan Law): New study: AI assistants prefer to cite "fresher" content (17 million citations analyzed)
- Seer Interactive (Sonny Vasquez): Study: AI brand visibility and content recency
- G-Squared Interactive (Glenn Gabe): Google's broad core updates and the difference between relevancy adjustments, intent shifts, and overall site quality problems
- Search Engine Journal (Roger Montti): Google answers SEO question about keyword cannibalization
- Search Engine Journal (Adam Riemer): Ask an SEO: Is it better to refresh content or create new pages?
- Lily Ray: Your GEO strategy might be destroying your SEO
- Yoast (Edwin Toonen): Don't relabel your old content as new; it's a lousy SEO tactic
- Moz (Anthony D. Nelson): Case study: can you fake blog post freshness?