Missing Lastmod Tags in Your Sitemap
The <lastmod> tag tells Google when a page was last meaningfully updated. Without it, Google has to rely on heuristics to decide what's worth re-crawling - which usually means freshly updated content sits in crawl limbo for days or weeks before Google notices the changes.
What is this error?
Missing lastmod means one or more <url> entries in your sitemap.xml don't include the <lastmod> child tag. A valid entry looks like: <url><loc>https://example.com/page</loc><lastmod>2024-01-15</lastmod></url>. Also flagged as errors: lastmod values in the wrong format (like DD/MM/YYYY), impossible future dates, or values older than 10 years.
Why does it happen?
Many sitemap generators skip lastmod entirely because it's optional. CMS platforms like Shopify and older WordPress plugin versions default to omitting it. Custom-built generators often fail to read the page's updated_at timestamp from the database, so they either skip the tag or hardcode today's date on every URL - which Google ignores.
Why does it hurt SEO?
Google's Gary Illyes and John Mueller have repeatedly said accurate lastmod is among the most useful sitemap signals. Without it, Google falls back to fetching the page and comparing content hashes - burning crawl budget. News sites, e-commerce product pages, and documentation sites with fast-moving content suffer most: updates can take 5-10x longer to be reflected in search results.
How to detect it
Open your sitemap and look for <url> blocks without a <lastmod> child. Sitemap Fixer parses every entry and gives you three reports: URLs missing lastmod entirely, URLs with malformed lastmod (wrong format), and URLs where lastmod looks suspicious (e.g., every URL has the same date - a sign of a bad generator).
How to fix it
1. In your database or CMS, identify the updated_at or modified_date column for each page. 2. Update the sitemap generator to read that column and emit <lastmod> in W3C datetime format (YYYY-MM-DD or full ISO 8601). 3. Only update lastmod when content meaningfully changes - not on every regeneration. 4. Never set lastmod to a future date or today's date for unchanged pages. 5. Regenerate the sitemap and spot-check: edit one page, and confirm its lastmod updates. 6. Resubmit in Search Console and monitor recrawl speed on updated pages.
Real-world example
A recipe blog updated 200 top-performing posts with fresh images and content but saw no ranking movement for 6 weeks. Their sitemap had no lastmod tags. After adding accurate lastmod values from their WordPress post_modified column, Google recrawled all 200 posts within 4 days and rankings improved on 73% of them.
Common mistakes
- Setting all lastmod values to today's date on every sitemap build (Google learns to ignore this)
- Using wrong formats like 15/01/2024 or "January 15, 2024" - only W3C datetime is accepted
- Updating lastmod for cosmetic-only changes (CSS tweaks, header changes) that don't affect page content