A website can contain dozens, if not hundreds, of pages. Without a clear reference point, search engines and visitors miss out on useful content. The sitemap page serves this reference point: it lists your URLs so that nothing remains invisible. Understanding how it works allows you to act on two fronts, natural referencing and user experience.
What Google Really Expects from Your Sitemap in 2025
You may have heard about the priority and changefreq tags in XML sitemap files. Google has largely ignored them for several years. The signal that matters today is the lastmod tag, the only reliable indicator for prioritizing crawl.
When this date reflects the actual last modification of a page, the bots know which URLs to revisit as a priority. If the date is incorrect or missing, the search engine wastes time exploring unchanged pages.
Another notable change: since June 2023, Google has closed its ping endpoint for sitemaps. You can no longer “notify” Google of a new sitemap with a simple HTTP call. There are two active methods left: submit the file via the Search Console or declare its path in the robots.txt file with the Sitemap: directive.
Many webmasters think their sitemap is broken because it does not appear in the Search Console. In reality, if the file is only declared in robots.txt, Google discovers it but does not display it in the Sitemaps report of the console. To track its status, it must be submitted manually through the interface. It is on the Skynet System sitemap page that you can observe a concrete example of a well-declared structure.
XML Sitemap and HTML Sitemap: Two Files, Two Audiences
The confusion between these two formats often arises. The XML sitemap is a technical file, readable by indexing bots. It contains a list of URLs with metadata (modification date, notably). Human visitors never consult it directly.
The HTML sitemap, on the other hand, takes the form of a standard web page. It displays a site map organized by sections. Its audience is your visitors.
When the HTML Sitemap Changes the Game for the User
A well-designed navigation menu is sufficient for a five-page site. After a few dozen pages, some content becomes difficult to access: old articles, deep category pages, product sheets that are not prominently featured.
An HTML sitemap page makes accessible in one click what the menu hides in three levels. It is particularly beneficial for e-commerce sites, large blogs, and information portals where the structures are deep.
Which URLs to Include in a Sitemap for SEO
Listing all URLs without sorting is a common mistake. Search engines have a limited crawl budget for each site. Sending hundreds of unnecessary pages in the sitemap dilutes the bots’ attention.
Here are the concrete selection criteria:
- Keep only the canonical URLs: if two addresses point to the same content, only the canonical version (the one declared with the
rel="canonical"tag) deserves its place in the sitemap - Exclude pages without indexing value: internal search result pages, filter pages, login or cart pages
- Ensure that each URL returns an HTTP 200 code. A URL with a 404 error or a 301 redirect in the sitemap sends a bad signal
- Provide a lastmod tag only when the content has actually changed, not with every automatic file generation
A clean sitemap contains fewer URLs but of better quality. Better to have fifty relevant pages than five hundred diluted pages.
Common Errors That Prevent Google from Utilizing Your Sitemap
Some issues regularly appear in technical audits and go unnoticed for months.
- The sitemap is generated but never submitted in the Search Console. It is discovered via robots.txt, with no possible follow-up on the webmaster’s side
- The lastmod dates are updated automatically with each rebuild of the site, even without content modification. Google eventually ignores this signal
- The file exceeds the size or number of URL limits. The XML format allows a maximum per file. Beyond that, an index of sitemaps must be created that points to multiple files
- URLs blocked by robots.txt appear in the sitemap. This conflict prevents indexing and generates warnings in the Search Console
Check the consistency between your sitemap, your robots.txt, and your canonical tags at least once a quarter. These three elements must tell the same story to search engines.
The Pitfall of the Sitemaps Report in the Search Console
The report displays the number of discovered URLs and the number of indexed URLs. A significant gap between the two does not mean that the sitemap is faulty. Google may choose not to index certain pages for quality reasons or duplicate content. This gap is normal on most sites, but it deserves a page-by-page analysis when it exceeds a significant proportion.
The sitemap page remains a technical lever often underutilized. It requires neither an advertising budget nor advanced development skills. A well-filtered XML file, reliable lastmod dates, and a submission in the Search Console are enough to effectively guide Google’s crawl towards your most useful content.
