Changing the date isn't updating the page

The article is two years old, so you change its date to today and call it updated. Maybe a plugin does it for you every time anything is saved. Google's guidance asks about this exact habit, and its sitemap documentation says it only uses dates it can verify.

Google asks about it by name

Google's guide to creating helpful, reliable, people-first content has a section on avoiding search engine-first content, with a list of warning signs. One asks whether you're changing the date of pages "to make them seem fresh when the content has not substantially changed." Another in the same list asks whether you're adding or removing lots of content to make the site seem fresh, and the page answers that one itself: no, it won't help your rankings.

A new date on the same words isn't an update. It's a claim the page doesn't back up, and readers can tell as soon as they get to a stale fact under a fresh date.

Sitemap lastmod has to be true

The same habit shows up in sitemaps, usually automated. If your build writes today's date into every <lastmod> whether a page changed or not, every date in the file is a guess. Google's sitemap documentation says it uses lastmod only if the value is consistently and verifiably accurate, for example by comparing it with the page's actual last modification. The value should reflect the last significant update: changes to the main content, structured data or links count, and a new copyright date doesn't.

Google's 2023 post on sitemaps says the same. Lastmod means the last significant modification, a small text change in a sidebar or footer isn't one, and the date needs to match reality consistently. If you can't date a page reliably, you can leave lastmod out. I've written more about what else sitemaps get wrong, including the priority tag Google ignores.

The visible date and the structured date

Google's documentation on byline dates says it doesn't depend on a single date factor, because all of them can be prone to issues, and looks at several to estimate when a page was published or significantly updated. What you control is the date people see and the datePublished and dateModified structured data. Google asks you to label dates clearly, with text like "Last updated", to keep the visible and structured dates matching, and not to give future dates.

Schema.org defines dateModified as the date the work was most recently modified. If your template fills it with the current date on every request, it records when someone looked, not when the article changed.

When a new date is honest

Changing the date is fine when the page changed. Google's 2019 post on page dates says that if you update a page significantly, you should also update the visible date, and that you shouldn't artificially freshen a story without adding significant information. New facts, a rewritten section, corrected numbers and new examples are updates. A fixed typo or a new footer year is not.

The fix

  1. Keep two dates. The published date never changes. The updated date changes only when the content does.
  2. Show both, labeled. Put "Published" and "Updated" dates on the page, and the same values in datePublished and dateModified.
  3. Say what changed. One line such as "Updated: new pricing table, removed the retired plugin" tells readers the date means something.
  4. Tie lastmod to content. Generate it from the last real content change, not the build time or the file's save time. If you can't, leave it out.
  5. Turn off auto-bumping. If a plugin or theme refreshes the date on every save, switch that off and set the updated date yourself.
  6. No future dates. Google's byline date guidance says not to use them.

To see what your sitemap is claiming, try Sitemap Inspector (my own product). It finds your sitemap, validates the XML, counts URLs, and checks lastmod freshness and the robots.txt declaration.