An HTML sitemap is an ordinary web page that lists links to the other pages on a site, usually grouped by section. It was once standard advice: put one in the footer so that both visitors and crawlers can reach everything. That advice has aged badly. If your pages can only be found through a single long list of links, the list is not the problem you should be solving.
This is not an argument that HTML sitemaps are harmful. They rarely hurt anything. The point is that building one is often a way to avoid the harder, more valuable work of fixing how the site is organised.
HTML sitemap vs XML sitemap
The two share a name and little else. An HTML sitemap is a page written for people, rendered in the browser like any other page, linked from the footer or a help menu. An XML sitemap is a file written for crawlers, never meant to be read by a visitor, and submitted in Search Console. Our guide to XML sitemaps covers what that file does and does not do.
| HTML sitemap | XML sitemap | |
|---|---|---|
| Audience | Visitors, and crawlers following links | Crawlers only |
| Format | A normal web page of links | A machine-readable file |
| How it is found | Linked from the site, usually the footer | Submitted in Search Console or referenced in robots.txt |
| What it signals | Internal links to each listed page | A list of URLs you want discovered |
| When it helps | Very large archives, accessibility, a fallback route | Large, new or poorly linked sites |
The confusion matters because people sometimes build an HTML sitemap thinking it does the XML file’s job, or skip the XML file because the HTML page exists. They answer different questions, and one does not replace the other.
What Google has said about HTML sitemaps
Google’s John Mueller addressed this directly in late 2022, in comments reported by Search Engine Roundtable. His words: “I changed my mind on HTML sitemaps over the years, they should never be needed.”
He went on: “Sites small & large should always have a clear navigational structure. If you feel the need for a HTML sitemap, spend the time improving your site’s architecture instead.”
Note what he is and is not saying. He is not saying an HTML sitemap is penalised or ignored. He is saying the need for one is a symptom. If a visitor or a crawler can only reach a page through a sitemap, the page is poorly connected to the rest of the site, and that weakness affects how it is crawled and how much internal authority it receives.
HTML sitemap best practices: fix the architecture first
Our practical judgement, not Google’s: before building an HTML sitemap, work through the three things it usually compensates for. Each one does more for SEO than a list page ever will.
Navigation that reflects the site
Main navigation should reach every major section within a click or two, and each section page should link to its key children. If a category exists in your content plan but not in your menus, visitors will not find it either. Breadcrumbs reinforce this by giving every deep page a visible path back up; our guide to breadcrumbs for SEO covers the markup and the common mistakes.
Contextual internal links
Links from within body copy carry more context than a bare list. A guide that links to its related guides with descriptive anchor text tells crawlers what each target is about and why it matters. See our post on internal linking for SEO for how to plan those links rather than adding them at random.
Orphan pages
An orphan page has no internal links pointing to it. An HTML sitemap technically un-orphans it, but with one link from a page that links to everything, which says little about its importance. Find orphans with a crawl compared against your XML sitemap or analytics, then link them from relevant pages or retire them. Our guide to orphan pages walks through the process.
When an HTML sitemap is still reasonable
There are cases where a page of links serves visitors well, even on a site with good architecture. The test is whether a person would actually use it.
- Large archives. A publisher with years of content, or a directory with thousands of entries, may benefit from a browsable index by date, topic or letter. That is a useful page in its own right, not a crawling workaround.
- Accessibility. Some visitors find a plain text list easier to use than complex menus, particularly with assistive technology. A simple, well-structured list page can help them.
- A fallback. If your main navigation relies on scripts that sometimes fail, a plain HTML list gives visitors another route. Treat it as insurance while you fix the menus.
- Search and help pages. A site map linked from a 404 page or help centre can rescue visitors who are lost.
In each case the page exists because it helps someone. That is the bar. A sitemap added only because an audit tool flagged its absence does not meet it.
An HTML sitemap example that is worth having
If you do build one, make it useful rather than exhaustive. A good HTML sitemap example groups pages under clear section headings, mirrors the structure of the main navigation, and links to section hubs rather than every single URL on a large site. A stripped-down version might look like this:
Keep it generated from the same source as your navigation so it never goes stale. A hand-maintained list drifts quickly: removed pages stay listed and new ones never appear, which turns the page into a source of broken links.
Exclude anything you would not want a visitor to land on: tag archives with one post, parameter URLs, thank-you pages, anything noindexed. If the list is so long that nobody would scroll it, split it by section or replace it with links to the section pages, which should themselves list their contents.
One limitation is worth stating plainly. There is no clean way to measure what an HTML sitemap contributes. If you add one at the same time as fixing navigation, any change in crawling or rankings could come from either, and the navigation work is the more likely cause. Do not read a sitemap’s arrival as proof that it worked.
The practical order is simple. Fix menus, add contextual links, resolve orphans, and then decide whether a list page still adds anything for visitors. On most sites, by that point, it does not.
Frequently asked questions
Is an HTML sitemap good for SEO?
It rarely hurts, but it is a weak substitute for clear navigation and internal links. Google’s John Mueller has said HTML sitemaps “should never be needed”.
Do I need both an HTML and an XML sitemap?
They do different jobs. An XML sitemap helps crawlers discover URLs; an HTML sitemap is a page for visitors. Most sites benefit from the first and can skip the second.
When should I keep an HTML sitemap?
When visitors would genuinely use it: large archives, accessibility needs, or a fallback route if script-driven menus fail.
Does an HTML sitemap fix orphan pages?
Only technically. A single link from a list page says little about importance. Link orphans from relevant content instead.
The takeaway If you feel you need an HTML sitemap, treat that as a sign your navigation needs work. Fix the architecture first, and keep a list page only if visitors would use it.
