Enter two traffic figures for each article, one from an earlier period and one from now, and the calculator shows what each post has gained or lost, what the loss adds up to over a year, and which posts to look at first. Built for bloggers, content marketers and SEOs working out where a content refresh is worth the time. It runs in your browser and nothing you type is sent anywhere.
Copy columns straight from a spreadsheet, or use commas or semicolons. A header row is skipped automatically. With comma-separated text, write numbers without thousands separators. Exports differ in which period comes first, so check your header row.
Your results
Results appear here once at least one article has both figures. No data yet? Press Load example data to see a filled-in run, or open the Search Console Pages report, compare two date ranges and paste the clicks in.
| Rank | Article | Earlier to current | Change | Visits a year at risk | Refresh priority |
|---|
How to read the results
Refresh first (score 70 to 100) means the article lost a large share of its own traffic and is one of the bigger losses in your list. Review soon (40 to 69) is worth a look this month. Monitor (1 to 39) lost something, but not enough to jump the queue. No decline means traffic held or grew.
A falling number tells you where to look, not what went wrong. Traffic can drop because a post is out of date, but also because demand is seasonal, a tracking tag broke, Google changed the results page, or another of your own pages started ranking instead. Work through the checks below before rewriting anything, and treat a refresh as a test rather than a guaranteed recovery.
Content refresh checklist
Diagnose first
Then refresh
The ticks are only for you while you work; they are not saved.
Worked example
One article had 1,000 visits in the previous three months and 600 in the last three months. It is of medium importance to the business and a medium-effort refresh. Revenue per visit is 0.03.
| Step | Calculation | Result |
|---|---|---|
| Change | 600 minus 1,000 | minus 400 visits |
| Percentage change | minus 400 divided by 1,000 | minus 40% |
| Visits a year at risk | 400 lost per period x 4 three-month periods | 1,600 |
| Revenue a year at risk | 1,600 x 0.03 | 48.00 |
| Decline signal D | 0.5 x 0.40 + 0.5 x (400 / 400) | 0.70 |
| Multiplier M | 0.5 + 0.3 x 0.5 + 0.2 x 0.5 | 0.75 |
| Priority score | 100 x 0.70 x 0.75 = 52.5, rounded | 53, review soon |
Because it is the only article in this example, it is also the largest loss in the set, which is why the second half of D is 1. Press Load example data above to see how scores spread across six made-up articles.
Methodology and formulas
Periods per year: 13.04 for 28 days (365 divided by 28), 12 for one month, 4 for three months, 2 for six months and 1 for twelve months.
Why these choices. Half of the decline signal is the share of the article’s own traffic that went, so a small post that lost everything is not ignored. The other half is size relative to your biggest loser, so a big post that slipped a little is not ignored either. Business importance and effort can only scale a score between half and full strength: they reorder articles that lost traffic, but they cannot push an article that lost nothing into the queue. A change within plus or minus 5% is labelled stable, and an article under 50 visits in both periods is flagged as low volume, because at that size a handful of visits swings the percentage.
The weights are a judgement, not a law. If you would weight things differently, download the CSV, which includes every input and output, and re-score it in a spreadsheet.
Limitations and troubleshooting
The yearly figures are a run-rate. They assume the gap in the current period repeats for twelve months. Traffic might recover, keep falling or follow the season, so read them as “what this would cost if nothing changed”, not a forecast.
Scores are relative to your list. Add an article with a bigger loss and every other score drops a little. Compare scores within one run, not across runs with different articles.
A row is left out of the results. Both figures are needed and must be zero or more. Thousands separators like 1,200 are fine in the boxes; letters and minus signs are not.
Imported rows came in reversed. Switch “Which number comes first?” and import again, after pressing Reset.
An article shows “n/a” for percentage change. It had no traffic in the earlier period, so there is nothing to take a percentage of. It is counted as new traffic.
Everything looks like decline. Check the comparison period. Month against previous month picks up seasonal swings; the same month a year apart, or a 12-month comparison, usually gives a cleaner read.
Frequently asked questions
What is content decay?
Content decay is a sustained fall in the traffic an existing article earns, usually from search. It is a symptom rather than a diagnosis: the cause can be outdated content, stronger competing pages, a changed results page, seasonality or a measurement problem.
Where do I get the traffic numbers?
For organic search, Google Search Console is the most direct source: open Performance, choose Pages, set a date comparison and export or copy the clicks for each page. Google Analytics organic sessions also work. Use the same source and metric for both periods.
Which comparison period should I use?
Three months against the previous three months smooths out week-to-week noise. If your topic is seasonal, compare the same month a year apart, or the last 12 months against the 12 before. 28-day comparisons react fastest but are the noisiest.
Will refreshing a post bring its traffic back?
Not necessarily. If the loss came from out-of-date content or a better competing page, a substantial update can help. If it came from seasonality, lower demand, a new search feature or a tracking change, rewriting the article will not fix it. That is why the checklist starts with diagnosis.
How is the refresh priority score calculated?
It multiplies a decline signal by a business multiplier. The decline signal blends the share of the article’s own traffic lost with its loss relative to the biggest loss in your list. The multiplier ranges from 0.5 to 1 based on the importance and effort you set. The full formula is in the methodology section.
Is my data stored or sent anywhere?
No. The calculation runs in your browser. Article names and traffic figures are not sent to Blogging Titan, and the CSV is created on your device. Reset clears everything on the page.