Content and On-Page SEO skill 11 of 13

Content Refresh and Decay Recovery SKILL.md

The Content Refresh skill makes Claude, Codex or another AI agent find pages that are losing organic traffic, work out why each one declined, and plan a refresh that fixes the cause. It separates outdated facts, intent shifts, stronger competitors, cannibalisation, lost links, technical faults and seasonality, then updates the substance of the page, dates the change truthfully and measures recovery against a baseline.

content-refresh/SKILL.md, version 1.0.0, 1,167 words.

Pages lose traffic over time. Facts go out of date, searchers start wanting a different format, competitors publish better pages, links disappear and new pages on your own site start competing. Refreshing an existing page that already has history and links is often faster and cheaper than publishing a new one.

This skill finds decaying pages, works out why each one declined and plans a refresh that fixes the cause.

Operating principles

  1. Diagnose before you rewrite. A seasonal dip or a technical fault won't be fixed by new paragraphs.
  2. Refresh the substance, not the date. Change facts, examples, sections and evidence; then update the date.
  3. Keep the URL. A refreshed page keeps its links and history on the same address.
  4. Start where the upside is biggest. Pages with the most lost clicks and the most business value come first.
  5. Measure against a baseline, with enough time for re-crawling and re-ranking.

When to use, and when not to

Use it for blogs and resource centres with pages older than a year, after traffic declines, on a regular quarterly schedule, and before publishing new pages on topics you already cover.

Don't use it when two pages split the same query (keyword-cannibalisation), when pages should go (content-pruning) or when the cause is technical (Technical SEO skills).

Inputs to ask for, in one message

  1. Search Console data by page and by page plus query, comparing the last 3 months with the same period a year earlier.
  2. Analytics conversions by landing page.
  3. Publish and last-updated dates for each page.
  4. Backlink history for important pages, if available.
  5. Any recent technical changes or migrations.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as content-refresh/SKILL.md.

---
name: content-refresh
description: "Find pages losing organic traffic, diagnose why (outdated information, intent shift, new competitors, lost links, cannibalisation, technical or seasonal causes), and refresh them with real updates: current facts, new sections, better answers, evidence, internal links and honest dated changes, then measure recovery against a baseline. Use whenever someone mentions content decay, declining blog traffic, updating old posts, refreshing content, pages that used to rank, historical optimisation, or which articles to update first."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/content-seo/content-refresh/
  category: marketing
  subcategory: content-seo
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Content Refresh and Decay Recovery

Pages lose traffic over time. Facts go out of date, searchers start wanting a different format, competitors publish better pages, links disappear and new pages on your own site start competing. Refreshing an existing page that already has history and links is often faster and cheaper than publishing a new one.

This skill finds decaying pages, works out why each one declined and plans a refresh that fixes the cause.

## Operating principles
1. **Diagnose before you rewrite.** A seasonal dip or a technical fault won't be fixed by new paragraphs.
2. **Refresh the substance, not the date.** Change facts, examples, sections and evidence; then update the date.
3. **Keep the URL.** A refreshed page keeps its links and history on the same address.
4. **Start where the upside is biggest.** Pages with the most lost clicks and the most business value come first.
5. **Measure against a baseline,** with enough time for re-crawling and re-ranking.

## When to use, and when not to
Use it for blogs and resource centres with pages older than a year, after traffic declines, on a regular quarterly schedule, and before publishing new pages on topics you already cover.

Don't use it when two pages split the same query (`keyword-cannibalisation`), when pages should go (`content-pruning`) or when the cause is technical (Technical SEO skills).

## Inputs to ask for, in one message
1. Search Console data by page and by page plus query, comparing the last 3 months with the same period a year earlier.
2. Analytics conversions by landing page.
3. Publish and last-updated dates for each page.
4. Backlink history for important pages, if available.
5. Any recent technical changes or migrations.

## Workflow

### Step 1. Find decaying pages
List pages with a meaningful drop in clicks year on year, and with steady or falling impressions. Exclude pages whose decline matches site-wide seasonality.

