Freshness Markers Calculator
GeneralEnter how long ago your content was updated and its half-life to get an instant freshness score. Use the result to prioritise which pages need a refresh.
Last updated: April 2026
This calculator is designed for real-world usage based on typical engineering scenarios and publicly available documentation.
Freshness markers are signals that tell search engines and readers how current a piece of content is. Every page decays at a different rate — a news article is stale within hours while an evergreen tutorial stays relevant for years. This freshness markers calculator quantifies that decay so you can act on it. The score runs from 0 to 100 using exponential decay: a page updated today scores 100, and by the time one full half-life has passed the score drops to 50. The half-life is configurable — set it to 30 days for a typical blog post, 180 days for documentation, or 1 day for news content. The calculator also shows your average update frequency, which is a key editorial health metric. Content teams, SEO analysts, and developers maintaining documentation sites use freshness scoring to build automated audit pipelines. Instead of reviewing every page manually, you can rank pages by score and focus effort on the most decayed content first.
How to Calculate Freshness Markers
1. Enter the number of days since the page was last meaningfully updated. 2. Set the half-life for your content type — the number of days after which freshness drops to 50. 3. Enter total content age (days since first publication) and how many updates have been made. 4. The calculator applies exponential decay: Score = 100 × 2^(−daysSinceUpdate ÷ halfLife). 5. Read the score label (Very Fresh → Outdated) and the average update frequency to plan your next refresh.
Formula
Freshness Score = 100 × 2^(−d ÷ h) [0–100]
d — days since last meaningful update
h — content half-life in days
News ≈ 1 · Blog ≈ 30 · Docs ≈ 180 · Evergreen ≈ 365
Update Frequency = days since publication ÷ number of updates
Score labels: ≥80 Very Fresh · ≥60 Fresh · ≥40 Aging · ≥20 Stale · <20 Outdated Example Freshness Marker Calculations
Example 1 — Blog post updated last month
Days since update: 30 · Half-life: 30 days (blog) Score = 100 × 2^(−30 ÷ 30) = 100 × 2^(−1) = 50.0 ──────────────────────────────────────────────── Result: 50.0 / 100 — Aging Recommendation: refresh within the next 2 weeks to recover to Fresh territory
Example 2 — Documentation page, 90 days since update
Days since update: 90 · Half-life: 180 days (docs) Score = 100 × 2^(−90 ÷ 180) = 100 × 2^(−0.5) ≈ 70.7 Days since publication: 540 · Updates: 6 Update frequency = 540 ÷ 6 = 90 days ──────────────────────────────────────────────── Result: 70.7 / 100 — Fresh · Avg update every 90 days Recommendation: on track; schedule next review in ~90 days
Example 3 — News article, 3 days old
Days since update: 3 · Half-life: 1 day (news) Score = 100 × 2^(−3 ÷ 1) = 100 × 0.125 = 12.5 ──────────────────────────────────────────────── Result: 12.5 / 100 — Outdated Recommendation: archive or add a "this article is from X date" notice
Tips for Managing Content Freshness
- › Set half-life per content type, not per site. A pricing page decays faster than a conceptual overview — treat them differently in your audit pipeline.
- › Schedule refreshes before scores drop below 40. Recrawl rates and user trust both fall sharply once content is perceived as stale.
- › A "last reviewed" date signal (even with no edits) resets the clock for readers, but does not fool search engines — make at least one substantive change per refresh.
- › Automate scoring. Export your sitemap, calculate freshness scores in a spreadsheet or script, and sort ascending to build a ready-made refresh backlog.
- › Use update frequency alongside score. A high-frequency page that hasn't been updated lately is a stronger anomaly than a page that rarely gets touched.
- › For documentation, pair freshness tracking with version pinning — mark pages as valid for a specific product version so decay signals stay meaningful as the product evolves.
Notes
- › Results are estimates and may vary based on actual usage.
- › Always validate against your production environment.