A sitemap does not guarantee the crawling or indexing of a URL. This file remains a discovery signal that search engines may ignore if the page redirects, has a different canonical URL, or lacks quality. Understanding this mechanism changes the way we read and utilize a sitemap, whether in XML for bots or in HTML for visitors.
Lastmod attribute and signals ignored by Google in the XML sitemap
Google does not consider the changefreq and priority fields in an XML sitemap. Only the lastmod attribute retains usefulness, provided it reflects a real and substantial change in content.
We regularly observe sitemaps where lastmod is automatically updated with each deployment, without any content having changed. This behavior degrades the reliability of the signal in the eyes of Googlebot, which ultimately ignores the attribute for the concerned domain.
A technically valid sitemap but filled with fictitious dates does not speed up indexing. It slows it down. When the crawler detects that lastmod does not correlate with a visible change on the page, it reduces the frequency with which it checks the file.
Before submitting a sitemap in Google Search Console or via robots.txt, we recommend cross-referencing the listed URLs with canonical tags and indexing directives. A page present in the sitemap but carrying a canonical tag pointing to another URL sends a contradictory signal. The result: neither is indexed predictably.
HTML Sitemap as a navigation tool for visitors
Navigating a content-rich site quickly becomes laborious when the structure exceeds three levels deep. An HTML sitemap exposes all (or a relevant selection of) URLs in a human-readable hierarchical structure.
This format differs from the XML sitemap on one fundamental point: it is aimed at visitors, not bots. A user looking for a section buried in a menu can find it directly from the site map, without having to browse through each category. By browsing the sitemap page of britishandco.com, one can visualize the entire range of product universes and editorial pages of the site in a few seconds.
Accessibility and keyboard navigation
Since June 28, 2025, the European Accessibility Act regulates the accessibility of certain digital services, including e-commerce. Navigation must be usable via keyboard and follow a logical traversal order.
An HTML sitemap can serve as a supplementary aid for users of assistive technologies, but it is not sufficient to make a site compliant. It does not replace ARIA landmarks, a properly marked main menu, or a structured breadcrumb trail in Schema data.
Cross-audit of sitemap and internal linking
The real leverage lies in comparing the content of the sitemap with the actual internal linking of the site. We recommend a three-step audit:
- Extract all URLs from the XML sitemap, then confront them with the URLs discovered by a complete crawl of the site. Orphan pages (present in the sitemap but without any internal links) have very little chance of being indexed.
- Check that each URL in the sitemap returns an HTTP 200 code and has a self-referential canonical tag. Any URL that is redirected 301, returns a 404, or is canonicalized to another address should be removed from the file.
- Compare the URLs indexed in Google Search Console with those in the sitemap. A significant discrepancy reveals either content quality issues or contradictory directives (noindex, robots.txt blocking the crawl).
An URL in the sitemap is not an indexed URL. This mental shortcut is costly in SEO diagnostics. The sitemap remains a suggestion tool, never an imperative instruction for the engine.
Low-value pages and crawl budget management
On large sites (e-commerce catalogs, directories, document databases), the number of URLs submitted in the sitemap influences the distribution of the crawl budget. Including low-value pages (facet filters, pagination pages, variants without unique content) dilutes the crawler’s attention on the pages that matter.
We recommend segmenting the sitemap into several thematic files, referenced in a sitemap index. This approach allows tracking, file by file, the crawl rate and indexing rate in Search Console.
Submitting an XML sitemap to Google and Bing
Submission in Google Search Console remains the most reliable method. After adding the file via the interface, the coverage report indicates the detected URLs, those indexed, and those excluded with their reason.
For Bing, Webmaster Tools offers an equivalent report. Both platforms also accept the declaration of the sitemap in the robots.txt file, via the directive Sitemap: https://example.com/sitemap.xml. This method has the advantage of working without a Search Console account, but it does not provide any feedback on the indexing status.
Update frequency and freshness signals
A sitemap that never changes ends up being consulted less often by crawlers. Conversely, a sitemap whose lastmod changes every hour without reason loses all credibility.
The right rhythm depends on the volume of publication. A site that adds a few pages per month can suffice with a weekly regeneration. A news site or a catalog with daily updates should regenerate the sitemap with each content change and reflect the actual date of the change in lastmod.
The sitemap, whether XML or HTML, is not a passive document to be generated once and then forgotten. It is a living diagnostic tool. When kept up to date and consistent with the internal linking, it accelerates the discovery of new pages and helps identify technical inconsistencies before they affect ranking.
