Update date or publish date: which one should a search result snippet show?

A search result snippet should show the date that best explains whether the page can still answer the current query.

Publish date and update date answer different questions. Publish date tells when the record first appeared. Update date tells when the page was last reviewed or changed. For evergreen concepts, the original date may be fine if the explanation is stable. For pricing, product limits, regulations, software versions, event schedules, or policy language, update date usually matters more because the answer can expire.

The problem is that update dates can be misleading. A page may update because of a typo, layout change, comment import, or footer refresh. If a snippet shows only “updated today,” a search user may assume the substance was reviewed. That is why the page body should say what changed or what was checked. “Reviewed for API limit values on June 24” is more useful than a generic timestamp.

A good pattern is to show the primary date in the snippet and explain the other date near the top of the page. For example, a tutorial can say “published 2024, reviewed for version 3.2 in 2026.” A policy summary can say “checked against official page on 2026-06-24.” This gives both history and current relevance.

For search packaging, the date should match the query risk. If the query contains “current,” “2026,” “price,” “limit,” “deadline,” “support,” or a version number, freshness should be visible. If the query asks for a concept definition, the date can be secondary unless the concept has changed.

The practical rule is: show the date a reader would need before acting. If acting on stale information could cost money, time, access, or compliance risk, make the review date visible.

Update date or publish date: which one should a search result snippet show?

// COMMENTS

ON THIS PAGE