For articles, news and blog posts, Google recommends the datePublished and dateModified properties in , each in ISO 8601 format and ideally with a time zone. datePublished stays the original publication date, while dateModified shows the last relevant content revision.

Key principles:

  • The visible date on the page should not be contradictory.
  • Multiple conflicting dates can confuse.
  • The should not be set automatically on every deploy or template change.

As with lastmod in the , the date should reflect real, significant changes. A new date without a real update is a pseudo-update that can damage credibility.

Where the modification date appears #

The same date should be consistent in three places: the visible "updated" line on the page, the dateModified property in Article schema, and the lastmod value in the . Search engines cross-check these signals; contradictions make all of them less trustworthy.

Common mistakes #

The classic anti-pattern is bumping the date without changing the content — engines compare the stored copy and learn to ignore your dates. Equally common: a that rewrites dateModified on every deploy, so every page claims to be brand new. Update the date only when the substance of the page actually changed.