### Step 2. Diagnose each page
| Cause | Signs | Fix |
|---|---|---|
| Outdated information | Old prices, years, screenshots, tools or rules | Update facts, examples and screenshots |
| Intent shift | Results now show a different format or angle | Rework the page to the new format (`search-intent-serp-analysis`) |
| Stronger competitors | New pages cover more, with better evidence | Add depth, original data, expert input |
| Lost rankings for some queries | Query-level drops in Search Console | Cover those subtopics properly |
| Cannibalisation | Another of your pages now ranks for the same queries | Merge or separate (`keyword-cannibalisation`) |
| Lost links | Referring domains fell | Reclaim links, earn new ones |
| Technical | Indexing, canonical or speed changes | Fix first, then judge content |
| SERP features | AI Overview or other features took clicks, positions stable | Aim for citation, improve CTR, add what summaries can't |

### Step 3. Plan the refresh
For each page: the cause, the sections to add, change or cut, facts to update with sources, evidence to add, internal links to add, and a new title or meta if CTR is weak.

### Step 4. Refresh
Rewrite outdated sections, add missing subtopics and questions, replace generic examples with real ones, update screenshots with capture dates, and remove anything no longer true. Keep what still ranks.

### Step 5. Date the update truthfully
Update the "last updated" date and `dateModified` only when the content changed meaningfully. A short "What changed" note helps readers on time-sensitive topics.

### Step 6. Re-promote
Add links from newer related pages, update the sitemap `lastmod` and request indexing for the most important pages.

### Step 7. Measure
Compare clicks, impressions and position for the page's queries 6 to 12 weeks after the refresh against the period before.

## Refresh schedule
| Content type | Review cycle |
|---|---|
| Prices, rates, rules, laws | When they change, and at least every 3 to 6 months |
| Tool and software guides | Every 6 months |
| Evergreen how-to guides | Every 12 months |
| Opinion and news | Rarely; link to newer coverage instead |

## Worked example
An HR software blog had 60 posts losing more than 30% of clicks year on year. Diagnosis split them into 24 with outdated rules and screenshots, 14 where results had shifted to templates, 9 cannibalised by newer posts, 8 with stable rankings but lower CTR after AI Overviews appeared, and 5 hit by a canonical bug. The canonical bug was fixed first; the outdated posts were refreshed with current rules and new screenshots; the template-intent posts gained downloadable templates; the cannibalised pairs were merged. After ten weeks, clicks to the refreshed group were back above the previous year's level (Search Console).

## Output format
```
# Content refresh plan: <site>, <date>
## Decaying pages
| URL | Clicks now | Clicks a year ago | Change | Cause | Action | Priority |
## Refresh briefs (per page: sections to add, change, cut; facts to update; evidence; links)
## Measurement plan and dates
```

## Refresh depth: light, medium or full
| Depth | When | What changes | Effort |
|---|---|---|---|
| Light | Facts and dates out of date, structure still fine | Figures, screenshots, links, date note | Under an hour |
| Medium | Missing subtopics, weaker evidence than competitors | New sections, examples, data, internal links, title | Half a day |
| Full | Intent shifted or the page no longer serves its query | New format and structure on the same URL | One to three days |

## Refresh brief template
```
Page: <URL>
Cause of decline: <outdated facts / intent shift / competitor depth / cannibalisation / CTR loss>
Depth: <light / medium / full>
Keep: <sections and queries that still perform>
Change: <sections to update, add or remove>
New evidence: <data, screenshots, expert input>
Title and description: <new options>
Internal links to add: <pages and anchors>
Re-check date: <6 to 12 weeks>
```
A short brief keeps refreshes focused on the diagnosed cause instead of rewriting pages that only needed new figures.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Page decays every year in the same months | Seasonal: refresh before the season, not during the dip |
| Clicks fell but rankings and impressions held | Likely CTR loss to SERP features; improve title and add what summaries can't give |
| Several pages decay at once after a release | Suspect a technical cause first |
| Refreshed page didn't recover | Re-check intent, competitors and cannibalisation; consider merging |
| Page has a fixed publication context (news, event) | Don't rewrite history; link to newer coverage instead |

## What to keep during a refresh
- The URL.
- Sections that still rank for valuable queries (check Search Console by query).
- Accurate content that earned links.
- Structured data that still matches the page.

