A sitemap serves two distinct functions depending on its format: the XML file feeds indexing bots, while the HTML sitemap provides a navigation path for visitors. Confusing the two is akin to addressing a crawl issue with a usability tool, or vice versa. Understanding this technical distinction informs every subsequent decision.
XML Sitemap Tags: lastmod, changefreq, and priority in practice
The structure of an XML sitemap is based on the protocol defined by sitemaps.org. Each entry <url> encapsulates at least one <loc> tag containing the canonical URL of the page. Optional tags are often poorly utilized.
The <lastmod> tag must reflect the actual date of content modification. Too many CMSs update it with every minor save (fixing a space, adding a tag), which dilutes the signal sent to the engine. Googlebot eventually ignores a lastmod that changes without any actual content change.
The <changefreq> tag (daily, weekly, monthly) no longer has a direct influence on Google’s crawl frequency. If you also target Bing Webmaster Tools, filling it out retains marginal interest.
The <priority> tag is relative to the site itself: a value of 0.8 on a page means nothing in absolute terms. It serves only to prioritize your own URLs within the file. We recommend removing it to lighten the file and avoid false arbitrations.
On a large site, structuring the sitemap into multiple files indexed by a sitemap index (<sitemapindex>) remains the standard method.
HTML Sitemap and Navigation: What W3C Recognizes as an Alternative Path
The HTML sitemap is not an artifact from the 2000s. W3C recognizes it as one of the legitimate means to help a user find a page, alongside a main menu or a search function. For a visitor who cannot find a section through the usual path, the sitemap page of Geekob illustrates this type of alternative navigation with a clear hierarchy by categories.
A poorly designed HTML sitemap becomes counterproductive. Listing all URLs without grouping transforms the page into a wall of unusable links. W3C recommends grouping content by editorial categories and excluding pages without navigational value (duplicate tag pages, paginated archives, temporary landing pages).
Accessibility determines the actual usefulness of the sitemap. A usable HTML sitemap requires:
- Explicit links whose titles describe the target page, not “click here” or bare URLs
- A hierarchy of headings (h2, h3) that structures the sections for screen readers
- Fully usable keyboard navigation, without focus traps or blocking scripts
Completeness does not mean ease of use. A sitemap with 300 unorganized links will be ignored by both the visitor and the bot. It is better to select strategic pages and visually organize the hierarchy.
Declaring and Submitting an XML Sitemap to Search Engines
Two methods coexist to signal the existence of the sitemap to bots. The first is to add a directive in the robots.txt file:
Sitemap: https://example.com/sitemap.xml
This line is sufficient for any compliant crawler to discover the file. It works for Google, Bing, and secondary engines that adhere to the standard.
The second method involves direct submission in Google Search Console or Bing Webmaster Tools. The advantage: a status report (number of submitted URLs, number of indexed URLs, detected errors). Bing Webmaster Tools also processes submissions via API, which can automate the process for sites with frequently changing content.
The two methods are not mutually exclusive. Declaring in robots.txt ensures passive discovery. Submitting in the Search Console provides active tracking. Combining both remains the most reliable practice.
Arbitration Between XML Sitemap and HTML Sitemap Depending on Site Type
The choice is not framed in terms of “one or the other.” The question is which one deserves maintenance investment.
- A site with fewer than a few hundred pages and a solid internal linking structure can do without an XML sitemap without measurable impact on indexing. The HTML sitemap, on the other hand, improves navigation for visitors arriving on a deep page via search.
- An e-commerce or editorial site with several thousand URLs needs the XML sitemap to ensure that orphaned or newly published pages are discovered by bots.
- A multilingual site benefits from an XML sitemap that includes hreflang tags to signal matches between language versions, a use that the HTML plan does not cover.
The XML sitemap serves bots, the HTML sitemap serves humans. The two address different issues. On a medium-sized site with a clear architecture, the HTML plan often provides more perceived value to the user than the XML file does for crawling.
A sitemap, regardless of its format, does not fix a flawed architecture. If your strategic pages are buried more than three clicks from the homepage, the XML file will partially compensate for the crawl issue, but the visitor will still not find the content. Internal linking remains the primary lever, and the sitemap is a complement that documents a structure already conceived.
