Content Freshness Score

How it works

1. Enter the URL of the page you want to check — the tool fetches the live HTML exactly as a crawler receives it.
2. It scans the visible page for on-screen dates, "last updated" or "reviewed on" language and any year references in the copy.
3. It parses your structured data for datePublished and dateModified values, comparing the modified date against the published date.
4. It weighs current-year mentions against stale-year signals and, when the server provides it, calculates the real days since the last modification.
5. All signals are combined into a freshness score with a clear Fresh, Aging or Stale verdict and specific notes on what is aging the page.

What it checks

• Visible dates — on-page publish, update or review dates that readers and crawlers can see directly in the content.
• Date schema — datePublished and dateModified values in your JSON-LD or microdata, and whether they agree with the visible dates.
• Current-year references — mentions of the present year that signal the content has been reviewed recently.
• Stale-year signals — old years, outdated statistics or references that make the page look neglected.
• "Last updated" language — explicit maintenance cues such as "last updated," "reviewed" or "revised" that reinforce recency.
• Days since modified — when available, the true elapsed time since the last change, feeding the Fresh / Aging / Stale verdict.

Why it matters

Search engines factor recency into ranking through Query Deserves Freshness — for many topics, a page that looks current out-ranks an older one covering the same ground. Content also decays: rankings that once held slide as competitors publish updated material and your dates drift further into the past. Stale years, dead statistics and absent update signals quietly erode both algorithmic trust and reader confidence. A page that clearly shows recent maintenance tells crawlers and visitors alike that the information can still be relied on today.

How to improve freshness

Start by genuinely revising the content — refresh statistics, examples and any year references so the copy reflects the present. Add a visible "last updated" date near the top and keep your dateModified schema in sync with it, but only when you have made real changes; faking dates erodes trust and can backfire. Remove stale-year mentions, update outdated links and re-verify claims. Then re-run the checker to confirm the visible dates, schema and current-year signals all line up on a Fresh verdict.

Frequently asked questions

What is the difference between Fresh, Aging and Stale?

Fresh means the page shows recent dates, current-year references and matching schema, so it reads as actively maintained. Aging means some signals are current while others are drifting out of date. Stale means old years, missing update cues or a long gap since modification make the page look neglected to search engines.

Does updating only the date improve freshness?

No. Changing a date without changing the content is misleading, and search engines increasingly detect the mismatch. Freshness should reflect real revisions — updated facts, statistics and examples. Update the visible date and dateModified schema honestly, only after you have genuinely improved the page.

Why does the tool sometimes miss the days since modification?

The real days-since-modified figure depends on signals the server or page exposes, such as dateModified schema or response headers. When a page provides none of these, the tool relies on visible dates and year references instead, so the verdict leans on those softer freshness cues.