HTML Sitemap: What It Is, How It Differs From XML and When It Is Still Useful in 2026

An HTML sitemap is one of the oldest pages on the web, and one of the most debated in SEO. Some guides still sell it as a ranking lever, others call it useless. The truth sits in between and comes from how Google discovers pages: through links. As the Google Search Central documentation on crawlable links puts it, every page you care about should have a link from at least one other page on your site. An HTML sitemap is one way to guarantee that, and a fallback when the rest of your navigation does not. This guide explains what it is, how it differs from the XML format, what Google said about it in 2022 and again in October 2026, and how to build one that helps people and crawlers.

What is an HTML sitemap?

An HTML sitemap is a page, usually at an address such as /sitemap or /site-map, that shows the structure of a website as clickable lists of links. It is written in plain HTML (standard link tags inside headings and lists), it has the same design as the rest of the site, and it is usually linked from the footer of every page.

A good example is Apple's site map: a few hundred links grouped under headings (Mac, iPad, iPhone, Support, About Apple...), each heading split into sub-groups such as "Shop and Learn" or "Accessories". It does not list every product variant or every support article, only the doors that lead to them. Sorank uses the same principle on its own site map page, which groups features, free tools, guides and integrations.

The important point is the audience: an HTML sitemap is built for humans who are lost, and crawlers benefit as a side effect because they follow the same links.

HTML sitemap vs XML sitemap: what is the difference?

The two share a name and little else. An XML sitemap is a machine file that lists URLs with optional data (last modification date, images, videos, languages). An HTML sitemap is a page for people.

So the choice is rarely "one or the other". Every site that wants to be indexed should have an XML file (a free XML sitemap generator builds one in a minute), and you then submit that sitemap to Google. The HTML page is an optional layer on top.

Does an HTML sitemap still help SEO?

Google's position has been consistent for years. In December 2022, John Mueller wrote on Mastodon, as reported by Search Engine Roundtable: "I changed my mind on HTML sitemaps over the years, they should never be needed." His reasoning: if a site needs a separate page for visitors to find its content, its navigation is the real problem.

In October 2026, he came back to the subject with Martin Splitt in Google's Search Off the Record podcast, as summarised by Search Engine Journal. His points: an HTML sitemap is "not something that replaces an XML sitemap file", it cannot be processed like one, crawlers can still follow its links, and on an online store "you wouldn't list all of your products" but rather the categories, "so that people can go to the right place".

From this, the real SEO effects are easy to list:

• Discovery of deep pages. A page linked from the sitemap is at most two clicks from the home page, which shortens the path for crawlers and helps when your site architecture has sections buried five or six clicks deep.
• Extra internal links with descriptive anchors. Each entry is an internal link whose anchor text names the destination, which is a small relevance signal.
• A safety net for weak navigation. Menus built entirely in JavaScript, mega-menus that render late or filters that hide links are common; a static list of plain links works for every crawler.

What it does not do: it does not make Google index a page it judged low quality, it does not replace contextual links from your articles, and a link from a page holding 400 other links carries little weight on its own.

When is an HTML sitemap worth building?

Google's own guide to sitemaps says a site of about 500 pages or fewer that is well linked internally may not even need an XML file (Google Search Central, Learn about sitemaps). The same logic applies, even more strongly, to an HTML sitemap. Here is where it pays off and where it does not.

Accessibility is the most solid argument. The W3C lists "providing a site map" as technique G63 of the Web Content Accessibility Guidelines, a way to meet success criteria 2.4.5 Multiple Ways and 2.4.8 Location. For sites that must follow accessibility rules (public bodies, large companies in many countries), a site map page, together with a search function, is a simple way to offer more than one path to each page.

What should an HTML sitemap include?

A useful HTML sitemap is selective. Follow these rules:

1. Mirror the real structure. One heading per main section, sub-lists for sub-sections, in the same order as the menu. The W3C technique states that a site map which presents an organisation different from the real one, or leaves sections out, does not count.
2. List hubs, not everything. Categories, key service pages, guides, tools, company pages. For a store, stop at category or sub-category level; product pages are reached from there, as explained in our guide to ecommerce category page SEO.
3. Only indexable URLs that return 200. No redirects, no noindex pages, no filtered or paginated URLs, no login pages. Check the page regularly with a broken link checker.
4. Descriptive anchors. "Running shoes for women" rather than "Category 12". The anchor is the label people read and the hint crawlers receive.
5. Keep it readable. No official limit exists, but a few hundred links is a practical ceiling. Beyond that, split into one sitemap page per section, linked from a main sitemap page.
6. Link it from every page. The footer is the convention. The W3C technique asks that every page listed in the site map links back to it.
7. Generate it automatically. A hand-edited sitemap goes stale within months. Build it from the same source as your XML file or your navigation.

A simple structure for a services company looks like this:

• Services: SEO audit, Content writing, Link building, Local SEO
• Industries: Healthcare, Legal, Retail, SaaS
• Resources: Blog (with its categories), Guides, Free tools, Glossary
• Company: About, Team, Careers, Contact, Legal notice, Privacy policy

How to create an HTML sitemap

1. Map the sections first

Export your indexable URLs (from the XML file or a crawler such as Screaming Frog) and group them by section. This step often reveals orphan pages and sections that sit too deep. An internal link analyzer shows which pages receive few or no internal links.

2. Choose a generation method

On WordPress, several plugins and some themes output an HTML sitemap through a shortcode or a block. On Shopify and other hosted platforms, apps or a custom template can list collections and pages. On a custom or static site, generate the page at build time from the same data that produces the XML file and the menu, so all three stay aligned.

3. Publish, link and maintain

Place the page at a stable address, add it to the footer, and keep it crawlable: it should and appear in your XML file like any other page. Review it each time you add or remove a section, and watch crawl budget on very large sites, where a bloated sitemap page full of low-value URLs wastes crawler visits.

If a page still does not get indexed after all this, the sitemap is rarely the cause: our guide to Google indexing covers quality, duplication and rendering issues.

HTML sitemaps, SEO and AI visibility

AI crawlers such as GPTBot, ClaudeBot or PerplexityBot discover pages the way Googlebot does: through links and files they can read without running scripts. A static list of plain links is one of the easiest structures for them to follow, which makes an HTML sitemap a modest help for sites whose navigation depends on JavaScript. For the AI side, the closer equivalent is an llms.txt file, a Markdown summary of your key pages written for language models.

The deeper lesson is structure. A site organised in clear topic clusters, where each hub page links to its sub-pages and back, needs little help from a sitemap page, and it is easier for Google and for ChatGPT, Gemini or Perplexity to understand. Sorank's topical cluster generator groups your keywords into silos with one page per topic, the same structure a good HTML sitemap reflects.

Sorank then writes and publishes the articles for each cluster with its blog article generator, with internal links added automatically, so new pages are linked from day one instead of waiting for a sitemap update.

The short version

An HTML sitemap is a navigation aid for people that crawlers can follow, never a substitute for an XML sitemap or for good internal linking. Build one if your site is large, sells across many categories or must meet accessibility rules; keep it selective, generated automatically and linked from the footer. If you want a site whose structure and internal links are planned from the start, see Sorank's plans, from $49 per month on annual billing, with a 3-day free trial.