HTTP Last-Modified Headers: Keep Content Dates Accurate

The HTTP Last-Modified response header tells a client when the server believes a resource was last changed. It can support conditional requests and help crawlers understand whether a page may need another fetch. It is useful only when it reflects a real change: a timestamp that updates on every request or stays stale after a substantial edit misstates the page’s history.

Choose what counts as a meaningful modification

Decide which changes should update the page’s modification time. A substantive content revision, updated data, or changed page structure may qualify; a request counter, cache refresh, or analytics event usually does not. Align the header with the content-management system’s editorial timestamp where practical.

Keep the response header and visible publication or update dates consistent in meaning. The publication date answers when the item first appeared; the last-modified date answers when its content last materially changed. Do not replace one with the other.

• Use a stable timestamp tied to the resource version.
• Avoid changing it just because the page was requested or cached.
• Use a consistent time zone and valid HTTP date format.
• Document which editorial changes advance the date.

Test conditional requests and caches

Check the header on representative pages and verify that a client sending an If-Modified-Since request receives an appropriate response for unchanged content. Test how the origin, CDN, and application interact; a cache can serve a different timestamp than the CMS intended.

Inspect canonical URLs, redirects, and localized versions as separate resources. Make sure a redirect does not imply that two pages share the same content history when they do not.

Treat dates as crawl information, not a guarantee

A consistent modification signal can help infrastructure avoid unnecessary transfers and can inform a crawler’s scheduling. It does not guarantee that a search engine will recrawl, index, or rank a page differently. Accurate content and accessible pages remain necessary.

Monitor changes to headers after deployments and bulk imports. If every URL suddenly receives the same new date, investigate before assuming that all pages were meaningfully updated.