Skip to content

rampstackco/claude-skills / skills/content-refresh-system

content-refresh-system

Verified

Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.

references/refresh-prioritization-matrix.md

View on GitHub
# Refresh prioritization matrix

The 2x2 prioritization matrix with quadrant strategies. The discipline of NOT refreshing the high-value-stable quadrant. The under-recognized failure of treating low-value-decaying as automatic refresh candidates.

Most libraries have more pieces showing signals than the team has capacity to refresh. Without prioritization, refresh work happens on the cheapest pieces or the most visible pieces, leaving high-value-decaying pieces in the backlog while editorial capacity goes to pieces that would not have produced recovery worth the effort.

The matrix shifts the program from refresh-everything to refresh-the-quadrant-that-warrants-it.

---

## The two axes

**Piece value.** A composite of business value, traffic value, and strategic role.

- **Business value.** Pieces that drive conversions, qualified leads, or specific business outcomes. Sometimes measurable directly (pieces that close a defined funnel step), sometimes attributed (pieces that influence subsequent conversions).
- **Traffic value.** Pieces that drive meaningful organic traffic, especially on commercial-intent keywords or topical-authority-building queries.
- **Strategic role.** Pieces that anchor a hub, that establish the brand's POV on a flagship topic, or that earn external citations and links. Strategic role can outweigh raw traffic; a 500-traffic flagship piece is high-value if it is the canonical statement of the brand's position.

Pieces are classified as high-value (HV) or low-value (LV). The line between HV and LV is judgment-driven; teams typically settle the criteria by establishing tiers (top 10% by value, next 30%, bottom 60%, or similar).

**Traffic state.** A composite of recent and trending traffic.

- **Stable.** Traffic over the last 90 days is within 10-15% of the prior 90-day baseline, accounting for seasonality.
- **Decaying.** Traffic over the last 90 days is down meaningfully (15%+ beyond seasonal baseline), or trending consistently down over multiple quarters.

Pieces are classified as stable or decaying. The classification is the easier of the two axes because traffic data is cleanly measurable.

---

## Quadrant 1: High-value, decaying

**Top priority.**

**The pieces.** Pieces that drive meaningful traffic, conversions, or topical authority and are losing position.

**The strategy.** Refresh first; the traffic loss compounds and the lost equity is hard to recover. These pieces are usually worth substantial-revision or full-rewrite refresh depth because the value at stake justifies the work.

**The disposition decision.** Almost always refresh. Merge candidates in this quadrant exist (a high-value piece that is decaying because a sister piece is competing for the same query) but are uncommon. Delete is essentially never the right disposition for a high-value piece.

**Capacity allocation.** This quadrant gets the largest share of refresh capacity. Many programs allocate 60-70% of total refresh capacity to high-value-decaying pieces.

**Expected outcomes.** Recovery measured at 30 and 90 days. Strong refreshes on this quadrant typically produce 20-50% traffic recovery within 90 days; full rewrites can produce more.

**Common failures.**

- Treating this quadrant as "save for later" because the work is heavy. The traffic loss continues during the delay.
- Light-editing high-value-decaying pieces when substantial revision is warranted. The light edit does not move the needle and the team concludes refresh does not work.
- Not investigating the cause. A piece that is decaying because a competitor published a better resource needs different work than a piece decaying because of SERP intent shift.

---

## Quadrant 2: High-value, stable

**Monitor; do not refresh proactively.**

**The pieces.** Pieces that are performing strongly and showing no decay signals.

**The strategy.** Leave alone. Refresh-everything-on-calendar treats this quadrant the same as the high-value-decaying quadrant and damages performance. Pieces that are working should not be touched without clear signal.

**The disposition decision.** No action; monitor through continuous monitoring for emerging decay; review at quarterly audits for content drift signals.

**The discipline.** This is the quadrant that calendar-refresh programs damage most. A piece ranking position 2 with stable traffic gets refreshed because it is the next piece in the rotation; the refresh introduces minor changes that shift the SERP signals; ranking drops to position 5; traffic drops 30%. The refresh that was meant as maintenance was actually destruction.

**When to revisit.** Monitor for emerging signals. If traffic starts decaying or rankings drop, the piece moves to high-value-decaying. If content drift becomes pronounced (the piece is performing but the team sees positioning misalignment), substantial revision may be warranted but only if the team is willing to risk the performance.

**Common failures.**

- Refresh-on-calendar damaging stable pieces.
- Treating stable rankings as a refresh target because the team wants to "improve" the piece. Improvement on stable pieces is a high-risk operation.
- Touching the URL, schema, or core copy of a stable piece without strong rationale.

---

## Quadrant 3: Low-value, decaying

**Audit for merge or delete.**

**The pieces.** Pieces with low traffic that are decaying further. Pieces that never had strong demand and are now losing what little they had.

