content-refresh-system

# Content Refresh System

A senior editorial leader's playbook for systematic content refresh. The discipline that distinguishes intentional refresh programs from set-and-forget decay, and the prioritization framework that prevents both over-refresh (refresh-everything-on-calendar) and under-refresh (refresh-nothing-until-traffic-collapses).

Content decays. Search behavior shifts; SERP intent reshapes; facts go stale; competitors publish stronger pieces; the brand's own positioning evolves past what older pieces represent. Programs that ignore this reality watch traffic erode silently across the library. Programs that overreact (rewriting everything on calendar) burn editorial capacity that should be producing new flagship work. The discipline is in the middle: refresh what matters when signals say so, and document the decisions so the program is auditable.

This skill is the program-level refresh discipline across the whole content library. It builds on `pillar-content-architecture`'s hub-level refresh consideration (refresh as ONE consideration in hub design) and `editorial-qa`'s pre-publish quality gate (this skill is post-publish lifecycle, not pre-publish QA). Together those skills cover content quality at the moments quality decisions get made; this skill covers the moments between, when content is in the field and decaying or holding.

The voice is the senior editorial leader who has watched refresh programs fail in both directions and who has shipped the systems that produced durable refresh discipline.

When to use this skill: building a refresh program from scratch, auditing why refresh work is happening but traffic is not responding, designing the prioritization that keeps refresh tractable across a 200-piece or 2,000-piece library, or fixing a refresh program that is eating editorial capacity without clear results.

---

## What this skill covers

This skill spans the post-publish lifecycle of content. The content suite distinction:

- `content-strategy` is program scope: what to produce.
- `pillar-content-architecture` is HUB scope; refresh appears as ONE consideration in hub design.
- `content-brief-authoring` is per-piece scope at production time.
- `content-and-copy` is execution scope at production time.
- `editorial-qa` is gate scope: pre-publish verification.
- **`content-refresh-system` (this skill)** is lifecycle scope: program-level refresh discipline across the whole content library, after pieces are in the field.

The audience: editorial leads, content directors, content ops managers, in-house teams running content libraries of 50-5,000+ pieces, agencies maintaining client content programs across years.

What is not in scope: writing the refreshed pieces themselves (that is `content-and-copy`), the brief that drives the refresh (that is `content-brief-authoring`), the pre-publish gate on the refreshed piece (that is `editorial-qa`). This skill is the prioritization and lifecycle discipline; the actual content work plugs into the existing skills.

---

## Refresh-everything vs refresh-nothing vs triaged-refresh

The keystone framing. Two failure modes plus the discipline.

**Refresh-everything.** Full rewrites on calendar. Every piece gets a refresh on a 12-month or 18-month rotation regardless of signals. Output: editorial capacity consumed by maintenance work that often was not needed, while strong pieces are touched into worse versions and weak pieces consume the same effort as flagship pieces. Cost: opportunity cost on new flagship production; maintenance fatigue in the editorial team; some pieces that were performing well get diluted by unnecessary edits.

**Refresh-nothing.** Set-and-forget. Pieces ship and never get touched again. Output: traffic decays silently across the library as facts go stale, competitors publish stronger pieces, and SERP intent shifts away from the piece's framing. The library's compounding value erodes invisibly until an algorithm update or a competitor's flagship piece exposes the rot. Cost: cumulative traffic loss that nobody attributes to refresh failure because the loss is gradual; trust loss when readers find stale facts in pieces they expected to be current.

**Triaged-refresh.** Refresh what matters when signals say so. Audit cadence catches decay early; prioritization concentrates effort on high-value-decaying pieces; weak pieces get refresh-vs-merge-vs-delete dispositions instead of automatic refresh; the program is auditable because every refresh decision was a deliberate response to specific signals. Output: editorial capacity preserved for new production; the library's compounding value protected; refresh work is seen, understood, and measured.

The litmus test. Ask of any refresh decision: what signal triggered this refresh, what depth of refresh did the signal warrant, what outcome do we expect, and how will we measure whether the refresh worked? If the answer is "it was scheduled" or "we always refresh after 12 months," the program is on calendar rather than on signal.

---

## Refresh signals

Five categories of signal that trigger refresh consideration. Pieces that show no signals do not need refresh; pieces that show multiple signals are higher priority.

**Traffic decay.** Organic traffic to the piece is trending down over a 90+ day window beyond the seasonal baseline. The decay can be slow (5-10% over a year) or sharp (40%+ in a month after an algorithm update). Slow decay typically indicates content drift; sharp decay typically indicates external change.

**Ranking drops.** The piece is losing position on its target keywords. Drops from page 1 to page 2-3 are particularly consequential; drops within page 1 (position 3 to position 7) are less so but still tracked. Persistent ranking drops over 30+ days indicate a real shift, not search-result volatility.

**Factual staleness.** The piece contains statistics, references, examples, or claims that are dated. A 2018 stat in a 2026 piece on a fast-moving topic is sta