A sitemap is an XML file that lists a website’s URLs and sometimes the date they were last modified. Search engines use it to discover and crawl pages more efficiently. For users, the same file provides a readable map of all published content—provided they know where to find it and how to read it.
Find the XML sitemap file via robots.txt
Any website can declare the location of its sitemap in a text file available at the root of the domain. To view it, simply add /robots.txt to the website address, for example https://example.com/robots.txt.
In this file, a line beginning with Sitemap: indicates the exact URL of the XML file. Multiple lines of this type may appear if the site uses several topic-specific sitemaps or a sitemap index.
This method works regardless of the CMS in use. It is the most reliable approach because it relies on an explicit declaration by the site owner, rather than a URL convention. Browsing Optimum Santé’s sitemap takes you directly to the complete structure of the content published on the domain.
If robots.txt does not mention a sitemap, two standard paths are worth checking: /sitemap.xml and /sitemap_index.xml. The first is the most common convention; the second is the structure generated by WordPress plugins such as Yoast SEO or Rank Math.
Sitemap index and child sitemaps: understanding the nested structure
A sitemap file can contain up to 50,000 URLs. Beyond that limit, or when a site separates its content by type (articles, product pages, images, videos), a sitemap index serves as a parent file. It does not list page URLs, but URLs pointing to other sitemaps.
Opening a sitemap index is like viewing a table of contents. Each child sitemap groups a coherent set of pages. On an e-commerce site, one child sitemap might contain product pages, another categories, and a third blog posts.
Find useful sections in a large index
The names of child sitemaps often provide a clue to their contents. A file named post-sitemap.xml will contain articles, while page-sitemap.xml will group static pages. Names vary depending on the CMS and installed plugins, but the logic is the same: each file corresponds to a type of content.
There is no need to browse thousands of URLs across an entire site to find specific information. Identifying the right child sitemap and opening it directly narrows the search to a few dozen or a few hundred relevant pages.
Read sitemap XML tags to filter for recent pages
Each entry in an XML sitemap can contain several tags. Two are particularly useful for exploring a site:
<loc>contains the page’s full URL. This is the key information that lets you access the content directly.<lastmod>indicates the last modification date declared by the site. It helps identify content that was recently published or updated.<changefreq>and<priority>sometimes appear in the file, but Google ignores both fields. Including them does not affect crawl frequency or rankings.
The lastmod tag deserves particular attention. Its reliability depends entirely on how carefully the site is maintained: some CMSs update it every time the file is regenerated, even when the content itself has not actually changed. Comparing the page with a cached version or an archiving tool is the only reliable way to confirm that a date reflects a real change.
Navigate a raw XML file
Opening a sitemap in a browser displays raw XML, which can be difficult to read. The browser’s search function (Ctrl+F or Cmd+F) lets you filter URLs by keyword. Typing a term such as “guide”, “pricing” or “2025” into the search bar brings up matching pages without having to go through the file line by line.
For more advanced processing, copying the content into a spreadsheet or text editor lets you sort URLs by date or by section of the site structure.
Sitemap limitations: what the file does not guarantee
A sitemap lists the URLs that the site owner wants search engines to see. Its presence does not guarantee that the pages it contains will be crawled or indexed. Google may choose not to crawl some listed URLs, or may index others discovered through different means.
The file also does not reflect the entirety of a site. Pages protected by authentication, URLs blocked in robots.txt, or dynamically generated content may be missing. Exploring a sitemap gives you a partial view shaped by the webmaster’s technical choices.
A sitemap containing URLs that return 404 errors or redirects points to a maintenance issue. If several URLs in the file do not load any page, the remaining sitemap information may be out of date.
Sitemaps and information research: practical use cases
Beyond SEO, a sitemap provides a quick starting point for specific tasks:
- Find all the blog posts on a given topic by filtering URLs by keyword in the posts sitemap.
- Estimate the amount of content on a competitor’s site without crawling the entire domain. The number of entries in the sitemap gives a reliable ballpark figure for the number of published pages.
- Identify recently updated pages using the
lastmodtag, so you can follow a site’s editorial updates without checking it manually every day. - Check whether a specific page is listed in the sitemap, confirming that the site owner considers it relevant for indexing.
A sitemap is a useful alternative to a full crawler when you simply want to know which pages exist. A crawler follows internal links page by page, using time and bandwidth. A sitemap provides the list in a single HTTP request.
Reading a sitemap is a simple technical task that requires no paid tools. A browser, its built-in search function and, for large files, a spreadsheet are all you need to extract useful information from a well-structured site.