## Handoffs to related skills
- Intent shifts: `search-intent-serp-analysis`
- Rewriting: `seo-content-writing`
- Final checks: `on-page-seo`, `title-tags-meta-descriptions`
- Competing pages: `keyword-cannibalisation`
- Pages with no future: `content-pruning`
- Technical causes: the Technical SEO `crawlability-indexation-audit` skill

## Quality bar: what an excellent plan includes
- A diagnosed cause for every page.
- Refresh depth chosen per page, with effort.
- Substantive changes, with dates updated only when content changed.
- A baseline and a re-check date.

## Common mistakes
- Changing the date without changing the content.
- Rewriting the whole page and losing the sections that ranked.
- Moving refreshed content to a new URL.
- Refreshing seasonal pages in the off season and calling it a recovery.
- Ignoring the cause and adding words.

## Questions to ask before you recommend a refresh
- Which pages drive conversions, not only traffic?
- What changed in the business or market since the page was written?
- Who can supply up-to-date facts and expert input?

## Self-check before you answer
- Did I diagnose a cause for each page before planning changes?
- Are seasonal and technical causes ruled out?
- Are updates substantive and dated truthfully?
- Is there a baseline and a measurement date?

## Official documentation
- Creating helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Influencing bylines and dates in Google Search: https://developers.google.com/search/docs/appearance/publication-dates
- Search Console Performance report: https://support.google.com/webmasters/answer/7576553
- Google Search Status Dashboard: https://status.search.google.com/

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/content-seo/content-refresh/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Find decaying pages

List pages with a meaningful drop in clicks year on year, and with steady or falling impressions. Exclude pages whose decline matches site-wide seasonality.

Step 2. Diagnose each page

CauseSignsFix
Outdated informationOld prices, years, screenshots, tools or rulesUpdate facts, examples and screenshots
Intent shiftResults now show a different format or angleRework the page to the new format (search-intent-serp-analysis)
Stronger competitorsNew pages cover more, with better evidenceAdd depth, original data, expert input
Lost rankings for some queriesQuery-level drops in Search ConsoleCover those subtopics properly
CannibalisationAnother of your pages now ranks for the same queriesMerge or separate (keyword-cannibalisation)
Lost linksReferring domains fellReclaim links, earn new ones
TechnicalIndexing, canonical or speed changesFix first, then judge content
SERP featuresAI Overview or other features took clicks, positions stableAim for citation, improve CTR, add what summaries can't

Step 3. Plan the refresh

For each page: the cause, the sections to add, change or cut, facts to update with sources, evidence to add, internal links to add, and a new title or meta if CTR is weak.

Step 4. Refresh

Rewrite outdated sections, add missing subtopics and questions, replace generic examples with real ones, update screenshots with capture dates, and remove anything no longer true. Keep what still ranks.

Step 5. Date the update truthfully

Update the "last updated" date and dateModified only when the content changed meaningfully. A short "What changed" note helps readers on time-sensitive topics.

Step 6. Re-promote

Add links from newer related pages, update the sitemap lastmod and request indexing for the most important pages.

Step 7. Measure

Compare clicks, impressions and position for the page's queries 6 to 12 weeks after the refresh against the period before.

Refresh schedule

Content typeReview cycle
Prices, rates, rules, lawsWhen they change, and at least every 3 to 6 months
Tool and software guidesEvery 6 months
Evergreen how-to guidesEvery 12 months
Opinion and newsRarely; link to newer coverage instead

Worked example

An HR software blog had 60 posts losing more than 30% of clicks year on year. Diagnosis split them into 24 with outdated rules and screenshots, 14 where results had shifted to templates, 9 cannibalised by newer posts, 8 with stable rankings but lower CTR after AI Overviews appeared, and 5 hit by a canonical bug. The canonical bug was fixed first; the outdated posts were refreshed with current rules and new screenshots; the template-intent posts gained downloadable templates; the cannibalised pairs were merged. After ten weeks, clicks to the refreshed group were back above the previous year's level (Search Console).

Output format

# Content refresh plan: <site>, <date>
## Decaying pages
| URL | Clicks now | Clicks a year ago | Change | Cause | Action | Priority |
## Refresh briefs (per page: sections to add, change, cut; facts to update; evidence; links)
## Measurement plan and dates

