Part of the SiteMap Series
In the last lesson, we mapped out the different types of sitemaps and noted that the HTML sitemap sits in a slightly different category from the rest of the XML family. I promised we’d come back to that distinction properly, because it’s where most of the foundational confusion about sitemaps happens. This is that lesson.
The question this one sets out to answer is straightforward. Of the two things people commonly call “sitemaps”, the XML version and the HTML version, which one does your site actually need?
If you only have time for the short answer, it sits near the bottom of the page. But the reasoning matters, because the answer shifts depending on what kind of site you’re running, and getting it wrong wastes effort that could be better spent elsewhere.
What each one actually is
Before we put them side by side, it’s worth being clear on what each one is in plain terms. They share a name, but they’re genuinely different things.
What is an XML sitemap?
An XML sitemap is a machine-readable text file that lists the URLs on your site for search engines. It usually sits at /sitemap.xml on your domain, gets generated automatically by your CMS or your SEO plugin, and looks like a wall of structured code if you ever open it in a browser. Its entire job is helping crawlers discover URLs. Humans aren’t meant to read it. We covered the full definition in Lesson 1: What is a Sitemap.
Highly Related
What is an HTML sitemap?
An HTML sitemap is a regular web page on your site that contains a list of links to other pages on the same site. It’s written in HTML like every other page on your site, styled with your site’s fonts and colours, and typically linked from the footer, where any visitor who wants it can find it. Its job is to help human visitors navigate the site when the main menu and the search box aren’t enough. We touched on its high-level shape in the last lesson: Types of Sitemaps.
Same word, different file, different audience, different purpose. Once you’ve seen both, the only reason the confusion persists is the shared name.
How they actually differ
When you put the two side by side, the differences are more obvious than when you read about them separately. There are five worth naming explicitly.
- The first difference is the format. XML sitemaps are written in XML, a structured format designed for machine reading. HTML sitemaps are written in HTML, the same language every web page is written in. One is computer-readable. The other is human-readable. That single distinction shapes everything else.
- The second difference is the audience. An XML sitemap exists for search engine crawlers. An HTML sitemap exists for human visitors. You might never look at your own XML sitemap. Visitors might never look at your HTML sitemap. But each has its respective audience in mind, and each is doing its job whether anyone notices or not.
- The third difference is the purpose. XML sitemaps are about discovery, which means helping search engines find URLs they might otherwise miss. HTML sitemaps are about navigation, which means helping visitors find their way around your site when the menu and the search box aren’t enough. Both involve “finding pages”, but the kind of finding is fundamentally different in each case.
- The fourth difference is where they live. XML sitemaps almost always sit at the root of the domain as
sitemap.xml. HTML sitemaps usually live at a friendly URL like/sitemapor/site-map, and they’re typically linked from the footer so visitors who want them can find them from any page. - The fifth difference is how they update. XML sitemaps are usually generated automatically, either by your CMS, your SEO plugin, or a custom build script, so they refresh whenever you publish or change content. HTML sitemaps tend to be manually maintained or generated by a separate plugin, which means they can fall out of date if nobody is paying attention to them.
With those differences clear, there’s a question that almost always comes up at this point, so it’s worth addressing before we get to the practical decision.
Does an HTML sitemap help with SEO?
This is the question I get asked most often about HTML sitemaps, and it deserves its own section because the answer isn’t a clean yes or no.
The honest answer is that an HTML sitemap helps a little, in indirect ways, but probably not enough to justify creating one solely for SEO reasons.
Here’s what’s happening underneath. An HTML sitemap is a regular page with a lot of internal links on it. Internal links are one of the ways search engines discover pages, and they’re one of the signals search engines use to understand how a site is structured. So in theory, having an HTML sitemap with links to every important page on your site could help search engines find those pages and understand how they relate to one another.
In practice, though, if your site has good navigation, a clean menu structure, and proper internal linking inside your content, your pages will be found and crawled just fine without an HTML sitemap. The XML sitemap takes care of the discovery angle. The internal linking already in your content takes care of the rest. An HTML sitemap on top of that is largely duplicating work that’s already being done.
The exception is very large sites. If you have a site with thousands of pages, some of which are several clicks deep from the homepage and not linked from the obvious navigation places, an HTML sitemap can genuinely help search engines reach pages they would otherwise struggle to find. Major e-commerce platforms and large content sites sometimes use HTML sitemaps for exactly this reason. For most sites, that’s not a concern.
So if you’re wondering whether to add an HTML sitemap purely for the SEO benefit, my honest recommendation is to focus your energy elsewhere. If you want to add one for accessibility or as a navigation aid for visitors, those are stronger reasons.
That brings us to the practical question you came here to answer.
So which one do you actually need?
If you’ve read this far, the answer is probably already forming in your head. Let me make it explicit.
You need an XML sitemap. This part of the answer is straightforward and applies to almost every site. Any site that takes SEO seriously, that publishes content with any regularity, or that wants to be found in search engines should have one. We covered the reasoning for that in Lesson 1.
You probably don’t need an HTML sitemap, but the answer changes depending on your site and your audience.
If your site is small or medium-sized, with a clean menu structure that visitors can use to find what they need, you can skip the HTML sitemap with no real loss. Most modern sites do exactly that. The footer link to a “Sitemap” page that you used to see on every site in the early 2000s has quietly fallen out of fashion because better navigation made it redundant.
If your site is very large, has deep page hierarchies, or serves users with accessibility needs that genuinely benefit from a linked index, an HTML sitemap earns its place. Some major brand sites and large content platforms still have them sitting quietly in their footers, doing real work for the small percentage of users who use them.
If your site is somewhere in between, an HTML sitemap is optional. It won’t hurt to have one, and it won’t hurt to skip it. The decision should be based on whether you think your visitors would actually use it, not on whether you think it might help your SEO.
If you decide you need an HTML sitemap, build it properly
If you’ve worked through the decision above and concluded an HTML sitemap earns its place on your site, the next question is how to build one that actually works rather than one that quietly underperforms.
A good HTML sitemap is structured, not just a flat list of links. Group the links by section, mirror the navigation hierarchy of your site, and use proper headings (H2 and H3) to indicate sections. A reader who lands on the page should be able to scan it, find the section that matches what they’re looking for, and click through. A wall of 2,000 unstructured links is functionally useless to a visitor, no matter how complete it looks.
The conventional URL is /sitemap or /site-map, linked from the footer of every page on the site so any visitor can reach it from anywhere. Don’t bury it three menus deep or behind a click that requires the visitor to already know it exists.
Keep it current. Either generate it dynamically from your CMS so it updates with new content, or set yourself a regular reminder to refresh it when you publish new sections of the site. An HTML sitemap that hasn’t been touched in two years is worse than not having one, because it sends visitors to dead links and signals the rest of the site might be similarly stale.
For WordPress sites, the major SEO plugins (Yoast, Rank Math, and AIOSEO) all offer HTML sitemap features in some of their versions, and dedicated HTML sitemap plugins exist as well. Whichever route you take, the test that matters is the same. Click through the links yourself, check that the structure mirrors how visitors actually navigate your site, and revisit it twice a year to catch the drift.
Where this leaves us
XML and HTML sitemaps share a name but do entirely different jobs. The XML kind is the one that matters for SEO, and almost every site needs one. The HTML kind is a navigation aid for human visitors that earns its place on some sites but not most.
From this point onwards, when I say “sitemap” in this series without specifying which kind, I mean the XML version. That matches how the rest of the SEO industry talks too. The HTML sitemap is now properly tucked into its own category in your mental model: useful sometimes, optional usually, and never confused with the XML version again.
In the next lesson, we’ll look at another pair of files that often get confused, but in a different way. Sitemaps and robots.txt are both ways of communicating with search engines about your site, but they do genuinely different jobs. Understanding how the two relate is the next foundational piece worth getting right.
Up next: Sitemap vs Robots.txt: What’s the Difference? →
This is Lesson 3 of The Sitemap Series, a Technical SEO series on sitemaps from first principles, built for the AI Search era.