Can a sitemap lastmod date be in the future?
Rubric check: sitemap lastmod in the future (check id sitemap_lastmod_future)
No. <lastmod> should say when a page last changed, so a date in the future is wrong by definition. Search engines may then ignore your sitemap's dates, and those dates are how they spot updated pages quickly.
Why it matters for SEO
Google says it uses lastmod only when it's consistently accurate. Bing also leans on it to decide what to recrawl. One wrong date is a small problem, but a sitemap full of them teaches search engines to ignore the field.
The usual causes are a timezone bug, scheduled posts listed before they go live, or a plugin that stamps a future date.
Does this matter for ChatGPT and AI Overviews?
This can matter for AI search. Copilot answers from Bing's index, and Bing uses sitemap dates to find fresh content to recrawl, so trusted dates help your updates reach it sooner.
For ChatGPT and AI Overviews, the effect is indirect. Rubric counts this as a minor check.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: A future lastmod is impossible, so search engines may stop trusting the sitemap's dates.
It is read from your XML sitemap.
Every Rubric score starts at 100. When this check fails, it takes up to 3 points off. Even one failing page costs at least 1.5 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 1 of 234 sites where Rubric could judge it (0.4%). That is 1 of 222 judged sites in Rubric's 313-site test set and 0 of 12 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build bbcec7c.)
Real sites: people checked 3 of its findings by hand and 0 were wrong (0%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Open your sitemap (Yoast SEO:
/sitemap_index.xml; Rank Math:/sitemap_index.xml; WordPress core:/wp-sitemap.xml) and find the future dates. - Check Settings > General > Timezone matches your real timezone.
- Check that scheduled posts aren't listed before they publish. If they are, update your SEO plugin, or report it to its developer.
Shopify
Shopify builds the sitemap and its dates itself, and there's no setting to change them. Check your store's timezone in Settings > General is right. If Rubric still reports future dates, contact Shopify support with an example.
Webflow
Webflow builds the auto-generated sitemap and its dates itself. Check the time zone in Site settings > General is right, then republish. If you use a custom sitemap (Site settings > SEO > Indexing, with auto-generate turned off), fix the dates in it by hand.
Custom code
Set lastmod from the page's real last-modified time, in UTC or with an offset:
<url>
<loc>https://example.com/boots</loc>
<lastmod>2026-11-16T09:00:00+00:00</lastmod>
</url>Never set it to the build time or a scheduled date. Leave scheduled pages out until they go live.