A poorly configured sitemap is useless to both crawlers and visitors. Confusion between XML sitemaps, HTML sitemaps, and navigation hierarchies is common, even among technical professionals. Each format serves a distinct purpose, and mixing them up sends contradictory signals to search engines.
XML sitemaps and HTML sitemaps: what each format actually tells crawlers
An XML sitemap is a discovery file. It lists URLs so Googlebot or Bingbot can find them, but it does not guarantee that they will be crawled or indexed. Google is clear about this: including a URL in a sitemap is a hint, not an instruction. A page can appear in a sitemap and never show up in search results.
An HTML sitemap, by contrast, is a navigable page designed for people as well as crawlers. It works as a structured index of the site’s content, with actual hyperlinks. Its SEO value comes from the internal linking it creates: each link passes PageRank and reduces crawl depth.
Confusing the two leads to common mistakes. Automatically generating an XML sitemap without checking its URLs can waste crawl budget. Publishing an HTML sitemap without a clear hierarchy helps no one. To see how an HTML sitemap can organize dozens of pages into clear categories, MYN Idee’s sitemap is a good example of this approach to grouping content by topic.
The lastmod field: a useful signal, under strict conditions
Google and Bing use the lastmod field in XML sitemaps to prioritize crawling recently updated pages. The condition: the date must reflect a significant content change, not a simple footer update or an automatic refresh.
If the date is inconsistent or systematically identical across all URLs, crawlers eventually ignore it. We find that many CMS platforms update lastmod with every minor save, reducing the reliability of the signal across the entire file.
Internal linking architecture: why a sitemap can’t make up for weak internal links
An XML sitemap does not replace navigation links. Google explicitly describes it as a discovery aid, not a substitute for a crawlable internal linking architecture. If a page is accessible only through the sitemap, with no contextual links from other pages on the site, it remains an orphan page from a crawling perspective.
An HTML sitemap partly addresses this issue by creating a centralized access point. But it does not eliminate the need to add links from thematically related pages.
- A product page linked only from the XML sitemap and HTML sitemap, with no link from its parent category, receives a weak relevance signal.
- A blog page linked from related articles and included in the HTML sitemap benefits from a double boost: semantic context and structural accessibility.
- Strategic pages (landing pages, core services) should be reachable within three clicks from the homepage, regardless of whether they appear in the sitemap.
A well-designed sitemap acts as a safety net for internal linking. It never replaces it.
Outdated XML sitemap signals: Google ignores priority and changefreq
Google ignores the priority and changefreq fields. Filling them in has no effect on crawl frequency or rankings. Continuing to include them is not harmful, but it can skew analysis if you think these parameters control crawling.
Google has also retired its old sitemap ping endpoint. Submitting the file through Search Console or declaring it in the robots.txt file remains the recommended approach.
Segmenting sitemaps by content type
On large websites, a single sitemap file containing thousands of URLs becomes difficult to audit. Segmenting by type (articles, product pages, corporate pages) makes it possible to monitor indexing by category in Search Console.
Each child sitemap can be listed in a sitemap index, a parent file that references the child sitemaps. This approach makes diagnosis easier: if one segment has a low indexing rate, the issue is isolated without having to audit the entire site.
Creating an HTML sitemap that supports navigation and SEO
An effective HTML sitemap is not just a raw list of links. It relies on a visual hierarchy that reflects the site’s actual structure. Main categories appear at the top level, with subpages indented beneath them.
- Limit the number of links on each page to a few hundred at most. Beyond that, the value passed by each link is diluted, and the page becomes difficult for visitors to read.
- Give each link descriptive anchor text that includes the target page’s keywords, rather than generic labels such as “click here” or “learn more.”
- Update the HTML sitemap whenever a page is added or removed. An outdated sitemap containing broken links harms the user experience and sends negative signals to crawlers.
- Place a link to the sitemap in the site footer, accessible from every page, to ensure that both crawlers and visitors can find it.
An HTML sitemap works like a book index: it provides an immediate overview and points visitors to the right section without making them browse every chapter. This function remains useful even on sites with an internal search engine, since not every visitor knows exactly what to search for.
On the technical side, make sure the HTML sitemap contains no URLs blocked by the robots.txt file and no pages marked noindex. Listing a page that crawlers cannot crawl or index creates an inconsistency that Search Console flags as a coverage issue.
A well-designed sitemap brings together two dimensions: technical discovery for search engines through the XML sitemap, and structural clarity for visitors through the HTML sitemap. Neither can fix a confusing site hierarchy or a lack of internal links. They complement a solid architecture; they do not replace it.
