Sitemaps report

Use the Sitemaps report to see which sitemaps were processed for your site, any processing errors, or to submit a new sitemap for your site. The new Search Console encourages the use of sitemaps to help Google discover the right content on your site, and to improve content tracking and error reporting.

OPEN SITEMAPS REPORT

Add a sitemap

To submit a new sitemap for crawling:

  1. Post a sitemap on your site.
  2. Enter the relative URL for the sitemap on the Sitemaps report and click Submit.
  3. The sitemap should be processed immediately. However, it can take some time to crawl the URLs listed in a sitemap, and it is possible that not all URLs in a sitemap will be crawled, depending on the site size, activity, traffic, and so on.

To resubmit a sitemap, perform these steps again.

Understanding the report

The report has the following information. For additional information not shown here, you can open the old Sitemaps report.

The following information is provided for each submitted sitemap:

  • Sitemap URL: The URL where the sitemap is posted. Sitemaps located in any directory or subdirectory will be shown. So if the property is example.com/, the sitemaps example.com/map.xml, example.com/a/map.xml, and example.com/a/b/map.xml can all be shown.
  • Type: The type of sitemap. Possible values:
    • Sitemap: Standard sitemap
    • Sitemap index: A sitemap of sitemaps
    • Unknown: The submitted file is not a known sitemap type or the sitemap hasn't been processed yet.
  • Submitted: The date when the sitemap was submitted.
  • Last processed: The last time the sitemap was processed by Google.
  • Status: Status of the submit or crawl. Possible values:
    • Processed successfully: The sitemap was loaded and processed successfully with no errors. All URLs will be queued for crawling.
    • Has issues: The sitemap has one or more errors; any URLs that can be retrieved from the sitemap will be queued for crawling.
    • Couldn't be fetched: The sitemap could not be fetched for some reason.
  • Count of URLs: The number of URLs listed in the sitemap. If this is a sitemap index, the number is the count of all URLs in all referenced sitemaps. Duplicate URLs are counted only once.

My sitemap isn't listed!

Here are a few reasons you might not see a sitemap listed here:

  • It lives in another property Sitemaps associated with one property won't be visible in another property. Thus, sitemaps that you've submitted for the site http://example.com won't be visible in the Sitemaps report for http://www.example.com. or https://example.com. To address this issue, make sure that you've added all versions of your site then, tell Google your preferred domain and only submit sitemaps for the preferred one.
  • You did not submit the sitemap using this report Only sitemaps submitted using this report are listed; sitemaps found or submitted other methods won't be shown, even if Google can find and use them.

Sitemap errors

The following errors are reported by the sitemaps report.

Complete error list

URLs not accessible

Indicates that Google encountered an error when attempting to view a URL in your sitemap. Inspect the URL in the sitemap using the URL inspection tool to see whether the URL is available to Google.

URLs not followed

Typically indicates that Google can't completely process your sitemap because some of URLs contain too many redirects for Google web crawlers to follow. We suggest that you replace each URL redirecting to another page with the URL that the redirect is pointing to (the destination URL).

The following list describes some additional reasons a redirect could not be followed along with possible solutions:

  • Use a text browser such as Lynx to examine your site, since many search engines see your site much as Lynx would. If features such as Javascript, cookies, session IDs, frames, DHTML, or Flash keep you from seeing all of your site in a text browser, then simple search engine spiders might have trouble crawling your site.
  • If you are permanently redirecting from one page to another, you can use a permanent redirect; you should avoid using JavaScript or meta-refresh type redirects.
  • Where possible, use absolute or complete links rather than relative links. For instance, when linking to another page in your site, link to https://www.example.com/mypage.html rather than simply mypage.html.

URL not allowed

Your sitemap includes some URLs that are at a higher level or different domain than the sitemap file.

Higher level: If your sitemap is listed under http://www.example.com/mysite/sitemap.xml, the following URLs are not valid for that sitemap:

  • http://www.example.com/ - it's at a higher level than the sitemap
  • http://www.example.com/yoursite/ - it's in a directory parallel to the sitemap

Different domain: Check that the URLs all begin with the same domain as your sitemap location. For instance, if your sitemap is at http://www.example.com/sitemap.xml, the following URLs are not valid for that sitemap:

  • http://example.com/ - Missing "www"
  • www.example.com/ - Missing "http"
  • https://www.example.com/ - Using https rather than http

