A sitemap, or XML sitemap, is a file that lists the URLs of a website to facilitate their discovery by crawling bots. Its structure directly influences the ability of search engines to crawl and understand the organization of your pages. Each URL included and each associated piece of information must follow a specific logic for the sitemap to truly fulfill its role with search engines.
The XML sitemap as a discovery signal, not as an indexing order
A common misconception is to think that including a URL in a sitemap guarantees its indexing. Google Search Central documentation is clear: a sitemap helps discover URLs, but does not guarantee either their crawling or their indexing. Google treats this file as a hint among others, not as a directive.
This distinction changes the way to approach the construction of the file. Rather than listing all existing pages, the strategy is to select the URLs that deserve to appear in search results. Filter pages, duplicates, pagination pages without unique content, or non-canonical URLs have no place in a well-constructed sitemap.
On the site www.digitalinnovators.be, the structure of the sitemap illustrates this selective approach: only the URLs intended to be indexed are included, which sends a coherent signal to crawling bots.
lastmod, priority, and changefreq tags: what Google really uses
Three optional tags accompany each URL in an XML sitemap. Their actual usefulness varies significantly, and two of them are simply ignored by Google.
- lastmod: the only tag that Google takes into account, provided that the date reflects a significant content change. Updating the footer or copyright does not justify a date change. Systematically refreshing dates with each sitemap generation makes this signal unreliable in the eyes of the engine.
- priority: this numerical value between 0 and 1 is supposed to indicate the relative importance of a page. Google completely ignores it. Spending time calibrating these values brings no benefit in terms of crawling or ranking.
- changefreq: it indicates the supposed frequency of a page’s updates (daily, weekly, monthly). Google does not use it either to plan its crawls.
The time invested in fine-tuning priority and changefreq is thus wasted time. It is better to focus the effort on the reliability of lastmod dates and the relevance of included URLs.
Segmenting sitemaps for high-volume sites
A single sitemap that mixes blog articles, product sheets, category pages, and institutional pages complicates diagnosis. Segmenting sitemaps by content type facilitates crawl analysis and allows for quick identification of which segment is problematic.
An e-commerce site can, for example, separate its files into a sitemap dedicated to products, another for categories, and a third for editorial content. The index file (sitemap_index.xml) then references each of these sub-files.
This segmentation provides a concrete advantage in Google Search Console. By submitting each sitemap separately, you can compare the number of submitted URLs to the number of URLs actually indexed by segment. A significant discrepancy on a specific type of page (out-of-stock products, empty categories) reveals a structural issue that you would not have spotted with a monolithic file.
Consistency between sitemap, canonicals, and internal architecture
The sitemap does not function in isolation. Its effectiveness depends on its consistency with two other technical elements: canonical tags and internal linking.
A URL present in the sitemap must be the canonical version of the page. If your canonical tag points to a different URL than the one listed in the sitemap, you are sending contradictory signals. Google must then arbitrate, and the result does not always match your expectations.
Internal linking plays a complementary role. A page listed in the sitemap but accessible only through it, without any internal links from other pages of the site, is unlikely to be considered a priority. Crawling bots use internal links to assess the structure and relative importance of pages.
Three checks ensure this consistency:
- Each URL in the sitemap returns a HTTP 200 code (no 301 redirects, no 404 errors).
- Each URL in the sitemap corresponds to the canonical version declared in the page’s source code.
- Each URL in the sitemap receives at least one internal link from another indexable page on the site.
Update frequency and sitemap submission
Generating a sitemap once and then forgetting about it is like leaving an outdated city map in circulation. Pages evolve: some are created, others deleted or merged. A dynamically updated sitemap reflects the actual state of the site and helps engines focus their crawl budget on relevant pages.
Most modern CMSs (WordPress, Shopify, Prestashop) automatically generate a sitemap. The risk with these tools is that they include all URLs by default without distinction. Regularly checking the content of the generated file allows you to exclude pages that should not appear in search results.
Submission in Google Search Console remains the most direct way to signal the existence of your sitemap. After a redesign or a massive content addition, a new submission speeds up the consideration of changes by the bots.
A well-structured sitemap will not, on its own, transform a site’s SEO. Its role is more modest but real: it ensures that search engines have a reliable map of your pages. Visibility gains then come from the quality of the content, internal linking, and the relevance of the pages you choose to highlight.
