Content Freshness Audit

What this tool does

Summarises the age of sitemap lastmod values and samples the 12 most recently modified pages to compare sitemap dates with on-page dates and Last-Modified headers.

Who should use it

Editors planning content reviews.

How it works

The sitemap is parsed for lastmod, ages are bucketed, and sampled pages are scanned for article:modified_time, <time datetime>, JSON-LD dateModified and the Last-Modified header.

How to use it

1. Enter the full address of the page or site, including https://.
2. Press the run button. The check makes live requests from our server and can take up to about 30 seconds.
3. Read the findings first, then open the tables for detail. Each finding has a severity and a suggested fix.
4. Copy or download the results if the tool offers it, fix the issues on your site and run the check again to confirm.

Practical example

A sitemap where every URL has the same lastmod is flagged because the date is probably not meaningful.

Understanding the results

An old date is not bad if the page is still accurate. Mismatched dates suggest unreliable lastmod values.

Limitations

This is a live check made from our server within a time and size budget; it examines a sample, not necessarily the entire site. Dates are what the site reports; the tool cannot know whether content really changed.

Accuracy and report transparency

Findings come from a real HTTP request made by our server. The result panel shows the checked URL, the UTC time of the check and the data source, and separates measured findings from limitations. We do not show random or sample metrics.

Privacy

The URL you enter is used only to make the request and is not stored in our database. Results may be cached for about ten minutes to limit repeat requests, and the checker blocks local and private network addresses. See the Privacy Policy.