Compression error

Google encountered an error when trying to uncompress your compressed sitemap file. Recompress your sitemap (using a tool such as gzip), upload it to your site, and resubmit it.

Empty sitemap

Your sitemap doesn't contain any URLs. Check your sitemap and ensure that it is not empty. If your sitemap uses the sitemap protocol, ensure that the URLs are tagged correctly.

Sitemap file size error: Your sitemap exceeds the maximum file size limit.

Your sitemap is larger than 50MB when uncompressed. If your sitemap is larger than the limit, break it into several smaller sitemaps and list these in a sitemap index file and submit the sitemap index file(s).

Invalid attribute value

You assigned an invalid value to an XML tag attribute. Check your sitemaps to make sure that only the allowed attributes are present, and that you assign only allowed values according to the sitemap specifications. Check your attributes and values for typos.

Invalid date

Your sitemap contains one or more invalid dates. This error could be because a date is in the incorrect format, or the date itself is not valid. Dates must use W3C Datetime encoding, although you can omit the time portion. Make sure your dates match one of the following W3C Datetime formats:

2005-02-21 
2005-02-21T18:00:15+00:00

Specifying time is optional (the time defaults to 00:00:00Z), but if you do specify a time, you must also specify a time zone.

Invalid tag value

Your sitemap contains one or more tags with an invalid value. The error should list the tag in error. Check the specifications for your sitemap type (index, standard, video, and so on).

Invalid URL

