Content
How to decide what content to refresh next
content-decay-refresh a saved expert workflow your assistant follows, in Claude, ChatGPT or Cursor
Find the pages and queries that decayed since their peak, rank them by recoverable clicks, and recommend refresh vs consolidate vs leave for each, the refresh-first content worklist.
Try it
what should we refresh
Private beta Part of the quattr-ai-search plugin, rolling out org by org. Request access ↗
Say any of these
content decaywhich pages decayedwhat should we refresh nextdeclining pagesrefresh worklistpages losing traffic over timestale content to update
You never name the skill or a tool, the assistant routes on what you asked. These are the phrasings it recognises for this one.
And when it stays out of the way
Not for one week's movers (rank-movement-review), for "why did page X drop" diagnosis (anomaly-investigator), or for net-new content planning (keyword-gap-audit feeds that).
Use it instead of rank-movement-review when the frame is decay-over-months and the deliverable is a refresh worklist; use anomaly-investigator instead for a single page's cause hunt.
What it runs
compare_periodsseo_ranking_movement_reportctr_curve_model
3 governed analyses, composed and scoped for you. Named here for transparency, not because you have to ask for them.
The numbers behind it
Metrics it reads, each defined in the reference
Content-category search market shareCTR delta versus the curveExpected CTR at positionPage-level search market sharePeriod-over-period changePotential clicks, before the AI-Overview discountRanking movement (gainers and losers)Striking-distance candidatesUnique pagesWeighted CTR at a position bucket
Reports these numbers feed
AI Overview and SERP feature reportCannibalization reportContent decay reportContent performance reportCrawl log reportCTR opportunity reportInternal linking reportKeyword ranking and movement reportMonthly executive search reportSearch market share reportSearch opportunity reportSERP volatility and algorithm update reportWeekly search report
What it refuses to do
- Recoverable clicks are modeled from the site's own curve, labeled, never promised; refresh lift claims post-execution use controls, not trend lines.
- Consolidation is recommended only after intent review, intentional multi-page coverage is not cannibalization.
What the answer looks like
What should we refresh next?
Analysis plan, every step, resolved for you
- Routed to the governed workflow
content-decay-refresh - Dates bound explicitly
Jun 1 to Jul 31, 2026 - 3 analyses queued in parallel
compare_periods · seo_ranking_movement_report · ctr_curve_model - Honesty gates armed
scope echo · freshness
31 pages decayed from peak; 12 are worth refreshing first, about 6.1K recoverable weekly clicks.
- Decayed pages
- 31 ≥30% below their prior peak clicks
- Recoverable clicks
- ≈6.1K/wk modeled from each page's own peak, not a promise
- Worklist
- 12 refresh · 4 consolidate · 15 leave refresh-first triage
Jun 1 to Jul 31, 2026 vs each page's prior peakorganic
⚠ Observationalas of Aug 1, 2026 (GSC lags 1 to 2 days)IllustrativeOpen in Quattr ↗
Start with the three How-to guides, biggest recoverable clicks, smallest rewrites.
A simulated conversation on fictional data. Scope, freshness and the ⚠ Observational marker are attached by the same director that renders every demo here, not written by hand.
See this Skill inside a real analysis
All runs →A recorded run where this Skill does the work, the prompts as typed, and the decision that came back.
Want this Skill running on your own accounts? Every Quattr customer works with an AI Search Strategist who sets it up with you.