**The strategy.** The default disposition is NOT refresh. Refresh on these pieces rarely justifies the effort; the underlying issue is usually that the piece never had strong demand. The actual disposition is usually merge (consolidate into a stronger sibling piece) or delete (and 301 to the closest sibling or relevant hub).

**The disposition decision.**

- **Merge** when a sibling piece on a related topic is performing better and could absorb the failing piece's content. Merging consolidates authority and produces a stronger consolidated piece. The merged URLs redirect to the survivor.
- **Delete** when no merge candidate exists, the topic is not load-bearing for the program, and the piece's residual value (small as it is) does not justify maintenance. Delete and redirect to the closest sibling piece or hub.
- **Refresh** is occasionally warranted: when the piece has clear strategic role (anchors a small but important sub-topic) and the decay is recoverable. Rare in this quadrant.

**Capacity allocation.** This quadrant gets the smallest share of refresh capacity but a meaningful share of disposition work (merges and deletes are real work, less than full rewrites but more than light edits).

**Common failures.**

- Refreshing pieces in this quadrant by default. The team spends hours improving a low-value piece that even at its best will not recover meaningful traffic, while a merge candidate that would have produced a stronger consolidated piece sits unaddressed.
- Skipping the merge analysis. Pieces that should have been merged get refreshed in isolation, leaving the authority-splitting problem intact.
- Avoiding deletes because deleting feels destructive. Maintaining a library of low-value pieces forever costs ongoing audit attention and dilutes overall library quality.

---

## Quadrant 4: Low-value, stable

**Leave alone.**

**The pieces.** Pieces with low traffic that are not actively decaying. They are at the floor.

**The strategy.** Leave alone. Low traffic is the floor; the piece is not costing anything to keep. Touching these pieces in a refresh program burns capacity for no return.

**The disposition decision.** No action. Pieces that have been low-traffic-stable for multiple audits are candidates for batch consideration: do they collectively represent a topic that is no longer load-bearing for the program? If yes, a structural decision (delete the topic cluster, merge into a hub, archive) may be warranted at program level. If no, leave alone.

**When the strategy fails.** If a low-value-stable piece starts decaying further (moves to low-value-decaying), the disposition is reconsidered. Usually merge or delete.

**Common failures.**

- Refresh-on-calendar touching this quadrant. Pure capacity waste.
- Treating low-traffic as a problem to be solved. Low traffic on a low-value piece is the right outcome; not every piece needs to drive significant traffic. Some pieces serve narrow but real strategic roles at low volume.

---

## Capacity allocation by quadrant

A typical refresh program's capacity might split as:

- **High-value, decaying:** 60-70% of refresh capacity. The largest share, on the highest-value work.
- **Low-value, decaying:** 15-20% of capacity, mostly on merge and delete dispositions, occasional refresh on strategically important pieces.
- **High-value, stable:** 5-10% of capacity, on the rare cases where content drift warrants substantial revision despite stable performance.
- **Low-value, stable:** 0-5% of capacity. Mostly batch reviews to identify topic-level decisions.

The allocation varies by library age and decay rates. Newer libraries with limited decay have less work in the decaying quadrants and may invest more in continuous-monitoring infrastructure. Older libraries with significant decay have more work to do across quadrants.

---

## Common matrix failures

**The "every piece is high-value" trap.** Teams that classify too many pieces as high-value lose the prioritization signal. A library where 60% of pieces are "high-value" is essentially unprioritized; the matrix fails to discriminate.

**The traffic-only value classification.** Classifying value purely by traffic misses strategic-role pieces that have lower traffic but high importance. A flagship manifesto that earns 800 visits a month but drives external citations and brand recognition is high-value despite lower traffic.

**The "refresh = recovery" assumption.** Some pieces in the high-value-decaying quadrant cannot be recovered through refresh. The topic is genuinely declining; competitors are too strong; SERP intent has shifted away from any format the brand can produce. The matrix prioritizes refresh; it does not promise refresh will work. The effectiveness measurement (see `effectiveness-measurement.md`) catches the cases where refresh is not producing recovery.

**Static classification.** Value and traffic state both shift over time. A piece in low-value-stable that suddenly draws traffic from an emerging keyword moves to high-value-stable; a piece in high-value-decaying that fully recovers moves to high-value-stable. The matrix is not a one-time classification; it is the framework run at each audit.

---

## Methodology-level choices that stay in the public skill

The two axes (value, traffic state), the four quadrants with strategies, the capacity allocation guidance, the common matrix failures, the dynamic-classification discipline.

## Implementation choices that stay internal

Specific value-classification rubrics the team uses (revenue attribution models, strategic-role tagging, traffic-tier definitions). Specific scripts that classify pieces into quadrants from data pulls. Specific dashboards that visualize the matrix at audit time. The team's own conventions for high-value-stable refresh decisions when content drift is pronounced. These vary by team, business model, and analytics setup.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall