GSC Sitemaps Report: The Complete 2026 Guide

The Sitemaps report in Google Search Console is where you submit XML sitemaps and monitor their processing status. Despite being one of the simplest reports in GSC, it is frequently misunderstood and underutilized. This guide covers sitemap best practices, error diagnosis, and the 2025-2026...

Submitting a Sitemap

To submit a sitemap, navigate to the Sitemaps report, enter the full URL of your sitemap (e.g., https://example.com/sitemap.xml), and click Submit. Google then begins fetching and processing the sitemap. The report shows:

Status: Success, Has errors, Couldn't fetch, or Pending
URLs submitted: The total number of URLs in the sitemap
URLs indexed: The subset of submitted URLs that Google successfully indexed
Last read date: The most recent successful fetch time

As of 2025, Google supports sitemap indexing up to 500 MB uncompressed and 50,000 URLs per sitemap, consistent with the sitemaps.org protocol. You can provide multiple sitemap files via a sitemap index file. The 2026 GSC update added a "Sitemap coverage by type" breakdown, showing indexed rates for standard pages, images, videos, and news separately.

Sitemap Best Practices

Include Only Canonical 200 URLs

Every URL in your sitemap should return a 200 HTTP status and be the canonical version. Including 301-redirected URLs, 404s, or noindex pages wastes crawl budget and results in "Submitted URL not selected as canonical" or "Submitted URL not found" errors in the Coverage report.

Keep Sitemaps Fresh

Update your sitemap whenever you add, remove, or significantly update content. Google recommends incremental sitemap updates rather than complete regenerations. If your CMS supports it, ping Google's indexation system using the ping endpoint: https://www.google.com/ping?sitemap=<full_sitemap_url>.

Use Sitemap Index Files for Large Sites

If your site has more than 50,000 URLs, create a sitemap index file that references multiple child sitemaps. Organize child sitemaps logically (e.g., posts-sitemap.xml, categories-sitemap.xml, products-sitemap.xml). This allows Google to process each section independently and makes it easier to identify which content type has indexing issues.

Image and Video Sitemaps

For sites heavy on media, use Google's image and video sitemap extensions. The <image:image> and <video:video> tags within your sitemap provide metadata that helps Google surface your media in specialized search features. The 2026 Sitemaps report now shows per-sitemap breakdowns of how many images and videos were discovered.

Troubleshooting Sitemap Errors

"Couldn't fetch"

Googlebot could not access your sitemap. Check: robots.txt does not block the sitemap path, the sitemap URL is publicly accessible (no authentication), and your server returns a 200 status. Verify with curl -I https://example.com/sitemap.xml.

"Has errors"

The sitemap has formatting issues. Common problems include: unescaped XML characters (&, <, >, ", '), URLs exceeding 2048 characters, or nested sitemap index files beyond two levels. Validate your sitemap using Google's official sitemap testing tool or an XML validator before submission.

"URLs indexed" significantly lower than "URLs submitted"

This indicates that many submitted URLs were either not crawled, not indexed, or excluded after crawling. Cross-reference with the Coverage report. Filter by "Submitted in sitemap" to see exactly which sitemap URLs are erroring or excluded.

Sitemap Monitoring Strategy

Set up automated monitoring using the GSC API v2 sitemaps.list and sitemaps.get endpoints. The API returns the same metadata as the UI: contents, errors, warnings, isPending, isSitemapsIndex, lastDownloaded, and lastSubmitted. Build a dashboard that alerts on:

A sitemap remaining in "Pending" status for more than 24 hours
"URLs indexed" dropping below 90 percent of "URLs submitted" for any individual sitemap
A sitemap showing "Couldn't fetch" after a deployment

Audit and Verification

Quarterly, export the full sitemap URL list and cross-reference it against your CMS content inventory. Confirm every sitemap URL returns a 200 status and has a valid canonical tag. Remove any URLs that 301 redirect or return 4xx/5xx. For each sitemap file, verify the "URLs indexed" count is at least 90 percent of "URLs submitted." Document any sitemap that falls below this threshold and schedule a content quality or crawl budget review for the affected section.

Ready to Build Your Dream Website?

Let's discuss your project and create something amazing together.