content-refresh-system

What it does

A program-level guideline for systematic content refresh across a library. It prioritizes which pieces to refresh, when, and how deeply, and prescribes dispositions (refresh, merge, delete) based on signals like traffic decay, ranking drops, and content drift. It distinguishes intentional refresh from decay and ties into hub design and post-publish lifecycle, not pre-publish QA. It targets editorial leads, content directors, and ops managers overseeing libraries of tens to thousands of pieces. It covers the lifecycle between publication and renewal, and provides a framework to audit and maintain content quality over time.

How it works

• Establishes a refresh-everything, refresh-nothing, and triaged-refresh framing to guide decisions.
• Defines five signals to trigger refresh consideration: Traffic decay, Ranking drops, Factual staleness, SERP intent shift, and Content drift; pieces with zero signals are deemed stable.
• Describes an audit cadence with two patterns: Quarterly audits (90 days) and Continuous monitoring, plus a hybrid pattern combining both.
• Introduces a 2x2 prioritization matrix (piece value vs traffic state) to decide which pieces to refresh, merge, or delete.
• Outlines four refresh depth options: Light edit, Substantial revision, Full rewrite, Structural redesign, and advises matching depth to signal strength.
• Specifies decision criteria for Refresh vs Merge vs Delete and cautions against inappropriate refresh strategies.
• Describes execution patterns: ownership, editorial integration, capacity allocation, and batching.
• Mentions post-refresh signals to search engines (re-promotion steps) and overall lifecycle integration.

When to use it

Use when building a refresh program from scratch, auditing why refresh work is happening without traffic response, designing prioritization for large libraries, or repairing a refresh program that overuses editorial capacity without clear results.

What it can touch

• The skill specifies touchpoints across the content lifecycle and relies on signals and prioritization concepts; it does not describe content creation itself.
• It references related resources and templates for signals checks, audit cadences, prioritization matrices, and depth-decision criteria, and indicates how to apply these within an existing editorial workflow.

Caveats

• Focused on lifecycle discipline and program-level management rather than item-level content production.
• Details rely on external reference materials (e.g., references/refresh-signals-checklist.md, references/audit-cadence-patterns.md) for signal checks and cadences.
• Uses terminology like Refresh, Merge, Delete and depth levels which must be operationalized within the agency or edition’s workflow; no guarantees about traffic outcomes are stated.