Content freshness and AI citations: dates, dateModified and lastmod
Perplexity cited content about 3x fresher than Google in one study. Put an accurate date in three places, visible, schema and sitemap, and never fake it.
LLaunchScaler·Published ·8 min read
Freshness matters for AI citations, most visibly on Perplexity: in a March 2026 study, the median age of Perplexity's top-3 cited sources for SaaS, tech and e-commerce queries was 32.5 days, against 108.2 days for Google's top results, about 3.3 times fresher. To count as a freshness signal, a date has to appear in three places that agree: visible on the page, in Article schema as datePublished and dateModified, and in your sitemap as lastmod.
It also has to be true. Google's guidance on helpful content warns against changing dates when the content has not substantially changed. Below is the evidence, the markup for each place, and the date tricks to avoid, checked in September 2026.
Does content freshness matter for AI search?
For some engines and topics, yes. One public measurement compares Perplexity with Google and finds Perplexity's cited sources much newer across every topic speed tested. Microsoft says the same about its own AI answers: "Regular updates help ensure AI systems reference the most current version of your content."
The study, published by AI+Automation in March 2026, pulled the top-3 citations from Perplexity through its API and Google's top results through the Custom Search API, for queries in three "topic velocity" tiers:
Topic velocity
Median age of Perplexity's top-3 sources
Median age of Google's top-3 results
Difference
High (news, finance, sports)
1.8 days
28.6 days
16x fresher
Questions, answered
What people ask about this
01
Does content freshness matter for AI search?
The evidence says it does for some engines. In a March 2026 study, the median age of Perplexity's top-3 cited sources for SaaS, tech and e-commerce queries was 32.5 days, against 108.2 days for Google's top results. Microsoft also tells publishers that regular updates help AI systems reference the current version of a page.
Medium (SaaS reviews, tech comparisons, e-commerce)
32.5 days
108.2 days
3.3x fresher
Low (history, education, evergreen reference)
84.1 days
1,089.7 days
13x fresher
Read it as one author's measurement, not a law of every engine. It compares Perplexity's citations with Google's classic results, not with AI Overviews. The direction is consistent with what Microsoft and Bing tell publishers, and the medium tier is the one that covers SaaS reviews and tech comparisons. How Perplexity chooses sources more broadly is in how to get cited by Perplexity.
Where does a date need to appear to count as a freshness signal?
In three places, each read by different systems: a visible, labelled date for readers and parsers; datePublished and dateModified in the page's Article JSON-LD; and lastmod in the XML sitemap for crawlers deciding what to refetch. Google says its systems "look at several factors" because "all factors can be prone to issues," so one date alone is weak.
Where
What to put there
Who reads it
On the page
"Published" or "Last updated" with the date, in a <time datetime="..."> element
Readers, and any system that parses the HTML
Article JSON-LD
datePublished and dateModified in ISO 8601
Search engines and other structured-data parsers
XML sitemap
<lastmod> for the URL, set to the page's real last change
Crawlers deciding which URLs to refetch
Bing adds a fourth, technical signal: "freshness signals like accurate lastmod values and HTTP validation headers such as ETags help Bing detect content changes more reliably."
How do you add a visible date to a page?
Put a labelled date near the top of the article, and wrap it in a <time> element whose datetime attribute holds the machine-readable form. Google asks for a user-visible date featured "prominently," labelled with text like "Published" or "Last updated." MDN describes datetime as translating dates "into machine-readable format."
<p>
Published <time datetime="2026-03-02">March 2, 2026</time> ·
Last updated <time datetime="2026-09-10">September 10, 2026</time>
</p>
The datetime value can be a date alone (2026-09-10) or a date and time with an offset (2026-09-10T14:30:00+02:00). Google also recommends you "Minimize the presence of other dates on the page," so dates in sidebars, related-post lists or footers do not compete with the one you want read.
How do you add datePublished and dateModified to Article schema?
Add both properties to the page's Article or BlogPosting JSON-LD, in ISO 8601 with a timezone, matching the visible dates. Google's Article documentation recommends dateModified "if you want to provide more accurate date information to Google," and says that without timezone information it defaults to the timezone Googlebot uses.
Google's byline date rules apply to both places at once: "The date is required; the time is not," dates must be consistent between the visible and structured versions, and you should not "specify future dates, or the date of the action described on the page." The author side of this block is covered in Article schema and author markup.
How should sitemap lastmod work?
Set lastmod to the date the page's content last changed, and only change it when the content changes. The sitemap protocol is explicit: "the date must be set to the date the linked page was last modified, not when the sitemap is generated." Google says it uses lastmod only "if it's consistently and verifiably" accurate.
The most common failure is a sitemap generator that stamps every URL with the build time. Every deploy then tells crawlers that every page changed, which fails Google's test of a value that is consistently and verifiably accurate. Google also ignores <priority> and <changefreq>, so setting them does nothing. Bing asks for sitemaps that "Include freshness signals (such as lastmod) where applicable" and list only canonical URLs. More detail is in sitemap lastmod.
What date tricks does Google warn against?
Changing the date without changing the content. Google's helpful-content questions include "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" and a second about adding or removing lots of content "primarily because you believe it will help your search rankings overall by somehow making your site seem 'fresh?'" Its answer: "No, it won't." Google lists these under content made mainly for search engines, and says answering yes to such questions "is a warning sign that you should reevaluate how you're creating content."
Avoid each of these:
Bumping "Last updated" or dateModified for a typo fix, a new ad slot or a template change.
Setting lastmod to the sitemap's generation time.
Showing a future date, or the date of an event the page describes, as its publish date.
Removing the original publish date so only the update date shows, when the update was minor.
Mass-rewriting old posts only to reset their dates.
Beyond Google's wording, faking freshness also undermines the signal for your real updates: once a site's dates move without content moving, no system has a reason to trust them. When and how to update an old post's date honestly is in should you update a blog post's date?
What counts as a substantive update?
A change a returning reader would notice and care about: new or corrected facts, new data, changed prices or plan names, steps that now work differently, a new section answering a question the page did not cover, or removed advice that no longer applies. Fixing a typo, swapping an image or rewording a sentence is maintenance, not an update.
A practical rule for teams: record what changed whenever you change dateModified. If you cannot write one sentence describing the change for a reader, it did not earn a new date. For pages that compare products or quote prices, a scheduled review every few months keeps the facts current and gives you honest reasons to update.
Which pages need freshness signals most?
Pages whose facts change, and pages that compete on questions where newer answers win. Comparison pages, pricing pages, "best tools" roundups, integration guides and anything quoting numbers go stale fastest, and they sit in the medium-velocity tier where the study found Perplexity's sources about a month old against more than three months for Google's.
Publish date; update date only after a real revision
Legal pages
On policy changes
Effective date stated in the text
Evergreen pages do not need a fresh date to be cited; they need a correct one. The low-velocity tier in the study shows Perplexity still citing sources that were months old when the question did not change.
How do you keep the three dates in sync?
Drive all three from one field that changes only when the content does. In most CMSes and frameworks that is the content's own modified timestamp, not the file's build time. Render the visible date, the JSON-LD dateModified and the sitemap lastmod from that one value, then check a live page.
Store published_at and content_updated_at on each post, and update the second only on substantive edits.
Render the visible dates from those fields inside <time datetime>.
Render datePublished and dateModified in the JSON-LD from the same fields.
Generate the sitemap's lastmod from content_updated_at.
After deploying, fetch the page and the sitemap with curl and confirm the three dates match.
For Bing, send changed URLs through IndexNow when you publish an update, as its guidelines recommend.
Check your freshness signals
LaunchScaler's free scan checks whether your sitemap exists, is discoverable and carries lastmod. The full audit adds the on-page freshness check: whether a page carries a visible date, a <time datetime> element or datePublished and dateModified in its schema, alongside the answer-engine panel that puts 10 buyer questions to 7 engines. It costs $19 once for your domain and unlocks on your report. Run the free scan first, then open the full audit.
02
What is dateModified in schema?
dateModified is the schema.org property for the date on which a creative work, such as an Article or BlogPosting, was most recently modified; schema.org reports it in use on 10M+ domains. Google recommends it in Article structured data, in ISO 8601 format with a timezone, and asks that it match the date shown on the page.
03
Where should the date appear on a page?
In three places: a visible date labelled Published or Last updated, ideally wrapped in a time element with a datetime attribute; datePublished and dateModified in Article JSON-LD; and lastmod in your XML sitemap. All three should agree.
04
Can I change a post's date to make it look fresh?
Google's guidance on helpful content asks whether you are changing the date of pages to make them seem fresh when the content has not substantially changed, and treats it as a sign of search-engine-first content. Change the date only when you change the content.
05
Does Google use the lastmod date in sitemaps?
Only when it can trust it. Google says it uses lastmod if the value is consistently and verifiably accurate, for example when it matches the page's actual last modification. It ignores priority and changefreq.
