Prioritize a refresh queue for declining content
Compare page performance across consistent periods, separate measurement problems from likely content decay and rank a small queue of evidence-backed refresh briefs.
How this works
Turn portfolio performance into a limited refresh queue. Keep observed losses, hypotheses and proposed edits separate.
Select and scope maintenance across existing pages. Hand selected articles to a deeper editorial audit; do not promise recovery or automatically publish.
Before you start
Metric and comparison rule
Choose the traffic metric, channel, country or device segments and comparable periods. Preserve definitions; sessions, clicks and impressions measure different things.
Page identity and history
Use stable page IDs or a reviewed canonical mapping, redirects, publication dates and major revisions. Confirm the analytics source covers the relevant site.
Prepare the inputs
- Performance export
- Required
Page identifier, date, metric, value and applicable segment dimensions.
Check complete, equal periods, metric changes, duplicates and baseline sufficiency.
- Content inventory
- Required
Canonical page reference, current text, owner, published and updated dates.
Resolve redirect and URL changes before treating a disappearing URL as lost demand.
- Change context
- Required
Known product changes, migrations, campaign shifts and permitted search evidence.
Date each observation and separate confirmed events from hypotheses; missing context remains a limitation.
- Prioritization rule
- Required
Business relevance, decline threshold, review capacity and effort categories.
Make the selection rule explicit and configurable; traffic lost is not equivalent to recoverable traffic.
Implementation, step by step
Create a comparable portfolio snapshot
- Normalize page identity and select consistent channel and segment definitions. Compare complete periods of equal duration and consider a seasonal comparison when available.
- Exclude incomplete days; never turn missing metrics into zero. Retain exports and comparison transformations.
Checkpoint: Each page has comparable baseline and current values or an explicit data issue.
Separate significant declines from noisy alerts
- Calculate absolute and percentage change, with a clear convention for zero baselines. Apply the agreed minimum volume and persistence rule.
- Check whether losses are sitewide, concentrated in a segment or explained by a redirect, tracking interruption or ended campaign before opening a content refresh.
Checkpoint: Content work, measurement checks and observation-only pages remain separate.
Inspect evidence for a bounded explanation
- Read the current page and relevant dated product information. Where permitted, compare current search intent and competing pages without copying their material.
- Record stale facts, missing coverage or changed reader needs with exact supporting references. Treat ranking changes and competitors’ edits as possible factors unless stronger evidence supports a cause.
Checkpoint: Evidence, alternatives and uncertainty accompany each diagnosis.
Rank a queue that fits available capacity
- Rank eligible pages by the agreed combination of absolute loss, business relevance, evidence strength and estimated effort. Show these factors instead of hiding them behind an unexplained score.
- Select available review slots. Watch weak diagnoses; exclude steady, growing and baseline-free pages. Lost traffic is not recoverable upside.
Checkpoint: The top queue has a transparent selection reason and an accountable owner.
Draft the smallest useful refresh brief
- Specify the stale section or reader need, the factual source needed, proposed change and acceptance check. Draft selected replacement passages only where the evidence is sufficient.
- Keep content changes distinct from technical fixes, redirects or tracking repairs. Capture page version and assign review before any authorized publication.
Checkpoint: Each brief has scope, dependencies and review.
Track completion and measure without overclaiming
- Retain the pre-change baseline, edit date and actual published version. Schedule or propose follow-up using the agreed lag and comparison window.
- Record observed changes with seasonality, concurrent campaigns and other confounders. Carry unfinished briefs forward under the same page ID instead of duplicating them each week.
Checkpoint: The queue distinguishes proposed, reviewed, published and measured work.
Decisions along the way
Many unrelated pages fall at the same time
Investigate measurement, channel or sitewide changes before ordering individual rewrites.
A page moved to a new URL
Reconcile the old and new identity and redirect history; do not treat migration alone as content decay.
A large percentage decline comes from a tiny baseline
Show the absolute loss and apply the agreed minimum-volume rule before assigning work.
The page contains an incorrect product claim
Flag factual correction for the editor even if its traffic priority is low; do not silently publish the change.
What you will produce
content-refresh-queue.csv
CSVA limited queue with ranking factors.
Include: page_id · baseline_period · current_period · baseline_value · current_value · absolute_change · percentage_change · data_quality · hypothesis · evidence · priority_reason · owner · state
refresh-briefs.md
MarkdownSelected changes and follow-up plan.
Include: page_id · current_version · problem · proposed_changes · fact_checks · alternatives · reviewer · measurement_window · unresolved_items
Check the result
- Recalculate absolute and percentage change from the retained export.
- Check that redirects, missing data and metric changes are handled before ranking.
- Distinguish an observed decline from a causal claim or forecast of recoverable traffic.
- Confirm each queued page has one brief, a reviewer and a measurable completion state.
When something goes wrong
Analytics definitions changed between periods
Build a comparable segment if possible; otherwise hold the ranking and document the break.
Search or competitor content is unavailable
Use available page and product evidence, mark the missing comparison and reduce diagnostic confidence.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: choose two refresh candidates from four pages.
Inputs
Page A falls from 1,000 to 700 comparable visits and contains outdated setup steps. B falls from 20 to 5 visits. C appears to fall from 600 to zero after moving URL. D falls from 800 to 650 and has a documented stale product section.
Expected result
Reconcile C with its new URL before judging its performance. Apply the volume rule to B. If A and D satisfy the agreed criteria, queue their bounded factual refreshes with losses of 300 and 150 visits. Do not promise either loss will be recovered.
Run a small pilot
Start small
Use one content library and two or three review slots across several reporting cycles.
Record the baseline
Retain current editorial selection effort, rejected alerts and comparable page performance.
Agree success criteria
Agree the useful-alert and accepted-brief rates before expansion; measure later performance separately from publication completion.
Stop or revise
Pause ranking if changed measurement or unresolved URL mapping makes losses unreliable.
Keep the scope clear
- Do not copy competing content, fabricate factual updates or publish without the existing editorial authorization.
- Do not remove low-traffic pages automatically or interpret correlation as proof of the cause of a decline.
Check before using
The analytics owner verifies the comparison and the editor approves the diagnosis, scope and factual changes before publication.
Business activities
- Create and publish content
- Review business performance
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Page-level performance history · Current content inventory · Editorial capacity and product changes
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow