Blogger Sitemap Couldn't Fetch in Search Console? How to Fix

By ·

You submitted your Blogger sitemap in Google Search Console and the status says Couldn't fetch. It looks like an error, and it is one of the most common worries for new Blogger users. The good news: on a Blogger blog, the sitemap itself is almost never broken. Usually Google simply has not processed it yet, or it was submitted in the wrong property.

This guide explains what the status means according to Google's own help page, how to check and fix the few real causes on Blogger, and when to stop worrying and wait. It also covers where Blogger's two sitemaps live and how to submit them correctly to Google and Bing.

What "Couldn't fetch" means

Google's Sitemaps report help page describes "Couldn't fetch" as Google not being able to fetch the sitemap, and lists the usual reasons:

  • The sitemap is blocked by robots.txt.
  • The site has an unresolved manual action.
  • The sitemap URL is wrong and returns a 404 error.
  • A general, often temporary, error such as the server being unavailable.
  • Low crawl demand for the sitemap, which is common for new sites.

Product experts on the Google Search Central community frequently point out that for new sites the status often just means the sitemap has not been processed yet. On Blogger, where Google hosts the blog, the first, third and fourth causes are rare unless something was changed by hand.

How to fix "Couldn't fetch" on Blogger, step by step

  1. Open the sitemap in your browser. Go to https://yourdomain.com/sitemap.xml. If you see a list of your post URLs in XML, the file is fine.
  2. Check the property. If you use a custom domain, the sitemap must be submitted in the Search Console property for that domain (for example https://www.yourdomain.com/ or a Domain property), not the old blogspot.com address. A mismatch is the most common real cause.
  3. Submit the short path. In the property, type just sitemap.xml in Add a new sitemap, so the address matches the property exactly. Do the same for sitemap-pages.xml.
  4. Check robots.txt. Open /robots.txt. Blogger's default file allows the sitemap and lists it. If you enabled a custom robots.txt, make sure it does not block /sitemap.xml. Our robots.txt guide shows the default Blogger file.
  5. Run a live test. Paste the sitemap URL into the URL Inspection bar and click Test live URL. Google's help page recommends this to confirm the sitemap is accessible; you want the page fetch to be successful.
  6. Check Manual actions. Open Security & Manual actions > Manual actions. Sitemaps are not read while a manual action is unresolved.
  7. Resubmit once, then wait. If everything above checks out, resubmit and give it time. Repeatedly deleting and resubmitting does not speed it up.

When to stop worrying

A sitemap is a hint, not a requirement for indexing. Google also finds pages through links. If the sitemap opens, the property is right and robots.txt allows it, put your time into publishing helpful posts and linking them together. You can request indexing for your most important posts with the URL Inspection tool while you wait. Many new blogs see the status change to Success on its own after some days or weeks.

What an XML sitemap does

An XML sitemap is a file that lists the URLs on your site you want search engines to know about, optionally with the date each one last changed. Google's sitemaps overview explains that a sitemap helps search engines crawl a site more efficiently, and is especially useful for new sites with few external links, large sites and sites whose pages are not well linked internally.

A sitemap is a hint, not a command. Listing a URL does not guarantee it will be crawled or indexed. Search engines still decide based on quality, duplication and their own crawling priorities.

A simple sitemap looks like this:

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

Where Blogger's sitemaps are

Blogger generates two sitemaps for every blog:

SitemapURLWhat it lists
Postshttps://yourblog.com/sitemap.xmlYour published blog posts. On larger blogs this becomes a sitemap index that links to several numbered sitemap files.
Pageshttps://yourblog.com/sitemap-pages.xmlYour static pages, such as About, Contact, Privacy Policy and any tool or resource pages.

Replace yourblog.com with your actual address. If you use a custom domain, use the custom domain version, for example https://www.yourdomain.com/sitemap.xml, not the old blogspot.com address.

Blogger also adds the posts sitemap to your blog's default robots.txt file, which you can check at /robots.txt. Our robots.txt guide explains the default Blogger file line by line.

What Blogger's sitemaps do not include

  • Draft and scheduled posts, until they are published.
  • Label pages and search result pages, which Blogger's default robots.txt keeps out of crawling.
  • Pages in the second file, if you only submit the first one. This is the most common gap.

Step by step: submitting to Google Search Console

  1. Verify your site in Google Search Console if you have not already. A Domain property covers every version of your domain; a URL-prefix property covers one exact address.
  2. Open Sitemaps in the left menu.
  3. Under Add a new sitemap, type sitemap.xml and click Submit.
  4. Repeat with sitemap-pages.xml.
  5. Check the status column after a while. "Success" with a count of discovered URLs means Google read the file.

You only need to submit once. Blogger updates the files automatically when you publish, and Google re-reads submitted sitemaps periodically.

Step by step: submitting to Bing

  1. Sign in to Bing Webmaster Tools.
  2. If your site is already verified in Google Search Console, use the import option to add it and its sitemaps in a few clicks.
  3. Otherwise, add the site, verify it, then open Sitemaps and submit the full URLs of both sitemap files.

Bing's results also power several other search engines, so this one step widens your reach.

Other Blogger sitemap problems

Pages are missing

Static pages appear only in sitemap-pages.xml. Submit both files.

"Discovered, currently not indexed" or "Crawled, currently not indexed"

These are not sitemap errors. They mean Google knows about the URL but has not indexed it, often because it is new, or because Google did not consider it valuable enough yet. Improve the content, add internal links from related posts and give it time. You can request indexing for important pages with the URL Inspection tool.

Old blogspot.com URLs

If you moved to a custom domain, Blogger redirects the old address. Submit the sitemaps under the custom domain property.

Thin label or archive pages

These are not in Blogger's sitemap, which is a good thing. You do not need to add them.

Do you need a custom sitemap?

For a normal Blogger blog, no. The automatic sitemaps are correct and stay up to date. A hand-made sitemap is useful when:

  • You run a site on a platform that does not generate one.
  • You want to submit a specific list of URLs, such as a set of new pages, for a one-off check.
  • You are building a static site by hand.

In those cases, paste your URLs into the XML sitemap generator, add optional lastmod dates and download a valid file. Upload it to the root of your site and submit it as above.

Rules for a valid sitemap

  • List only canonical, indexable URLs that return a normal 200 response. Leave out redirects, error pages and noindex pages.
  • Use full absolute URLs.
  • One sitemap can hold up to 50,000 URLs or 50 MB uncompressed. Larger sites split into several files listed in a sitemap index. See Google's guide to building and submitting a sitemap.
  • Google ignores the priority and changefreq fields. It uses lastmod when the dates are consistently accurate, so only set lastmod to the date content genuinely changed.

Reading the Sitemaps report

Once Google has processed your sitemaps, the Sitemaps report in Search Console shows each submitted file, when Google last read it, its status and how many URLs it discovered. Click a sitemap to open a page indexing view filtered to just its URLs. This is useful for answering a specific question: of the posts in my sitemap, how many are indexed, and why are the others not?

  • A discovered count close to your number of published posts means the sitemap is complete.
  • A much lower count may mean you submitted an old address or the wrong property.
  • The indexing view lists reasons for any excluded URLs, such as duplicates, redirects or pages that are not yet indexed, so you can focus on the ones that matter.

FAQ

Does "Couldn't fetch" stop my posts from being indexed?

No. Google can still discover and index posts through links and other signals. The sitemap helps discovery, but it is not required.

How long after submitting will my posts be indexed?

There is no fixed time. It can be days for some pages and longer for others. A sitemap helps discovery; content quality and internal links influence whether and when pages are indexed.

Should I resubmit my sitemap every time I publish?

No. Blogger updates it automatically, and search engines re-read it.

Can I use the old atom.xml feed as a sitemap?

Search engines accept RSS and Atom feeds as sitemaps, and older tutorials recommend Blogger's feed URL. Blogger's dedicated sitemap.xml is simpler and covers all your posts, so use that.

Conclusion

For Blogger users, sitemaps are mostly about knowing where they are and submitting both: sitemap.xml for posts and sitemap-pages.xml for pages, in Google Search Console and Bing Webmaster Tools. After that, focus on what sitemaps cannot do for you: publishing helpful posts and linking them together well. If your blog also needs a custom robots.txt, build it with the robots.txt generator, which includes a Blogger preset.

Want keyword ideas for your own topic? Use the free keyword research tool → or browse all free SEO tools.

Comments