{"id":22913,"date":"2026-08-30T09:34:05","date_gmt":"2026-08-30T07:34:05","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22913"},"modified":"2026-08-30T09:34:06","modified_gmt":"2026-08-30T07:34:06","password":"","slug":"submit-xml-sitemap-to-google","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/seo-monitoring\/xml-sitemap-google-einreichen\/","title":{"rendered":"XML Sitemap: What it does and how to submit it to Google"},"content":{"rendered":"<p class=\"wp-block-paragraph\">An XML sitemap helps search engines discover important URLs on a website and obtain information about those URLs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Especially for new, extensive, or frequently updated websites, it can help Google to understand the structure and relevant pages of a website more efficiently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, a sitemap is neither a guarantee for indexing nor a tool that can be used to improve rankings. It primarily tells Google which URLs you are providing as relevant for your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we explain how XML sitemaps work, which URLs belong in them, what a sitemap index is, and how you submit and monitor a sitemap in the Google Search Console.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Briefly explained:<\/strong> An XML sitemap is a machine-readable list of your website's important URLs. It helps search engines discover pages, but does not obligate Google to crawl or index these URLs.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What is an XML sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An XML sitemap is a file in a structured format that lists the URLs of a website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a very simplified sitemap can look like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>https:\/\/example.com\/\n  \n\n  \n    https:\/\/example.com\/leistungen\/\n  \n\n  \n    https:\/\/example.com\/kontakt\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Normal website visitors do not need to use this file. It is primarily intended for search engines and other systems that can process sitemap data.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What does Google need a sitemap for?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google discovers websites in different ways. Links between pages play an important role.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap provides an additional way for Google to discover relevant URLs.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>internal and external links\n          \u2193\n      URL discovery\n\nXML sitemap\n          \u2193\nadditional information\nabout relevant URLs<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, a sitemap does not replace a good website structure and meaningful internal linking.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Does every website need an XML sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not necessarily.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A small website whose important pages are easily accessible via normal links can be discovered by Google even without an XML sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nevertheless, a sitemap is often useful and is provided automatically by many content management systems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, it can be particularly useful for:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>new websites\nextensive websites\nwebsites with many subpages\nfrequently published content\nmore complex site structures\npages that have only a few external links<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Since modern content management systems often manage sitemaps automatically, there is usually little reason not to provide them to Google on a correctly configured website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A sitemap does not replace internal linking<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A page should not be able to exist simply because its URL is listed in an XML sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Important content should be reasonably accessible within the website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Home\n   \u2193\nOverview of services\n   \u2193\nIndividual service\n\n\nBlog\n   \u2193\nCategory\n   \u2193\nArticle<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If an important page only appears in the sitemap and is otherwise barely integrated within the website, you should review the site structure.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> Consider the XML sitemap as a complement to your website structure\u2014not as a replacement for navigation and internal links.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">A sitemap is no guarantee of indexing<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most common misconceptions is:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>URL in Sitemap = URL is indexed by Google<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is not true.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap informs Google about a URL. Google then decides for itself whether and when this URL is crawled and whether it is indexed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, if an important page is not indexed despite a correct sitemap, you should investigate the specific URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how you proceed under <a href=\"\/en\/help\/seo-monitoring\/google-is-not-indexing-website\/\">Google is not indexing my website: Check causes<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Which URLs belong in an XML sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Basically, a sitemap should contain the URLs that you want to provide to search engines as the preferred, indexable versions of your content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical examples are:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Home page\n\nimportant service pages\n\nproduct and category pages\n\nrelevant blog articles\n\nguides\n\nother standalone indexable content<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The sitemap should thus convey as clean a picture as possible of the URLs that are actually intended to appear as independent pages in search engines.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Which URLs should normally not be in the sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">URLs that are intentionally not to be indexed do not normally belong in a sitemap for indexable pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Problematic or unnecessary examples include:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>noindex URLs\n\n404 pages\n\nredirect URLs\n\nnon-canonical duplicates\n\ninternal search results\n\nspecific technical URLs\n\npassword-protected content<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When you tell Google that a URL is relevant via a sitemap and at the same time make it clear through other signals that it should not be indexed, conflicting signals are created.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Redirect URLs do not belong as target pages in the sitemap<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Assuming an old URL was permanently redirected to a new page:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>https:\/\/example.com\/alte-seite\/\n\n        \u2193 301\n\nhttps:\/\/example.com\/neue-seite\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then the new target URL should normally be in the sitemap and not the old redirect URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how permanent redirects work at <a href=\"\/en\/help\/seo-monitoring\/set-up-a-301-redirect\/\">Set up a 301 redirect: Permanently redirect URLs<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Remove 404 URLs from the sitemap<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A URL that permanently no longer exists and with <code>404 Not Found<\/code> responds, should no longer be listed as a regular content URL in a sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Otherwise, on the one hand you are telling Google that this URL is relevant, while on the other hand the server is reporting that the resource does not exist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to properly handle such URLs at <a href=\"\/en\/help\/seo-monitoring\/find-and-fix-404-errors\/\">Find and fix 404 errors<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Canonical and sitemap should match<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If multiple similar URL variants exist, the preferred canonical version should generally be used in the sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>preferred URL:\n\nhttps:\/\/example.com\/produkt\/\n\n\ntechnical variant:\n\nhttps:\/\/example.com\/produkt\/?sort=preis<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the first URL represents the canonical version, the technical variant should not be unnecessarily signaled as an independent preferred URL in the sitemap.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Use only complete absolute URLs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">URLs in an XML sitemap are specified in full.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Correct:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/example.com\/leistungen\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Not solely:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>\/services\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The correct protocol and the correct hostname are also relevant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">HTTPS sitemap for an HTTPS website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your website operates entirely over HTTPS and HTTPS represents the preferred version, the URLs in your sitemap should also point to the corresponding HTTPS addresses.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/example.com\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">and not unnecessarily:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>http:\/\/example.com\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">if this HTTP version is redirected to HTTPS anyway.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where do you find your website's sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">That depends on the content management system and the SEO solution used.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible addresses could look like this, for example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>https:\/\/example.com\/sitemap.xml\n\nhttps:\/\/example.com\/sitemap_index.xml\n\nhttps:\/\/example.com\/wp-sitemap.xml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You should check which address is actually used on your website directly in your system or SEO plugin.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> Do not simply copy a sitemap address from another website. Always check which sitemap your own website actually provides.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress can provide its own sitemap<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress has an integrated XML sitemap feature.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, SEO plugins can provide their own sitemap systems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the configuration, a WordPress sitemap or a sitemap generated by the SEO plugin can therefore be used, for example.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You do not have to submit multiple different sitemap systems to Google in parallel just because technically multiple variants might be accessible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is a sitemap index?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For larger or structured websites, URLs are often distributed across multiple individual sitemaps.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap index does not contain all page URLs directly, but rather links to additional sitemap files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sitemap_index.xml\n\n   \u251c\u2500\u2500 post-sitemap.xml\n   \u251c\u2500\u2500 page-sitemap.xml\n   \u251c\u2500\u2500 product-sitemap.xml\n   \u2514\u2500\u2500 category-sitemap.xml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Google can read the sitemap index and subsequently retrieve the individual sitemaps referenced within it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">For a sitemap index, the index is usually sufficient<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your system generates a complete sitemap index, you can submit it in the Google Search Console.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You then do not necessarily have to submit each sub-sitemap contained within it individually as well.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>https:\/\/example.com\/sitemap_index.xml<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google can use this to find the contained sitemap files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why are there multiple sitemaps?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The division can have various practical reasons.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, it can separate different content types from one another:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Pages\n\nPosts\n\nProducts\n\nCategories\n\nImages\n\nVideos<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In addition, technical size limits apply to individual sitemap files. Extensive websites may therefore require multiple sitemaps and a sitemap index.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How large can a sitemap be?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">According to the sitemap protocol, a single sitemap can contain at most <strong>50,000 URLs<\/strong> contained and a maximum of when uncompressed <strong>50 MB<\/strong> to be tall.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If either of these limits is reached, the URLs must be distributed across multiple sitemap files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap index can then combine these individual files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What does lastmod mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap can optionally include a modification date for a URL via the element <code>&lt;lastmod&gt;<\/code> specify.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>https:\/\/example.com\/ratgeber\/\n  August 30, 2026<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This date should reflect an actual substantial change to the page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should not be artificially set to the current date on every sitemap request or for trivial changes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Don't overestimate changefreq and priority<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Sitemap protocol also includes elements such as <code>&lt;changefreq&gt;<\/code> and <code>&lt;priority&gt;<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google does not use these values as binding directives for crawling.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So you can't replace Google with:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>1.0<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">force to rank a page higher or better.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A sitemap is not an SEO priority switch. The inclusion of a URL or a high <code>priority<\/code>-Value does not automatically improve your ranking.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Check sitemap before submitting<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before submitting a sitemap to the Search Console, you should check whether it is publicly accessible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To do this, open the actual sitemap address in your browser.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>https:\/\/example.com\/sitemap.xml<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">or:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>https:\/\/example.com\/sitemap_index.xml<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The sitemap must not only be accessible to logged-in administrators.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pay attention to the HTTP status<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google should be able to reliably retrieve a working sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if the sitemap returns a server error or access protection, Google cannot process it normally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain the meaning of important HTTP status codes at <a href=\"\/en\/help\/seo-monitoring\/http-status-codes-explained\/\">HTTP status codes explained: 200, 301, 404, 403, and 500<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Submit a sitemap to Google Search Console<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open Google Search Console and select the correct property for your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then call the area <strong>Sitemaps<\/strong> on.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There you can tell Google the address of your sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the displayed property and input field, the domain may already be specified. In that case, enter the corresponding sitemap path.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>sitemap_index.xml<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and submit the sitemap.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What does \u201esubmit a sitemap\u201c mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The wording can be misleading.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You do not upload the sitemap to Google as a file from your computer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, to put it simply, the following happens:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Sitemap is located on your website\n\n        \u2193\n\nyou share its address with Google\n\n        \u2193\n\nGoogle fetches the sitemap\n\n        \u2193\n\nGoogle processes the information it contains<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The sitemap must therefore remain accessible on your website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happens after submission?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google is trying to retrieve and process the submitted sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the sitemap report, you can then see, among other things, whether Google was able to successfully read the sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, successful processing still does not mean that all URLs contained within it will be crawled or indexed immediately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What does the status \u201eSuccessful\u201c mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When Google reports a successful status for a sitemap, it means the sitemap was successfully retrieved and processed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This means:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>technically readable sitemap<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It does not mean:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>All URLs are indexed.<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You should strictly distinguish between these two statements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How do you check the indexing of the sitemap URLs?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The actual indexing is not solely answered by the successful sitemap status.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the Search Console, you can use the page indexing report and filter the evaluation by a specific sitemap or submitted URLs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With this, you can check which of the pages included in the sitemap Google has indexed and which URLs have other statuses.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We discuss the diagnosis of individual important URLs in detail under <a href=\"\/en\/help\/seo-monitoring\/google-is-not-indexing-website\/\">Google is not indexing my website: Check causes<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What does \u201eSitemap could not be fetched\u201c mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If Google cannot retrieve a sitemap, you should first check its accessibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible causes can include, for example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>incorrect sitemap address\n404 error\nserver error\nDNS issue\naccess protection\nrobots.txt blocking\ntemporary technical issue<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open the sitemap yourself and check its actual technical condition.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Google can read the sitemap, but reports errors<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap can generally be accessible and still contain faulty entries.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then you should examine the details shown in the sitemaps report.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible problems may include, for example, invalid URLs, formatting errors, or other syntactic issues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your content management system or SEO plugin generates the sitemap automatically, you should not edit the generated XML file manually directly, but rather look for the cause in the corresponding configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not edit the sitemap manually if it is generated automatically<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In WordPress and other content management systems, sitemaps are often generated dynamically.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Manual modification of the output XML file would then either be impossible entirely or would be overwritten during the next automatic generation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If incorrect URLs appear in the sitemap, you should check instead:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Is the content published?\n\nShould the content be indexed?\n\nWhat sitemap settings does the SEO plugin use?\n\nIs the URL canonical?\n\nIs the content type allowed for search engines?<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Why does a specific page not appear in the sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There can be various causes if an expected page is missing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Page is noindex\n\nPage is not published\n\nContent type is excluded from the sitemap\n\nSEO plugin excludes page\n\nCanonical configuration is unusual\n\nSitemap has not been updated yet\n\nCaching shows an older version<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">First, check whether the page should even be indexed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why is a noindex page still in the sitemap?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a page deliberately <code>noindex<\/code> set, it should normally not appear simultaneously as the desired index URL in the sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the event of such a contradiction, you should check the system settings or the SEO plugin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The goal is a consistent configuration:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>URL should be indexed\n\u2192 indexable\n\u2192 canonical URL\n\u2192 sitemap\n\nURL should not be indexed\n\u2192 noindex\n\u2192 normally not sitemap<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Does the sitemap need to be resubmitted after every new page?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Usually not.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When a sitemap has been successfully submitted and is automatically updated at the same address, Google can crawl it again on a regular basis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So you don't have to delete and re-add the sitemap from the Search Console after every new blog post.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> On a standard WordPress system with an automatically updated sitemap, it is usually sufficient to submit the correct sitemap or sitemap index cleanly once and then monitor its status.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">When can a resubmission make sense?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you have made extensive changes to the sitemap or the website structure, you can notify Google about the sitemap again.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For normal ongoing changes, on the other hand, Google can follow its regular crawling schedule.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Remove a sitemap from Search Console<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You can remove a submitted sitemap from the Sitemaps report.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, this does not mean that Google automatically forgets all the URLs contained within it or removes them from the index.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google may already know the sitemap itself through other channels.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Removing a sitemap from the Search Console report is not a tool for removing webpages from Google.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">A new sitemap after a relaunch<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After a website relaunch, you should check the sitemap particularly carefully.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should contain the current preferred URLs of the new website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Old URLs that now redirect or no longer exist should not unnecessarily remain as current content pages in the new sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check in particular:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>new URL structure\n\nHTTPS\n\nwww \/ without www\n\nCanonical URLs\n\nold redirect URLs\n\n404 URLs\n\nnoindex pages\n\nnew important pages<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Old sitemap after a relaunch<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During larger migrations, an old sitemap can under certain circumstances be temporarily helpful for diagnostic purposes, for example to make old URLs and their redirects accessible to Google again.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, this is a special migration case.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the permanently used current sitemap, you should generally provide the preferred current URLs of the website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Sitemap and robots.txt<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The address of a sitemap can also be found in the <code>robots.txt<\/code>-file must be specified.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, the principle looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Sitemap: https:\/\/example.com\/sitemap.xml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This allows search engines to discover the sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This does not necessarily replace the practical benefit of submitting via Search Console, because there you can additionally see whether Google was able to successfully retrieve and process the submitted sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How the <code>robots.txt<\/code> works, we will explain below <a href=\"\/en\/help\/seo-monitoring\/robots-txt-explained\/\">Robots.txt Explained: Controlling Search Engine Crawlers Properly<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not confuse a sitemap with robots.txt<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both files serve completely different tasks.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>XML Sitemap<\/th><th>robots.txt<\/th><\/tr><\/thead><tbody><tr><td>points to relevant URLs<\/td><td>contains crawling rules<\/td><\/tr><tr><td>supports URL discovery<\/td><td>can keep crawlers away from areas<\/td><\/tr><tr><td>no indexing guarantee<\/td><td>not a reliable replacement for noindex<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">These two mechanisms should therefore not be played off against each other.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Regularly check sitemap and Search Console<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After successful setup, you do not need to open the sitemaps report daily.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, occasional checking is useful, especially:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>after a relaunch\n\nafter major URL changes\n\nafter changing the SEO plugin\n\nin case of indexing problems\n\nwhen new pages are not found\n\nwhen Google reports a sitemap error<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Common sitemap errors<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>Incorrect sitemap address entered\n\nSitemap returns 404\n\nSitemap is password-protected\n\nContains old HTTP URLs\n\nContains redirect URLs\n\nContains 404 URLs\n\nContains noindex pages\n\nContains non-canonical URLs\n\nView sitemap as a guarantee for indexing\n\nResubmit sitemap after every new article\n\nManually edit automatically generated XML file\n\nDelete sitemap from Search Console and expect index removal\n\nView sitemap as a replacement for internal linking<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Checklist: Check XML Sitemap and Submit to Google<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>Determine sitemap address\n        \u2193\nOpen in browser\n        \u2193\nPublicly accessible?\n        \u2193\nCorrect HTTPS URLs?\n        \u2193\nOnly desired\nindexable URLs?\n        \u2193\nNo 404 URLs?\n        \u2193\nNo redirect URLs?\n        \u2193\nNo unnecessary noindex URLs?\n        \u2193\nCanonical signals plausible?\n        \u2193\nOpen Search Console\n        \u2193\nSelect correct property\n        \u2193\nOpen Sitemaps\n        \u2193\nSubmit sitemap or\nsitemap index\n        \u2193\nWait for processing\n        \u2193\nCheck status\n        \u2193\nCheck details in case of errors\n        \u2193\nCheck page indexing<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An XML sitemap is a machine-readable file that allows you to point search engines to important URLs on your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It helps Google discover pages, but it neither replaces a meaningful website structure nor good internal linking.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap should fundamentally contain the preferred indexable URLs of your website. Redirect URLs, 404 pages, intentionally on <code>noindex<\/code> Indexed pages and non-canonical duplicates typically do not belong in the regular sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For larger websites, multiple sitemaps can be used and combined via a sitemap index. If such an index is generated automatically, it is usually sufficient to submit it to the Google Search Console.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Submitting doesn't mean you are uploading a file to Google. You are simply telling Google where the sitemap is located on your website. Google will then retrieve it itself.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even a successful sitemap status does not mean that all contained URLs have been indexed. First, it confirms that Google was able to retrieve and process the sitemap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A good sitemap does not tell Google, \u201eThese are the pages you must index,\u201c but rather, as clearly as possible: \u201eThese are the current, preferred, and indexable URLs of my website.\u201c<\/strong><\/p>","protected":false},"excerpt":{"rendered":"<p>Eine XML-Sitemap hilft Suchmaschinen dabei, wichtige URLs einer Website zu entdecken und Informationen \u00fcber diese URLs zu erhalten. Besonders bei neuen, umfangreichen oder h\u00e4ufig aktualisierten Websites kann sie Google dabei unterst\u00fctzen, die Struktur und relevante Seiten einer Website effizienter zu erfassen. Eine Sitemap ist jedoch weder eine Garantie f\u00fcr die Indexierung noch ein Werkzeug, mit [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[85],"doc_tag":[],"class_list":["post-22913","docs","type-docs","status-publish","hentry","doc_category-seo-monitoring"],"year_month":"2026-10","word_count":2978,"total_views":"23","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"SEO &amp; Monitoring","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/seo-monitoring\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22913","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22913"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22913\/revisions"}],"predecessor-version":[{"id":22915,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22913\/revisions\/22915"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22913"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22913"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22913"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}