How to Easily Find a Website’s Sections and Resources Using Its Sitemap?
An XML sitemap lists raw URLs, not a navigation hierarchy. This distinction changes how you use the file to find a site’s sections. Reading a sitemap without a method is like browsing a phone book with no alphabetical order: the information is there, but it isn’t useful as is.
XML sitemap and HTML sitemap: two files with different purposes
An XML sitemap is a technical file intended for search engine crawlers. It contains a list of URLs enclosed in <url> and <loc> tags, sometimes accompanied by metadata such as the last modified date or update frequency. This file describes neither the hierarchy of pages nor how they are grouped into sections.
An HTML sitemap, by contrast, is a web page designed for visitors. It presents sections, categories, and subcategories as clickable links arranged visually. This is the format that lets you find a resource through logical navigation.
It’s easy to confuse the two. Someone who types /sitemap/ into the address bar may land on an unreadable XML file or a structured HTML page, depending on how the site is configured. To illustrate the difference, the Geektroniques sitemap provides an organized view of content grouped by section, whereas its XML equivalent is intended solely for Googlebot.
When the goal is to find content as a user, the HTML sitemap is the right tool. The XML sitemap is only relevant for an SEO audit or technical migration.

Limitations of XML sitemaps for finding a site’s resources
Google points out that a URL included in a sitemap is not necessarily crawled or indexed. The file helps search engines discover pages, but doesn’t guarantee they can be accessed. A listed page may return a 404 error, be blocked by robots.txt, or no longer exist in the site’s navigation.
Lastmod dates pose a similar problem. They’re only reliable if the CMS updates them when the content actually changes. We find that many sites regenerate their sitemap with updated dates even when no editorial changes have been made, making this signal useless for assessing how fresh a resource is.
On large sites, the main sitemap is often an index that points to several child files. Google’s documentation sets a limit of 50,000 URLs or 50 MB uncompressed per file. Navigating this fragmented structure to find a specific page means checking each subfile, which isn’t practical for a nontechnical user.
What an XML sitemap doesn’t show
- Hierarchical relationships between pages: the file doesn’t indicate parent or child pages
- Orphan pages missing from the internal link structure, which may appear in the sitemap without being accessible from the menu
- Editorial context: titles, summaries, and categories don’t appear in standard XML sitemap tags
HTML sitemap: navigation structure and finding sections
A well-designed HTML sitemap reproduces the site’s complete hierarchy as an organized list. Main sections appear at the top level, subcategories are indented, and individual pages appear at the bottom level. This format lets you scan all the content in seconds.
For an HTML sitemap to be genuinely useful, it needs to reflect the site’s navigation structure rather than simply list URLs. The best sitemaps use the same labels as the menus, group pages by topic, and stay consistent with the breadcrumb trail.
An up-to-date sitemap reduces the time it takes to find a resource compared with using the internal search engine, which often performs poorly on medium-sized sites. An HTML page at /plan-du-site/ or /sitemap/ acts as a table of contents: it points you in the right direction without requiring you to guess the exact keywords.
How to find a domain’s sitemap
The quickest approach is to try a few common paths in the address bar:
- /sitemap/ or /plan-du-site/ for the HTML version intended for visitors
- /sitemap.xml or /sitemap_index.xml for the technical XML file
- The site’s footer, where a link to the sitemap is often placed as a usability convention
- The robots.txt file (available at /robots.txt), which sometimes specifies the location of the XML sitemap
If none of these options work, the CMS in use can offer a clue. WordPress generates a sitemap at /wp-sitemap.xml, Shopify at /sitemap.xml, and Wix at /sitemap.xml. Each platform uses these standard paths.

Use a sitemap for a quick content audit
Beyond simple navigation, a sitemap (HTML or XML) is a starting point for assessing a domain’s content coverage. Comparing the listed sections with the pages actually accessible from the menu helps identify inconsistencies: abandoned sections, orphan pages, and duplicate content under different URLs.
Cross-referencing the XML sitemap with a technical crawl (Screaming Frog, Xenu) reveals discrepancies between what the site tells search engines and what’s actually live. A URL included in the sitemap but missing from the internal link structure signals an architecture problem.
For visitors simply looking for an article or resource, the HTML version is the most direct option. It avoids relying on the internal search engine, which is often limited in relevance, and provides a comprehensive view that dropdown menus don’t always offer.
Sitemaps remain an underused tool. Most sites have one, but nobody checks it because they don’t know where to find it or what it contains. Trying /sitemap/ or looking for a link in the footer takes less than ten seconds and can save several minutes of aimless browsing.