Refresh Strategy
Content Decay Playbook: When to Update, Expand, or Sunset
Most pages fade over time. This playbook shows you how to diagnose true content decay in Search Console, choose the smallest effective fix, and measure recovery across the entire cluster.
What content decay is
Content decay is a sustained decline in impressions, clicks, and average position after a stable period. It can be caused by fresher competitors, new SERP layouts, product changes, or your own internal link drift. Decay is not seasonal dips or temporary volatility. Confirm with rolling windows rather than week to week noise.
Use the Search Console performance report to compare 28, 84, and 168 day windows. This smooths out weekly variance and seasonality.
How to confirm decay
Trend signals
- Impressions down for two or more 28 day windows
- CTR down and position slightly worse or flat
- Fewer queries in top 10 for this page
Quality signals
- Outdated screenshots, features, or pricing references
- Missing answer box and weak definitions
- Competitors shipping fresher examples or comparisons
Site signals
- Orphaned or weak internal links from the hub
- Anchor drift where multiple pages use the same anchor
- Duplicate variants like yearly versions without a canonical strategy
| Signal | Green | Yellow | Red |
|---|---|---|---|
| Impressions change vs previous 84 days | Within ±5% | -5 to -15% | < -15% |
| CTR change vs previous 84 days | Within ±5% | -5 to -12% | < -12% |
| Share of queries in top 10 | > 40% | 20 to 40% | < 20% |
Thresholds are working rules. Always check the SERP to verify intent and layout changes. See Google guidance on helpful content.
Update vs Expand vs Sunset
Pick the smallest change that fixes the problem. A clean update is faster than a rewrite. An expansion adds missing depth. A sunset removes duplication and preserves equity with redirects.
| Fix type | Use when | Main actions | Typical effort |
|---|---|---|---|
| Update | Intent unchanged and content out of date | Refresh entities, screenshots, numbers. Add short answer and FAQ | 6 to 12 hours |
| Expand | Page is thin or missing key sections | Add comparisons, steps, tables, visuals. Improve internal links | 12 to 20 hours |
| Sunset | Page duplicates another, or yearly variants collide | Pick winner, merge value, 301 redirect, update hub and sitemap | 10 to 16 hours |
How to run a clean Update
Keep the frame but refresh the substance. Aim for speed without sacrificing accuracy.
Research checklist
- Scan current top results for entities and examples
- Pull the last 12 months of queries for this URL in Search Console
- Identify decayed sections by scroll and time on page in analytics
On-page changes
- Add a short answer block after the H1
- Update screenshots and pricing references
- Refresh tables. Replace vague bullets with exact steps
- Add two to three internal links to relevant BOFU pages
Technical checks
- Validate FAQ or HowTo in the Rich Results Test
- Ensure canonical and breadcrumbs are correct
- Resubmit the page in Search Console
Keep the URL. Preserve age and backlinks. Only change the title if intent or angle truly shifted.
When to Expand with depth
Expand when the page is thin or the SERP expects more depth. Do not bloat. Add the sections that solve the job better than competitors.
Depth adders that work
- Comparison tables with objective criteria
- Process steps with inputs, outputs, and common mistakes
- Role or industry views where intent splits by audience
- Embedded glossary blocks for key entities
What to avoid
- Repeating the intro in multiple ways
- Adding paragraphs without examples or numbers
- Creating a second page for the same job instead of expanding the primary
Confirm depth expectations by reading the current top results and People Also Ask. Google’s starter guide on creating descriptive content is a useful baseline.
When to Sunset and consolidate
Sunset when there is duplicate intent or yearly variants. Do not let multiple URLs compete for the same anchor. Merge, redirect, and repair routing.
Redirect map
- List source URLs, destination, and reason
- Update hub, breadcrumbs, and nav links
- Submit updated sitemap in Search Console
Yearly topics
- Keep one evergreen URL with year in the title, not the slug
- Archive old yearly pages or redirect to evergreen
- Keep a “last updated” stamp near the title
Fix the cluster, not only the page
Decay often spreads because internal links and anchors drift. Repair the whole cluster so gains compound.
Recluster first
Confirm intent splits with a SERP-aligned tool. Recluster head terms and ensure one URL per job before you write. You can export fresh clusters with Keyword Insights.
Anchor governance
- One primary anchor per intent across hubs and children
- Use descriptive anchors like “pricing” or “implementation” rather than generic “learn more”
- Audit anchors quarterly
Routing rules
- Hub links to all children and key BOFU paths
- Children link back to hub and to one or two siblings
- Remove links to sunset pages
QA and publishing checklist
Content QA
- Short answer after H1 covers the core question
- Updated examples, screenshots, and numbers
- Tables and steps replace vague bullets
- FAQ reflects current People Also Ask
Technical QA
- Canonical, breadcrumbs, and internal links are correct
- Schema validated in the Rich Results Test
- 301 map tested and live for any consolidations
Submission
- Request Indexing for the destination URL
- Annotate ship date in your tracking sheet
- Prepare 14, 28, and 84 day comparisons in Search Console
Measure recovery
Measure the page and the cluster. Wins often show up first in rank distribution and CTR before overall traffic catches up.
| Metric | Where | Target after 4 to 8 weeks |
|---|---|---|
| Share of queries in top 10 | Queries report for the URL and cluster | +5 to +15 percentage points |
| CTR | Pages report | Within 10 percent of baseline or higher |
| Impressions | Pages report | Return to baseline band or higher |
| BOFU path clicks | Internal link tracking | +10 to +25 percent |
Expect some testing. The SERP may trial your refresh before settling. Keep internal links consistent to speed up recovery.
FAQ
How do I separate decay from seasonality
Use 84 and 168 day comparisons in Search Console. If the drop repeats at the same time each year it is seasonal. If it is new and sustained it is likely decay.
Should I change the URL when I refresh
No. Keep the URL unless the topic is wrong. Preserve link equity. If you retarget intent you may need a new page but then redirect the old one.
How often should I refresh
Audit monthly for high value clusters. Plan refresh waves quarterly. Start with Update. Move to Expand or Sunset only when needed.
Do images and media affect decay
Yes. Outdated screenshots and diagrams increase pogo sticking. Update visuals and captions. Follow Google’s basics on helpful page construction.