On an online health platform, a sitemap serves a purpose that the search bar cannot: it displays the entire site structure on a single page. When users are looking for specific health information, keyword searches assume they already know the right terminology. A sitemap removes that constraint by making the full editorial structure visible, from the main sections to the most deeply nested pages.
Site structure and keyboard navigation on a health website
A sitemap’s quality is first measured by its hierarchical heading structure. On a health portal, sections cover a wide range of topics: prevention, medical conditions, patients’ rights, and directories of healthcare professionals. If the sitemap does not reflect this hierarchy with consistent heading levels (H2 for sections, H3 for subsections), users lose the benefit of the overview.
Keyboard accessibility is a technical criterion that is often overlooked. France’s RGAA accessibility standard includes the sitemap among the pages sampled during an accessibility audit. Every link must be reachable using the Tab key, with a clear label that describes the destination page—not a generic “click here.”
Assistive technologies, especially screen readers, rely on the DOM order to present a page. If the navigation order in a sitemap does not match its thematic structure, it becomes an obstacle rather than a shortcut. This is what distinguishes a functional sitemap from a decorative one.
Finding reliable health sections through a sitemap
We recommend starting any health-related search with the sitemap rather than the internal search engine, when the portal provides one. The reason is simple: a sitemap reveals the true breadth of the available content. An internal search engine only returns what its algorithm considers relevant to the query. A sitemap shows what is there.
On platforms such as Santé.fr, which indexes several thousand editorial resources and lists hundreds of thousands of healthcare professionals, the sheer volume of information makes conventional menu navigation inadequate. A well-structured sitemap helps users find sections that are not highlighted in the main menus, such as clinical trials, medical glossaries, and regional content produced by regional health agencies.
The same principle applies to specialist portals. By consulting the Santé 365 sitemap, users can see at a glance which categories are covered and how deeply they are organized, avoiding the need to navigate nested menus blindly.
What to check in a health sitemap
- Link labels should describe the content of the destination page. A label such as “Article 47” does not do this, unlike “Symptoms and treatment of type 2 diabetes.”
- The sitemap should be updated whenever the website is updated. If it does not list pages published in recent months, that points to a maintenance issue.
- Separate sections for institutional content (official recommendations, regulations) and editorial content (articles, guides) make it easier to assess the level of evidence.
XML sitemap and HTML sitemap: two different uses in healthcare
The HTML sitemap is for visitors; the XML sitemap is for search engines. The two are often confused, even on large health portals. The sitemap.xml file, intended for Google and other indexing bots, lists URLs along with metadata such as the last modified date and update frequency. It is of no direct use to someone looking for information about a medical condition or care pathway.
An HTML sitemap, by contrast, is a navigable page. This is the version that should be accessible from the footer or main menu. On institutional health websites subject to the RGAA, this page is included among the elements required in the audit sample.
A portal that offers only an XML sitemap, with no HTML equivalent, deprives users of a practical navigation tool. This technical choice undermines the user experience, particularly for people who are unfamiliar with the medical terms needed for keyword searches.
Digital accessibility and regulatory requirements for health websites
Public health organizations must comply with France’s RGAA framework for website accessibility. Since June 28, 2025, the European Accessibility Act has introduced new requirements for certain consumer-facing services, including e-commerce. This directive does not apply indiscriminately to all health websites, but it expands the range of organizations covered.
Compliance involves more than publishing a sitemap. The French framework also requires an accessibility statement and a user feedback mechanism. An accessible sitemap surrounded by non-compliant pages does not meet regulatory requirements.
What this means for finding health information
- A website that complies with the RGAA ensures that sitemap links work with screen readers, which also benefits sighted users who need to navigate quickly.
- The requirement to use clear labels in navigation encourages publishers to give pages descriptive names, making the sitemap easier to understand.
- When published, an accessibility statement provides information about the website’s actual level of compliance. It is an indicator of the portal’s technical reliability.
A well-designed sitemap on a health portal is not a footer gimmick. Combined with a coherent site structure and descriptive labels, it is a navigation tool that reduces the time needed to find reliable information. Checking whether a sitemap is available and assessing its quality before browsing remains one of the most overlooked habits when searching for health information online.
