CiteRanger CiteRanger
Content FreshnessStructured DataSEO

"Last Updated": How Google Reads dateModified and Visible Dates

How Google picks the date for your page, when a date helps, when it hurts, and how to implement dates that stay honest.

Richard Roth

Richard Roth

Founder & SEO Strategist

October 19, 2026

11 min read

Light interface illustration: an article carrying a green "Last updated" badge, with a calendar and a clock card beside it

The date next to a search result is one of the few things a user sees before clicking. It is also one of the few a site can influence with a single line of markup. That makes it tempting to game, and Google’s documentation on dates reads like it was written by people who have watched sites try. Here is what it actually asks for, what happens when you follow it, and what happens when you do not.

Key Takeaways
  • Google determines the byline date itself from visible dates and structured data; you can influence it, not set it
  • Two rules cover most of the documentation: label the visible date, and keep it consistent with datePublished and dateModified
  • Dates must describe the page, not the story. No future dates, no event dates, and dates that describe a real publication or update
  • A fresh date on stale content fails the rules and the raters. The date is a claim that the page was worked on; make it true
Know when a page actually needs a new date, not just when it is convenient Claim 15 Free Credits

How does Google decide which date to show?

It works it out from the page. Google’s documentation on byline dates opens with a clarification. The date in search results is determined by Google. The site’s job is only to make the right date easy to find. The two sources Google reads are a user-visible date and structured data, and it wants them to agree.

The practical instructions, in Google’s order:

  1. Add a user-visible date and feature it prominently. Labelled with text like “Published” or “Last updated”. The documentation’s examples are as plain as “Published February 4, 2019” and “Last updated: Feb 14, 2018”.
  2. Add structured data. A CreativeWork subtype such as Article or BlogPosting with datePublished and/or dateModified, in ISO 8601 format, ideally with time and timezone.
  3. Keep them consistent. The visible date and the structured date must match. Time and timezone are optional in the visible version even if the markup has them.
  4. Describe the page, not the content. In Google’s words:
Google Search Central, Add a byline date to Google Search results

Don’t specify future dates, or the date of the action described on the page. The dates must describe the publication or update date of the page, not the stories or events described therein.

Source

  1. Minimize other dates on the page. If Google keeps picking the wrong date, remove the competing ones: dates in sidebars, comment timestamps, “related posts” dates.

Google adds that no byline date is guaranteed to appear. Following the guidelines does help its algorithms find and process the information. That is the whole official position: no ranking promise, a clear format, and one rule about honesty.

What does dateModified actually do?

It tells Google when the page was last changed. The byline can then show the update instead of the original publication, and freshness-sensitive queries weigh the page correctly.

Google’s Article structured data documentation lists dateModified as a recommended property. It means the time of the most recent change, and Google recommends including time and timezone. It is recommended, not required, which is itself a hint: the property exists to be accurate when used, not to be present at all costs.

What it does not do:

  • It does not make a page rank for being “fresh”. The freshness systems Google introduced in 2011 apply to queries that expect recent results. The mechanism is explained in Query Deserves Freshness explained. A page on an evergreen query gains nothing from a new date.
  • It does not override the visible date. If the two disagree, Google has to guess, and the documentation asks you to make sure it does not have to.
  • It does not describe the content’s events. A page about a 2024 conference published in 2026 has a 2026 datePublished, not a 2024 one.
Good to Know

“Recommended” in Google’s structured data documentation means the property can add value when present and correct. It does not mean pages without it are penalised. A page with no dateModified is more honest than a page with a wrong one.

When does a page deserve a new date?

When its content changed in a way a reader would care about. The documentation’s rule is that the date must describe “the publication or update date of the page”. An update, in any reasonable reading, is a change to what the page says or shows.

Changes that justify a new dateModified and visible “last updated”:

  • Corrected facts: numbers, prices, versions, laws, names, with sources updated
  • Replaced or added sources
  • New or removed sections
  • Updated screenshots, examples or recommendations
  • Restructured headings that change how the page answers the query

Changes that do not:

  • Fixing a typo or a broken internal link
  • Reformatting, restyling, template changes
  • Republishing the same text with a new year in the title
  • Touching the page in the CMS without changing the content

We laid out the cadence by content type in how often to update content. The date question is downstream of that: first decide whether the page needs an update, do the update, then change the date. Never the other way round.

Richard Roth Founder CiteRanger, SEO Strategist

My test is a sentence. If I can write one honest sentence describing what changed, the page gets a new date and that sentence goes into the change log. If the sentence would be “we changed the date”, it does not. Sites that skip the sentence and keep the date are betting that nobody checks. Raters check, and increasingly, so do AI systems comparing what a page says against what other current sources say.

What happens when dates lie?

Three things, in order of how fast they happen: readers notice, raters notice, and the freshness advantage disappears.

