Most content teams churn. An article ships, lives for six months, loses visibility, and gets replaced by a new piece targeting the same question. The old piece goes to the archive. The new piece starts from scratch.
We don’t do that. Our default is to update, not to retire. The decision changes the economics of an editorial team enough that we are writing about it.
Reason one: updating is cheaper
A full refresh of a published roundup takes an editor about 45 minutes. New price ranges. One or two product swaps. A fresh “as of” line. The visibility layer re-crawls, the article is current again, and the reader lands on a piece that reads like it was written this quarter.
Writing the same roundup from scratch takes an editor a full day. Research, outline, draft, edit, review, publish. Twelve times the time for roughly the same reader-visible output. The math only works out if the old piece is unsalvageable, which it almost never is.
Reason two: older pieces earn more reader trust
An article dated “updated October 2026” that was first published in April 2024 reads as a living reference. An article dated “October 2026” with no history reads as something a brand paid to put online this month.
Readers can tell the difference. They stay longer on the living reference. They click through at a higher rate. They come back to the same article when they’re ready to buy, which the fresh piece never earns because they haven’t seen it before.
The “first published” line is a trust artefact we used to hide. We now show it. It is a specific, verifiable detail about a piece’s history, which is exactly the kind of signal a reader uses to decide whether to trust the recommendation.
“An article with a history reads as a reference. An article without one reads as press.”
Reason three: updates compound
Every update is a reason for the visibility layer to re-crawl and re-weigh the piece. A piece that got updated four times in a year accrues weight at four separate moments. A piece that didn’t accrues weight once and then slowly loses it.
The compounding is quiet. You don’t see it in week two. You see it in month twelve, when a piece that was updated three times is still earning readers and the sibling piece that was published and left alone has slipped out of view.
What this requires operationally
Three things.
An update calendar. Every piece gets a quarterly check. Fifteen minutes to decide if it needs a touch, 30 minutes to make the touch, done. The checks are scheduled, not reactive.
A visible “last updated” line. Every article shows when it was first published and when it was last touched. Both dates. No fuzziness about whether this is a fresh article or a refreshed one.
Discipline about what counts as an update. We don’t backdate. We don’t add a comma and claim an update. If an editor touches a piece, the touch has to be a real one. The reader has to be able to tell the difference the second time she lands on it.
Where this fails
Two kinds of article should still be retired. A piece that recommended something that turned out to be bad, where the fix is a different recommendation. And a piece that was written to a question that no longer matters.
Everything else is cheaper to update than to replace. Our ratio of updates to new pieces is roughly four to one. It used to be reversed, and nothing was getting better for it.