Sitemaps in Google Search Console: Managing Indexation in 2026

This page is for SEO managers, marketers and business leaders who declare their pages to Google through a sitemap and want to know whether that signal is being taken into account. It covers sitemaps in Google Search Console: building a clean file, submitting it, reading the Sitemaps report and deciding what to fix when submitted URLs stay out of the index.

The role of each report is explained in our Google Search Console guide. A sitemap helps with discovery and diagnostics, but it does not guarantee indexation.

Sitemaps in Google Search Console: create, submit and optimise indexation

Internal linking structures navigation; the sitemap explicitly signals to Google which URLs you consider priority and indexable. It becomes indispensable in three situations:

• A launch: new pages have neither external links nor a solid place in the internal linking yet.
• A migration: the file lists the new final URLs that Google needs to discover.
• Pages with few links: deep pages or pages rarely reached by internal linking benefit from being declared.

The sitemap acts on discovery: Google learns that a URL exists. Crawling and then indexation depend on the accessibility, quality and relevance of the pages; the full cycle is detailed in our guide to indexing in Google Search Console.

Creating a compliant sitemap: formats, rules and pitfalls to avoid

Choosing the right structure: XML sitemap, index and segmentation

The XML format (sitemap.xml) is the standard; for a large site, a sitemap index references several sitemaps segmented by page type or language. When one file shows a gap, you know which template to inspect. Three rules guide the segmentation:

• By page type: blog, products, categories, each in a stable thematic sitemap.
• By language or country: one sitemap per version, consistent with hreflang tags and free of duplicates.
• Under a single index: one sitemap index referencing every file you need to monitor.

Segmentation depends on the type of site; here is a starting point and the indicator to track:

Defining which URLs to include (and exclude) to send the right signals

Every URL added by mistake sends a contradictory signal and blurs monitoring. Include only URLs that meet four conditions:

• Canonical: the URL is the reference version of the page.
• Indexable: no noindex directive and no robots.txt blocking.
• Accessible: the page returns status 200, with no redirect.
• Relevant: the page provides stable SEO value.

So remove noindex, redirected or 404 URLs, which distort the comparison between submitted and indexed URLs, as well as filter, facet or parameter URLs that provide no stable value.

Tags and metadata: lastmod, changefreq, priority and real impact

Only lastmod counts for Google, provided it reflects a genuine modification. The table below summarises the decision for each tag, at the time of writing:

Hosting the file and making it accessible: technical prerequisites

Recommended location, naming and HTTP(S) accessibility

