XML Sitemap Troubleshooting: Fix “Couldn’t Fetch”, Errors and Missing URLs

An XML sitemap is a list of the URLs you want Google to crawl. It doesn’t force indexing, and Google calls a submission “merely a hint”, but a clean sitemap helps Google find new and changed pages faster, especially on larger or newer sites.

Search Console’s Sitemaps report shows whether Google could fetch and parse your sitemap. This guide explains each status and error, the checks to run before you change anything, and how to set up a sitemap that stays healthy.

What the three statuses mean

Status	Meaning	What to do
Success	Loaded and processed with no errors; URLs queued for crawling	Nothing; check indexing of key URLs separately
Has errors	Fetched, but one or more entries or tags are invalid; valid URLs are still queued	Open the sitemap row and fix each listed error
Couldn’t fetch	Google couldn’t retrieve the file at all	Confirm the URL, status code and robots.txt; test with URL Inspection

Fixing “Couldn’t fetch”

Start by proving the file works, so you don’t change a working setup. Open the sitemap URL in a private browser window: it should load, return 200 and show XML (not an HTML page). Then paste the sitemap URL into URL Inspection and run a live test. Google’s own advice is to confirm “Crawl allowed?” shows Yes and “Page fetch” shows Successful.

• Blocked by robots.txt: Google respects robots.txt when fetching sitemaps. Remove the rule that blocks it.
• 404: the address is wrong (a common mix-up between /sitemap.xml and /sitemap_index.xml on WordPress SEO plugins).
• Manual action: sitemaps aren’t read while a manual action is unresolved. Check the Manual actions report.
• Server or temporary errors: often transient; Google keeps retrying for a few days.
• Firewall or bot protection: some security rules challenge crawlers. The live test will fail if so.

Fixing “Has errors”

Error	Cause	Fix
URL not allowed	URLs on another host, protocol, www variant, or above the sitemap’s folder	Keep all URLs on the same host and protocol as the sitemap; place the sitemap at the root
URLs not followed	Listed URLs redirect, often through several hops, or use relative paths	List final destination URLs as absolute addresses
Sitemap contains URLs blocked by robots.txt	Listed URLs are disallowed	Remove them from the sitemap or allow crawling
Parsing error	Invalid XML, often an unescaped & or <	Escape special characters; validate the XML
Invalid date	lastmod not in W3C Datetime format	Use formats like 2026-10-12, with a time zone if you include a time
Too many URLs / File size error	More than 50,000 URLs or 50MB uncompressed	Split into several sitemaps listed in a sitemap index
Nested sitemap indexes	An index file lists another index file	Index files may list only sitemaps
Missing www / Includes www	URL host doesn’t match the sitemap’s host	Make the host consistent

Sitemap is fine, but URLs aren’t indexed

“Success” only means Google read the file. The Sitemaps report’s discovered-pages count comes with Google’s caveat that there’s no guarantee those URLs will be crawled or indexed. To see what happened, filter the Page indexing report by that sitemap and read the reasons. See how to fix indexing problems.

A useful trick from Google’s own documentation: submit a small sitemap of your most important pages and filter the Page indexing report by it. It gives you a clean view of the URLs that matter.

What a healthy sitemap looks like

• UTF-8 encoded XML, placed at the site root.
• Fully qualified absolute URLs (https://www.example.com/page/, not /page/).
• Only canonical URLs that return 200 and aren’t noindexed.
• No redirected, 404 or parameter URLs.
• lastmod updated only for significant changes to content, structured data or links.
• Referenced in robots.txt with a Sitemap: line and submitted in Search Console.

Google ignores the priority and changefreq tags, so there’s no need to tune them. If your CMS generates sitemaps (WordPress SEO plugins, Shopify), use the built-in one rather than maintaining a manual file.

Sitemap index files for larger sites

Once a site passes the per-file limits, or when you want to see indexing by content type, split URLs into several sitemaps and list them in a sitemap index. Splitting by type (pages, posts, products, categories) has a practical benefit: Search Console reports each sitemap separately, so you can see at a glance which section has indexing problems.

• An index file lists sitemaps only, never another index file.
• Each listed sitemap needs a full absolute URL.
• Submit the index once; Google reads the child sitemaps from it.
• Keep child sitemaps on the same host as the URLs they list.

Getting lastmod right

Google says it uses lastmod only when the value is consistently and verifiably accurate. That means updating it when the main content, structured data or links on a page change significantly, and not when a footer year or a sidebar widget changes. Plugins that stamp every URL with today’s date on each request teach Google to ignore the field.

If your CMS can’t produce accurate dates, it’s better to leave lastmod out than to publish misleading values.

Platform notes

WordPress

WordPress has a core sitemap at /wp-sitemap.xml, and SEO plugins usually replace it with their own index. Make sure only one is submitted, that excluded post types (attachments, tags) aren’t listed if you noindex them, and that a caching plugin isn’t serving a stale copy. Our WordPress SEO service covers these setups.

Shopify

Shopify generates /sitemap.xml automatically with child sitemaps for products, collections, pages and blogs. You can’t edit it directly; control what appears by publishing, unpublishing or noindexing content.

When to resubmit

• After fixing a fetch or parse error.
• After moving the sitemap to a new address.
• After a site migration (submit the new sitemap; keeping the old one for a while helps you watch redirects).

You don’t need to resubmit every time you publish a page; Google recrawls submitted sitemaps on its own schedule. For broader checks, see the technical SEO checklist.

Frequently asked questions

Sources

• Google Search Central: Build and submit a sitemap
• Search Console Help: Manage your sitemaps using the Sitemaps report
• Search Console Help: URL Inspection tool
• Search Console Help: Page indexing report
• Google Search Central: How Google interprets the robots.txt specification

Last reviewed October 12, 2026.