Content Decay Recovery Playbook: From Detection to Shipped Refresh

Calculators diagnose. Playbooks ship.

A decay score without a queue is anxiety with decimals. You learn eighteen pages are declining. You still do not know which one pays rent. The content decay recovery playbook bridges score to shipped refresh: one URL at a time, evidence attached, human review before publish.

Recover organic traffic without publishing more states the doctrine. This article is the operations manual: detect, diagnose, draft, relink, measure. Automated detections from connected Search Console reduce manual export work. You still own judgment on keeper URLs and information gain.

Step 1: Detect decay in Search Console

Open GSC Performance Pages for twenty-eight days vs prior period. Sort by click delta ascending. Flag URLs where impressions hold or rise while clicks fall. That split often means CTR decay or SERP competition, not index loss. Flag URLs where clicks and position both slide on a persistent query cluster. That is classic content decay.

• Ignore brand navigational queries when judging editorial decay.
• Require minimum impression volume so noise does not rank.
• Compare engagement in GA4 on the same URL before you prescribe rewrite depth.
• Log detection date. Decay is a trend, not a single red arrow.

GSC low CTR recovery workflow handles the CTR-only branch. This playbook focuses on full refresh when the answer got relatively worse. Content Refresh Tools: Turn Traffic Decay Into a Shippable Queue compares software that should accelerate this playbook, not replace measurement.

Step 2: Diagnose why the answer lost

Use analyst answers with query movement and overlap when Confidence is medium. Use them for stakeholder questions. Do not skip manual SERP review on money pages.

Step 3: Scope the refresh order

A refresh order names URL, primary query cluster, diagnosis, change type, owner, and success signal. ICEE from Mission Brief Method ranks it against cannibalization and striking-distance work. High Impact decay on a commercial page beats low Impact net-new blog ideas most weeks.

Website growth backlog generator tool ranks decay against cannibalization and CTR gaps when you lack connected data. Mission Brief replaces manual scoring when GSC sync is live.

Step 4: Draft through Content Operations

Route deep refreshes to Content Operations. Input keyword cluster, keeper URL, diagnosis notes, and Knowledge Base context. Output is a draft with metadata, internal links from URL Library, FAQ suggestions, and QA flags. Human review is mandatory. Learn Domains does not auto-publish.

Ground drafts in information gain: new operator examples, updated comparisons, corrected misconceptions. QA rejects slop, fake stats, and keyword stuffing. A refresh that reads like generic AI filler often loses again within a quarter.

GSC data to content tasks explains how to turn query evidence into writer-ready briefs when your bottleneck is fulfillment.

Step 5: Relink and consolidate

Decay recovery fails when sister posts keep competing or orphaning the refreshed URL. Audit internal links pointing to and from the keeper. Point high-traffic hubs at the refreshed page with descriptive anchors. Merge or redirect true duplicates per keyword cannibalization workflow.

1. •List inbound internal links to the refreshed URL.
2. •List outbound links that should cite deeper sections added in refresh.
3. •Fix cannibal pairs identified by Opportunity Engine.
4. •Update XML sitemap and submit URL in GSC after publish.

Step 6: Measure recovery without fantasy metrics

Success is movement on target query cluster clicks and engaged sessions, not a promised position. Re-sync GSC after two to four weeks. Compare the refreshed URL to its own baseline. Note seasonality before you declare victory or failure.

Asset Yield ties revenue pages to growth orders when Stripe connects. Decay on money URLs deserves earlier refresh priority because commercial Impact weights higher in ICEE.

Common decay recovery mistakes

Mistake one: cosmetic refresh. Changing the publish date without information gain trains crawlers to ignore you. Mistake two: net-new duplicate. Publishing a second URL for the same intent splits equity and triggers cannibalization. Mistake three: ignoring internal links. A brilliant refresh hidden behind orphan architecture still loses. Mistake four: measuring too early. Forty-eight hours after publish proves nothing except impatience.

Mistake five: unfocused AI rewrites. Generic AI filler often ranks worse than the original decayed page because it adds length without adding operator insight. Content Operations QA exists to catch that pattern before human review wastes time.

• Name one primary query cluster per refresh cycle.
• Document what information gain means for that cluster specifically.
• Schedule relink pass in the same sprint as publish.
• Set calendar reminder for fourteen-day GSC check, not twenty-four hours.

Weekly decay standup rhythm

Monday: pull decay detections, pick one keeper URL. Tuesday to Wednesday: draft or light-touch edit. Thursday: relink pass. Friday: log signal movement. If decay count grows faster than completions for two months, cut net-new publishing until refresh debt shrinks.

Organic traffic dropping playbook covers site-level drops that are not single-URL decay. GA4 GSC combined workflow adds engagement context when clicks and sessions diverge.