An XML sitemap hands Google a map of the pages you want indexed, though Google treats it only as a hint, not a guarantee of crawling or indexing. Search Console flags a sitemap error when it cannot read that map. Per Google, "Couldn't fetch" points to robots.txt blocking, a 404, server errors, or low crawl demand, and can also appear briefly after submission then clear. Real errors include malformed or non-UTF-8 XML, out-of-property URLs, and exceeding the 50,000 URL or 50 MB limit. We validate, clean, and resubmit for $49-$79.
An XML sitemap is a file that lists the URLs on your site you want search engines to know about, along with signals like when each was last updated. It is how you hand Google a map instead of making it find every page by following links. Google is explicit that this is only a hint: in its own words, "submitting a sitemap is merely a hint: it doesn't guarantee that Google will download the sitemap or use the sitemap for crawling URLs on the site." When Search Console reports a sitemap error, it means Google tried to read that map and hit a problem, so some or all of your pages may go undiscovered through it. The most misread status is "Couldn't fetch," which Google attributes to real causes like robots.txt blocking the sitemap, a 404 on the sitemap URL, server errors, or low crawl demand, though it can also appear briefly right after submission and then clear. Genuine errors are different: malformed or non-UTF-8 XML that will not parse, URLs that fall outside the submitted property, URLs that redirect or return 404s, or a sitemap that exceeds Google's limits of 50,000 URLs and 50 megabytes uncompressed per file. A sitemap is not strictly required for a small, well-linked site, Google can crawl those fine, but it becomes important for large sites, new sites with few backlinks, sites with pages that are not well linked internally, and sites with rich media.
Fix This Error Now →XML Sitemap Errors can be caused by several issues. Here are the most common.
The most common and most misread status. Google's Sitemaps report documentation lists its causes as robots.txt blocking the sitemap path, a manual action on the site, the sitemap URL returning a 404, the server being unavailable or erroring, or low crawl demand. In practice it can also appear transiently right after submission and clear once Google processes the file, which is why it should not be assumed broken or assumed fine, it should be checked. The way to tell is to fetch the sitemap URL yourself: if it returns clean XML with a 200 and is not blocked, the status usually resolves; if it does not, one of Google's listed causes is real.
The sitemap does not follow the XML syntax the sitemaps protocol requires: an unclosed tag, an unescaped ampersand or special character in a URL, the wrong namespace declaration, or stray HTML from a PHP notice printed at the top of the file. Google cannot parse a malformed sitemap and rejects the whole thing, so every URL in it is ignored.
When you submit a sitemap in Search Console, its URLs should belong to that property, using the exact protocol and host. Listing http URLs in a sitemap served over https, or mixing www and non-www, makes those URLs look like they are outside the property and they get dropped. Google does support sitemaps that reference other hosts, but only with cross-submission verification such as declaring the sitemap in each site's robots.txt, so casual cross-domain URLs simply fail. Protocol and host mismatches are common after an HTTPS or domain migration when the sitemap still points at old URLs.
A sitemap should list only canonical, indexable URLs that return 200. Including URLs that 404, redirect elsewhere, are blocked by robots.txt, or carry a noindex tag sends Google mixed signals: the sitemap says "index this" while the page says "do not." Google flags these and may distrust the whole sitemap if too many URLs conflict.
A single sitemap file can contain at most 50,000 URLs and must be no larger than 50 megabytes uncompressed. A large site that crams everything into one file will have it rejected. The solution is multiple sitemaps referenced from a sitemap index file, which most SEO plugins generate automatically but custom setups often get wrong.
A sitemap your CMS generates does nothing until Google knows about it, either through submission in Search Console or a reference line in robots.txt. Submitting the wrong path, or having the sitemap at a URL Google cannot guess, means it is never read. Many owners do not realize their sitemap exists or that it has to be pointed to explicitly.
If a Disallow rule in robots.txt covers the sitemap's path, Google cannot fetch the file even though it exists, producing a fetch failure. The sitemap URL must always be crawlable, and it is good practice to also declare it with a Sitemap line in robots.txt.
70-80% of our customers have WordPress sites. Here are WordPress-specific causes for this error.
WordPress core generates its own sitemap at wp-sitemap.xml, and Yoast, Rank Math, and All in One SEO each generate their own. Running more than one leaves competing sitemaps, and you may submit the wrong one or send Google conflicting URL sets. Pick one source, usually your SEO plugin, and disable the others.
A caching plugin or CDN can serve an old cached copy of the sitemap that still lists deleted pages or misses new ones. Excluding the sitemap from caching and purging after major changes keeps Google seeing the current URL set.
A plugin or theme printing a PHP notice or warning injects stray text before the XML declaration, which breaks parsing and makes an otherwise valid sitemap invalid. Fixing the underlying PHP notice restores a clean file.
Open the Sitemaps report in Search Console to see the exact status and error, then fetch the sitemap directly to distinguish a real error from a not-yet-processed "Couldn't fetch"
Validate the XML against the sitemaps protocol to catch malformed tags, unescaped characters, wrong namespaces, and stray output before the declaration
Confirm the sitemap URL returns a clean 200, is not blocked by robots.txt, and is declared with a Sitemap line in robots.txt
Audit the listed URLs and remove anything that 404s, redirects, is noindexed, or is blocked, so the sitemap contains only canonical indexable pages
Ensure every URL matches the property exactly on protocol and host, correcting leftover http or www mismatches from past migrations
Split oversized sitemaps into multiple files under the 50,000 URL and 50 megabyte limits and tie them together with a sitemap index file
On WordPress, consolidate to a single sitemap source and exclude it from caching
Resubmit the corrected sitemap and monitor the Sitemaps report until it reads Success with the expected number of discovered URLs
Fixed in 2 hours or your money back. We do not waste time.
No hourly billing. You know the price before we start.
Cannot fix it? You do not pay. Zero risk to you.
Our Google & SEO Issues team has fixed thousands of sites with this exact issue. 2-hour turnaround, guaranteed.
Maybe, maybe not, and it is worth checking rather than assuming either way. Google's Sitemaps report documentation attributes "Couldn't fetch" to real causes: robots.txt blocking the sitemap path, a manual action on the site, the sitemap URL returning a 404, the server being unavailable or erroring, or low crawl demand. Separately, the status is also widely observed to appear transiently right after you submit a sitemap and then clear once Google processes it. The way to tell which you have is to fetch the sitemap URL yourself and confirm it returns clean XML with a 200 and is not blocked by robots.txt. If it does and the status clears within a few days, it was the harmless kind. If it does not, one of Google's listed causes is real and we fix it.
Not always, but often yes. Google can crawl a small site with good internal linking without one, and Google is clear that a sitemap is only a hint that does not guarantee crawling or indexing. A sitemap becomes important when your site is large, brand new with few backlinks, has pages that are not well linked from other pages, or uses rich media Google struggles to discover. Even when not strictly required, a clean sitemap is a reliable way to help Google discover new and updated content, so for most business sites it is worth having and worth keeping error-free. What it will not do is force indexing of a page Google has judged not worth indexing, that is a content and quality problem, not a sitemap one.
A single sitemap file is limited to 50,000 URLs and 50 megabytes uncompressed. If your site has more URLs than that, you split them across multiple sitemap files and reference all of them from a single sitemap index file, which itself can point to up to 50,000 sitemaps. Most SEO plugins handle this splitting automatically. Custom or hand-built sitemaps are where the limit usually gets violated.
No. A sitemap should list only the canonical, indexable URLs you actually want in search, each returning a 200 status. Do not include pages that redirect, return 404, carry a noindex tag, or are blocked by robots.txt, because that contradicts the page-level signals and erodes Google's trust in the sitemap. Tag archives, paginated pages, and thin utility pages are commonly and correctly left out. A focused sitemap of your best pages works better than an exhaustive one full of noise.
Most sitemap fixes cost $49 to $79. Validating and correcting a malformed sitemap, fixing the submission, or cleaning out bad URLs is quick work. Rebuilding sitemap structure for a large site with index files, or untangling conflicting plugin-generated sitemaps after a migration, runs $99 to $149. You get a firm quote up front.
Every technical claim on this page traces back to primary documentation and the named vendor references below.
Why your pages are not indexed, what every Search Console status means, and how to get back into Google.
Visit the SEO & Search Console Repair hub →Get xml sitemap errors fixed today. Expert engineers. 2-hour guarantee.
Fix My Error Now →