A URL in your sitemap is not valid. This error might be because it contains unsupported characters, spaces, or other characters such as quotes, or it might be incorrectly formatted (for example, htp:// instead of http:// ). Make sure that the URLs listed in your sitemap are encoded for readability and escaped properly. Check for any incorrect characters such as spaces or quotes. You also try copying the URL into a browser to see if the browser can understand the URL and load the page.

Invalid URL in sitemap index file: incomplete URL

Your sitemap index file doesn't include the full URL for each sitemap file that it lists. When we see a sitemap index file, we look in the same directory for the files that it references. For instance, if your sitemap index file is http://www.example.com/folder1/sitemap_index.xml and lists a sitemap as sitemap.xml, we'll look for that sitemap at http://www.example.com/folder1/sitemap.xml. If we can't find it there, then you'll see this error.

Update your sitemap index file to include the complete path to each listed sitemap file, then resubmit.

Invalid XML: too many tags

Your sitemap contains duplicate tags. For example, the following entry would cause this error because the <loc> tag is listed twice:

<url>
  <loc>http://www.example.com/</loc>
  <loc>http://www.example.com/page1.html</loc>
  <lastmod>2005-01-01</lastmod>
  <changefreq>monthly</changefreq>
  <priority>0.8</priority>
</url>

The error lists the problematic tag and the line number. Remove the duplicate tag and resubmit your sitemap.

Missing XML attribute

A tag in your sitemap is missing a required attribute. Check your sitemaps to make sure that no required attributes are missing. Once you have fixed the attribute values, resubmit your sitemap.

Missing XML tag

One or more entries in your sitemap is missing a required tag. The error message lists the line number. Review the sitemap fundamentals page for information on required tags.

Missing thumbnail URL

One or more video entries is missing a URL to a thumbnail image. Make sure that the location of any thumbnail URLs are specified using the <video:thumbnail_loc> tag.

Missing video title

One or more video entries is missing a title. Make sure that each video in your sitemap has a title, specified in the the <video:title> tag. 

Incorrect sitemap index format: Nested sitemap indexes

One or more entries in your sitemap index file uses its own URL or the URL of another sitemap index file.

A sitemap index file can't list other sitemap index files, only sitemap files.

Remove any entries pointing to sitemap index files, then resubmit your sitemap.

Parsing error

Google could not parse the sitemap's XML.

Often, this problem is caused by an unescaped character in the URL. As with all XML files, any data values (including URLs) must use entity escape codes for certain characters such as & ' " < > symbols. Be sure that your URLs are properly escaped.

Temporary error

Our system experienced a temporary problem that prevented us from processing your sitemap. Generally, when you receive this error, you do not need to resubmit your sitemap. Google can try to retrieve your sitemap again later. If the error still exists after several hours, try resubmitting your sitemap.

Too many sitemaps in sitemap index file

Your sitemap index file lists more than 50,000 sitemaps. Split your sitemap index into multiple sitemap index files and ensure that each lists no more than 50,000 sitemaps.

Too many URLs in sitemap

Your sitemap lists more than 50,000 URLs. Split your sitemap into multiple Sitemaps and ensure that each contains no more than 50,000 URLs. You can also use a sitemap index file to manage your sitemaps.

Unsupported format

Your sitemap is not in a supported format.

Some common XML mistakes:

  • Your sitemap must use the correct header. For example, if your sitemap contains video information, it would have the following header:
    <?xml version="1.0" encoding="UTF-8"?>
    <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
            xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
  • The namespace in the header must be "http://www.sitemaps.org/schemas/sitemap/0.9" (not .9).
  • All XML attributes must enclosed in either single quotes (') or double quotes (") and those quotes must be straight, not curly. Word-processing programs such as Microsoft Word can insert curly quotes.

Path mismatch: Missing www

The path to your sitemap does not contain the www prefix (for example, http://example.com/sitemap.xml), but the URLs it lists do (for example, http://www.example.com/myfile.html).

If you want to submit your sitemap to non-www, but the URLs it contains to be www, select www as the preferred domain for your site.

Otherwise, modify your sitemap to remove "www" from all the URLs to match your sitemap location.

Path mismatch: Includes www

The path to your sitemap contains the www prefix (for example, http://www.example.com/sitemap.xml), but the URLs it contains do not (for example, http://example.com/myfile.xml.

If you want to submit your sitemap to www, but the URLs it contains to be non-www, select non-www as the preferred domain for your site.

Otherwise, modify your sitemap to add "www" to all the URLs to match your sitemap location.

Incorrect namespace

The root element of your sitemap doesn't contain the correct namespace, or the namespace is declared incorrectly, or has a typo or incorrect URL.

Be sure that you are using the correct namespace for your file type. For example:

  • A sitemap file: xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
  • A video sitemap file: xmlns:video="http://www.google.com/schemas/sitemap-video/1.1"
  • A sitemap index file:  <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  • Other sitemap types...

Leading whitespace

Your sitemap begins with leading whitespace, rather than a namespace declaration. XML files should begin with the XML declaration that specifies the version of XML being used.

This error won't prevent Google from processing your sitemap, but you might want to remove the whitespace so that the file adheres to the XML standard and you no longer see this error.

HTTP error [specific code]

Google encountered an HTTP error when when attempting to download your sitemap. This message displays the status code we received (for example, 404). Make sure that the sitemap URL you specified is correct and that the sitemap exists at that location. Then, resubmit your sitemap.

Thumbnail too large

The video thumbnail image specified in your sitemap is too large. Resize your video thumbnail image to 160 x 120 px. Update your sitemap with the new information, and then resubmit it. More information about adding video information to a sitemap.

Thumbnail too small

A video thumbnail image specified in your sitemap is too small. Resize your video thumbnail image to 160 x 120 px. Update your sitemap if necessary. More information about adding video information to a sitemap.

Video location and play page location are the same

In a video sitemap, the video content URL and the player URL cannot be the same. If you provide  both <video:player_loc> and <video:content_loc>, the URLs must be different. More information about adding video information to a sitemap.

Video location URL appears to be a play page URL

In a video sitemap, the <video:content_loc> URL points to the page hosting the player. More information about adding video information to a sitemap.

Sitemap contains urls which are blocked by robots.txt

Google cannot access your sitemap, or can't access all the content listed in your sitemap, because it is blocked by robots.txt. Verify using the URL Inspection tool to confirm which file is blocking it, and modify your robots.txt file to allow Googlebot to access it.

Known issues

The following are known issues in this beta version of the new Search Console. No need to report them to us, but we'd love your feedback on any other features or issues you spot. Use the Feedback mechanism in the navigation bar.

  • RSS feeds are not yet supported.
  • The mobile experience is still a work in progress.
  • Property sets are not yet supported.
  • Only URLs scoped to the currently selected property are reported on.
Was this article helpful?
How can we improve it?