Home Services Method Pricing Work About Insights Get a content audit

Home / Insights / Content refresh

Content refresh

The refresh math: when updating beats publishing

If your blog has more than a hundred posts, some of next month's budget probably belongs to articles you already own.

Editorial demonstration. This sample has no named expert review or client-data attribution.

Key takeaways

  • Refreshes usually pay back faster than new articles because the page already has history and links.
  • Score every URL on trend, rankings, links and conversion before touching it.
  • Consolidating thin posts often does more than rewriting them one by one.

Why older articles decay

Articles lose ground for predictable reasons. Competitors publish something newer. The facts age. Search intent shifts from "what is" to "which one should I buy". None of this means the article was bad. It means it stopped being tended.

In our audits, decaying URLs are rarely the weakest pages on a site. They are often former top performers that still hold links and history, which is exactly why they are worth saving.

A simple scoring model

We give each URL a score from one to five on four questions. Is traffic falling over the last six months? Does it rank on page one or two for anything valuable? Does it have links from other sites? Did it ever drive a lead or signup?

A page that ranks 11th with good links is usually one refresh away from page one. A new article starts from zero.

When publishing still wins

Refreshes cannot fill gaps. If your Hive Map shows a cluster with no pillar, or buyers ask questions you have never answered, new content comes first. The practical split for most mature blogs is somewhere between one third and one half of hours going to refreshes.

What a good refresh includes

  • New data, dated and sourced
  • An example or quote from someone who does the work
  • A structure that answers the main question in the first paragraph
  • Internal links into and out of the cluster
  • A visible "last updated" date with a short change note

About the author

Wordhive editorial team

Practical notes on planning and maintaining a connected content library.

Editorial standards · Report a correction