Sitemap lastmod: what it is and how to set it correctly

Sitemap lastmod is an optional tag in your sitemap.xml that tells search engines when a page last changed in a meaningful way. It looks like a minor detail, but on sites with many URLs it helps crawlers decide what to recrawl first, and it only works if the dates are honest.

What the lastmod tag looks like

Each entry in an XML sitemap has a required loc tag with the page address. Next to it you can add lastmod, for example <lastmod>2026-10-01</lastmod>. In effect it says to the search engine: this page last changed on this date.

The value follows the W3C Datetime format: year, month and day separated by hyphens. You can add a time and a time zone, which for Tashkent is +05:00, but a plain date is enough for most sites. A format like 20.10.2026 is invalid and may simply be ignored.

How search engines use lastmod

Google states that it uses lastmod when the value is consistently and verifiably accurate. If a crawler visits pages marked as updated, finds nothing new several times, it stops trusting the tag across the whole site. Yandex also treats the date as a hint, not a command.

Google ignores priority and changefreq. That makes lastmod the only optional sitemap field that can realistically influence crawl scheduling, so it is the one worth getting right.

When to update the date and when to leave it

The rule is simple: change the date when something a visitor reads in the main part of the page has changed. Everything else is noise.

  • the main text was rewritten or expanded
  • price, availability, delivery terms or specifications changed
  • a new section, FAQ block or set of photos was added
  • an important fact was corrected, such as an address, phone number or opening hours

What does not count as a change

Leave the date alone if only the copyright year in the footer, a related-posts block, a sidebar banner, a view counter or the order of menu items changed. For the visitor the page is the same, and a crawler will most likely see the same content.

If an article shows a visible “Updated” date, it should match lastmod. Bumping it just to look fresh is pointless, because search engines compare versions of the page and notice when the text is unchanged.

Common sitemap lastmod mistakes

In practice the problem is rarely understanding and almost always generator configuration. These are the cases that come up most:

  • every page gets today’s date or the date the file was built
  • the date never changes even though pages are edited every week
  • dates in the future because the server time zone is wrong
  • an online shop stores price and stock in a separate table, so the product date never updates
  • lastmod in the sitemap disagrees with dateModified in the article’s structured data

Does a small or bilingual site need it?

A brochure site for a clinic or studio with a handful of rarely edited pages gains almost nothing from lastmod, since crawlers revisit such sites regularly anyway. The benefit shows up on online shops, classifieds-style catalogues and blogs with large archives, where fresh edits must not get lost among thousands of unchanged URLs.

If you run Russian and Uzbek versions, each is a separate URL with its own date. Update prices in the Russian version of a service page and only that date changes. When shared details such as contacts or a price list change, update both versions together.

How to set it up and check it

Most CMS platforms store a modified date for every record. Make sure your plugin or generator reads that field rather than the system clock. On a custom-built site, store the time of the last meaningful change in the database and output it into the sitemap.

To check, open sitemap.xml in a browser and compare the dates of a few pages with their real edit history. If every URL carries the same recent date, the generator is misconfigured. After fixing it, resubmit the sitemap in Google Search Console and Yandex Webmaster.

If your site has many pages and you are not sure the sitemap is working for you, this is easy to review as part of a technical SEO audit. At markdev we check details like this alongside indexing and site structure, so you are welcome to discuss your project and see what is worth fixing first.

FAQ

Is lastmod required in a sitemap?

No, it is optional. But if you include it, the dates need to be accurate. Wrong values are worse than none, because the search engine stops trusting your sitemap.

What date format should lastmod use?

W3C Datetime: YYYY-MM-DD, for example 2026-10-01. You can add a time and a time zone if needed, which for Tashkent is +05:00.

Does lastmod improve my rankings?

Not directly. It only hints which pages deserve an earlier recrawl. Rankings depend on page content, quality and many other factors.

What should I do if every page has the same lastmod date?

That usually means the generator uses the build date. Connect it to the real modified-date field in your CMS or database, rebuild the sitemap and resubmit it in Search Console and Yandex Webmaster.

Let’s look at your task for free

Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.