An HTML sitemap lists all the pages of a domain in the form of clickable links, organized by section. On a site dedicated to responsible construction, this page focuses on dozens of topics (thermal regulations, environmental labels, manufacturer sheets, project feedback). Knowing how to read this structure allows you to locate specific information without going through the internal search engine, which is often limited on niche sites.
Digital accessibility and sitemap: what the European Accessibility Act changes
Since June 28, 2025, the European Accessibility Act extends the obligation of accessibility to the private sector. E-commerce services, banking services, passenger transport, telecommunications, and audiovisual media are concerned. Microenterprises with fewer than 10 employees and a turnover or balance sheet not exceeding 2 million euros benefit from an exemption.
For a showcase site like that of a network of builders, the question arises differently. Sites falling under Article 47 of the 2005 law must publish an accessibility statement, a multi-year plan, and annual action plans. The EAA, on the other hand, targets services intended for consumers. It is therefore necessary to first determine whether the site is a simple showcase or a transactional space with online booking or quotes.
A well-structured sitemap facilitates keyboard navigation and reading by assistive technologies. However, its mere presence does not demonstrate accessibility compliance. Automated tests only cover part of the criteria. The consistency of paths, link titles, and actual usage with a screen reader require human checks.
Consulting the Constructeurs Responsables sitemap gives a first idea of the overall structure, but a complete audit would require checking each link in a real navigation path.
Typical structure of a sitemap in the construction sector
Websites specialized in construction and building share a recurring architecture. The table below compares the sections typically found on these types of platforms and their usefulness for a visitor seeking technical information.
| Sitemap Section | Expected Content | Usefulness for Navigation |
|---|---|---|
| Institutional Pages | Company presentation, legal notices, contact | Low for technical search, useful for verifying the legitimacy of the site |
| Manufacturer Sheets / Directory | List of referenced professionals, geographic areas | High if the visitor is looking for a specific builder in their region |
| Editorial Content (blog, news) | Articles on standards, labels, materials, project feedback | High for regulatory and technical monitoring |
| Regulatory Pages | RE2020, BBC labels, NF Habitat certifications | High for professionals and project owners |
| Downloadable Resources | PDF guides, product sheets, BIM documents | Variable depending on the update of documents |
Editorial content and regulatory pages concentrate the majority of value for a visitor in the building sector. Institutional pages, on the contrary, rarely provide information that would not be found on the homepage.
The case of dynamic sections
The blog or news sections pose a readability problem in a sitemap. If each published article generates an additional line, the page becomes an inventory of several hundred links. An effective sitemap groups these contents by category or by year rather than listing everything flatly.
On a site dedicated to responsible construction, articles cover topics as varied as bioclimatic design, bio-sourced materials, or project management. A thematic grouping makes the sitemap truly navigable, where an alphabetical or chronological list drowns out relevant information.
Concrete verification of a sitemap: points to check
Accessing the sitemap is not enough. Its usefulness depends on specific technical criteria that a visitor can verify in a few minutes.
- Each link must point to an active page, without 404 errors or chain redirections. A broken link in the sitemap indicates a lack of content maintenance.
- Link titles must be explicit. A label like “page 1” or “article from March 12” does not indicate what will be found behind the link, neither for a human nor for a screen reader.
- The visual hierarchy (indentation, section titles) must reflect the actual structure of the site. If the sitemap displays sections that no longer exist in the main menu, it is a sign of a desynchronization between the published content and the navigation page.
- Old content and some third-party content may fall under regulatory exceptions. The French implementing decree notably excludes office documents published before a certain date and third-party content not funded by the organization.
An up-to-date sitemap reflects the overall quality of maintenance of the domain. Conversely, a page that has been static for several months often indicates that other aspects of the site (security, mobile compatibility) are also neglected.
HTML sitemap and XML sitemap: two complementary tools for SEO
The confusion between HTML sitemap and XML sitemap file persists. The HTML sitemap is a web page intended for human visitors, accessible from the footer. The XML sitemap is a technical file intended for search engines, which lists URLs with their modification dates and update frequency.
For a responsible construction site, the XML sitemap ensures the indexing of deep pages (technical sheets, design documents, old articles) that crawlers might not always discover through internal linking alone. The HTML sitemap, on the other hand, serves visitors looking for an overview of the editorial offering.
The two formats complement each other without replacing one another. A site that only has an XML sitemap deprives its visitors of a direct navigation tool. A site that offers only an HTML sitemap without an XML sitemap risks having its least linked pages ignored by search engines.
The sitemap page of a domain specialized in responsible building should be updated with each significant publication, especially when new regulatory pages or new manufacturer sheets are added. A regular synchronization between the HTML sitemap and the XML sitemap avoids indexing discrepancies.
