A sitemap is a file, most often in XML format, that lists the URLs of a website to notify search engine crawlers. Its presence does not guarantee either the indexing or the ranking of a page. Google reminds us in its official documentation: the sitemap facilitates discovery, nothing more. Understanding this distinction allows for the effective use of this file without expecting miracles.
XML Sitemap and Crawl Budget: What the File Changes for Crawlers
Search engines allocate a crawl budget to each site, which means a limited number of pages that their crawlers will explore during a given session. On a small showcase site with about ten pages, this budget is rarely an issue: crawlers find all the URLs by following internal links.
The situation changes as the site grows. An e-commerce catalog, a blog with several hundred articles, or a multilingual site generates URLs that the internal linking may not always connect. Orphan pages (without links pointing to them) then remain invisible to Googlebot.
The XML sitemap comes into play precisely here. By providing a complete and up-to-date list of URLs to explore, it directs the crawlers to the priority pages instead of letting them wander down random paths. On a large site, a well-structured sitemap reduces crawl budget waste by preventing crawlers from spending their time on secondary or duplicate pages.
To concretely observe how a sitemap structures this discovery, the sitemap page of success-man.fr offers a telling example of a file organized by categories of URLs.
Submitting and Resubmitting a Sitemap in Google Search Console
Creating a sitemap is not enough. It must be declared in Google Search Console so that the engine knows where to find it. The procedure is straightforward: in the “Sitemaps” tab, you enter the URL of the file (often yoursite.fr/sitemap.xml) and click “Submit.”
What is less known is the usefulness of resubmission. Recent experiences show that sites whose sitemap had not been read by Google for over two years unlocked their indexing simply by resubmitting the same file without changing the content. Resubmission acts as a reminder signal that restarts discovery.
When to Resubmit a Sitemap
- After a migration or a domain name change, to signal the new URLs and prevent Google from getting stuck on the old structure
- When the indexing report in Search Console shows an abnormally low number of indexed pages compared to the number of URLs in the sitemap
- After a significant redesign of the site, even if the sitemap URL has not changed, to force a new pass from the crawlers
The Google Search Central documentation, updated in March 2026, removed specific instructions for Google Sites as they no longer automatically generate a sitemap. This change confirms that Google now expects active management of the sitemap by the site owner, not just a simple “generate and forget.”
Lastmod, Priority, Changefreq: Tags that Google Ignores or Not
An XML sitemap can contain several optional tags for each URL. Not all have the same value in Google’s eyes.
The lastmod tag indicates the last modification date of a page. Google takes it into account, but only if it reflects a real change in content. Updating this date artificially (by regenerating it every day without changing the page) does not speed up crawling. Google detects the inconsistency and eventually ignores the signal.
The priority and changefreq tags, on the other hand, have been ignored by Google for years. Filling them out does not cause an error, but they do not influence either the crawl frequency or the ranking. Therefore, it is unnecessary to spend time on them when configuring a plugin or sitemap generator.
What to Include and Exclude from the File
An effective sitemap does not list everything blindly. The URLs to include are those that the site wants to appear in search results: content pages, active product sheets, published articles.
- Exclude pages protected by a password or blocked by the robots.txt file (declaring them in the sitemap while forbidding them from crawling sends a contradictory signal)
- Exclude pagination URLs, internal search results pages, and duplicate versions (sorting or filtering parameters)
- Exclude 301 redirects: the sitemap should list destination URLs, not old addresses
Sitemap Index for High URL Volume Sites
An XML sitemap file is limited to 50,000 URLs and a size of 50 MB uncompressed. For sites that exceed these thresholds, the solution is the sitemap index: a master file that points to several child sitemaps, each grouping a subset of URLs.
This architecture allows for segmenting URLs by type of content (products, articles, categories) or by section of the site. The benefit goes beyond simple technical compliance. By separating the sitemaps, one can identify in Search Console which segment poses an indexing problem. If product sheets are indexed normally but blog articles are stagnant, the diagnosis is immediate.
On e-commerce sites that manage tens of thousands of references, this segmentation becomes a real SEO management tool. It transforms the sitemap from a simple passive file into a dashboard of indexing coverage.
The sitemap remains a discreet technical file, often configured once and then forgotten. Sites that gain real benefits from it are those that treat it as a living document: updated with each publication, resubmitted after each migration, cleaned of obsolete URLs. A neglected sitemap file is not neutral; it sends noise to the crawlers instead of guiding them.