Colquhoun.AI
← All guides

Research Guides

Audit Article Dates Without Mistaking a Timestamp for Fresh Research

· Colquhoun.shop editorial

A recent date is easy to display. Recent evidence takes work. When you review a reference article, a competitor guide or your own editorial archive, ask two separate questions: when did the page change, and when were its important claims checked?

Those answers can differ. A pricing paragraph may be obsolete inside a newly redesigned page. A careful explanation may remain accurate years after publication. A date audit should help readers judge relevance, not make every page look new.

Separate the four date signals

Google recommends clearly labeled visible publication or update dates and corresponding structured fields such as datePublished and dateModified. Equivalent visible and structured dates should agree. Google uses multiple signals to estimate byline dates and does not guarantee that a supplied date will appear in search. Dates should describe the page, not a future event discussed in it. Google Search Central byline-date guidance.

A sitemap's lastmod serves another purpose. Google says it uses the value when it is consistently, verifiably accurate and reflects the last significant page update. Changes to main content, structured data or links can qualify; changing a copyright year does not. Google sitemap guidance.

An HTTP Last-Modified header reports when the origin server believes the resource changed and helps clients validate cached copies. It is not, by itself, an editorial sign-off on every statement. That distinction follows from its protocol role rather than from an assumption about the publisher's workflow. MDN Last-Modified reference.

Finally, an evidence-check date is an editorial record: when someone actually revisited a source or tested an assertion. Keep that record even if the review results in no page edit.

Make a claim-level worksheet

Start with five pages that people use to make decisions. Do not begin by changing dates across the entire archive. For each page, record:

Field What to capture
Page Exact URL and title
Visible dates Labels as well as values
Structured dates Publication and modification values, if present
Sitemap date Value for this exact URL, if present
HTTP date Header value, if available
Important claim One statement a reader may rely on
Supporting evidence Direct source URL and relevant passage or test
Last checked Your actual review date
Decision Retain, correct, qualify or remove

A missing field is not permission to invent it. If you cannot access the publisher's revision history, mark the underlying change as unknown. Public timestamps can establish what a page reports, but not everything that happened behind it.

Prioritize by the cost of being wrong

Review volatile decision-making claims first: prices, eligibility, availability, software interfaces and service limits. Then inspect examples and background explanations. This is a practical editorial triage rule, not a search-engine ranking formula.

For each important statement, ask what would falsify it. A current provider pricing page may settle a fee; a screenshot of an old checkout may not. A successful test can support behavior under those test conditions; it does not prove every customer's experience.

Avoid the shortcut of replacing an old year in the title while leaving the evidence untouched. Instead, maintain a short change log that identifies the meaningful revision and its source.

A fictional example

Imagine a guide published in March. Its header reports a November modification, but its visible update label still says March. The guide recommends a plan that its provider discontinued in September.

The first repair is not to make all timestamps November. Verify the replacement plan, correct or remove the recommendation, and record the evidence checked. Then reconcile the page's editorial dates with the real revision. Investigate how the HTTP date is generated separately; a server timestamp may have changed for a different reason.

A useful note would say: “Replaced the discontinued plan recommendation and rechecked current limits.” That gives a reader more information than “Updated for this year.”

Leave a review trail someone can reuse

Finish with the claim reviewed, the evidence consulted, the decision and the responsible editor. Preserve the original publication date when it is known, and distinguish a substantive revision from a review that found no necessary changes.

The objective is not the newest-looking timestamp. It is a page whose dates, claims and supporting evidence tell a coherent story. That makes the article easier for another writer to evaluate and cite without treating a freshness label as proof.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.