Your XML sitemap is one of the most important communication tools
between your website and Google. It tells Google which pages exist on
your site, how they are organised, and when they were last updated. When
sitemap errors appear in Google Search Console, pages may not be
indexed, may be slow to get crawled, or may be missing from search
results entirely.
This guide covers every sitemap error type reported in GSC, explains
what causes each one, and gives you the specific steps to fix it.
Where to Find Sitemap Errors in GSC
Go to Google Search Console → Indexing → Sitemaps. This section shows:
- All sitemaps you have submitted
-
The status of each sitemap (Success, Has errors, Couldn’t fetch)
- The number of URLs submitted vs discovered
- Error details when applicable
You can also check individual sitemap URLs using the URL Inspection tool
to see what GSC sees when it fetches your sitemap.
Sitemap Error 1: “Couldn’t Fetch” (Sitemap Not Accessible)
What it means
Google attempted to download your sitemap URL but received no response
or a server error. The sitemap URL is returning a 404 (not found), 500
(server error), or timing out.
Common causes
- The sitemap URL you submitted does not exist at that path
- A server configuration change broke the sitemap URL
- A plugin that generated the sitemap was deactivated (WordPress)
- Your robots.txt is blocking the sitemap URL (rare)
- Server downtime when Google attempted to fetch
How to fix it
Step 1: Visit the sitemap URL directly in your browser
(e.g. yourdomain.com/sitemap.xml). Does it load?
-
If it loads fine: The error may have been temporary.
Re-submit the sitemap in GSC and monitor. If the error persists, check
your server logs for when GSC attempted to fetch.
-
If it returns 404: The sitemap URL has changed or the
file no longer exists. For WordPress, check if your SEO plugin’s
sitemap feature is still active (go to Yoast → Features or Rank Math →
Sitemap Settings). Re-enable if disabled, then re-submit the correct
URL.
-
If it returns a server error: A server or plugin
issue is preventing the sitemap from generating. Check your WordPress
error logs or contact your host.
Step 2: Verify the sitemap URL in GSC is correct.
Remove the incorrect URL and re-submit with the current, accessible
sitemap URL.
Sitemap Error 2: “Sitemap URL Returns HTTP Error” (4xx or 5xx)
What it means
Similar to “Couldn’t fetch,” but GSC received a specific HTTP error code
rather than a timeout. The sitemap URL exists but returns an error
response.
How to fix it
The fix depends on the HTTP error code:
-
404 (Not Found): The sitemap file does not exist at
that path. Regenerate your sitemap through your SEO plugin, or correct
the submitted URL in GSC.
-
403 (Forbidden): Your server is blocking access to
the sitemap. This can happen if you have added IP-based restrictions
or htpasswd protection to your site. Ensure the sitemap is publicly
accessible without authentication.
-
500 (Internal Server Error): A server-side error is
preventing sitemap generation. Check PHP error logs and your SEO
plugin’s sitemap settings. A plugin conflict is a common cause —
deactivate plugins one by one to identify the conflict.
Sitemap Error 3: “Sitemap File Could Not Be Read” (Invalid XML)
What it means
Google successfully downloaded the sitemap file but cannot parse it
because the XML is invalid or malformed.
Common causes
-
A URL in the sitemap contains invalid characters (ampersands &, angle
brackets <>, quotes that are not encoded)
-
The sitemap file has been corrupted (truncated, encoding error, or
mixed encoding)
- A plugin generated malformed XML due to a bug or conflict
-
The sitemap contains characters outside ASCII range without proper
encoding
How to fix it
Step 1: Validate your sitemap. Paste your sitemap URL
into an XML validator tool (Google “XML sitemap validator”) or use
Screaming Frog to crawl your sitemap and check for errors.
Step 2: Look for URLs with special characters. In XML,
these characters must be entity-encoded:
& → &
< → <
> → >
" → "
' → '
A URL like yourdomain.com/page?id=1&type=product in a sitemap must
appear as yourdomain.com/page?id=1&type=product.
Step 3: For WordPress, try deactivating and
reactivating your SEO plugin’s sitemap feature to regenerate a fresh
sitemap. If the issue persists, check for plugin conflicts.
Step 4: After fixing, re-submit the sitemap in GSC.
Sitemap Error 4: “URLs in Sitemap Are Blocked by robots.txt”
What it means
Your sitemap lists URLs that are blocked from crawling by your
robots.txt file. Google is telling you there is a conflict — you are
asking it to index pages via the sitemap but also blocking it from
accessing those pages via robots.txt.
Why this matters
A robots.txt block prevents Google from reading the page content. A page
cannot be meaningfully indexed if it cannot be crawled. Having blocked
URLs in your sitemap means these pages will not rank, and the sitemap
entry is wasted.
How to fix it
First, determine which URLs are blocked. In GSC, click through to the
sitemap error details to see the specific affected URLs. Alternatively,
use Screaming Frog to crawl your sitemap and check each URL against your
robots.txt.
Then, make a decision for each blocked URL:
-
If the page should be indexed: The robots.txt block
is a mistake. Edit your robots.txt to remove the Disallow rule
affecting this URL. See our
robots.txt fix guide
for instructions.
-
If the page should NOT be indexed: Remove it from
your sitemap. Your sitemap should only contain URLs you want Google to
index.
Never submit blocked URLs in your sitemap — it is contradictory and
wastes GSC’s attention on unresolvable conflicts.
Sitemap Error 5: “URLs in Sitemap Return Redirect”
What it means
URLs listed in your sitemap are redirecting to different URLs before
Google can crawl them. Your sitemap should always list the final,
canonical destination URL — not an intermediate URL that redirects
somewhere.
Common causes
-
You changed your URL structure (e.g. added or removed trailing
slashes) but the sitemap still lists old formats
- HTTP URLs in the sitemap when the site is now HTTPS
-
www URLs in the sitemap when the canonical is non-www (or vice versa)
- URLs that have been permanently moved and now 301 redirect
How to fix it
Update your sitemap to use the final canonical URL for each entry. If
your site is HTTPS, all sitemap URLs should start with https://. If your
canonical is non-www, all sitemap URLs should be non-www.
For WordPress, check your SEO plugin settings:
-
In Yoast: Settings → Site Representation → ensure the site URL matches
your canonical format
- In Rank Math: General Settings → site URL configuration
After correcting, regenerate and re-submit your sitemap.
Sitemap Error 6: “URLs in Sitemap Are Not Indexable”
What it means
Your sitemap contains URLs that have noindex directives, canonical tags
pointing to different URLs, or other signals telling Google not to index
them. As with blocked URLs, these entries are contradictory — your
sitemap says “please index this” but the page itself says “do not index
me.”
How to fix it
For each affected URL, you have two choices:
-
Remove the noindex/canonical issue: If the page
should be indexed, check why it has a noindex directive or an
incorrect canonical. Fix the meta robots or canonical tag to allow
indexing.
-
Remove the URL from the sitemap: If the page should
not be indexed (it has a noindex for a good reason), remove it from
your sitemap. Your sitemap should only contain the canonical,
indexable versions of your content pages.
Sitemap Best Practices: Prevent Future Errors
Building a clean, correct sitemap from the start prevents most of these
errors from recurring.
-
Only include canonical URLs. Every URL in your
sitemap should be the canonical version — the one with the correct
protocol (https), the correct www preference, and no redirects.
-
Only include indexable pages. No noindex pages, no
pages blocked by robots.txt, no login pages, no admin pages.
-
Keep URLs to a manageable size. Google recommends
keeping each sitemap file under 50,000 URLs and 50MB uncompressed. For
large sites, use a sitemap index file that references multiple
individual sitemaps.
-
Update automatically. For WordPress, your SEO plugin
should automatically add new pages to the sitemap when you publish
them and remove deleted pages when you delete them.
-
Use hreflang in sitemaps for multilingual sites. If
your site targets multiple languages or regions, implement hreflang
annotations in your sitemap (or in your page headers). See our hreflang strategies guide.
-
Test before submitting. Before submitting a new or
updated sitemap in GSC, visit the sitemap URL directly and validate
the XML using an online tool.
Checking Sitemap Health in GSC Monthly
A healthy sitemap in GSC shows:
- Status: Success
- No error warnings
-
High ratio of “Discovered” to “Submitted” URLs (ideally above 90%)
A significant gap between submitted and discovered URLs is not
necessarily an error — it means Google has chosen not to index some of
your submitted URLs, which is a content quality signal worth
investigating. See our guide on
Crawled — Currently Not Indexed
and our guide on
Indexed, Not Submitted in Sitemap for context
on what these gaps mean.
Summary: Sitemap Error Fix Priority
| Error | Severity | Fix Time |
| Couldn’t fetch / 404 | High — pages may not be discovered | 15 minutes |
| Invalid XML | High — entire sitemap unreadable | 30 minutes |
| URLs blocked by robots.txt | High — pages cannot be indexed | 30–60 minutes |
| URLs returning redirects | Medium — wasted crawl signals | 30 minutes |
| URLs with noindex/canonical issues | Medium — contradictory signals | 1–2 hours |
| HTTP error (403, 500) | High — depends on server config | Variable |
If you have resolved all sitemap errors and are still seeing pages not
indexed or slow to be crawled, the issue may be crawl budget or content
quality rather than the sitemap itself. See our
crawl budget management guide
for next steps.
For a full review of your site’s indexing health, our
technical SEO team can audit
your sitemap, coverage report, and crawl patterns as part of a complete
audit.
Related reading:
