An XML sitemap is more than a passive file placed in a server’s root directory. Used correctly, it becomes an auditing, diagnostic, and discovery tool that goes well beyond SEO. Understanding how it works internally can reveal insights that conventional site navigation does not.
Use your sitemap to audit site structure
One practical use of a sitemap, often overlooked in general guides, is comparing the URLs it lists with those actually accessible through the site’s internal links. A gap between these two sets points to orphaned or poorly linked pages.
Download the XML file (usually available at /sitemap.xml or /sitemap_index.xml), then compare it with a full site crawl to identify three categories: URLs found both in the sitemap and the crawl, URLs found only in the sitemap (isolated pages), and URLs found in the crawl but missing from the sitemap (omitted URLs).
This inventory method works for any public website. For example, Mon Habitat’s sitemap reveals the site’s complete structure, making it easy to see the full range of published resources without manually browsing every section.
For large websites, we recommend automating this comparison with a spreadsheet or a script that parses the XML and compares it with the URLs found during the crawl. Discrepancies can reveal internal linking issues before they affect indexing.

The lastmod tag in an XML sitemap: reliability and pitfalls
The <lastmod> tag indicates the date a page was last genuinely modified. Google may use it to prioritize recrawling, but only when the date reflects an actual content change. Updating the lastmod value with every technical deployment, without making editorial changes, sends a misleading signal.
The most common pitfall is a CMS that automatically regenerates the lastmod date when a template changes or a plugin is updated. If the search engine finds that the dates do not correspond to actual content updates, it may eventually ignore the tag across the entire domain.
Check that the dates are consistent
Compare the declared lastmod date with the modification date shown on the page (or in the Last-Modified HTTP headers) to spot inconsistencies. A systematic discrepancy between the two values indicates a CMS configuration issue.
- Keep the lastmod tag only on pages whose editorial content changes regularly
- Remove lastmod from static pages (legal notices, terms and conditions) rather than displaying a misleading recent date
- Configure the CMS to update lastmod only when a page is manually saved or a text field is changed
The sitemap report in Google Search Console: what it shows and what it doesn’t
The sitemaps report in Search Console displays three pieces of information: whether the file was read, any syntax errors, and the number of URLs discovered. This report does not confirm that URLs have been indexed. A “discovered” URL may remain in the crawler’s queue indefinitely without ever being indexed.
To verify actual indexing, compare the sitemap report with the coverage report (or the “Pages” report in the current version of Search Console). URLs listed in the sitemap but missing from the index will then appear with a reason for non-indexing: duplicate page, redirect, blocked by robots.txt, or deemed to offer no added value.
Submit a sitemap to Bing via Bing Webmaster Tools
Google is not the only search engine that uses sitemaps. Bing Webmaster Tools accepts direct sitemap submissions and also supports the IndexNow protocol, which lets you report URL additions, changes, or removals in real time. This protocol complements the sitemap for sites whose content changes frequently.

Sitemap index: structuring an XML file for large websites
A single sitemap file is subject to size limits: a maximum uncompressed file size and a maximum number of URLs per file. When a site exceeds these limits, the solution is to use a sitemap index, a parent XML file that references multiple child sitemaps.
Each child sitemap groups a logical section of the site: blog posts, product pages, or category pages. This segmentation makes it possible to monitor indexing by content type in Search Console, since each child sitemap has its own report.
- Segment by content type (articles, products, media) rather than alphabetically or chronologically
- Use descriptive filenames (sitemap-articles.xml, sitemap-produits.xml) to make troubleshooting easier
- Declare the sitemap index in the robots.txt file using the Sitemap: directive followed by the file’s full URL
- Make sure each child sitemap contains only canonical URLs, with no session parameters or duplicates
Access a third-party site’s sitemap to map its resources
Exploring the resources of a website you do not own often starts with checking its sitemap. Most sites make this file publicly accessible. Two common entry points are the direct URL /sitemap.xml and the Sitemap directive in the robots.txt file (available at /robots.txt).
Some CMS platforms generate sitemaps at non-standard paths (/sitemap_index.xml, /wp-sitemap.xml for WordPress). Checking robots.txt remains the most reliable way to locate the file, since the directive points to its exact URL.
Once you have retrieved the file, opening it in a browser displays a raw list of URLs. For structured analysis, an XML parser or a simple spreadsheet import lets you filter by section, date, or URL depth. This approach is particularly useful for analyzing a competitor’s editorial coverage or inventorying a portal’s resources before a migration.
A sitemap is still a declarative file: it reflects what the webmaster chooses to make visible to search engines. Some pages may be deliberately excluded. Comparing the sitemap with an external crawl gives you a more complete picture of the site’s actual architecture.



