Should you still invest in an HTML sitemap for SEO?

Why does Google make a distinction between HTML and XML?

The HTML sitemap is a page visible to users, listing the main sections or URLs of the site. Google can crawl it like any other page, but it does not offer any structured information or metadata that can be utilized by bots. Historically, some SEOs believed that an HTML sitemap helped with indexing or ranking, but Mueller clearly contradicts this.

The XML sitemap, however, is a technical file that is automatically parsed by crawlers. It contains tags like lastmod, changefreq, priority, which signal which pages have been recently modified and warrant priority recrawling. It is this layer of metadata that makes all the difference for search engines.

Does the HTML sitemap still have any practical use?

Yes, but only for the user and for SEOs wanting to visualize the site’s architecture. A "Sitemap" page can facilitate navigation on complex sites, especially if the main menu is incomplete or if certain sections are poorly linked. Google can access it, but it does not use it to boost rankings.

From an SEO audit perspective, a well-structured HTML sitemap allows you to visually verify the consistency of internal linking and identify orphan silos. It is a control tool, not a ranking lever. If your site has clear navigation and strong linking, you do not need an HTML sitemap for pure SEO.

What metadata does the XML sitemap actually transmit?

The XML file communicates several pieces of information that Google can use to optimize its crawl budget. The lastmod tag indicates the last modification date, which helps Googlebot prioritize fresh pages. The changefreq tag suggests the update frequency (daily, weekly, etc.), although Google does not follow it blindly.

The priority tag remains controversial: Google has always claimed that it does not influence ranking, but some crawlers take it into account to decide which URLs to crawl first. In practice, lastmod has the most observable impact on crawler behavior.

• HTML Sitemap: no metadata, no direct impact on ranking, mainly useful for UX and structure audits
• XML Sitemap: transmits modification dates, update frequency, helps prioritize crawling
• The two formats are not interchangeable: XML is mandatory for large sites, HTML is optional
• Don't rely on an HTML sitemap to compensate for poor internal linking
• Google can crawl an HTML sitemap, but it does not use it as a source of structured metadata

Is this statement consistent with observed practices on the ground?

Absolutely. For years, audits have shown that sites with a well-performing HTML sitemap but a terrible internal linking structure do not rank better. The HTML sitemap will not save a poorly structured site. What matters is click depth, internal PageRank distribution, and clarity of contextual links.

On the other hand, sites that omit the XML sitemap or update it sporadically often face indexing delays, especially on deeply nested or recently published pages. The XML remains a weak signal but is exploited by Google to intelligently allocate crawl budget. If you have thousands of pages, failing to maintain a clean XML is a tactical mistake.

What nuances should be added to this statement?

Mueller says that the HTML sitemap "does not boost ranking," which is true. But he does not clarify that, in some cases, it can indirectly improve indexing by facilitating the discovery of orphan pages by bots. If a URL is not linked anywhere else on the site, having a link in an HTML sitemap may make it crawlable, even if it is not optimal.

Another point: [To be verified] the value of the priority tag in the XML remains unclear. Google officially states that it has no impact, but empirical tests show that some third-party crawlers (Bing, Yandex) take it into account. If you are targeting a multi-engine audience, do not overlook this tag, even if Google ignores it.

In which cases does this rule not apply?

On sites with complex navigation or dynamic content (filters, facets, multiple categories), a well-thought-out HTML sitemap can serve as a safety net for both users AND bots. If your main menu does not cover all sections, the HTML sitemap becomes a useful secondary entry point.

Similarly, on sites undergoing redesign or migration, the HTML sitemap can temporarily expose new URLs while internal linking is being rebuilt. This is not a long-term solution, but it can expedite the discovery of pages during the transition.

What should you actually do with these two types of sitemaps?

Prioritize the XML sitemap: ensure it is up to date, covers all indexable URLs, and excludes noindex or canonicalized pages. The lastmod tag should reflect the true modification date of the content, not the file generation date. Many CMSs update lastmod with each minor change (e.g., a comment), which distorts the signal.

For the HTML sitemap, create it only if your site has a complex architecture or if your users need it for navigation. Do not overload it with thousands of links: stick to the main sections and pillar pages. If your internal linking is strong, you can completely do without it without SEO penalties.

What mistakes should be avoided in managing sitemaps?

The classic error: including noindex, 404, or redirected URLs in the XML sitemap. Google tolerates this, but it wastes crawl budget and sends conflicting signals. Regularly clean your XML to ensure it contains only 200 indexable URLs.

Another pitfall: failing to submit the sitemap to Google Search Console after a major update. Google will eventually recrawl it, but submitting manually speeds up the acknowledgment of changes, especially after a redesign or large-scale content publishing.

How can I check that my setup is correct?

Compare the number of URLs in your XML sitemap with the number of pages indexed in Google Search Console. A significant discrepancy signals either indexing problems or an inflated sitemap with unnecessary URLs. Also check the consistency of lastmod dates: if they are all identical, your CMS is likely generating bogus timestamps.

For the HTML sitemap, test it through user navigation: is it easy to scan? Do all the links work? If you never use it yourself, neither will your visitors. You might as well delete it and invest that time in improving internal linking.

• Update the XML sitemap with every addition or modification of significant content
• Exclude all noindex, 404, or redirected URLs from the XML
• Ensure that the lastmod tag reflects the true content modification date
• Submit the XML sitemap via Google Search Console after any significant updates
• Create an HTML sitemap only if UX or site architecture justifies it
• Regularly audit the gap between the URLs in the sitemap and the indexed pages