Refresh depth: light, medium or full

DepthWhenWhat changesEffort
LightFacts and dates out of date, structure still fineFigures, screenshots, links, date noteUnder an hour
MediumMissing subtopics, weaker evidence than competitorsNew sections, examples, data, internal links, titleHalf a day
FullIntent shifted or the page no longer serves its queryNew format and structure on the same URLOne to three days

Refresh brief template

Page: <URL>
Cause of decline: <outdated facts / intent shift / competitor depth / cannibalisation / CTR loss>
Depth: <light / medium / full>
Keep: <sections and queries that still perform>
Change: <sections to update, add or remove>
New evidence: <data, screenshots, expert input>
Title and description: <new options>
Internal links to add: <pages and anchors>
Re-check date: <6 to 12 weeks>

A short brief keeps refreshes focused on the diagnosed cause instead of rewriting pages that only needed new figures.

Edge cases and judgement calls

SituationWhat to do
Page decays every year in the same monthsSeasonal: refresh before the season, not during the dip
Clicks fell but rankings and impressions heldLikely CTR loss to SERP features; improve title and add what summaries can't give
Several pages decay at once after a releaseSuspect a technical cause first
Refreshed page didn't recoverRe-check intent, competitors and cannibalisation; consider merging
Page has a fixed publication context (news, event)Don't rewrite history; link to newer coverage instead

What to keep during a refresh

  • The URL.
  • Sections that still rank for valuable queries (check Search Console by query).
  • Accurate content that earned links.
  • Structured data that still matches the page.
  • Intent shifts: search-intent-serp-analysis
  • Rewriting: seo-content-writing
  • Final checks: on-page-seo, title-tags-meta-descriptions
  • Competing pages: keyword-cannibalisation
  • Pages with no future: content-pruning
  • Technical causes: the Technical SEO crawlability-indexation-audit skill

Quality bar: what an excellent plan includes

  • A diagnosed cause for every page.
  • Refresh depth chosen per page, with effort.
  • Substantive changes, with dates updated only when content changed.
  • A baseline and a re-check date.

Common mistakes

  • Changing the date without changing the content.
  • Rewriting the whole page and losing the sections that ranked.
  • Moving refreshed content to a new URL.
  • Refreshing seasonal pages in the off season and calling it a recovery.
  • Ignoring the cause and adding words.

Questions to ask before you recommend a refresh

  • Which pages drive conversions, not only traffic?
  • What changed in the business or market since the page was written?
  • Who can supply up-to-date facts and expert input?

Self-check before you answer

  • Did I diagnose a cause for each page before planning changes?
  • Are seasonal and technical causes ruled out?
  • Are updates substantive and dated truthfully?
  • Is there a baseline and a measurement date?

Official documentation

When to use this skill, and when not to

Use it for blogs and resource centres with pages older than a year, after organic traffic declines, on a regular quarterly schedule, and before publishing a new page on a topic you already cover. Refreshing a page with history and links is often faster than starting again.

Don’t use it when two pages compete (use Keyword Cannibalisation), when a page should go (use Content Pruning) or when the cause is technical (use the Technical SEO Audit).

Example prompts

  • “Which posts lost the most clicks year on year, and why?”
  • “Refresh our 2023 guide to payroll deadlines for this tax year.”
  • “Plan this quarter’s refreshes for our top 30 decaying pages.”
  • “Our rankings held but clicks fell after AI Overviews appeared. What can we change?”
  • “Build a review schedule for our help centre and guides.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Content refresh plan: example.com/blog, 10 October 2026

## Decaying pages (extract)
| URL | Clicks now | A year ago | Change | Cause | Action |
| /blog/right-to-work-checks/ | 1,120 | 2,940 | -62% | Outdated rules and screenshots | Update rules, new screenshots |
| /blog/onboarding-template/ | 800 | 1,700 | -53% | Intent shift to templates | Add downloadable template |
| /blog/hr-software-cost/ | 450 | 900 | -50% | Cannibalised by newer post | Merge (keyword-cannibalisation) |

