Content staleness index

The content staleness index is a weighted score that captures how out of date a content library has become, measured by how long pages have gone without a meaningful update relative to the traffic and revenue they carry. A page that has not been touched in two years matters far more if it drives thousands of visits a month than if nobody reads it. The index reflects that by weighting each page before it counts age, so the number tracks risk to the business rather than raw shelf life.

It matters because content decays quietly. Prices change, product names move on, screenshots age, statistics fall out of date, and rankings slip as competitors publish fresher material. None of this throws an error. The pages keep serving, the analytics keep flowing, and the rot stays invisible until a customer or a search engine notices. A single staleness index gives content and SEO teams an early warning they can watch month over month instead of discovering decay one complaint at a time.

To calculate the content staleness index, weight every page by its importance, multiply that weight by how long the page has gone without a meaningful update, and divide by the same weighting applied to each page target refresh interval. The result is a ratio. A value of 1.0 means the library is, on average, exactly at its refresh deadline. Above 1.0 means it is overdue. Below 1.0 means content is being kept fresh ahead of schedule.

A worked example. Say a single page carries 5 percent of total traffic, was last updated 400 days ago, and its target refresh interval is 180 days. Its numerator contribution is 0.05 x 400, or 20. Its denominator contribution is 0.05 x 180, or 9. On its own that page scores 2.2, well overdue. Roll the same calculation across every page and the weighted totals give you one library-wide index.

1. 1

   Assign a weight to each page

   Use share of organic traffic, conversions or revenue so important pages count more. Normalise so weights are comparable across the library.

2. 2

   Record days since last meaningful update

   Count from the last substantive content change, not a plugin bump or a layout tweak. Trivial edits do not reset the clock.

3. 3

   Set a target refresh interval per content type

   Pricing and product pages refresh fast, evergreen guides slowly. A statistics roundup might target 90 days, a definition page 365.

4. 4

   Compute the weighted ratio

   Sum weight times age across all pages, divide by sum of weight times target interval, and read the single index value.

A single staleness number tells you the library is drifting, but not where or why. A metric tree decomposes the index into the drivers a team can actually act on. Break it down by what is ageing, which segments carry the most weight, and what is slowing refresh throughput, and the headline number turns into a set of specific, ownable problems.

This is the gap between a dashboard and a decision. A dashboard shows the index ticking up. A metric tree shows that the rise is concentrated in high-traffic guide pages whose authors left, that the refresh queue has stalled, and which owner is accountable for clearing it.

There is no universal benchmark because the index depends on the refresh intervals you set, but the ratio itself reads consistently. An index near or below 1.0 means the library is keeping pace. Once it climbs past 1.5, a meaningful share of valuable pages is overdue, and above 2.0 the backlog is large enough to drag rankings and erode trust. The ranges below give practical bands for a typical marketing content library.

Improving the index is not about refreshing everything. It is about refreshing the right pages in the right order and lifting throughput so the library stops falling behind. Because the index is value-weighted, the fastest gains come from updating a small number of high-traffic, overdue pages rather than clearing a long tail nobody reads.

1. 1

   Weighting every page equally

   An unweighted index lets a tail of dormant pages mask decay on the handful that drive revenue. Always weight by traffic, conversions or revenue.

2. 2

   Counting trivial edits as updates

   A plugin bump or a layout change should not reset the clock. Only meaningful content changes count, or the index will flatter a library that is actually stale.

3. 3

   Using one refresh interval for everything

   A single target punishes evergreen pages and lets fast-moving pages off the hook. Set intervals by content type so the index reflects real risk.

4. 4

   Tracking the index without owners

   A number with no accountable owner drifts forever. Tie each driver to a person so a rising index turns into action rather than a recurring agenda item.