An XML sitemap is not just a technical file placed at the root of a server. For an agency like Kiwik, whose offerings cover e-commerce, custom development, and natural referencing, the structure of the sitemap directly reflects the functional architecture of all services. Understanding this structure allows for quick identification of available content, thematic silos, and relevant entry points for a web project.
Diagnostic Value of the XML Sitemap for SEO
A well-constructed sitemap functions as a quality control tool, not just as a directory of URLs. We recommend analyzing it in terms of discrepancies between declared URLs and their actual status on the server side.
The presence of a URL in a sitemap does not guarantee its crawling or indexing. Google treats the file as a discovery mechanism, not as a directive. A listed page that returns a 301 redirect, a 404 code, or has a noindex tag pollutes the sitemap without providing any benefit to crawling.
When we audit a sitemap, we prioritize checking three points:
- Each URL returns an HTTP 200 status and corresponds to its canonical version, without duplicates or unnecessary parameters.
- The lastmod field reflects a substantial modification of the page, not a cosmetic update. Google ignores the priority and changefreq fields but utilizes lastmod when the date is reliable.
- URLs blocked by robots.txt or marked as noindex are absent from the file. Their inclusion creates a contradictory signal that reduces the overall reliability of the sitemap in the eyes of the crawler.
Consulting Kiwik’s sitemap with these criteria in mind provides an immediate reading of the technical quality of the existing SEO: each listed URL is accessible, canonical, and relevant for indexing.
Kiwik’s Structure: What the Sitemap Reveals About the Offering
Most visitors navigate through the main menu or the internal search engine. The sitemap offers a different advantage: it exposes the entire structure without layout filters or imposed visual hierarchy.
At Kiwik, the structure distinguishes several silos. Service pages (PrestaShop development, ERP integration, application maintenance) are separated from editorial content (blog, case studies). This separation is not trivial. It reflects a choice of SEO architecture where each thematic silo concentrates its internal authority on a specific cluster of keywords.
A project manager looking to assess the agency’s scope of intervention saves time by browsing the sitemap rather than navigating page by page. Dynamic sections (blog articles, news) appear in their entirety, while the menu often only presents the parent categories.
Difference Between HTML Sitemap and XML Sitemap
The HTML sitemap is aimed at human visitors. It lists pages as clickable links, organized by theme. The XML sitemap targets indexing robots with technical metadata (lastmod, canonical, hreflang if applicable).
Both formats serve complementary, not interchangeable functions. A site that offers only an XML sitemap deprives its users of a direct navigation tool. Conversely, an HTML sitemap alone does not convey any structured information to search engines.
Kiwik maintains both versions. The sitemap accessible from the footer meets the needs of human navigation, while the XML file declared in the Search Console feeds the crawling process.
Optimal Navigation: What the Sitemap Provides for Users with Disabilities
Screen readers navigate pages sequentially. On a content-rich site, finding a specific section without a sitemap requires tabbing through all interactive elements on each visited page.
The HTML sitemap offers a comprehensive view of the structure in a single access point. For a keyboard-navigating user, this eliminates intermediate steps between the homepage and the final destination.
This function is not limited to situations of disability. Any user faced with a site whose organization they do not master (new prospect, technical partner, external service provider) finds a shortcut to the desired page, without relying on the logic of the main menu.
Sitemap and Crawl Budget: Concrete Impact on E-commerce Sites
On a showcase site with a few dozen pages, the issue of crawl budget does not arise. Robots explore all URLs without constraint. On a PrestaShop online store with several thousand product pages, the situation changes radically.
A sitemap that lists clean URLs accelerates the discovery of new product pages. When a catalog frequently evolves (seasonal additions, promotions, end-of-line), a correctly filled lastmod field signals to robots which pages deserve a new visit.
The classic errors we observe on e-commerce sites include:
- URLs with sorting or filtering parameters included in the sitemap, creating hundreds of duplicates for the same product.
- Expired product pages still present, returning a 200 code when they should be redirected or removed.
- A single, monolithic sitemap exceeding the limit of 50,000 URLs, without segmentation into sub-sitemaps by category.
Cleaning the sitemap in these cases means directing the crawl towards high commercial value pages, rather than allowing robots to consume their budget on obsolete or redundant pages.
Kiwik’s sitemap illustrates a controlled approach to this issue: the URLs present correspond to active and indexable pages, without technical noise. For a decision-maker evaluating the SEO rigor of a provider, the cleanliness of the sitemap is a more reliable indicator than a commercial promise.
