A site of eighty pages, half of which do not appear on Google, is a concrete problem we encounter regularly. The cause is often the same: no XML sitemap in place, or an outdated file that no one has checked for months. The sitemap remains the most direct way to signal to search engines the URLs that matter on your website.
Orphan pages and wasted crawl: the problem the sitemap solves
On a site that grows through successive additions (product sheets, blog articles, seasonal landing pages), some pages end up without any internal links pointing to them. Crawlers like Googlebot cannot guess they exist. Without a sitemap, these orphan pages remain invisible.
The XML sitemap file provides a complete inventory of URLs to be crawled. It is submitted to Google Search Console or Bing Webmaster Tools, and the crawlers know exactly where to look. The sitemap does not replace internal linking; it complements it by covering blind spots.
A common example: a new category of content is published on a showcase site, but the main navigation is not updated immediately. If the sitemap is generated automatically, the new category will be presented to the crawlers as soon as it goes live. This type of coverage makes a difference, especially on TechSnack’s sitemap page, which illustrates this structured inventory logic well.
Lastmod tag of the XML sitemap: an SEO signal often misconfigured
Most competitors talk about the sitemap as a static file that is generated and forgotten. In practice, it is the lastmod tag that determines the file’s value for Google.
Google pays real attention to this date, provided it reflects a significant change in content. A paragraph change, the addition of structured data, or the update of a link justifies a new date. On the other hand, a technical redeployment without content change or a simple copyright update does not count.
The trap is common: some CMS or plugins update the lastmod date with every save, even minor ones. When Google detects systematically inconsistent dates, the trust placed in this signal decreases for the entire sitemap. You end up with a file that crawlers consult but do not really utilize anymore.
How to check the reliability of lastmod
- Open the sitemap file (often accessible at yoursite.com/sitemap.xml) and compare the displayed dates with the actual modifications of the corresponding pages.
- Disable the automatic lastmod update in the SEO plugin settings if it triggers on every save without substantive changes.
- After a content overhaul, manually force the regeneration of the sitemap so that the new dates are taken into account by Google Search Console.
Priority and changefreq attributes: what Google ignores in your sitemap
Many sites still have XML sitemaps containing priority values (from 0.1 to 1.0) and changefreq (daily, weekly, monthly). These two attributes seem useful on paper, but Google has completely ignored them for several years. Google Search Central documentation explicitly confirms this.
Spending time calibrating these values does not bring any measurable SEO benefit. The effort should be focused elsewhere: selecting the truly important URLs to include in the file, checking their accessibility (no chain redirects, no 404 error pages), and maintaining reliable lastmod dates.
This does not mean that these attributes are problematic if they are present. They are simply neutral. Feedback varies on this point for other search engines, but for Google, the question is settled.
Sitemap and AI engines: the role of IndexNow for Bing and Copilot
With the rise of AI-based search experiences (Bing Chat, Copilot), the sitemap takes on an additional dimension. Bing recommends a complete XML sitemap with reliable lastmod dates as a coverage base. But the sitemap alone is no longer sufficient to quickly signal changes.
This is where IndexNow, a real-time notification protocol, comes into play. When you add, modify, or delete a URL, IndexNow sends an immediate signal to Bing (and compatible engines) without waiting for the next crawler visit. The two systems are not interchangeable:
- The sitemap provides the overall inventory of the website, the reference map that crawlers consult periodically.
- IndexNow accelerates the acknowledgment of individual changes, page by page.
- Combined, they ensure both comprehensive coverage and responsiveness to fresh content.
For a site that publishes regularly, this combination of sitemap plus IndexNow reduces the time between the publication of a page and its appearance in Bing’s search results.
Submitting a sitemap does not guarantee the indexing of your pages
One point we want to clarify: submitting a sitemap in Google Search Console does not compel Google to index the listed URLs. The file serves as a suggestion, not an instruction. Google then decides, based on its own quality and relevance criteria, which pages deserve to be included in its index.
We regularly observe URLs present in the sitemap but marked “Discovered, currently not indexed” in Search Console. This means that the crawler knows the page but does not deem it useful to index at the moment. Thin content, a duplicate close to another page, or weak internal linking often explain this status.
The sitemap remains a signaling tool, not a positioning tool. A well-structured file improves crawl coverage, but the foundational work on content quality and site architecture determines what ultimately appears in search results.
