Home / Knowledge Base / Tools and integrations / Sitemap sitemap.xml: Checking and Common Errors

Sitemap sitemap.xml: Checking and Common Errors

Tools and integrations 2 min read Updated 12.09.2026
What should be in a proper sitemap, which findings from the analyzer are truly important, why the sitemap does not replace internal linking, and how to keep it up to date.

A sitemap is a list of addresses that you consider important. It does not guarantee indexing but speeds up the discovery of pages and helps the bot understand the structure. You can check an existing sitemap with the sitemap.xml analyzer, and generate a new one with the site crawling generator.

What Should Be in a Proper Sitemap

  • Only addresses that return a 200 code — without redirects and errors.
  • Only canonical versions of pages.
  • No addresses that are closed from indexing: this is a contradictory signal.
  • Current modification dates, if you specify them.
  • No more than 50,000 addresses and 50 MB in one file — otherwise, an index file with links to several sitemaps is needed.

What the Analysis Shows

FindingWhy This is Bad
Addresses with redirectsThe bot spends crawling on intermediate addresses
Broken addressesReduce trust in the sitemap as a whole
Pages with noindexYou are simultaneously asking to index and prohibiting
Duplicates and different variations of the same addressThe bot chooses the canonical itself, and not always as you wanted
Sitemap not specified in robots.txtIt has to be searched for manually
The Sitemap Does Not Replace Internal Linking
A page that has no internal links remains an orphan even if it is in the sitemap: such pages are indexed worse and receive almost no weight. The sitemap is a hint, not a replacement for structure.

When Multiple Sitemaps are Needed

Large websites find it convenient to break the sitemap down by types of pages: products separately, articles separately, categories separately. Then, in Search Console, coverage for each group is visible, and it is clear which section is poorly indexed. All parts are listed in an index file, which is specified in robots.txt. Such separation is mandatory when there are more than fifty thousand addresses and useful long before this limit.

How to Keep It in Order

  1. Generate the sitemap automatically, not manually — otherwise, it will become outdated in a month.
  2. Specify it in robots.txt and add it to Search Console.
  3. After major changes on the site, recheck it with the analyzer.
  4. Monitor the coverage report in Search Console: it shows what from the sitemap actually made it into the index.

Related Materials

Checking robots.txt, checking indexing, and the section on page indexing in the dashboard, where they can be sent to Google in bulk.

FAQ

Does the sitemap guarantee indexing?
No, it is a hint to the robot. It speeds up the discovery of pages, but the decision on indexing is made by the search engine.
How many addresses can be in one file?
Up to fifty thousand addresses and fifty megabytes; beyond that, an index file with links to several sitemaps is needed.
Should closed pages be included?
No. An address with noindex in the sitemap is a contradictory signal: you are simultaneously asking to index and prohibiting.
Was this article helpful?
Try it on your project Everything described in the article is available in the dashboard — the registration bonus is already in your balance.
Open dashboard