Will showing an updated date make AI more willing to cite a page?
Possibly a little, but no official statement guarantees it. What data exists: Ahrefs analysed about 17 million AI citations, and the URLs AI assistants cite are on average somewhat newer than Google's organic results; but the same data shows that cited pages are still nearly 3 years old on average, so freshness is one factor among many. The updated date should be true: change it only when the content really changed, so the date is useful to you.
| Metric | URLs cited by AI assistants | Google organic results |
|---|---|---|
| Average days since publication | 1064 days | 1432 days |
| Average days since last update | 909 days | 1047 days |
The data comes from the study Ahrefs published on 2025-07-28 (about 16.97 million cited URLs, ChatGPT, Perplexity, Copilot and Gemini combined; checked 2026-11-06). The author reports that URLs are 25.7% newer by publication date and 13.1% apart by update date.
Three things to note. First, ChatGPT shows the strongest preference for newer content, while Google AI Overviews are the exception: the pages they cite are on average 16 days older than organic results. Second, the author himself writes that AI assistants, like traditional search, prefer long-lived content. Third, the article's table and text disagree on two figures; we quote only the text.
What is the difference between a visible date, dateModified and sitemap lastmod?
They are three different places read by three kinds of reader: the visible date is for people, dateModified is for search engines reading structured data, and lastmod is for crawlers deciding whether to fetch again. All three should say the same thing.
| Location | Who reads it | What the official docs say | How to write it |
|---|---|---|---|
| Visible date on the page | Readers, and also one of the clues search engines use for dates | Google advises labelling with text such as "Publish" and "Last updated", keeping it consistent with structured data and keeping other dates on the page to a minimum | One "published" and one "updated" date, near the title |
| Structured data datePublished and dateModified | Search engines that read structured data | Google advises writing these two fields in Article and similar types, consistent with the visible date | An ISO 8601 date, the same day as the date on the page |
| sitemap lastmod | Crawlers deciding whether to fetch again | Google uses it only when it is consistently and verifiably accurate; Bing treats it as a key signal | The time the page content really changed; a full timestamp with time zone is safer |
Google's documentation also says it does not rely on a single date factor, because every factor can go wrong. So getting all three right matters more than doing only one. How to write a trustworthy lastmod is covered separately in how to write a trustworthy sitemap lastmod and is not repeated here.
Google's documentation does not say whether a small edit should update the date, and does not mention sitemaps. Our rule is practice, not an official requirement: fixing punctuation, styling or the footer year does not count as an update.
How do the three dates line up on one page? A real MochiStamp example
mochistamp.com/en/guide/size (read 2026-11-06) is a MochiStamp guide to LINE sticker sizes. On that one page:
| Location | Value read |
|---|---|
| Visible date on the page | Published 2026-10-16 · Updated 2026-11-05 |
| Article structured data | datePublished 2026-10-16 · dateModified 2026-11-05 |
| lastmod of the English and Japanese pages in the sitemap | 2026-11-05T23:01:07+09:00 |
| lastmod of the Traditional and Simplified Chinese pages in the sitemap | 2026-11-03T09:57:07+09:00 |
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "LINE sticker size and format guide",
"datePublished": "2026-10-16",
"dateModified": "2026-11-05"
}
All three say the same day, and each language version has its own lastmod: the English and Japanese versions of this page changed on 5 November, while the Traditional and Simplified Chinese versions last changed on 3 November. How lastmod is computed from page content is in how to write a trustworthy sitemap lastmod; here we look only at the result.
The whole sitemap (mochistamp.com/sitemap.xml, read 2026-11-06) has 938 URLs and lastmod is not a single date: 60 on 10-16, 40 on 10-28, 25 on 10-30, 2 on 11-03, 1 on 11-04 and 810 on 11-05. A crawler can tell from this which pages did not change.
For comparison, the kagentx.com site itself: on its guides, the visible "updated" date and the Article dateModified come from one variable, so they agree; but the lastmod of all 275 URLs in kagentx.com/sitemap.xml is the build day (all 2026-11-05 when read on 2026-11-06), so it cannot tell pages apart. That is a gap on our side, not yet fixed.
How do you make dates useful to AI without faking them?
1. Change the date only when the page really changed
Body text, numbers, structured data or links changed. Do not change the publication date just to look new; Ahrefs' article relays a warning on this from Google's John Mueller, whose exact words we did not check.
2. Write both "published" and "updated"
With only "updated", readers may think it is a new article; write both so people and crawlers can tell them apart.
3. Use one source for all three
Generate the visible date, dateModified and lastmod from the same "last real change of the page" value; do not type them three times.
4. Give a source and date for numbers in the content
"Checked 2026-11" is more specific than an updated date, and it is a sentence AI can lift directly; see How to write content AI will quote.
5. Spot-check after going live
Open the page, its structured data and the sitemap and check the three show the same day; for how to write the structured data see How to write structured data.
FAQ
Does changing the updated date every month help?
No data says it does, and you should not. Changing the date when the content has not changed makes lastmod untrustworthy, and Google's documentation says it uses lastmod only when it is consistently and verifiably accurate.
What happens if the visible date and dateModified differ?
Google's documentation asks that they be consistent. It does not say what it relies on when they differ, so do not let them differ.
Do Google AI Overviews prefer newer content?
In Ahrefs' data, AI Overviews are the exception: the pages they cite are on average 16 days older than organic results, making them the least affected by freshness.
Should pages other than news show an updated date?
We recommend it. For content that changes, such as data, prices and specifications, "updated" and a checked date are what readers and AI use to judge whether it can still be trusted.
Is it enough to write only lastmod and no visible date?
You can, but all three agreeing is safer. Google's documentation says it does not rely on a single date factor.
Sources
- Google Search Central · Add a Byline Date to Google Search Results （checked 2026-11-06）
- Ahrefs · Do AI Assistants Prefer to Cite Fresher Content? （Published 2025-07-28, checked 2026-11-06, about 17 million citations）
- Google Search Central · Build and submit a sitemap （Viewed 2026-11-05 (see the lastmod guide)）
- MochiStamp · LINE sticker size and format guide （Read 2026-11-06）
- MochiStamp · sitemap.xml （Read 2026-11-06, 938 URLs）
- kagentx evaluations: the data on the case study pages; each example gives its date.