A Date Is a Promise That the Page Changed. Don't Make It Falsely

The finding says a page has no freshness signal: no datePublished, no dateModified, nothing that tells a machine when the content was written or last really changed. For anything time-sensitive, that is a missing fact a reader and a crawler both want. For anything evergreen, it may not matter at all.

What makes this finding worth a second of thought rather than a reflex is the failure mode. The wrong fix, bumping the date to look recent without changing anything, is worse than leaving it blank, and it is the single most common thing people do when they see this.

Why this matters for AI traffic

A date is context. “Last updated March 2026” tells a person the advice is current and tells an answer engine the passage is safe to quote for a question where recency matters. This is the mechanism behind what SEOs call query-deserves-freshness: for some questions, a recent, relevant page beats an older, more authoritative one, and the date is how the engine knows which is which. AI answers lean on this hard, because citing stale information is exactly the failure they most want to avoid.

Google reads the signal from structured data. Its guidance is to “specify the datePublished and/or dateModified fields” using an Article or BlogPosting type, and to show a visible date to match, labeled plainly like “Last updated: Feb 14, 2018.” So the fix, where it applies, is small: a real date in the markup and the same date on the page.

The trap this finding walks people into

Here is the part every other explanation of this finding skips. Freshness helps only when the content actually got fresher. Google’s own John Mueller has been blunt that artificially bumping dates is “an old trick” that does not help a page rank, and that only a real change counts: “an update to the main content, the structured data, or links on the page is generally considered significant, however an update to the copyright date is not.”

Worse than useless, it can backfire. Mueller has also warned that automatically freshening dates, in your sitemap’s lastmod or your dateModified, can make it harder for Google to find your genuine updates, because you have taught it that your dates are noise. A site that stamps today’s date on every page every night has not made itself fresh. It has made its freshness signal worthless, and possibly trained the crawler to ignore the one update that was real.

Google states the rule directly: “The dates must describe the publication or update date of the page, not the stories or events described therein,” and the visible date and the structured date must match. A date is a claim. Make it a true one.

When is it worth fixing, and when should you skip it?

Fix it when:

• The page is time-sensitive: news, prices, anything where a reader’s first question is “is this still true.” Here the date is load-bearing and its absence costs you.
• You genuinely maintain the page. If you update it, say so with an honest dateModified. That is the case the signal was built for.

Skip it, or leave it minimal, when:

• The page is evergreen and you are not touching it. A datePublished is fine; a dateModified you would have to fake is not. No date beats a lying one.
• You would be tempted to automate the date. Do not. An auto-bumped date is the failure mode this whole finding is a trap for.

The honest tradeoff: on a page you actually keep current, this is a real, cheap signal and worth adding. On a page you do not maintain, the finding is asking for a promise you cannot keep, and the right answer is to leave it alone rather than manufacture freshness. I would add honest dates to the pages I update and ignore the finding on the ones I do not.

Adding a real date to a page’s structured data is markup, and Get AI Traffic writes it with upsert_schema when the page carries Article or BlogPosting data, or through set_content for the visible date the markup has to match. Note the limit that is the whole point of this guide: neither tool knows whether the page actually changed. Only you do, and the date is only worth anything if it is true.

Frequently asked questions

Does adding a date help my ranking? Only when it reflects a real change. For time-sensitive queries a genuine recent date is a strong signal (query-deserves-freshness). A date bumped without a content change does nothing, and Google’s John Mueller has called that an old trick that does not work.

Should I update the date every time I touch the page? Only for changes that matter, main content, structured data, links. Not for shuffling an image or bumping a copyright year. Google draws that line explicitly, and small cosmetic edits do not count.

Can faking freshness hurt me? Yes. Automatically freshening dates can make it harder for Google to find your genuine updates, because it stops trusting your dates as a signal. You can train the crawler to ignore the one update that was real.

Do the visible date and the structured data need to match? Yes. Google requires that the date in your markup matches the date shown to users. A mismatch is a defect, not a subtlety.

datePublished or dateModified? Publish date always, if the page is dated at all. Modified date only when the page really was modified in a way worth signaling. On an evergreen page you never touch, a publish date alone is honest and sufficient.

Sources

• Google Search Central: Article structured data and dates
• Search Engine Journal: Google’s John Mueller on updating dates and SEO
• Google Search Central: Article (Article, NewsArticle, BlogPosting) structured data