Your Sitemap Says One Thing. Google Sees Another.
A sitemap makes a claim: these are your important pages, and here’s roughly when they last changed. Google doesn’t have to believe any of it, and increasingly, it doesn’t. When a sitemap contradicts what the site itself says, the cost isn’t abstract, it’s crawl budget spent on the wrong pages and money pages that never get looked at as often as they should.
A sitemap is a hint, not an instruction
The sitemap protocol is just XML, a list of URLs with some optional metadata. Google is explicit that submitting a sitemap doesn’t guarantee crawling, indexing, or ranking. It’s a hint about what exists and what might be worth revisiting, weighed against everything else Google already knows about the site.
That framing matters because a lot of sitemap advice treats it like a lever you pull to control indexing. It isn’t. It’s one input, and a sitemap that contradicts other signals on the site doesn’t override them, it just looks unreliable.
The lastmod field that gets you ignored
Most sitemap generators stamp every URL with the current date on every build, whether the page actually changed or not. Google’s own guidance says it uses the lastmod value only “if it’s consistently and verifiably accurate,” and Google’s Gary Illyes has described the trust mechanism as binary: the whole field gets trusted or it gets ignored, not weighted somewhere in between.
That means a sitemap that lies about lastmod even occasionally can lose the benefit of the field entirely, on every URL, not just the inaccurate ones. For a large site, lastmod is one of the few signals that tells crawlers which of thousands of pages actually changed since the last pass. Losing it because a build script stamps every page with today’s date is a self-inflicted cost most sites never notice they’re paying.
When your sitemap contradicts your own canonical tags
A canonical tag is a separate claim, made on the page itself rather than in the sitemap: this specific URL is the authoritative version among any duplicates. Like sitemaps, Google treats canonical tags as a strong hint, not a strict rule, and it can choose a different canonical than the one specified if other signals disagree strongly enough.
None of what follows is exotic. It’s the kind of thing that accumulates quietly as a site adds filtering, pagination, and tracking parameters over time, with nobody checking whether the sitemap and the canonical tags still agree with each other. It’s the same pattern we found when we audited our own site’s structured data: the gaps weren’t on the pages anyone actively maintains, they were on the ones nobody thought to check twice.
Canonical mismatches
A sitemap lists a URL that carries a canonical tag pointing somewhere else entirely, sending Google two different answers to “what is this page.”
The pagination trap
Paginated listing pages get canonicalized back to page one, which quietly tells Google that pages two and three don’t need to exist independently, even when they contain products or content page one doesn’t.
Sitemap entries blocked by robots.txt
A sitemap includes URLs that robots.txt blocks from being crawled at all, asking Google to prioritize a page it’s also being told to stay away from.
Parameterized URLs and wasted crawl attention
Ecommerce and content sites that generate URLs with sorting or tracking parameters, ?sort=price or ?utm_source=newsletter appended to an otherwise normal page, run into a quieter version of the same problem. If that parameterized URL ends up in the sitemap while the canonical tag correctly points to the clean version without the parameters, the sitemap is effectively asking Google to prioritize crawling a URL that immediately defers to a different one. It isn’t wrong exactly, but it’s wasted crawl attention on a page that was never meant to be the authoritative version in the first place.
Does having a sitemap guarantee my pages get indexed?
No. A sitemap increases the odds a page gets noticed, particularly on a large site where not every page is well linked internally, but it doesn’t force indexing and it doesn’t override contradictory signals elsewhere on the site. A sitemap that’s technically valid but full of stale dates, blocked URLs, or canonical conflicts is often worse than a smaller, accurate one.
A quick self-audit
- Only include URLs that return a 200 status and aren’t blocked by
robots.txt. Redirects, errors, and blocked pages in a sitemap are contradictory signals. - Check that
lastmodactually reflects real content changes, not a build timestamp applied to every URL regardless of whether anything changed. - Confirm every URL in the sitemap matches its own canonical tag. A sitemap entry that points to a non-canonical URL is telling Google two different things about the same page.
- Reconsider blanket-canonicalizing paginated pages back to page one. If those pages have content the first page doesn’t, that canonical is hiding it.
Finding these discrepancies by hand across a site with thousands of URLs isn’t realistic. kant.au’s Site Analysis feature crawls your site and compares what it actually finds against your sitemap and your canonical tags, flagging conflicts automatically instead of leaving them for someone to stumble on. Want to see where your sitemap and your site actually disagree? Start a free 14-day trial and find out.
Google Search Central: Sitemaps overview
Google Search Central: Consolidate duplicate URLs (canonicalization)