A sitemap brings together the URLs on a domain in a dedicated file or page. Checking the sitemap lets you quickly see how the content is organized, which sections are available, and which pages have been added recently. Two formats coexist: XML for bots and HTML for visitors. Each provides different information about a website’s structure.
XML sitemap and HTML sitemap: what each format reveals
Both formats share the same name, but they serve different audiences and contain different metadata. Knowing which one to check before exploring a site can save you time.
| Criterion | XML sitemap | HTML sitemap |
|---|---|---|
| Primary audience | Search engine bots | Human visitors |
| File format | Machine-readable .xml file | Standard web page with clickable links |
| Information provided | URL, last modified date, priority, update frequency | Page titles, hierarchy by section |
| Typical access | domaine.com/sitemap.xml | Footer link or dedicated URL |
| Known size limit | Up to 50,000 URLs per file | No technical limit, but readability suffers beyond a few hundred links |
The XML file is useful for checking when a page was last modified or finding orphaned URLs. The HTML version, on the other hand, offers direct, hierarchical navigation. If you’re exploring a site as a visitor, the HTML page is the quickest place to start.
For example, the Take The Capital sitemap provides access to all the sections on the domain through links organized by category, making it easy to find specific content without using the search bar.
Finding a domain’s sitemap: practical methods
Not all sites make their sitemap visible in the same way. Some display it in the footer, while others generate it automatically through a CMS without ever including it in the navigation.
Try standard URLs
Start by adding /sitemap.xml or /sitemap_index.xml to the domain root. Most CMS platforms (WordPress with Yoast or Rank Math, Shopify, Wix) create this file by default. If your browser displays a structured XML document, the sitemap exists and you can browse its URLs.
For the HTML version, try /plan-du-site, /sitemap, or /sitemap.html. The URL varies depending on the site’s language and configuration.
Check the robots.txt file
The robots.txt file, available at domaine.com/robots.txt, often contains a “Sitemap:” line followed by the exact address of the XML sitemap. This method works even when the sitemap isn’t indexed in Google.
Use the site: operator with caution
Entering site:domaine.com in Google displays some of the indexed pages. This command doesn’t provide a complete inventory: Google notes that a site: operator search doesn’t necessarily return every URL indexed under a domain. Recent or protected pages may be missing.
Limitations of sitemaps when exploring a website
A sitemap doesn’t always reflect the content that’s actually accessible. Three discrepancies are common and worth keeping in mind.
- URLs in the sitemap return a 404 error. The file may retain URLs for pages that have been deleted or moved if the owner hasn’t updated it.
- Pages accessible on the site may not appear in the sitemap. Content behind a login, draft pages, or pages simply overlooked when the file was generated can be missing.
- Being listed in the sitemap guarantees neither crawling nor indexing by Google. A listed URL may never be crawled if the bot considers the content irrelevant or the domain’s crawl budget is limited.
To get an accurate picture of a site’s architecture, cross-checking the sitemap against internal links is the most reliable method. A crawling tool such as Screaming Frog or Xenu can also compare the URLs listed in the sitemap with those actually accessible through the site’s links.
Sitemaps and navigation: two complementary tools for exploring a site
A sitemap provides a flat view of all declared URLs. Standard navigation (menus, contextual links, breadcrumbs) reveals the actual hierarchy and relationships between content. Neither is sufficient on its own.
Visitors looking for a specific page can save time by checking the HTML sitemap first. To understand how sections fit together, menus and internal links provide context that the sitemap doesn’t.
For SEO professionals, the XML sitemap serves as a reference list to submit through Google Search Console. Comparing this list with crawl data highlights orphaned pages (listed in the sitemap but with no internal links pointing to them) and indexed pages missing from the sitemap—two useful signals for improving site architecture.
A sitemap works like a table of contents: it guides you and speeds up your search, but it doesn’t replace reading the content. Consistently cross-checking the sitemap against internal links gives you the most complete map of a domain, including its active areas and blind spots.
