Content Freshness Checker
Follow a client site’s sitemap trail, measure how much reliable update-date evidence exists, and turn the oldest pages into a focused review queue.
Evidence, not guesswork
A freshness signal your client can interrogate
The report separates current pages, likely update candidates, and missing date evidence. It never treats an absent or future date as proof of freshness, and it carries the sitemap limitations into the copied summary.
0–90 days
Fresh
A strong recency signal from a valid sitemap lastmod date.
91–180 days
Aging
A review window: prioritize pages tied to active offers or changing topics.
181+ days
Stale
An update candidate, pending a page-level review of accuracy and intent.
Once you find the update queue, inspect a priority URL with the published article quality checker.
Frequently asked questions
How does the content freshness score work?
The deterministic score uses pages with valid, non-future sitemap dates only. Fresh pages score 100, aging pages 60, and stale pages 20; pages without reliable dates are excluded.
Does an old sitemap date prove that a page is outdated?
No. A lastmod date is an audit lead, not proof about the page itself. CMS platforms may omit, reuse, or inaccurately regenerate these dates, so review the page before recommending an update.
How much of a site does the audit check?
It discovers sitemaps through robots.txt and /sitemap.xml, then checks up to 100 page entries across five sitemap files.
How many free audits can I run?
You can run up to 20 audits a day without an account, or 60 a day after signing in.