A sitemap is a page that lists all the links on a website, organized according to its hierarchy. It provides a complete overview of the site’s structure, independent of its navigation menus or internal search engine. A sitemap acts as a map: it makes visible what the interface sometimes hides behind several layers of clicks.
HTML sitemap and XML sitemap: two files with distinct purposes
These two formats are often confused. An HTML sitemap is a standard web page that human visitors can read. It displays clickable links to every page on the site, grouped by section.
An XML sitemap is a technical file intended for search engine crawlers. It lists URLs along with metadata, such as the date each page was last modified. Google uses this file as a hint to discover URLs, not as a guarantee that they will be indexed.
A site can have both. The HTML sitemap helps visitors find their way around, while the XML file makes Googlebot’s job easier. Confusing the two is like mixing up a printed directory with an automated import file. For a practical example of a well-structured HTML sitemap, the 10 Grammes sitemap groups its content by category and uses clear labels.

HTML sitemaps and web accessibility: WCAG criterion 2.4.5
WCAG criterion 2.4.5 (Level AA) requires a site to provide at least two ways to locate a page among all its pages. Recognized options include a navigation menu, an internal search engine, breadcrumbs, a table of contents, or a sitemap.
An HTML sitemap is therefore not mandatory in itself. It is one of the accepted ways to meet this requirement. RGAA, the French accessibility standard, follows the same principle in topic 12, which covers navigation.
Who uses a sitemap in practice?
Screen reader users benefit directly. Browsing a site page by page to understand how it is organized takes considerable cognitive effort and time. A sitemap displays the entire site hierarchy on a single page, without requiring sequential navigation.
People who navigate exclusively by keyboard can reach a specific section without tabbing through every interactive element that comes before it. On a site with more than a hundred pages, this saves a noticeable amount of effort.
Beyond accessibility needs, any visitor who can’t find their way back to a page they viewed the day before, or whose search in the internal search engine returns nothing relevant, can turn to the sitemap.
What an XML sitemap does (and doesn’t do) for SEO
A common misconception persists: submitting an XML sitemap to Google Search Console is enough to get all your pages indexed. Google Search Central’s official documentation explains that an XML sitemap is used to notify crawlers of URLs, not to force their indexing. If a page is low quality or blocked by the robots.txt file, the sitemap won’t change that.
Which fields matter and which Google ignores
The XML format provides several fields for each URL. Two of them, priority and changefreq, have no influence on Google. Filling them in has no practical effect on crawl frequency or rankings.
By contrast, the lastmod field can help guide Googlebot, provided the date reflects a genuine, substantial change to the page. Updating this date without actually changing the content sends a misleading signal that Google will eventually ignore.
- An XML sitemap complements internal linking but does not replace it. An orphan page (with no internal links) listed in the sitemap is less likely to be crawled than a page well connected to the rest of the site.
- A sitemap containing URLs that return 404 errors or redirect (301, 302) wastes crawl budget. Regularly cleaning up the file makes it more reliable in the eyes of crawlers.
- For large or frequently updated sites, such as media outlets and e-commerce stores, an XML sitemap remains the most direct way to quickly notify search engines about new pages.

How to structure a clear, useful HTML sitemap
An effective sitemap is not a raw export of every URL. Readability depends on grouping pages into logical sections and using descriptive link labels. Visitors should be able to tell where each link leads without clicking it.
Pages to include and pages to leave out
Key pages—such as the homepage, main sections, subsections, and service pages like the privacy policy or legal notices—belong in the sitemap. Internal search results, filter pages, and duplicates add no value for visitors and make the sitemap harder to read.
For dynamic sections such as a blog, listing every article individually becomes unmanageable once there are more than a few dozen posts. Grouping content by category or year, with a link to the corresponding archive page, keeps the sitemap readable without sacrificing coverage.
Keeping the sitemap up to date
An outdated sitemap no longer serves its purpose. When new sections are added or pages are removed, the sitemap should reflect those changes. CMS platforms such as WordPress offer plugins that automatically generate a sitemap from the site’s actual hierarchy. Manual generation is still an option for smaller sites, with the advantage of giving you precise control over what appears.
Whether HTML or XML, a sitemap does not replace coherent internal linking or a well-planned information architecture. It acts as a safety net: when the main navigation fails, when the internal search engine can’t understand a query, or when a crawler misses a deep page.
Its value lies less in technical sophistication than in completeness and regular updates.



