A sitemap lists all the pages on a website on a single page. For visitors, it’s a flat view of the site’s hierarchy: every section, subsection, and content page appears as a clickable link. It may seem rudimentary compared with mega menus and search bars, but it meets a need those features don’t always address.
HTML sitemap and XML sitemap file: two distinct things
These two formats are often confused. The XML file is intended for crawlers: it provides search engines with URLs, but does not guarantee that they will crawl or index them. The HTML page, on the other hand, is intended for human visitors. It displays links organized by topic that anyone can browse in a web browser.
| Criterion | HTML sitemap | XML sitemap |
|---|---|---|
| Primary audience | Human visitors | Search engine crawlers |
| Format | Web page with clickable links | Structured text file |
| Accessible in a browser | Yes, via a link in the footer or menu | Not visible without a dedicated tool |
| SEO role | Internal linking, secondary navigation | Submitting URLs for crawling |
| Useful for accessibility | Yes (WCAG 2.4.5 criterion) | No |
A site with only an XML file therefore offers visitors no alternative navigation tool. The HTML page is the only format that serves this purpose.
To see what this type of page looks like in practice, the Gloria Net sitemap displays a complete site hierarchy with links organized by category, illustrating the idea of an exhaustive overview from a single entry point.
Accessibility and WCAG criteria: why a sitemap is still required
WCAG 2.2, through criterion 2.4.5, requires that a page be findable using more than one method. The main menu provides one way to access it. The sitemap, search bar, or breadcrumb trail provides a second. A sitemap meets this requirement without requiring complex development.
Screen reader users benefit directly. Exploring a site page by page to understand its structure takes time and requires significant cognitive effort. A sitemap brings the entire hierarchy together on one page, which can be browsed in seconds using a screen reader or keyboard navigation.
RGAA 4.1.2 adds another requirement: the sitemap must be accessible from the same location across different pages. A footer link that appears on every page meets this condition. A link buried in a subsection does not.
Limitations to be aware of
A sitemap alone does not guarantee accessible navigation. If the page is not properly marked up or its links cannot be reached using a keyboard, the benefit is lost. The W3C recommends combining a sitemap with orientation aids: breadcrumbs, descriptive headings, and a consistent hierarchical heading structure on every page.
Creating a readable sitemap: what matters
A sitemap that lists hundreds of pages without any logical organization quickly becomes unusable. The goal is to reproduce the site’s hierarchy, with clearly identifiable levels.
- Group pages by main sections and then by subsections, following the same logic as the site’s navigation menu
- Limit the visible hierarchy to a maximum of three levels to avoid an endless list that discourages browsing
- Use link labels that match the actual page titles (avoid shortened rewordings that could cause confusion)
- Exclude technical pages that offer no value to visitors, such as login pages, redirects, and internal search results pages
An oversized or poorly organized sitemap can be counterproductive. Large websites (such as e-commerce sites with thousands of product pages) are better off grouping entries by category rather than displaying everything.
Dynamic pages and regularly updated content
Blogs, news sections, and FAQs present a specific challenge. A manually generated sitemap becomes outdated as soon as a new article is published. Most CMS platforms offer automatic HTML sitemap generation, ensuring that every new page appears without manual intervention.
Automatic generation has one drawback: it sometimes includes tag pages, date archives, or pagination pages, making the sitemap unwieldy. Filtering by content type (articles, static pages, categories) helps reduce this clutter.
How sitemaps, mega menus, and search bars work together
A mega menu reveals the main categories and a few subcategories on hover. A search bar helps when visitors know what they’re looking for. A sitemap serves a third purpose: visitors may not know exactly what they’re looking for but want to see everything that’s available.
- Mega menus work well for sites with broad but shallow hierarchies (fewer than three levels)
- Internal search suits sites with large volumes of content, provided the search engine performs well
- A sitemap is the only feature that provides a comprehensive overview without requiring complex interaction
These three features do not replace one another. A site that relies exclusively on its navigation menu deprives users of an alternative way to find content, creating an accessibility issue under the WCAG 2.4.5 criterion mentioned above.
The sitemap page also serves as an internal linking hub: every link it contains sends search engines a signal about the existence and hierarchy of pages. On sites where some deep pages receive few internal links, a sitemap provides a simple way to address this gap.
An HTML sitemap doesn’t need to be flashy. A simple, well-structured page that is keyboard-accessible and updated automatically does the job. The focus should be on consistent labels, a manageable hierarchy, and a link to the sitemap from every page on the site.
