Insights · Checklist
Refresh cycle checklist
Pages decay. Regulations change, prices move, cited sources update, competitors publish newer answers. This checklist runs the refresh cycle so that every page is reviewed on its interval, revised when needed and retired when it no longer serves.
How to use it
Before the first step.
- Generate the schedule from each page’s revision date and refresh interval.
- Prioritize pages that earn citations; protect them first.
Steps
Each one owned and evidenced.
| # | Step | Owner | Evidence |
|---|---|---|---|
| 01 | Generate the list of pages due or overdue for review from revision dates and intervals. | Editorial lead | Due list with dates |
| 02 | Add event-triggered reviews: pages affected by a regulatory, price, product or source change. | Editorial lead | Trigger log |
| 03 | Order the list by citation value: pages earning citations first, then by traffic and inquiry contribution. | Editorial lead | Prioritized list |
| 04 | For each page, the expert reviews for accuracy and currency and marks confirm, revise or retire. | Expert | Review decision per page |
| 05 | Revise pages marked for revision; re-run fact verification on changed claims. | Editor and verifier | Updated claims register |
| 06 | Re-sign revised pages and update the revised date and structured data. | Expert and technical owner | Sign-off record, dateModified |
| 07 | Confirm pages marked current with a new revised date only where the review actually occurred. | Editorial lead | Review record |
| 08 | Retire pages that no longer serve: redirect to the best alternative, remove from sitemaps and indexes. | Technical owner | Redirect map entry |
| 09 | Update internal links and related-page lists affected by revisions and retirements. | Technical owner | Link check report |
| 10 | Report currency monthly: pages due, overdue, reviewed, revised, retired. | Editorial lead | Currency report |
By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days