An XML sitemap does not index your pages. It helps them to be discovered. The confusion between these two mechanisms leads to misaligned expectations and often to a poorly maintained file that sends contradictory signals to crawlers. Understanding what the sitemap can and cannot do allows for a real SEO leverage, not just a simple technical gesture checked off in an SEO checklist.
Lastmod, changefreq, priority tags: what Google really uses in a sitemap
The sitemap protocol specification provides for three optional tags for each URL: lastmod, changefreq, and priority. In practice, Google completely ignores changefreq and priority. These two tags do not influence the crawl frequency or the ranking of pages.
The lastmod tag, on the other hand, retains a conditional usefulness. It is only taken into account when it reflects a real and significant change in content. Artificially updating this date (re-publishing an article without changes, modifying a space in the code) degrades the reliability of the signal. Googlebot eventually ignores the lastmod of a site that systematically cheats.
We recommend coupling lastmod with a specific editorial trigger: adding a paragraph, updating a data table, redesigning a section. The sitemap file then becomes a reliable communication channel with search engines, not just a simple listing of URLs.
To observe how a structured sitemap organizes its URLs and metadata, the sitemap page of Backlink Links illustrates this logic of a clean and up-to-date file well.
Sitemap cleanup: removed URLs, redirects, and non-canonical pages
A sitemap that references deleted pages, URLs redirected with a 301, or pages with a canonical tag pointing to another address sends contradictory signals to crawlers. This problem is common on e-commerce sites or media where content changes rapidly.
Each URL in the sitemap must return an HTTP 200 code and be its own canonical. Any URL that does not meet these two conditions has no place in the file.
The consequences of a polluted sitemap are not theoretical. When a crawler spends its crawl budget on dead or redirected URLs, it explores fewer useful pages. On a site with several thousand pages, the impact on the indexing of recent content becomes measurable in Google Search Console, through the gap between submitted URLs and those actually indexed.
A simple maintenance protocol is sufficient:
- Remove from the sitemap any URL returning a 3xx, 4xx, or 5xx code within 48 hours of modification
- Exclude URLs with a canonical tag pointing to another page, including sorting or filtering parameters
- Monthly check for consistency between the sitemap and the indexing coverage report in Search Console
XML Sitemap as an SEO diagnostic tool
Reducing the sitemap to a submission file misses its most operational use. The sitemap is a diagnostic tool for indexing, not just a discovery vector.
The method involves systematically comparing the list of URLs present in the sitemap with the data reported by Google Search Console or Bing Webmaster Tools. The gap between the two reveals specific problems:
- Submitted pages but not indexed signal a perceived quality issue, duplicate content, or a forgotten noindex directive
- Indexed pages but absent from the sitemap indicate a functioning internal linking structure, but also an incomplete sitemap
- Crawled pages but never indexed point to content that Google deems insufficient or redundant
This cross-referencing transforms the sitemap into a dashboard. We regularly observe that sites correct canonization or thin content issues solely because the sitemap analysis highlighted these gaps.
IndexNow and sitemap: two complementary mechanisms for Bing
Bing offers a protocol called IndexNow that allows for near real-time notification of the addition, modification, or deletion of a URL. This mechanism does not replace the XML sitemap. It complements it on a different temporal axis.
The sitemap remains the comprehensive reference of URLs to be crawled. IndexNow acts as a timely alert: a published article, an updated product sheet, a removed page. For sites with content that evolves daily (news, marketplace, listings), this combination speeds up the consideration of changes without waiting for the next crawler visit.
Google does not support IndexNow at this time. For the dominant search engine, the sitemap and internal linking remain the two main channels of discovery. The Google indexing API exists but its use is reserved for specific types of content (job offers, live broadcasts).
Sitemap and internal linking: why one does not replace the other
A sitemap signals the existence of a URL. Internal linking demonstrates its relevance. Without internal links, a page submitted via sitemap is unlikely to be indexed sustainably.
Search engines use internal linking to assess a page’s hierarchical depth, thematic context, and relative importance within the site. A sitemap without coherent linking is like giving an address without building the road.
In practice, the sitemap covers orphan pages (those that do not yet have an internal link) while the site’s architecture is corrected. It serves as a safety net, not a permanent strategy. Strategic pages should be accessible within three clicks from the homepage, referenced in the sitemap, and linked by relevant contextual anchors.
The XML sitemap file becomes more effective when it reflects a clean site: canonical URLs, coherent linking, up-to-date content. Treated as a diagnostic tool rather than a formality, it becomes a concrete lever for identifying and correcting barriers to indexing.
