A patient is trying to download their test results from a health portal. They click on “My space,” land on a login page, go back, attempt a dropdown menu that leads to a general FAQ. Three minutes wasted, no answer.
On a health website, this type of friction is not just a minor inconvenience: it discourages people who may not be comfortable with digital tools and delays access to medical information. The sitemap, whether intended for search engines or visitors, structures navigation and reduces these dead ends.
HTML Sitemap on a Health Website: A Map Designed for the Patient
We often talk about the XML sitemap, the one that Google crawls to index pages. On a health portal, the HTML sitemap is equally important, if not more so. It is the page accessible to visitors that lists all the sections of the site with direct links.
The uniqueness of a health website is the diversity of profiles that consult it: elderly patients, family caregivers, healthcare professionals, people with disabilities. A generic HTML sitemap (an alphabetical list of links) is not enough. It is necessary to segment the sections by concrete use: “Make an appointment,” “Access my results,” “Emergency,” “Teleconsultation.”
To see how this logic translates into practice, one can consult the sitemap page of Tsa E-Santé, which organizes its content by health themes rather than by technical hierarchy.
This patient-oriented segmentation changes the game: instead of searching through a three-level menu, the visitor can quickly spot the section that corresponds to their immediate need.
RGAA Accessibility and Sitemap: Constraints Ignored by Traditional Guides
French medical websites are subject to the RGAA 4.1 reference framework, which imposes specific rules on page structuring. These requirements have a direct impact on the design of a navigation-oriented sitemap.
- The hierarchy of headings must be consistent: one H1 per page, H2 for main sections, H3 for subsections. An HTML sitemap that uses headings out of order will be flagged during an accessibility audit.
- Navigation must work entirely via keyboard. Each link in the sitemap must be reachable using the Tab key, with a visible focus. Pure JavaScript menus that hide links pose problems.
- Color contrasts must meet a minimum ratio for standard text. A sitemap with light gray links on a white background will be unreadable for some patients.
- Any image carrying information requires a textual alternative. If the sitemap uses icons to distinguish sections, each icon must have a descriptive alt attribute.
Since 2025, French public health portals are subject to scheduled accessibility audits as part of multi-year plans. An RGAA non-compliant sitemap becomes a blocking point during these checks, not a cosmetic detail.
XML Sitemap for Health Page Indexing: What Changes Compared to a Standard Site
On an e-commerce site, we want to index product sheets. On a health site, the logic is different. Some pages contain personal health data protected by GDPR and HDS regulations (health data hosting). These pages should never appear in the XML sitemap.
Specifically, we exclude from the sitemap.xml file all pages behind authentication: patient area, test results, secure messaging, medical records. However, we include publicly accessible pages with high informational value: pathology sheets, regulatory updates, prevention guides, teleconsultation modalities.
Coordinate XML Sitemap and robots.txt File
The robots.txt file and the XML sitemap work together. The robots.txt blocks the crawling of sensitive directories (/mon-espace/, /resultats/, /messagerie/), while the XML sitemap explicitly signals the public pages to be prioritized for crawling.
A common mistake on health websites: forgetting to block in robots.txt test or staging pages that contain realistic but fictitious data. Feedback varies on this point depending on the CMS used, but checking the consistency between robots.txt and sitemap at least once a quarter remains a good practice.
Structuring the Sitemap to Guide Patients’ Daily Navigation
Beyond SEO, a well-designed sitemap serves as a safety net for navigation. When a patient cannot find what they are looking for via the main menu, the site map becomes their fallback.
For this fallback to work, we organize the HTML sitemap around patient journeys rather than administrative categories. The difference is concrete:
- “I want to make an appointment” rather than “Scheduling module”
- “I’m looking for a specialist near me” rather than “Directory of healthcare professionals”
- “I want to understand my prescription” rather than “Documentary resources”
This rephrasing work requires understanding the actual queries of patients. The site’s internal search data (the search field that visitors use) provides valuable clues about the vocabulary to adopt in the sitemap.
Updating the Sitemap After Adding Health Content
A health website regularly publishes new content: sheets on pathologies, regulatory news, prevention campaigns. Each new public content must be added to the XML sitemap within days of publication, otherwise Google may take weeks to discover it.
Most health CMSs automatically generate the XML sitemap. Nevertheless, we check that the new pages are included, especially when they are created manually outside the standard editorial flow.
An effective health sitemap is not a technical file generated once and forgotten. It is a navigation tool that reflects the real needs of patients, complies with French accessibility standards, and protects sensitive data by excluding private pages. Keeping it updated and thinking from the visitor’s perspective, not the developer’s, makes the difference between a functional health portal and a digital maze.