Each page is diagnosed before anything is rewritten, so seasonal and technical drops aren’t mistaken for content problems.

What the agent needs from you

The skill asks for Search Console data by page and by page plus query, comparing the last three months with the same period a year earlier, analytics conversions by landing page, publish and last-updated dates, backlink history for important pages, and any recent technical changes or migrations.

How this skill hands off to related skills

A refresh often needs help from other skills. Intent shifts are checked with Search Intent and SERP Analysis, rewrites follow SEO Content Writing, pages are re-checked with On-Page SEO Optimisation and titles with Title Tags and Meta Descriptions. Competing pages go to Keyword Cannibalisation, and technical causes to the Crawlability and Indexation Audit.

How to run the Content Refresh skill step by step

  1. Install the skill as content-refresh/SKILL.md.
  2. Export Search Console data by page and by page plus query, comparing the last three months with the same period a year earlier.
  3. Add analytics conversions by landing page and publish and update dates.
  4. Note recent changes: releases, migrations, template edits and backlink losses.
  5. Review the diagnosis per page and the refresh depth chosen: light, medium or full.
  6. Refresh, re-promote with internal links and measure after six to twelve weeks.

Situations this skill handles

Pages decay for different reasons. The skill diagnoses each one before anything is rewritten:

SituationWhat the skill does
Facts, prices or screenshots out of dateLight refresh: updates figures and screenshots with capture dates
Results now show a different formatFull refresh on the same URL, rebuilt for the new intent
Competitors added depth and dataMedium refresh: new sections, original evidence and expert input
Same queries now shared with a newer postHands off to the cannibalisation skill to merge
Rankings held but clicks fellImproves the title and adds what AI summaries can’t give
Same dip every yearTreats it as seasonal and refreshes before the season

What makes this skill different

Most refresh advice says “update old posts” and changes the date. This skill diagnoses why each page declined first, then chooses a refresh depth that fixes the cause, keeps the URL and the sections that still rank, and updates the date only when the substance has changed.

It also rules out causes a rewrite can’t fix: technical faults, seasonality and pages competing with each other, so effort goes where it can recover traffic.

Practical tips from real projects

  • Keep the URL. A refreshed page keeps its links and history.
  • Keep what still ranks. Check queries by section in Search Console before cutting anything.
  • Add a short “what changed” note on time-sensitive topics.
  • Re-promote with links from newer related pages.

A worked example: an HR software blog had 60 posts losing more than 30% of clicks year on year. Diagnosis split them into 24 with outdated rules and screenshots, 14 where results had shifted to templates, 9 overlapping newer posts, 8 with stable rankings but lower click-through after AI Overviews appeared, and 5 hit by a canonical bug. The bug was fixed first, outdated posts were updated, templates were added where intent had shifted, and overlapping pairs were merged. After ten weeks, clicks to the group were back above the previous year.

Refreshing is also the most reliable way to keep AI answers accurate. Engines that cite your pages repeat what those pages say, so outdated prices or rules on an old post can spread into AI answers. A regular refresh schedule (prices and rules when they change, software guides every six months, evergreen guides yearly) keeps both search results and AI answers current.

Choose the refresh depth by the cause, not by habit. A light refresh fixes facts in under an hour. A medium refresh adds missing sections, evidence and links in half a day. A full refresh rebuilds the page for a new intent on the same URL and can take a few days. The skill estimates effort for each page, so a quarter’s refresh plan fits the time you actually have.

Keep a refresh log with the date, depth and reason for each page. It shows leadership what the work recovered and stops the same page being rewritten twice in a year.

Frequently asked questions

A steady fall in a page’s organic traffic over time, usually because information went out of date, searchers began wanting something different, competitors improved or other pages on your site started competing.

Changing the date without changing the content doesn’t help readers and can mislead them. The skill updates dates only after meaningful changes to the substance of the page.

No. Keep the same URL so the page keeps its links and history. Changing it means redirects and a fresh start.

It depends on the topic: pages with prices, rates or rules when they change, software guides about every six months, evergreen guides once a year.

Usually six to twelve weeks, once Google has re-crawled the page and rankings have settled. The skill sets a baseline and a re-check date for each page.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.