Readers. Stanford’s credibility research found that people assign more credibility to sites that show they were recently updated or reviewed. The flip side follows immediately. A page dated last week that cites a 2022 study as current reads as careless. The reader withdraws exactly the trust the date just bought. We covered the broader pattern in website credibility signals.

Raters. Google’s rater guidelines instruct raters to lower their trust assessment when they find factual inaccuracies. Deception about the site or its content is grounds for the lowest rating. A misleading date is a claim about the page that is not true. Whether a rater treats it as inaccuracy or as deception depends on the pattern, and neither reading helps.

Freshness. If a page’s date says 2026 and its content, sources and numbers say 2022, the signals contradict each other. Google’s guidance to minimise conflicting dates exists because its systems read all the evidence, not only the byline. A date that is contradicted by the page is a date that is not believed.

The honest alternative costs almost nothing. A page that was reviewed and found current can say so: “Reviewed October 2026, no changes needed”. That sentence is true, it tells the reader the page is maintained, and it does not change dateModified, because nothing was modified.

How should dates be implemented?

With one source of truth in the CMS, rendered consistently in three places. For a typical article:

In the visible page:

Published: 19 September 2026 · Updated: 14 October 2026

Both labelled, both prominent, near the byline. The publish date stays; the update date appears only after a real update.

In the structured data:

{
  "@type": "Article",
  "datePublished": "2026-09-19T08:00:00+02:00",
  "dateModified": "2026-10-14T10:30:00+02:00"
}

ISO 8601, with timezone as Google recommends. dateModified equals datePublished until the first real update.

In the Open Graph tags, for consistency across platforms:

<meta property="article:published_time" content="2026-09-19T08:00:00+02:00">
<meta property="article:modified_time" content="2026-10-14T10:30:00+02:00">

Three rules for the implementation:

  1. One field, many outputs. The CMS holds publishDate and updatedDate; templates render all three places from them. Hand-edited dates drift.
  2. updatedDate is set by a person, not by the save button. Most CMS platforms update a “modified” timestamp on every save, including typo fixes and template migrations. Do not feed that timestamp into dateModified. Use an explicit field the editor sets when the content changed.
  3. No other dates near the byline. Sidebar “latest posts” dates, comment timestamps and “related” dates all compete. Google’s advice is to minimise them if the wrong date gets picked.
Quick Tip

Add a short change log at the end of long-lived articles: date, what changed, one line each. It gives readers and raters the evidence behind the “last updated” date, it stops future editors from wondering why a number changed, and it makes “reviewed, no changes” a legitimate entry that keeps the page honest without touching dateModified.

What about the date in the URL or the title?

Leave it out. A date in the URL freezes the page in time and turns every real update into a choice between a misleading URL and a redirect. A year in the title (“Best tools 2024”) does the same, and when the year rolls over, the title is wrong until someone remembers.

If the topic genuinely refreshes every year, keep the URL year-free and let the visible date and the content carry the currency. Where a year in the title is warranted, it should change only when the content has been reviewed for that year. Which brings us back to the opening question: has the page really been updated?

Conclusion

Google’s rules for dates are short. Label the visible date. Match it to the structured data. Describe the page rather than the story, and avoid competing dates. The rule that matters most sits in the phrase about the publication or update date of the page. A date is a claim: that the page was worked on. Make the claim true, and the date is a credibility signal for readers, raters and systems. Make it false, and it is evidence against you.

Decide whether the page needs an update, do the update, write one sentence about what changed, then change the date. In that order.

Frequently asked questions about dates and dateModified

How does Google determine the date shown in search results?
From the page itself: a prominent, labelled user-visible date and structured data such as datePublished and dateModified. Google decides which date to show and does not guarantee one will appear, but consistent, clearly labelled dates help it pick the right one.
Should I update dateModified every time I edit a page?
Only when the content actually changed in a way readers would care about: corrected facts, new sources, new or removed sections, updated examples. Typo fixes, restyling and template changes do not justify a new date. Use an explicit editor-set field, not the CMS's automatic save timestamp.
Does changing the date improve rankings?
Not by itself. Freshness matters for queries that deserve recent results, and only when the content is actually current. A new date on unchanged content contradicts the page's own signals, and Google's guidance requires dates to describe a real publication or update.
Should the visible date match the structured data date?
Yes. Google's documentation explicitly asks for the user-visible date and the structured data values to be consistent. Time and timezone can be omitted from the visible version even if the markup includes them.
Can I show both a published and an updated date?
Yes, and it is the clearest option: keep the original publish date and add a labelled 'Last updated' date after a real update, mirrored in datePublished and dateModified. Until the first real update, dateModified should equal datePublished.
What if I reviewed a page and nothing needed changing?
Say so in the text, for example 'Reviewed October 2026, no changes needed', without changing dateModified. That tells readers and raters the page is maintained while keeping the date honest, since nothing was modified.
Find outdated facts first15 free credits, no cardStart free