Sitemap: the complete guide to optimizing your indexing

In short: An XML sitemap is a file that lists all the pages of a website to guide Google's bots during crawling and indexing. Limited to 50,000 URLs and 50 MB per file, it must be submitted manually via Google Search Console and updated regularly to stay reliable. When poorly configured, a sitemap file directly penalizes the crawl budget: during our SEO audits, issues with XML sitemaps consistently rank among the five most common technical errors.

‍

What is a sitemap and why is it vital for your SEO?

A sitemap is a file that lists all the pages of a website and gives search engines the information they need to crawl and index its content efficiently. In practice, it acts like a digital roadmap: it tells Googlebot which pages exist, when they were last updated and how important they are relative to the rest of the site.

‍

For small sites with solid internal linking, Google can theoretically discover every page without help. But for e-commerce sites, large blogs, sites with multimedia content or recently created domains with few inbound links, the sitemap file becomes a strategic indexing lever that should not be overlooked.

‍

The roadmap for search bots

A well-structured XML sitemap contains, for each URL, four key tags that Google analyzes when crawling your site:

‍

• <loc>: the absolute, complete URL of the page.
• <lastmod>: the date of the last significant content update (changes to the main text, structured data, internal links, etc.).
• <changefreq>: the estimated frequency of change (Google often ignores it in practice, but it remains indicative for other search engines).
• <priority>: the relative priority of the page compared with the other pages of the site (Google also ignores this value in most cases).

‍

It is important to understand that submitting a sitemap does not guarantee the indexing of the pages it contains. Google treats it as a suggestion, not an obligation. Content quality, internal linking and the authority of the website remain decisive in whether the engine actually chooses to index a URL.

‍

XML sitemap vs HTML sitemap: what are the differences and uses?

There are two main sitemap formats, which serve distinct purposes. Confusing them is a common mistake, even among experienced technical teams working on large sites.

‍

‍

The XML sitemap file takes priority from a technical SEO standpoint. It is the one Google processes via the Search Console and uses to steer the crawling of your site's pages. The HTML sitemap, for its part, improves the browsing experience and contributes to internal linking, but it in no way replaces its XML counterpart.

‍

Note: there are also extensions of the XML format for images, videos and Google news. These specialized XML sitemaps let you give search engines enriched metadata about these content types, improving their visibility in specialized search results.

‍

Why does a well-configured sitemap optimize your crawl budget?

The crawl budget refers to the number of pages a search engine agrees to crawl on a site within a given timeframe. This budget is limited and influenced by domain authority, loading speed and overall content quality. A poorly built XML sitemap can waste it significantly, at the expense of your site's strategic pages.

‍

"Submitting a sitemap helps improve the crawling of large or complex sites, as well as highly specialized files."

‍

Google Search Central, official documentation, 2026

‍

In practice, if your sitemap file contains URLs returning 404 errors, pages that redirect, content set to noindex or low-quality pages automatically generated by your CMS (WordPress is particularly affected by this issue), you are pointing Google toward useless resources. Every irrelevant URL crawled represents a priority page that is not being crawled.

‍

The signs that your crawl budget is poorly optimized

‍

• Important pages are still not indexed despite having been on the site for a long time.
• The coverage report in Google Search Console shows many URLs submitted but not indexed.
• Your XML sitemap contains URLs with a 3xx or 4xx status detected during a site audit.
• Private, thank-you or empty tag pages appear in the file.
• The update of the sitemap file is not automated and has not been carried out for several months.
• Your CMS automatically generates irrelevant content types (authors, tags, pagination pages, post formats).

‍

How to create and configure an effective sitemap?

There are three main approaches to creating a sitemap, depending on the size and complexity of the site. The choice depends above all on your CMS and the volume of pages to manage.

‍

The 3 methods for creating your sitemap

1. Through your CMS (recommended method): WordPress, Wix, Shopify, PrestaShop and most CMS platforms automatically generate an XML sitemap file. On WordPress, plugins such as Yoast SEO or Rank Math offer fine-grained control over the pages included: excluding content types, taxonomies or specific URLs, with automatic updating of the file on every new publication.
   ‍
2. Through an online sitemap generator: tools such as XML-Sitemaps.com (free up to 500 URLs) or Screaming Frog's xml sitemap generator let you quickly produce a sitemap file for modestly sized sites. These tools crawl your site and generate the XML file in a few minutes.
   ‍
3. Manually (for specific sites): for custom architectures or sites with advanced needs, manual creation in XML offers full control over the pages included. This method is tedious at scale but relevant for projects with few URLs and complex update rules.

