Fix 'Sitemap Could Not Be Read' & 'Couldn't Fetch' in Google Search Console (2026)

When you submit sitemap.xml in Google Search Console and see Couldn't fetch or Sitemap could not be read, Google either failed to reach the URL or received invalid XML (such as an HTML 404 page, a redirect loop, a missing XML namespace, or a blocked robots.txt rule).

You can diagnose and fix the error in under five minutes by checking four things in order: HTTP status code, Content-Type header, XML syntax, and robots.txt access. If your current file is broken, you can generate a clean, standards-compliant replacement in our free XML sitemap generator.

Quick Diagnostic Table: Match Your Exact GSC Sitemap Error

Search Console Error Message	Most Common Root Cause	Immediate Fix
Couldn't fetch (Pending / Immediate)	GSC UI bug before first crawl, or robots.txt / WAF blocking Googlebot	Run URL Inspection → Test Live URL on your sitemap URL to verify Googlebot can fetch it
Sitemap could not be read: General HTTP error (404 / 403 / 500)	Sitemap URL returns 404, 403 (Cloudflare bot fight mode), or 301 redirect	Test your sitemap URL in our live HTTP status checker to confirm HTTP 200 OK
Sitemap is HTML	Your /sitemap.xml URL is redirecting to your homepage or rendering a soft-404 HTML page	Serve raw XML with Content-Type: application/xml; charset=utf-8
Namespace incorrect / Missing XML tag	Missing xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" or unescaped & in URLs	Rebuild the file with escaped & entities in the XML sitemap generator
Invalid date in <lastmod>	Using human dates (Nov 3, 2026) instead of W3C ISO 8601 (2026-11-03)	Format all <lastmod> dates as YYYY-MM-DD

---

Step 1: Verify Your Sitemap Returns HTTP 200 OK (Not a 301 or 404)

Google Search Console requires your submitted sitemap URL to match your property's canonical protocol and subdomain (https://www. vs https://) and return HTTP 200 OK directly without a redirect chain.

1. Open our free HTML & Live HTTP Status Checker and switch to 2. Check Live URL HTTP Status (200 / 301 / 404).
2. Paste your exact sitemap URL (for example, https://www.example.com/sitemap.xml) and run the check.
3. If the tool reports HTTP 301 or HTTP 308 (for instance, redirecting from https://example.com/sitemap.xml to https://www.example.com/sitemap.xml), delete the old sitemap entry in Search Console and submit the final destination URL instead.

---

Step 2: Use GSC's "Test Live URL" Trick to Force Googlebot to Fetch the Sitemap

Sometimes Search Console displays Couldn't fetch immediately after you click Submit simply because Google has not queued the background sitemap fetch yet.

To verify whether Googlebot can actually read your sitemap—and often nudge Search Console to clear the false error:

1. Copy your full sitemap URL (https://www.example.com/sitemap.xml).
2. Paste it into the Inspect any URL search bar at the very top of Google Search Console.
3. Click Test Live URL in the top right corner.
4. Confirm that Page fetch says Successful and Crawl allowed? says Yes.
5. Return to the Sitemaps tab and resubmit https://www.example.com/sitemap.xml.

---

Step 3: Check Your XML Sitemap Syntax & Escaping

A single unescaped ampersand (&) in a query string or a missing closing tag will cause Google's XML parser to fail with Sitemap could not be read. Every valid XML sitemap must follow this exact structure:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/</loc>
    <lastmod>2026-11-03</lastmod>
  </url>
  <url>
    <loc>https://www.example.com/tools/xml-sitemap-generator</loc>
    <lastmod>2026-11-03</lastmod>
  </url>
</urlset>

4 Strict XML Sitemap Rules in 2026

• Escape special characters: Replace every & in URLs with &, ' with ', and " with ".
• Use W3C ISO 8601 dates: Always write <lastmod>2026-11-03</lastmod> (or full ISO timestamp 2026-11-03T12:00:00+00:00).
• Include only canonical 200 OK URLs: Never include 301 redirects, 404 pages, or noindex pages in your sitemap. Verify your canonical tags with the canonical URL generator.
• Omit <priority> and <changefreq>: Google officially ignores both attributes; only <loc> and accurate <lastmod> dates matter.

---

Step 4: Confirm robots.txt and Cloudflare Are Not Blocking Googlebot

If your sitemap syntax is valid and returns HTTP 200 in your browser, check two server-level blockers:

1. Check /robots.txt: Make sure your robots.txt does not accidentally disallow /sitemap.xml or /*.xml$, and include a Sitemap: https://www.example.com/sitemap.xml directive at the bottom. You can generate a clean file with our robots.txt generator.
2. Check Cloudflare Bot Fight Mode / WAF: On Cloudflare free plans, aggressive "Bot Fight Mode" or "Under Attack Mode" can serve a 403 Forbidden HTML challenge page to Google's sitemap fetcher. Check Security → Events in Cloudflare and ensure verified bots (cf.client.bot) are allowed.

Related Technical SEO Tools & Guides

• Build a clean sitemap in seconds: Free XML Sitemap Generator
• Read our complete sitemap strategy guide: XML Sitemap Best Practices in 2026
• Filter your indexed pages in Search Console: Free GSC RE2 Regex Generator
• Generate Next.js App Router SEO metadata: Free Next.js Metadata Generator