On a dedicated housing platform, the volume of published content often exceeds what a main menu can reasonably display. Service pages, housing sheets, energy renovation guides, work request forms: the depth of the hierarchy makes traditional navigation insufficient to reach certain sections. The site map, often relegated to the footer, then fulfills a function that neither the menu nor the internal search engine fully covers.
The site map as a regulatory audit tool on housing platforms
The RGAA (General Reference for Improving Accessibility) requires public organizations and private companies whose revenue in France exceeds a certain threshold to make their digital services accessible. In this context, the site map page is one of the mandatory pages to audit, alongside the homepage, contact page, or legal notices.
For a social landlord, a community, or a large real estate company, this obligation changes the game. The site map is no longer just an ergonomic shortcut: it becomes a regulatory control point. Its compliance with accessibility criteria partly determines the overall score of the RGAA audit.
Three documents must accompany this process:
- An accessibility declaration for each site or service, specifying the compliance rate and any exemptions
- A multi-year accessibility plan, covering a maximum duration of three years
- An annual action plan detailing the planned compliance work
These documents must be easily retrievable from the site. When properly structured, the site map serves as an entry point to these resources for both auditors and users. Navigating the ID Habitat site map illustrates this logic: each section is presented linearly, making it easier to locate strategic pages without going through multiple menu levels.
Limitations of the main menu on a housing and renovation site
A traditional navigation menu works by thematic grouping. On a housing platform, this often translates into entries like “Housing,” “Work,” “Aid,” “My Account.” The problem arises when the user is looking for information that does not exactly fit these categories.
Let’s take a concrete case. A homeowner wants to check the eligibility conditions for energy renovation aid in their municipality. This page could be categorized under “Aid,” “Renovation,” or a geographical section. The menu reveals only one or two levels of depth, forcing users to guess the classification logic chosen by the site designer.
The internal search engine partially compensates for this flaw, provided the user types the right terms. Field feedback varies on this point: some users formulate queries that are too broad (“work aid”), while others are too specific (“subsidy for attic insulation 2025 intercommunity”). In both cases, the results can drown the relevant page in related content.
What the site map exposes and what the menu hides
The site map displays the entire hierarchy in the form of a structured list. Each page is listed with its exact title, without truncation or artificial grouping. For a user who cannot find what they are looking for via the menu, browsing the site map is akin to consulting the complete table of contents of the platform.
This comprehensiveness has a useful side effect: it allows users to discover sections they were unaware of. On a housing site, this may include the housing information booklet, energy consumption simulators, or service pages specific to a neighborhood or construction program.
Digital accessibility and alternative navigation on housing platforms
The RGAA recommends providing at least two means of navigation among a main menu, a site map, and a search engine. This requirement is not arbitrary. Each means of navigation caters to a different user profile, and none alone is sufficient to cover all cases.
Screen reader users, for example, often browse the site map rather than the dropdown menu. A menu rich in sub-levels, poorly marked in ARIA, can become an obstacle. The site map, structured in simple HTML lists, offers a readable alternative for assistive technologies without special configuration.
The available data does not allow for a conclusion on the exact proportion of users who prefer the site map over the menu. However, the recommendations from AcceDe Web and the RGAA converge: removing the site map from a public platform exposes it to a compliance defect during an accessibility audit.
Case of platforms with dual audiences
Many housing sites cater simultaneously to tenants, homeowners, housing applicants, and construction professionals. This multiplicity of profiles complicates menu navigation, as the priority entries differ depending on the visitor.
The site map neutralizes this problem. It does not prioritize content by target audience but by technical structure. A housing applicant and a construction professional find the same links, organized according to the actual architecture of the site. This neutrality of presentation avoids navigation dead ends related to poor entry choices in the menu.
XML site map and HTML site map: a useful distinction for housing
The confusion between XML site maps (intended for search engines) and HTML site maps (intended for human visitors) persists on many platforms. Some housing sites only offer an XML sitemap, accessible only via the technical URL, without an equivalent HTML version viewable by users.
The HTML site map serves a navigation function. It lists pages in a readable, clickable, organized format. The XML sitemap, on the other hand, is for indexing: it informs indexing bots of the update frequency and the relative priority of the pages.
- The HTML map helps users find a specific page on the site, such as a sheet on renovation aids or a housing application form
- The XML sitemap helps Google discover and index newly published pages, particularly recently added construction program sheets
- Both formats can coexist and complement each other, but only the HTML map meets the RGAA accessibility requirement
On a housing platform that regularly publishes new content (real estate programs, regulatory updates, information on energy consumption), maintaining both versions up to date requires editorial discipline. An outdated HTML map, which no longer reflects the actual hierarchy, loses all usefulness and can even mislead.
The site map remains an underestimated tool in the digital ecosystem of housing. Its dual function, aiding navigation for users and serving as a control point for regulatory compliance, makes it a structural element that platforms should keep updated rather than treat as a secondary page.
