In August 2026 Webflow started writing a lastmod date beside every URL in its auto-generated sitemaps. The change shipped platform-wide, it costs nothing, and for most sites it arrived silently with the next publish. It is worth two minutes of your attention because of who reads those dates.
What a lastmod date is
A sitemap is the file at yoursite.com/sitemap.xml that lists every page you want search engines to know about. The lastmod field sits beside each URL and states when that page last changed.
Before this change, a Webflow sitemap listed URLs with no dates. A crawler had to guess which pages were fresh, and it guessed by re-crawling everything on its own schedule. With dates in place, a crawler can see at a glance which three pages changed this week and fetch those first.
Why the timing points at AI engines
Webflow’s own release note says the timestamps help “search and AI answer engines” find fresh content faster. That second audience is the reason this matters now.
AI answer engines reward freshness more visibly than classic search ever did. An AI Overview or a ChatGPT answer prefers a page it believes is current, and a dated sitemap is the cheapest possible way to prove currency. Google’s Preferred Sources feature makes the same point from another angle: its picker drops sites that are not updated regularly, so the signals that show updating now carry real weight. We covered that feature in Google Preferred Sources: what it is and how to use it.
We checked the sitemaps of three Webflow sites we manage the week the change landed. All three carried the new dates on every URL, from 191 entries on the smallest to just over 1,000 on the largest, with no action taken by anyone.
Who gets it automatically
Every Webflow site using the auto-generated sitemap gets lastmod on its next site publish. The sitemap regenerates at publish time, so the only sites still serving dateless sitemaps are ones that have not published since the change shipped.
Two groups miss out. Sites with a custom, hand-written sitemap pasted into their settings keep serving exactly what was pasted, dates or none. And sites on other platforms get whatever their platform emits: several static-site generators still ship sitemaps with no dates at all unless configured, which is worth checking on your own stack today.
What to do with this
- Open yoursite.com/sitemap.xml and look for lastmod entries. On a Webflow site with auto-sitemap on, publishing the site is the whole fix.
- If you maintain a custom sitemap, weigh whether the reasons for it still stand. The auto-generated file now does something yours probably does not.
- Treat the dates as a promise you have to keep. A lastmod that updates when nothing changed teaches crawlers to ignore your dates. Real updates, honestly dated, are the signal.
Freshness signals are one strand of the wider technical layer we run for clients: sitemaps, structured data, crawl access and indexing, measured monthly. The full picture is on the Technical SEO service page.
Frequently asked questions
Does lastmod improve rankings?
It improves crawl efficiency: engines find your changed pages sooner. Faster discovery of fresh content is an advantage in AI answers and news-like results, and the dates on their own move no ranking.
Do I need to do anything on my Webflow site?
Publish the site. The sitemap regenerates with dates at publish time, and every publish after that keeps them current.
What about the pages I never update?
They keep an old lastmod, and that is correct. Honest dates are the point: a crawler that trusts your dates spends its visits on the pages that actually changed.
