A sitemap is a page or file that lists the accessible URLs on a website. Its main purpose is to provide an overview of the content structure for both human visitors and search engine crawlers such as Google and Bing. A well-organized sitemap makes it easier to find any page, even one buried several levels deep in the site hierarchy.
Navigation, site hierarchy, and sitemap: three distinct concepts
Confusing these three terms can lead to design mistakes. The site hierarchy is the structure that organizes content: homepage, categories, subcategories, and individual pages. It is planned before the design stage.
Navigation refers to the practical tools that help users move around a site: the main menu, breadcrumbs, and internal search bar. A sitemap provides another way to find a page. It complements navigation rather than replacing it.
WCAG 2.2 criterion 2.4.5 (Level AA) also requires sites to offer multiple ways to find a page. A menu alone is not enough: combining a menu, search, and sitemap meets this accessibility requirement. On content-rich portals, the Sortie 24 sitemap is a good example of this approach, listing sections and pages directly without making users navigate through several levels of menus.
HTML sitemap and XML sitemap: roles and technical limitations
An HTML sitemap is a standard web page intended for visitors. It displays clickable links organized by topic or section. Its purpose is straightforward: users who get lost can find the page they’re looking for in seconds.
An XML sitemap is a technical file intended for crawlers. It lists URLs using structured tags and can include metadata such as the date of last modification (the lastmod attribute). Search engines use it to discover pages they might not find through internal links.
What an XML sitemap does not guarantee
Submitting an XML sitemap to Google does not automatically get the listed pages indexed. Google treats it as one signal among many. Internal links remain the main driver of crawling: a page with no links pointing to it from elsewhere on the site is unlikely to be crawled regularly, even if it appears in the sitemap.
The lastmod attribute is only useful if it reflects an actual content change. If the date is automatically updated every day without any real changes to the page, crawlers will eventually ignore it.
Organize a sitemap to guide users
A poorly structured sitemap that lists dozens of links without any hierarchy can be just as confusing as an overloaded menu. A few principles can make the page genuinely useful:
- Group links by topic rather than by creation date. Visitors are looking for a subject, not a publication date.
- Limit the hierarchy to two or three visible levels. Beyond that, the list becomes harder to read and users lose interest.
- Give each link a clear, descriptive label. A label such as “Page 12” or “Article from March 3” tells users nothing about the actual content.
- Keep the sitemap consistent with the main navigation menu. If a section appears in the menu but not in the sitemap (or vice versa), users can lose their bearings.
Filter XML sitemap URLs: what belongs in it
A comprehensive XML sitemap is not necessarily a good one. Including redirected URLs, pages marked noindex, or duplicate content sends confusing signals to search engines.
Only canonical URLs intended for indexing belong in the file. Each entry should point to an accessible page that returns an HTTP 200 status code and corresponds to the version the site wants to appear in search results.
Practical checks before submission
- No URL should return a 301, 302, or 404 status code. A sitemap validation tool can detect these issues in seconds.
- Password-protected pages and pages blocked by the robots.txt file should not be included.
- If the site uses
canonicaltags pointing to another URL, only the canonical URL should appear in the sitemap.
Regularly reviewing the sitemap whenever content is added or removed ensures that it accurately reflects the site’s actual structure. Search engines are then more likely to trust the information it contains.
Accessibility and crawling: the sitemap as a safety net
On a site with several hundred pages, some content can become orphaned, with no internal links leading to it from the main pages. An HTML sitemap then acts as a safety net by providing direct access to these overlooked pages.
For users with disabilities, a well-marked-up sitemap with clear labels offers a reliable alternative to menu navigation, especially when dropdown menus are difficult to use with a keyboard or screen reader.
A sitemap cannot fix a flawed site architecture. A site with confusing navigation remains confusing, with or without a sitemap. It works as a complement, not a substitute. The main effort should go into the site hierarchy and internal linking, with the sitemap reinforcing both by making every page accessible through at least one additional path.
