A sitemap is a page that lists all the content accessible on a blog, organized by categories and subcategories. On a blog rich in articles, this page functions as a structured summary: it allows users to locate specific content without going through the main menu or the search bar.
The distinction from the XML sitemap file (intended for search engines) is fundamental. The sitemap in question here is a HTML page accessible to visitors, designed to facilitate human navigation.
HTML Sitemap and XML Sitemap: Two Distinct Functions
The confusion between these two elements remains common. The XML sitemap file is a technical document submitted to search engines to index pages. It never appears in a visitor’s browser.
The HTML sitemap, on the other hand, is a page of the blog accessible from the footer or the menu. Its role is to present a comprehensive view of the structure to a human reader. A blog that publishes several articles per week quickly accumulates dozens of pages that the navigation menu cannot display all at once.
To visualize what a well-structured sitemap looks like on a blog, the Chez Sylvie sitemap provides a good example of a readable page, organized by sections with clear headings.
Structure of a Readable Sitemap for a Blog
A sitemap is not just a raw list of links. Its value depends on how the content is grouped and prioritized. Three principles guide its construction.
Group by Categories, Not by Date
A blog often displays its articles from the most recent to the oldest. The sitemap should adopt a different logic: classify by theme rather than by chronology. A visitor looking for all articles on a specific topic can browse the corresponding category without scrolling through months of archives.
Name Each Link with a Clear Label
Each entry in the sitemap should carry the full title of the article or page, not a shortened title or a number. Recent accessibility guidelines emphasize this point: a clear label helps users of screen readers understand the destination of the link without additional context.
Limit Depth to Two or Three Levels
An overly detailed sitemap (four levels or more) becomes as difficult to read as an overloaded menu. The recommended structure follows this scheme:
- Level 1: the main sections of the blog (categories, static pages like “About” or “Contact”)
- Level 2: subcategories or series of articles grouped by theme
- Level 3: individual articles, only if the section contains enough content to justify this detail
Beyond three levels, the page loses its advantage of quick readability.
Accessibility and Keyboard Navigation on a Sitemap
The sitemap addresses a concrete need for people who navigate without a mouse. Keyboard users can access a section directly without tabbing through all the interactive elements of the menu and content that precede their destination.
For screen reader users, browsing a blog page by page to understand its structure consumes time and cognitive effort. The sitemap provides a global view of the structure in one place.
A technical complement often overlooked: the skip link. This link, placed as the first focusable element on each page, allows users to jump directly to the main content. Accessibility recommendations specify that it should remain visible to keyboard users and not be hidden by a sticky header. On a sitemap, the skip link avoids tabbing through the navigation menu before reaching the list of links.
Marking Up Your Sitemap with the Right Semantic HTML
The technical quality of the markup directly influences the navigation experience. A sitemap built with correct semantic tags is better interpreted by browsers and assistive technologies.
- Use the <nav> tag with an aria-label attribute to identify the navigation area of the sitemap, distinct from the main navigation
- Structure links in ordered or unordered lists (<ul>, <ol>) rather than in paragraphs or tables
- Use <h2> and <h3> headings to separate major sections of the sitemap, allowing screen readers to navigate by headings
- Avoid ARIA roles designed for application interfaces (like “menubar”): a sitemap is a page of links, not an application
Recent accessibility examples discourage treating a blog’s navigation as an ARIA application menu. The combination of <nav> plus a list of links remains the most reliable method.
Automatic Generation or Manual Construction of the Sitemap
On WordPress and most CMS, plugins automatically generate an HTML sitemap from the existing structure. This approach is suitable for blogs that publish frequently, as each new article appears without manual intervention.
Manual construction has an advantage: it allows for the exclusion of certain pages (legal notices, irrelevant tag pages, empty archive pages) and reorganizes the display order according to editorial logic rather than publication date. For a blog with a few dozen pages, the effort remains reasonable. Beyond that, automatic generation with category sorting avoids omissions.
A sitemap does not replace the main menu or the search bar. It serves as a safety net for visitors who did not find what they were looking for through the usual paths and as a primary navigation tool for those who prefer an overview. The page deserves a permanent link in the blog’s footer, where readers expect to find it.
