How to add a sitemap to Google Search Console?
A sitemap helps Google find important website pages and understand which URLs the owner considers relevant for crawling. Most often, an XML sitemap is used, which contains page addresses and, if necessary, additional technical data about their updates.
To add a sitemap to Google, open the desired property in Google Search Console, go to the “Sitemaps” section, enter the sitemap URL, and submit it for processing. Afterward, check the file's status to ensure Google retrieved the sitemap without errors.
Having a sitemap doesn't guarantee indexing of all listed URLs. Google separately evaluates page accessibility, canonical tags, meta robots tags, content quality, duplicates, internal links, and other signals.
What is a Sitemap and why does Google need it?
A sitemap is a file containing a list of pages that a search engine bot should be able to find on a website. For a typical website, an XML sitemap is most often used, located at a URL like https://example.com/sitemap.xml.
The sitemap is especially useful for online stores, large corporate websites, new projects, and resources with many pages. It also helps after changing the site structure, launching new sections, or migrating the project to a different CMS.
The query “Google sitemap” typically refers to the XML file submitted to Google for page discovery. A user-facing HTML sitemap serves a different purpose and is not a replacement for the XML Sitemap.
How is an XML Sitemap different from an HTML Sitemap?
An XML sitemap is created in a search engine-friendly format and contains page URLs along with technical parameters. Website visitors typically don't interact with this file, although it can be accessed through a browser.
An HTML sitemap is created for human consumption and looks like a regular page with links to website sections. It can improve navigation and internal linking, but an XML sitemap is typically used to submit a list of URLs to Google Search Console.
Does every website need a Sitemap?
Google can crawl a small website with a simple architecture and good interlinking without an XML sitemap. The search robot navigates through internal links and gradually discovers accessible pages.
At the same time, a correct sitemap simplifies monitoring the technical status of a project and helps quickly inform search engines of current URLs. Therefore, it usually makes sense to maintain a sitemap even on a relatively small website.
Answers to your questions
How to add a sitemap to Google Search Console?
Open the desired Search Console property and go to the “Sitemaps” section. Enter the XML Sitemap or Sitemap Index URL, submit it, and check the status after processing.
Before submitting, it's recommended to open the file yourself and ensure it's accessible. The sitemap should contain current canonical URLs without redirects, 404s, or intentional noindexes.
What Sitemap URL should I add to Google?
You need to submit the actual URL of the current sitemap, for example, https://example.com/sitemap.xml. If the project uses a Sitemap Index, the address of the index file is added.
Don't copy the standard path without checking. Some CMSs use their own file names or create multiple sitemaps for different page types.
Do I need to add a Sitemap if it is already listed in robots.txt?
Google can detect the sitemap through a robots.txt directive. Adding it to Search Console is useful for monitoring the processing status and identifying errors.
Using both methods doesn't create a conflict. The main thing is that both robots.txt and Search Console contain the same website's current address.
Why does Google Search Console say “Unable to fetch Sitemap”?
The cause could be an incorrect URL, a server error, DNS, a redirect, or restricted access for Googlebot. First, open the file manually and check its HTTP code.
If the sitemap is accessible in the browser, check the XML, final URL, and server settings. Some security systems allow regular users to access it but block search engines.
Does a Sitemap guarantee that pages will be indexed?
No, having a URL in a sitemap doesn't guarantee a page will appear in search results. The sitemap helps Google detect the address and receive a technical signal about its existence.
Page accessibility, canonical, meta robots, duplicates, and content quality are also important for indexing. Problematic URLs should be checked separately in Search Console.
How many URLs can be in one Sitemap?
A single sitemap file can contain no more than 50,000 URLs. Its uncompressed size must not exceed 50 MB.
If the site is larger, create several separate files and combine them using the Sitemap Index. This can be done by page type or logical project sections.
Do I need to resubmit my Sitemap after adding new pages?
If the sitemap is automatically updated and maintains the same URL, resubmission is usually not necessary. Google continues to access the already known file and retrieves the updated content.
After a migration or major structural change, it's worth manually checking the sitemap. It's especially important to ensure that old URLs have disappeared and new pages have been added correctly.
Can I add multiple Sitemaps in Google Search Console?
Yes, Search Console supports working with multiple files. This is often used on large websites where products, categories, and articles are stored in separate sitemaps.
If all sitemaps are already listed within the Sitemap Index, submitting them separately is not necessary. Submitting them separately makes sense primarily for additional technical control.
What to check before adding a Sitemap to Google Search Console?
Before submitting the file, make sure the sitemap is accessible and contains the correct URLs. If the sitemap contains deleted pages, redirects, or noindex URLs, submitting such a file will create unnecessary inconsistencies.
You can open the sitemap directly in your browser or a technical SEO crawler. Afterward, it's worth checking the HTTP codes, canonical URLs, and whether the URLs match the current site structure.
Where is the sitemap located?
On many websites, the sitemap is available at the standard address https://example.com/sitemap.xml. Some CMSs create an index file like https://example.com/sitemap_index.xml, which lists individual sitemaps for pages, posts, categories, or products.
The exact path depends on the CMS and project settings, so the standard address isn't always suitable. If the file is created automatically, its URL can usually be found in the SEO settings or in robots.txt.
What pages should be added to the Sitemap?
The sitemap includes pages that should be accessible to search engines and potentially appear in search results. The sitemap is based on canonical URLs with a successful server response and without indexing restrictions.
Typically, the following types of pages are added to a Sitemap:
- main pages of services and categories available to users and search robots;
- product cards that exist, are available for purchase, and must be indexed;
- blog articles and informational materials with independent content;
- landing pages created for specific search intents;
- other canonical URLs with HTTP response code 200.
The sitemap's composition should correspond to the actual structure of the pages being indexed. If a URL shouldn't appear in Google, its inclusion in the sitemap should be reconsidered.
Why should a Sitemap have canonical URLs?
Canonical tells search engines which version of a page the site owner considers primary among identical or similar URLs. If a sitemap contains one version, but rel="canonical" specifies another, search engines receive conflicting signals.
Therefore, it is advisable to include the canonical URL in the XML sitemap. This approach is especially important for online stores, where the same content may be accessed through filters, parameters, sorting, or different path options.
What URLs should not be added to a Sitemap?
Avoid saving pages in your sitemap that you know shouldn't be indexed or that no longer exist. The sitemap should contain an up-to-date list of useful URLs, not a complete dump of every address ever created on the site.
The following groups need to be checked:
- pages with noindex, if the indexing ban is set intentionally;
- addresses with 404 and 410 responses that have already been removed;
- URLs that redirect the user via 301 or 302;
- non-canonical versions of pages and duplicates;
- technical URLs with unnecessary GET parameters;
- test and service pages closed from search.
After cleaning the sitemap, you should check it again. On large sites, it's best to automate this task at the CMS level to prevent erroneous URLs from returning after the next file generation.
What are the technical requirements for an XML Sitemap?
A valid XML sitemap should be accessible to Googlebot and contain absolute page addresses. It's best to use a single protocol and a single primary domain version that corresponds to the actual canonical pages.
In addition to the sitemap's content, you need to monitor its size, encoding, and XML validity. A technical error in the file may prevent Google from properly reading the listed URLs.
Limits on the number of URLs and file size
A single sitemap can contain up to 50,000 URLs and be up to 50 MB in uncompressed size. If a site exceeds these limits, the pages are split across multiple files.
To combine individual sitemaps, a Sitemap Index is created. This approach is suitable for large stores, catalogs, marketplaces, and sites with large archives of information materials.
URL encoding and format
The XML Sitemap uses UTF-8 encoding, and page addresses are specified in full. Instead of the relative /catalog/product/, the file should contain an absolute URL like https://example.com/catalog/product/.
All characters must be properly escaped according to XML. After generation, it's recommended to check the sitemap with a validator or SEO crawler, especially if the file was created by a custom script.
Should I use lastmod, changefreq and priority?
The lastmod parameter can be used to pass the date of the last significant change to a page. This date should be updated after the content is actually changed, not automatically each time the site is accessed.
Google doesn't use priority and changefreq in the way that older SEO guidelines often describe. Therefore, you shouldn't set all commercial pages to high priority or rely on changefreq to encourage Googlebot to visit a URL more frequently.
How to add a sitemap to Google Search Console?
Adding the sitemap takes a few minutes if the file has already been created and is accessible at the correct address. It's recommended to first open the sitemap manually and verify that the server is indeed returning the XML content without errors.
Next, use the Search Console section, which is specifically designed for working with sitemaps. Once submitted, Google processes the file and displays its status in the interface.
Step 1: Check the Sitemap URL
Open the sitemap URL in a regular browser and ensure the file loads without error. If you're using a Sitemap Index, it should contain links to the current domain's child sitemaps.
Additionally, check the HTTPS protocol, the primary domain version, and the absence of unnecessary redirects. Sitemaps that link to the old domain or previous URL structure are especially common during site migration.
Step 2: Open the desired property in Google Search Console
Log in to Google Search Console and select the property that matches your current site. If you have multiple domain or URL-prefix properties added to your account, review your selection before submitting the file.
An error at this stage often occurs after switching from HTTP to HTTPS or changing the primary domain. The sitemap should belong to the property you're currently working with.
Step 3: Go to the Sitemaps section
In the Google Search Console menu, open the “Sitemaps” section. At the top of the page, you'll find a field for adding a new sitemap address.
The interface also displays previously submitted files and their status. This data is convenient for monitoring after a site transfer or changes to the sitemap generation system.
Step 4: Add the sitemap URL
Enter the XML Sitemap or index file address and submit it through the form. If you're using a valid Sitemap Index, there's usually no need to manually add each child sitemap.
For large projects, individual sitemaps are sometimes submitted additionally to make it easier to analyze different URL groups. For example, products, categories, and articles can be monitored separately.
Step 5: Check the processing status
After submitting, Google displays the file's retrieval status. A successful status means the search engine was able to read the sitemap and process the data it contains.
However, successful processing does not automatically index every page. For certain important URLs, their status should be further monitored using URL Inspection in Search Console.
What does successful Sitemap processing mean?
This status indicates that Google received and read the file without a critical technical error. The interface may also display the number of URLs detected.
If some pages remain unindexed, the problem usually lies within the URLs themselves. Then, check robots.txt, noindex, canonical, page availability, and the exclusion reasons in Search Console.
What does a Sitemap error mean?
This error means that Google was unable to correctly retrieve or process the sitemap. This could be due to an invalid address, server response, invalid XML, or restricted crawler access.
First, open the same URL yourself and check the HTTP response. Once the issue is resolved, you can re-check the file in Search Console.
Should I add a sitemap to robots.txt?
The sitemap address can be specified in robots.txt so that search engines can find it when crawling your site. This directive is typically placed on a separate line:
Sitemap: https://example.com/sitemap.xml
This option is convenient to use in conjunction with Google Search Console. The robots.txt file communicates the sitemap's address to the search engine, and Search Console provides the website owner with additional information about how it's processed.
Should I use both Search Console and robots.txt?
Both methods can be used without conflict, as they solve related technical problems. A link in robots.txt helps robots find the file, and the Search Console interface displays the status and possible errors.
Re-referencing the same sitemap does not pose any indexing issues. The main thing is that both sources link to the current domain's current sitemap.
Why doesn't Google Search Console accept Sitemaps?
If Google shows an error, you should first check the file's accessibility and then address its contents. Simply resubmitting the sitemap without fixing the issue usually doesn't change anything.
Some problems originate on the server, while others are related to the URL or XML. Therefore, it's best to diagnose them sequentially, starting with the server's response.
Error: “Unable to retrieve sitemap”
The “Unable to retrieve sitemap” message may appear if Googlebot was unable to access the specified address. This may be due to server errors, an incorrect path, DNS issues, access restrictions, or hosting instability.
You need to check the file's HTTP code, the final URL after all redirects, and the sitemap's accessibility without authorization. If the server repeatedly returns 5xx errors, fix that issue first.
The sitemap opens in the browser, but Google shows an error.
A file opened by a website owner isn't always accessible to Googlebot under the same conditions. The server or security system may specifically block automated requests based on IP or User-Agent.
You should also check the XML validity and that the sitemap belongs to the selected property. After fixing a technical issue, Google may not process the file immediately, so the status may be updated with a delay.
The sitemap contains incorrect URLs.
After changing the domain, HTTPS, or directory structure, outdated URLs may remain in the sitemap. A similar problem occurs if the CMS generates the sitemap from a database without taking redirects and canonicals into account.
Check HTTP/HTTPS, www/non-www, test domains, parameters, and old pages. Then fix the generation mechanism so that errors don't return after the next XML update.
Why aren't pages from the Sitemap indexed?
A sitemap tells Google about a URL, but the indexing decision is made on a page-by-page basis. Just because an address appears in XML doesn't necessarily confirm its availability or value to the search engine.
You should check robots.txt, meta robots, canonical, HTTP code, duplicates, and internal links. For a specific page, it's useful to use URL Inspection to see which version Google considers canonical.
Lead SEO specialist — Gennady
I view a sitemap as a technical source of current website URLs. If the sitemap contains 404s, redirects, noindex, and non-canonical pages, we're sending the search engine robot inconsistent data. Therefore, I first check the URL structure, HTTP codes, canonical, and file availability, and only then submit the sitemap to Google Search Console.
Do I need to resubmit my Sitemap after updating my site?
If the sitemap address remains the same and the CMS automatically updates its contents, there's no need to constantly delete and re-add the file. Google periodically accesses the existing sitemap and retrieves its current version.
After a major migration or structure change, it's a good idea to double-check your sitemap status in Search Console. Make sure the new URLs have appeared and any deleted pages or redirects have disappeared.
How to add a sitemap for a large website?
Large projects typically split URLs into multiple files by page type or section. This approach simplifies technical control and helps quickly identify issues within a specific group of URLs.
For example, you can store products, categories, articles, and static pages separately. All these files are then linked via the Sitemap Index.
What is Sitemap Index?
The Sitemap Index contains links to several separate sitemaps. Instead of listing tens of thousands of URLs directly in a single file, the index lists the addresses of child sitemaps.
An example structure might look like this:
- sitemap-pages.xml contains the main static pages;
- sitemap-products.xml contains store product cards;
- sitemap-categories.xml contains indexed categories;
- sitemap-blog.xml contains articles of the information section.
This separation simplifies diagnostics. If the issue only affects products, the webmaster can check the corresponding file separately.
Do I need to submit each Sitemap separately?
With a properly configured Sitemap Index, all you need to do is submit the index file. Google will retrieve the child sitemap addresses from it and process them sequentially.
A separate submission can be used for additional control over a specific section. This is useful on large sites, but is not a mandatory technical requirement.
Do you need separate sitemaps for images, videos and news?
Google supports additional data for images, videos, and news content. It's only needed where the content type plays a significant role in search traffic.
A typical corporate website often doesn't require a separate Image Sitemap. An online store, media project, or video service might benefit more from specialized sitemap markup.
How to check a sitemap after adding it to Google?
Once you submit your sitemap, your work with it isn't over. You need to ensure that Google continues to receive the file and that its content matches the current indexed site structure.
The check is especially useful after migrations, mass URL changes, and CMS updates. In such situations, the sitemap is often the first to reveal system errors in page generation.
Check the status in Google Search Console
Open the submitted sitemap and view the current processing status. Note the number of URLs found and any error messages.
If the number of pages has changed dramatically without any planned maintenance, it's worth checking the sitemap generator. A decrease in the number of URLs could be due to a technical glitch or erroneous page filtering.
Check important pages with URL Inspection
For individual commercial pages, use the URL inspection tool. It shows whether the page is accessible to Google, whether indexing is allowed, and which canonical URL is used by the search engine.
This check is especially useful after publishing a new section. There's no need to repeatedly submit the same URL just to speed up indexing.
Check your Sitemap periodically
Sitemap monitoring is especially necessary after changing the CMS, domain, or URL structure. It's also worth checking after mass deleting products, categories, or information pages.
Regular technical audits help detect 404 errors, redirects, and non-canonical URLs. For a large website, it's advisable to automate this monitoring using a crawler or an internal SEO checker.
Common Mistakes When Working with Sitemaps
Most problems stem not from the file submission itself, but from its content. If the generator automatically adds any existing URLs, the sitemap gradually becomes cluttered with technical pages.
Below are typical errors and how to fix them.
| Error | Why does the problem occur? | What to do |
|---|---|---|
| The URL returns 404 | A deleted page was left in the sitemap | Remove address from Sitemap |
| URL is redirected | An intermediate address is specified | Add final URL |
| The page contains noindex | Indexing signals diverge | Remove URL or change meta robots |
| Non-canonical URL specified | Canonical points to a different version | Leave the main URL |
| Sitemap is unavailable | Googlebot doesn't receive the file. | Check server and access rights |
| Over 50,000 URLs | Single file limit exceeded | Split into several sitemaps via Sitemap Index |
| Invalid lastmod | The date does not reflect the actual change | Pass the actual date |
| The sitemap contains old URLs | Generation uses outdated data | Fix file generation mechanism |
After fixing the error, you need to check the source of the error, not just the manually edited XML. Otherwise, the next automatic generation will return incorrect pages again.
Checklist before submitting a sitemap to Google
Before adding a file, it's convenient to run a short technical check. It takes less time than fixing hundreds of incorrect URLs after discovering an issue in Search Console.
Please check the following points:
- The sitemap opens at an accessible HTTPS address and returns a successful HTTP code.
- The sitemap uses absolute URLs of the current primary domain.
- All added pages return response code 200.
- The Sitemap contains canonical versions of indexed pages.
- There are no pages with intentionally set noindex among the URLs.
- Removed pages with codes 404 and 410 are excluded from the file.
- Addresses with redirects have been replaced with final URLs.
- Technical GET parameters and duplicates are not included in the sitemap.
- For large projects, URL number limits are observed.
- A separate Sitemap Index is used if necessary.
- lastmod conveys the date the page was actually modified.
- The sitemap is automatically updated along with the site structure.
- The Sitemap address is specified in robots.txt if necessary.
- The file was submitted via the Google Search Console section.
- After sending, the processing status and any errors detected were checked.
After this check, the sitemap can be used as a stable source of up-to-date URLs. For projects with a frequently changing catalog, it's best to perform regular checks, not just during initial setup.
A correct sitemap should contain up-to-date canonical pages accessible to search engines and intended for indexing. Before submitting to Google Search Console, it's important to check the HTTP codes, meta robots, canonical, redirects, and the XML file itself.
After adding the sitemap, monitor its status and periodically check its contents, especially after major website changes. If Search Console shows errors or the sitemap contains technical URLs, order an SEO audit from Seo-Gen to check the site's indexing, structure, and crawl settings.