Place the sitemap at the domain root (https://www.example.com/sitemap.xml) or expose a sitemap index in the same location. The file must be:

• publicly accessible, with no authentication;
• served over HTTPS, on the site's canonical host;
• returning HTTP 200, with no redirect.

With a CDN, subdomains or directories, list only URLs within the scope of the Search Console property where the file is submitted; CDN configuration is a hosting matter.

Declaring the sitemap in robots.txt: when it is relevant

Declaring the sitemap URL in robots.txt facilitates its discovery by bots and avoids oversights during technical changes. This declaration complements submission in Search Console. The general syntax of this file is described in our guide to the robots.txt file.

Submitting a sitemap and interpreting the report in the console

Submission steps: property, path, validation and deployment

Submission takes place in the Sitemaps report, once the property is verified. It follows four steps:

• Deploy the file and check that it returns 200 in the correct XML format.
• Open the Sitemaps report of the property that covers these URLs.
• Enter the exact path of the sitemap or index, then submit it.
• Check the processing status and last read date displayed by the console.

Understanding the indicators: discovered, submitted and indexed URLs

For each file, the Sitemaps report shows its status and the number of discovered URLs, without saying which ones are indexed. To find out, open the Pages report and filter it by sitemap: you can then compare submitted URLs with indexed URLs.

Gaps between submitted and indexed URLs reveal duplication, quality or technical configuration problems. Read them sitemap by sitemap: a template that falls behind stands out immediately.

When to resubmit the file and how to manage updates

The sitemap must always reflect the reality of the site. Whether to resubmit it depends on the situation:

• Routine publishing: an automatically generated sitemap is re-read regularly by Google, so there is no need to resubmit it.
• Large-scale page additions or migration: resubmit the file to signal its new version, with no guarantee of faster processing.
• Weekly check: the Sitemaps and Pages reports flag a file that is no longer read or a gap that is widening.

Verifying and testing a sitemap: reliable methods before and after submission

Essential checks: HTTP status, encoding, XML structure and absolute URLs, then a sample

Before submission, four checks prevent the majority of processing errors:

• HTTP status: the file returns 200 and remains publicly accessible.
• Encoding: special characters in URLs are correctly encoded.
• XML structure: the file is valid, with no missing tags or non-compliant values.
• Absolute URLs: each URL is complete, with protocol and canonical host.

After submission, a valid file says nothing about the indexability of the pages. Run a sample from each sitemap through the URL Inspection tool: accessibility, selected canonical, no robots.txt or noindex blocking, rendering.

Explaining gaps: valid file but pages not indexed

An accepted sitemap with few indexed pages usually points to a page problem, not a file problem, template by template. The most common exclusion causes are the following:

• Divergent canonical: the page designates another URL as the reference version.
• Blocking: robots.txt or a noindex tag contradicts the URL's presence in the sitemap.
• Weak or overly similar content: Google does not consider the page worth keeping.
• Technical problem: server errors, incomplete JavaScript rendering, uncontrolled parameters.

Correcting common errors reported by the console

Each anomaly in the Sitemaps report points to an identifiable cause. The table below matches the most common ones with their probable cause and the expected fix:

Size and volume limits: sitemap indexes

At the time of writing, a sitemap file accepts at most 50,000 URLs or 50 MB uncompressed. Beyond that, split the content into several sitemaps referenced by a sitemap index, which also gives you section-by-section diagnostics.

Google retired the sitemap ping in 2023: to signal a file, you still have submission in the Sitemaps report and declaration in robots.txt.

Host inconsistencies: www, https and domain variations

List only URLs of the canonical site version (https, with or without www) to avoid scope errors and unnecessary redirects. After a migration or host change, the sitemap lists only the new URLs; the redirect plan is covered in our guide to 301 redirects in GSC.

Automating management at scale with the Search Console API

The Search Console API automates submission and monitoring of sitemap statuses for multi-domain or high-volume sites, and quickly flags an inaccessible sitemap or a drop in discovered URLs. Its resources, limits and use cases are detailed in our guide to the Google Search Console API.

Depending on your situation

Depending on what the Sitemaps and Pages reports reveal, proceed as follows:

• Sitemap URLs blocked by robots.txt: identify the rule at fault with the Search Console robots.txt report.
• Submitted URLs excluded by a noindex: decide between removing them from the sitemap and removing the directive with our guide to the noindex status in GSC.
• Declared URLs that Googlebot is slow to crawl: check host status in the GSC Crawl stats report.
• A valid file but a widening gap: inspect a sample from each sitemap, then fix the template at fault before resubmitting the file.

To track, template by template, submitted URLs that stay out of the index, the Incremys 360° SEO and GEO audit module brings indexation and error signals together in a single diagnostic.

Frequently asked questions about sitemaps and their management

How do I create a sitemap suitable for Google?

A sitemap suitable for Google is an XML file listing only canonical, indexable URLs with 200 status. For a large site, a sitemap index segments the files by page type or language. Add lastmod only when the content genuinely changes: Google ignores changefreq and priority.

How do I find a site's sitemap and verify its accessibility?

A site's sitemap is usually found at /sitemap.xml or /sitemap_index.xml, or in the line that declares it in robots.txt. Then open its URL: the file must be public, served over HTTPS and return 200. The Sitemaps report also shows its last read date.

How do I test a sitemap to avoid indexation errors?

Testing a sitemap takes two steps: the technical validity of the file, then the indexability of the listed pages. First check the 200 status, the XML structure and the absolute URLs. Then inspect a sample of URLs from each sitemap in the URL Inspection tool to verify the canonical, the absence of noindex and the rendering.

Where should I place the file so it is properly discovered?

The file goes at the domain root, for example https://www.example.com/sitemap.xml, or behind a sitemap index. Declare it in robots.txt and submit it in the Sitemaps report. All listed URLs must belong to the scope of the property where it is submitted.

Should the sitemap be declared in robots.txt?

Yes, declaring the sitemap in robots.txt is recommended, in addition to submission in Search Console. This line lets bots find the file without manual action and limits oversights during technical changes. Since the sitemap ping was retired in 2023, these are the two preferred ways to signal the file.

How many URLs per sitemap?

A sitemap file accepts at most 50,000 URLs or 50 MB uncompressed, at the time of writing. Beyond that, split it into several files referenced by a sitemap index. Even below the limit, segmenting by template lets you read the gap between submitted and indexed URLs section by section.