Whatever method you choose, the file must absolutely be hosted at the root of the domain (e.g.: *https://www.monsite.fr/sitemap.xml*), encoded in UTF-8 and contain only absolute, canonical URLs. Google reminds us in its official documentation that it ignores relative URLs and duplicates present in XML sitemaps.

‍

For sites exceeding 50,000 pages or 50 MB, you must split the file and create a sitemap index that lists all the sitemap files. This architecture is also useful for tracking performance by content segment directly in Google Search Console.

‍

How to submit your sitemap to Google Search Console?

Submission via Google Search Console is the official and most reliable method for flagging your sitemap file to Google. It lets you confirm that the search engine has indeed registered the file, review processing errors and monitor the number of pages submitted versus indexed on your site.

‍

Steps to submit a sitemap in Google Search Console

1. Sign in to Google Search Console and select the property matching your site.
   ‍
2. In the left-hand navigation menu, go to Indexing > Sitemaps.
   ‍
3. Enter the URL of your sitemap file (e.g.: sitemap.xml or sitemap_index.xml) in the field provided.
   ‍
4. Click Submit. Google will acknowledge receipt and begin processing the file within the following hours.
   ‍
5. Come back regularly to check the status: the report shows the number of pages discovered, any errors and the date the file was last processed.

‍

A complementary alternative is to reference the sitemap URL directly in the robots.txt file via the Sitemap: directive. This method lets other search engines (Bing, Yandex) discover it automatically, but it does not replace manual submission in Google Search Console for precise tracking of your site's indexing.

‍

The 5 critical errors we encounter in SEO audits

During our SEO audits, issues related to XML sitemaps are almost systematic, across all types of sites. Here are the five most common errors and their direct consequences for indexing by Google.

‍

Error no. 1: including non-canonical URLs

Submitting URLs with parameters, http versions instead of https or pages with a rel=canonical tag pointing to another URL creates an inconsistency that Google interprets negatively. The XML sitemap file must contain only the definitive canonical URLs of your site.

‍

Error no. 2: leaving noindex pages in the sitemap

This is a direct contradiction: telling Google to crawl a page via the sitemap, while forbidding it from indexing it via a noindex tag. Google processes these URLs but does not index them, wasting crawl budget for nothing, at the expense of your site's strategic pages.

‍

Error no. 3: failing to keep the sitemap updated

A static sitemap file without regular updating can quickly contain deleted URLs, pages returning 404 or outdated redirects. While modern CMS platforms generate dynamic XML sitemaps, files created manually require a manual update on every significant change to the site architecture.

‍

Error no. 4: submitting the default WordPress sitemap without filtering

Since version 5.5, WordPress natively generates an XML sitemap accessible at /wp-sitemap.xml, which automatically includes all content types: posts, pages, authors, tags, post formats. These irrelevant pages dilute the value Google perceives in the site and pollute the crawl budget. It is essential to filter these entries via a dedicated SEO plugin or via custom code in the WordPress functions.php file.

‍

Error no. 5: forgetting to submit the sitemap to Google Search Console

Referencing the sitemap URL in the robots.txt file is not enough. Without explicit submission in Google Search Console, it is impossible to know whether Google actually processes the file, to identify processing errors or to track the change in the number of indexed pages on your site.

‍

Frequently asked questions

‍

Is a sitemap mandatory for your site?

No, a sitemap is not technically mandatory. Google can crawl and index a site via its internal and external links. However, it is strongly recommended for sites with more than a few dozen pages, e-commerce sites, sites with multimedia content or recent domains with little authority. When in doubt, it is better to have an XML sitemap file that is properly configured and submitted to Google.

‍

How to create a free sitemap for Google?

The simplest method is to use your CMS. WordPress generates an XML sitemap natively (accessible at votresite.fr/wp-sitemap.xml), and SEO plugins like Yoast or Rank Math offer advanced configuration options for free, with automatic updating of the file. For sites without a CMS, an online xml sitemap generator like XML-Sitemaps.com lets you generate a free file for up to 500 pages. Screaming Frog SEO Spider also offers a generator in its free version (500 URL limit).

‍

Where should the sitemap.xml file be placed?

The sitemap.xml file must be placed at the root of your domain, that is, at the address *https://www.votresite.fr/sitemap.xml*. This position lets the sitemap cover all the pages of the site. A file hosted in a subdirectory (e.g.: /blog/sitemap.xml) only has authority over the URLs of the parent directory, which can limit its reach with Google. The file must be encoded in UTF-8 and publicly accessible without authentication.

‍

What is the difference between an XML sitemap and an HTML sitemap?

The XML sitemap is a technical file intended for the bots of search engines like Google. It lists the URLs of the pages with their metadata (update date, priority) and is submitted to Google Search Console. The HTML sitemap is a standard web page, visible to visitors, that presents the site structure as clickable links. The two are complementary, but the XML sitemap file takes priority for technical SEO.

‍

How often should you update your sitemap?

The ideal frequency depends on the site's publishing pace. For an active blog or an e-commerce site, the sitemap should be updated on every new publication or significant content change. Most CMS platforms like WordPress and their SEO plugins automate this update of the file. For more static sites, a monthly review is enough, provided you check via Google Search Console that no URL with an error appears in the XML sitemaps.