Sign in Start free

Refresh Decaying Content

Traffic decay has several distinct causes and they need opposite responses, but the standard reaction - update the date, add a few hundred words, resubmit - is applied to all of them. A page losing clicks because a SERP feature appeared above it cannot be fixed by editing the page. Diagnosis first, editing second, and for a meaningful share of decaying pages the correct action is consolidation or removal.

CATEGORY
Content production
FORMAT
refresh-decaying-content.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when pages that used to perform are losing traffic and you need to decide what to update and what to leave.

The skill file

refresh-decaying-content.md
---
name: refresh-decaying-content
description: Use when pages that used to perform are losing traffic and you need to decide what to update and what to leave.
---

# Refresh Decaying Content

Traffic decay has several distinct causes and they need opposite responses, but the standard reaction - update the date, add a few hundred words, resubmit - is applied to all of them. A page losing clicks because a SERP feature appeared above it cannot be fixed by editing the page. Diagnosis first, editing second, and for a meaningful share of decaying pages the correct action is consolidation or removal.

## What you need first

- Search Console data comparing the same period year on year, clicks and impressions separately
- the current SERP for the page's main queries
- a list of your own pages covering overlapping topics

## Method

1. Split impressions from clicks. Impressions steady with clicks falling means the SERP changed above you or your snippet aged; impressions falling means you lost rankings. These need different work.
2. Check whether the queries the page won on have shifted. Pages often keep their rankings on terms that stopped being asked, which no amount of rewriting recovers.
3. Look at what now ranks. If the result type changed - a tool, a video carousel, a forum thread - decide whether you can compete in that format at all before editing the text.
4. For genuine ranking loss, rewrite the section that answers the primary query rather than adding new sections. Additions dilute; most recovered pages get shorter.
5. If two of your pages both rank weakly for the same query, consolidate into the stronger URL and redirect the other. Two half-relevant pages compete with each other more than with anyone else.
6. Update the visible date only when the substance changed. Timestamp changes without content changes teach nothing to crawlers and mislead readers.

## What this produces

A per-page decision - rewrite, consolidate, reformat or leave - with the diagnosis that justified it recorded.

## Where this goes wrong

- Refreshing pages by adding words, which lowers the answer density that earned the ranking in the first place
- Treating seasonal troughs as decay by comparing against last month instead of the same month last year
- Refreshing the pages with the largest traffic loss first when the recoverable ones are usually mid-tail pages sitting at positions 8 to 20

---

From the QuQi skill library - https://www.quqi.io/skills/refresh-decaying-content
Free to download · no account, no email

What you need first

  • Search Console data comparing the same period year on year, clicks and impressions separately
  • the current SERP for the page's main queries
  • a list of your own pages covering overlapping topics

Method

  1. 01 Split impressions from clicks. Impressions steady with clicks falling means the SERP changed above you or your snippet aged; impressions falling means you lost rankings. These need different work.
  2. 02 Check whether the queries the page won on have shifted. Pages often keep their rankings on terms that stopped being asked, which no amount of rewriting recovers.
  3. 03 Look at what now ranks. If the result type changed - a tool, a video carousel, a forum thread - decide whether you can compete in that format at all before editing the text.
  4. 04 For genuine ranking loss, rewrite the section that answers the primary query rather than adding new sections. Additions dilute; most recovered pages get shorter.
  5. 05 If two of your pages both rank weakly for the same query, consolidate into the stronger URL and redirect the other. Two half-relevant pages compete with each other more than with anyone else.
  6. 06 Update the visible date only when the substance changed. Timestamp changes without content changes teach nothing to crawlers and mislead readers.

What this produces

A per-page decision - rewrite, consolidate, reformat or leave - with the diagnosis that justified it recorded.

Where this goes wrong

  • Refreshing pages by adding words, which lowers the answer density that earned the ranking in the first place
  • Treating seasonal troughs as decay by comparing against last month instead of the same month last year
  • Refreshing the pages with the largest traffic loss first when the recoverable ones are usually mid-tail pages sitting at positions 8 to 20

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/refresh-decaying-content/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When should I diagnose the decay rather than update the page and republish?

Before touching the page, every time. Decay has several distinct causes that need opposite responses, and a page losing clicks because a SERP feature appeared above it cannot be fixed by editing the text at all. The standard reaction of adding a few hundred words and bumping the date is applied to every case regardless of which one it is.

What data do I need in hand, and what goes wrong without it?

Search Console figures compared year on year with clicks and impressions kept separate, the current SERP for the page's main queries, and a list of your own overlapping pages. Comparing against last month rather than the same month last year turns an ordinary seasonal trough into a decay finding, and the quarter goes on rewriting pages that were never broken.

What do I end up with, and which part is worth keeping?

A per-page verdict of rewrite, consolidate, reformat or leave, with the diagnosis recorded beside it. The leave decisions are worth as much as the rewrites, since they are what stops the queue growing. The recorded diagnosis is what gets reused: without it, the next person who sees the same drop starts the whole analysis again.

What is the mistake that ruins a refresh?

Refreshing by adding words, which lowers the answer density that earned the ranking in the first place; most genuinely recovered pages come out shorter. The scheduling error costs nearly as much: working the largest traffic losses first, when the recoverable pages are usually mid-tail ones sitting at positions eight to twenty.

More in Content production