You’re looking for a specific page on a website, but you’re faced with an endless menu. You scroll, then eventually give up. There’s a shortcut: the site map, or sitemap, lists all accessible URLs in a single file. Knowing where to find it and how to read it makes all the difference when you want to quickly explore a website’s sections and content.
robots.txt file: the first place to look for a sitemap
Before trying random URLs, open the robots.txt file for the site you’re interested in. Simply type the domain followed by /robots.txt in your browser’s address bar. This text file, intended for crawlers, often contains a line beginning with Sitemap: followed by the exact URL of the sitemap.
This method works on most professional websites because popular CMS platforms (WordPress, Shopify, Wix) generate this declaration automatically. When the line is present, copy the URL, paste it into your browser, and go straight to the XML file listing the pages.
You’ll find the same approach on the Mister Tendance sitemap, which brings all the sections together in a structured file you can access in seconds.
If robots.txt doesn’t mention a sitemap, that doesn’t necessarily mean the file is missing. It may simply not have been declared, which brings us to the second approach.

Common paths and Google search operators for finding a sitemap
Most sitemaps are located at predictable addresses. First try domain.com/sitemap.xml, then /sitemap_index.xml, /sitemap/, or /wp-sitemap.xml for newer WordPress sites. On Shopify, the standard path is /sitemap.xml; on Wix, it’s often /sitemap.xml as well.
When no standard path works
Turn to Google. The search operator site:domain.com filetype:xml returns XML files indexed by the search engine. Not every sitemap is indexed, but this query finds the ones that are, including secondary files that site administrators may have overlooked.
Another option is to search for site:domain.com inurl:sitemap. This query targets URLs containing the word “sitemap” and brings up HTML sitemap pages, not just XML files.
Reading an XML sitemap: find sections without getting lost
Opening an XML sitemap in a browser displays a list of URLs between tags. The structure may look austere, but it provides useful information if you know what to look for.
- Sitemap index files group several topical sitemaps (articles, products, categories). Each link in the index leads to a subfile covering one section of the site, making it easy to go straight to the section you’re looking for.
- The
<loc>tag gives the URL of each page. Scanning these URLs quickly reveals categories, subfolders, and the site’s organizational structure. - The
<lastmod>tag shows the date of the last modification. It’s reliable only if the webmaster updates it when content actually changes, rather than with every technical deployment.
The <changefreq> and <priority> tags still appear in some files, but Google says it doesn’t use them to decide which pages to crawl first. You can ignore them without missing any useful information.
HTML sitemap or XML sitemap: two different purposes
Some sites offer an HTML sitemap page accessible from the footer. This version is designed for human visitors: it displays sections as clickable links, often organized by category. An XML sitemap, by contrast, is intended for search engines and lists URLs in raw form.
For quickly browsing content, the HTML version is easier to read. For auditing a site’s full structure or checking whether a page exists, the XML file remains the go-to reference.

Use a sitemap to access hidden or deeply nested content
A navigation menu shows only a fraction of a site’s pages. Deep pages (older articles, archived product pages, tag pages) often don’t appear in any menu. A sitemap lists them if the webmaster has configured its automatic generation correctly.
In practice, open the sub-sitemap for articles or products, then use your browser’s search function (Ctrl+F or Cmd+F) to filter by keyword directly in the file. In a sitemap containing thousands of URLs, this local search is much faster than browsing page by page.
Limitations to keep in mind
A sitemap doesn’t guarantee a complete inventory. Pages blocked by robots.txt or not declared won’t appear in it. Orphan pages (with no internal links) may also be missing if they were never added to the file manually.
The protocol allows up to 50,000 URLs per sitemap file. Large sites therefore split their sitemap into multiple topical files using an index. This makes it easier to find sections, as long as you understand the site’s naming convention (by publication date, category, or content type).
Summary of ways to find a sitemap
| Method | When to use it | Reliability |
|---|---|---|
| robots.txt file | First place to look; works on most sites | High if the sitemap is declared there |
| Standard paths (/sitemap.xml) | When robots.txt doesn’t mention anything | Good on popular CMS platforms |
| Google operators (site: filetype:xml) | When standard paths don’t work | Varies depending on indexing |
| HTML sitemap (footer) | Quick browsing for visitors | Depends on how well the site is maintained |
A sitemap is still the most direct way to understand how a site organizes its content. Start with robots.txt, try the standard paths, then move on to search operators to cover almost every case. Once the file is open, searching for keywords in your browser does the rest.



