A sitemap is an XML file that lists a website’s URLs. Search engines read it to discover and crawl the available pages. Accessing a third-party site’s sitemap can help you understand its structure, identify recent content, or find pages that aren’t highlighted in the usual navigation.
Reading an XML sitemap: what each tag tells you
Before looking for a site’s sitemap, it helps to know what to look for. An XML sitemap mainly contains <loc> tags, each enclosing a URL. This is the raw list of pages the site owner wants search engines to find.
Two other tags are worth noting. The <lastmod> tag indicates when a page was last modified. However, Google says this date is reliable only if it reflects an actual change to the content. An artificially updated date is not a useful signal.
The <priority> tag assigns each URL a value between 0 and 1. Google does not use this value for ranking. It simply reflects the hierarchy the site owner assigns to their own pages, which can offer a clue as to which content they consider most important.
Some sites use a sitemap index instead of a single file. This parent file links to several child sitemaps organized by content type (articles, products, categories, images). For example, exploring the Vos Jeux sitemap reveals this kind of segmented structure, making it easier to browse by section.
How to find a website’s sitemap
The file’s location depends on the site’s technical setup. There are several ways to find it, from the most reliable to the more exploratory.
Start with the robots.txt file
The robots.txt file is always located at the root of a domain and can be accessed at an address such as domain.com/robots.txt. It often contains one or more lines beginning with “Sitemap:”, followed by the file’s full URL. This is the quickest and most direct method.
Try standard paths based on the CMS
If robots.txt doesn’t mention a sitemap, try the most common URLs:
- /sitemap.xml works on most sites, regardless of the CMS they use
- /sitemap_index.xml is used by WordPress sites with SEO plugins such as Yoast or Rank Math
- /1_index_sitemap.xml is a common path for Prestashop stores
- Shopify sites generally place their file at /sitemap.xml, which links to child sitemaps by type (products, collections, blog posts)
If none of these URLs returns a result, the site may not generate a public sitemap, or the file may have a custom name.
Use Search Console or Bing Webmaster Tools
For a site you own or have administrative access to, Google Search Console displays submitted sitemaps in its dedicated section. Bing Webmaster Tools offers a similar report. Comparing the two tools can help identify a file that one search engine processes correctly but the other has trouble with.
A processed sitemap doesn’t mean its pages are indexed
A common mistake is to confuse sitemap submission with page indexing. A successfully processed sitemap does not guarantee that its URLs will appear in search results.
Google recommends comparing the Sitemaps report with the Page indexing report in Search Console. Inspecting URLs individually can confirm whether a URL listed in the sitemap has been crawled and indexed, or ignored.
This distinction matters when exploring a third-party site’s sitemap to assess its actual coverage. The XML file shows what the site owner wants to make visible, not what Google has decided to show.
Use a sitemap to identify useful pages
Once you’ve opened the file, the challenge is no longer finding it but picking out relevant pages from hundreds or even thousands of URLs. A few techniques can speed up the process.
Filter by directory in the URL to target a specific type of content. URLs containing /blog/ point to articles, those with /produit/ or /product/ to a catalog, and those with /category/ to classification pages. This structural overview gives you a sense of the site’s architecture without having to browse page by page.
The <lastmod> dates can help you sort content by recency, provided they’re reliable. If a site updates this date for every minor change (such as a sidebar update or adding a tag), sorting by date becomes less useful. A well-maintained site, on the other hand, makes it possible to spot recent publications in seconds.
When a sitemap isn’t enough
A sitemap doesn’t always list every page on a site. Orphaned URLs, dynamically generated pages, and content deliberately excluded from the XML file won’t appear in it. For a complete audit, an SEO crawler (Screaming Frog, Sitebulb) follows links across the site and identifies pages missing from the sitemap.
- The crawler identifies pages accessible through internal navigation but missing from the sitemap
- It detects URLs with errors (404s, redirect chains) that are still listed in the sitemap
- It lets you compare the site’s actual structure with the structure declared in the XML file
A sitemap is a quick discovery tool, not an exhaustive inventory. Combining the XML file with a technical crawl gives you a complete picture of a site’s architecture. For a quick check, the sitemap is enough. For an in-depth audit, it’s a starting point, not the finish line.
