Skip to main content
Published articles decay. Facts age, the question shifts, someone else publishes something more current, and none of that announces itself. This is the recurring cycle that catches it: pull the articles that are due, decide what each one needs, do the work, and set the next date.
This process runs on the hero article register and the supporting article register. The cadence defaults live in the article standards.

What you’ll end up with

  • Every article that came due either updated, consolidated, retired, or deliberately left alone with a reason recorded.
  • Updated last-updated and next-review dates in the register, with a note on what changed.
  • A register that reflects what is actually published today.

Why this exists

A hero article is a commitment to keep something true indefinitely, not a piece of work that finishes at publication. Without a cycle, articles get updated when somebody happens to notice a problem, which in practice means after they have stopped working. The signal is measurable. Published analyzes of AI citations on commercial queries put the large majority on pages updated within the past year, and well over half on pages updated within six months. An unmaintained article is a depreciating asset, and a library of them makes a site harder to trust.

When it runs

Run the sweep as a scheduled pass, monthly is usually enough, and work whatever is due that month. The pass has a defined trigger and an actor: a builder, person or AI agent, pulls what is due, runs the decay checks, and produces a triage list with evidence and a recommended decision per row. The rulings are the owner’s. A cadence that exists only in a document does not run; a scheduled pass does.
Do not set a cadence the team cannot sustain. A quarterly cycle across twenty hero articles is real recurring work. An honest twice-yearly cadence that actually runs is worth more than a quarterly one that is silently missed, because the register stays true.

The process at a glance

1

Pull what is due

Filter both registers for a next-review date in this period.
2

Check for decay signals

Look at what changed since the last review: traffic, citations, the facts themselves.
3

Triage each article

Update, consolidate, retire, or leave. Record the decision either way.
4

Do the work

Make substantive changes, not date bumps.
5

Update the register

New last-updated date, new next-review date, and a note on what changed.
6

Review the hero set once a year

Confirm the authority areas are still the right ones.

1. Pull what is due

Filter the hero and supporting registers for a next-review date falling in this period. That list is the work. Anything with a review date in the past is overdue and goes to the top of the list. A register with a growing pile of overdue rows is telling you the cadence is set faster than the team can run it, which is a cadence problem rather than a discipline problem.

2. Check for decay signals

For each article, look at what has changed since the last review. Every signal has a place it is read from; record yours once, in the data dictionary’s where-everything-lives section or the register itself, so any actor can run the checks.

3. Triage each article

Every article that came due gets one of four decisions. Leaving an article alone is a real decision, not a skipped one. Record it, so the next reviewer knows the article was looked at. The decision column is the owner’s on every row: a builder recommends with its evidence attached, and never rules “leave” on its own, because a pass that grades its own triage list checks nothing.
Consolidating and retiring both change URLs. A removed page with no redirect loses every inbound link and citation pointing at it, including ones you never knew existed. Redirect to the closest equivalent page rather than the homepage.

4. Do the work

An update is a substantive change to the article, not a change to its date. Bumping a timestamp without changing anything is visible to readers who have seen the page before, and it destroys the one signal that would otherwise tell your own team which articles genuinely need attention. If nothing needed changing, the decision was “leave,” and that is fine. A substantive update usually means one or more of:
  • New or corrected data, with the source updated.
  • A new section answering a question people have started asking.
  • Removing a section nobody needs any more.
  • Rewriting an opening that no longer answers the question directly.
  • Adding the internal links to articles published since this one.
A hero article that has drifted far enough to need rewriting rather than updating goes back through the article process with a fresh brief, keeping the same URL. Within a decided triage, the execution, refreshed data with updated sources, redirects on consolidation, register bookkeeping, is the builder’s; a change big enough to amount to a rewrite goes back to the owner instead of quietly growing inside an update.

5. Update the register

For every article touched: The one-line note is what makes the next review fast. A reviewer who can see that the last pass replaced the 2027 telemetry figures knows exactly where to start.

6. Review the hero set once a year

Once a year, the pass escalates instead of triaging: it assembles the evidence (review-date misses, traffic by area, citation share) and the owner answers the questions below. These are the judgment calls the cap exists to force.
  • Are these still the areas where we can answer better than anyone else?
  • Has an area stopped being ours, because the market moved or someone else now owns it?
  • Has a supporting article outgrown its tier and earned a hero slot?
  • Are any hero articles consistently missing their review dates, meaning the set is larger than the team can maintain?
Promoting a supporting article into the hero set means demoting or retiring another one. The cap is what makes the commitment real, and a hero set that grows quietly ends up as an ordinary content library with an aspirational label. The article library overview covers how areas are chosen.

Exceptions

  • An article breaks between reviews. A wrong price, a broken product reference, or a factual error gets fixed immediately rather than waiting for its date. Update the register when you do.
  • A launch or announcement dates an article overnight. Treat the launch as the trigger and update the affected articles as part of the launch, not at their next scheduled review.
  • An article is deliberately frozen. Some pieces are records of a moment: an announcement, an event recap, a dated report. Mark them as frozen in the register with no review date, rather than leaving them to fail a freshness check forever.
Type: process
Domains: content, reporting
Provides: process:article-maintenance
Uses: article-standards, authority-areas, checklist-review:article-update, data-dictionary, library:article, process:article
Triggers: “Review our articles” · “Which blog posts need updating?” · “Run the article maintenance pass” · “Refresh our hero articles”Asks, one per turn, in order:
  1. Which period are we reviewing, this month or everything overdue? Options: your answer. Skip when: scheduled run.
  2. For each flagged article: update, consolidate, retire, or leave? Options: triage. Skip when: never (owner rules).
  3. Should the annual hero-set review run this time? Options: your answer. Skip when: not the annual cycle.
Output: Triage list with evidence and recommendations, executed updates/redirects, register rows updated with last-updated, next-review, status and note.

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on October 30, 2026