All posts
Blogger Sitemap: Where to Find It, How to Submit It, and What to Ignore

Blogger Sitemap: Where to Find It, How to Submit It, and What to Ignore

Your Blogger blog already has a sitemap. Here's the URL to submit, why you can skip generators and atom.xml, and which Search Console warnings are normal.

November 2, 2026 · 8 min read

Your Blogger blog already has a sitemap, and you don't need a generator to make one. It lives at /sitemap.xml on your blog's own address:

  • Posts: https://yourblog.blogspot.com/sitemap.xml
  • Static pages (About, Contact): https://yourblog.blogspot.com/sitemap-pages.xml
  • Custom domain: the same two paths on your domain, such as https://www.yourdomain.com/sitemap.xml

Google says as much in its sitemap documentation: "If you're using a CMS such as WordPress, Wix, or Blogger, it's likely that your CMS has already made a sitemap available to search engines."

Most of the confusion around Blogger sitemaps comes from older tutorials written around feeds and generator tools. To see what Blogger actually serves today, we checked four Google-run blogs hosted on the platform on November 2, 2026. The results are below.

What Blogger Actually Serves

Here is what /sitemap.xml returned on each blog:

| Blog | What /sitemap.xml returned | URLs | | --- | --- | --- | | testing.googleblog.com | A single URL list | 405 | | blog.chromium.org | A single URL list | 646 | | security.googleblog.com | A single URL list | 654 | | android-developers.googleblog.com | An index pointing to ?page=1, ?page=2, ?page=3 | 800, 800, and 475 |

That table answers the two questions people ask most. First, a large Blogger blog doesn't need any manual splitting. The biggest blog in our check had its sitemap divided into pages automatically, and /sitemap.xml was still the one address that led to all of them. Second, you only ever need to submit that one posts URL, whatever the size of your blog.

Two details look wrong but aren't:

  • /sitemap-pages.xml can be empty. On the blogs we checked it returned a valid file with no URLs inside. That's what you should expect if your blog has no static pages, so it isn't an error.
  • The content type says Atom. These sitemaps were served as application/atom+xml, even though the file itself is a standard urlset sitemap. If a header checker flags this, the format of the file is what matters, and the file is fine.

How to Submit Your Blogger Sitemap to Google

You need a Search Console property for the blog first. A blogspot.com address can't use a Domain property, because that requires editing DNS records and you don't control DNS for blogspot.com. Use a URL prefix property with the exact address readers see. If you've set up a custom domain, you control its DNS, so either property type works. Then:

  1. Open https://yourblog.blogspot.com/sitemap.xml in a private window and confirm you see a list of URLs rather than an error.
  2. In Search Console, go to Sitemaps and enter sitemap.xml, then click Submit.
  3. If your blog has static pages, submit sitemap-pages.xml the same way.
  4. Come back in a day or two and check that the status reads Success.

Match the property to the address. The Sitemaps report only shows sitemaps in the current property, so a blogspot URL submitted under a custom-domain property (or the reverse) points at the wrong place. If you moved to a custom domain later, use the new address and read our website migration SEO checklist for what else needs to move with it.

Do You Need a Sitemap Generator or atom.xml?

No to both, for most blogs. This is the advice you'll run into most often, so it's worth explaining what it was for.

Many tutorials tell you to submit something like this:

atom.xml?redirect=false&start-index=1&max-results=500

Feeds are a valid format. Google accepts RSS 2.0 and Atom 1.0 feeds as sitemaps. But Google also warns that a feed "only provides information on recent URLs," which is why it's a poor substitute for a full list. The max-results=500 part doesn't guarantee 500 either. When we requested that exact URL on testing.googleblog.com, the feed returned 150 entries, while the same blog's /sitemap.xml listed 405 URLs.

Generator tools solve the same old problem by building batches of feed URLs for you. They aren't harmful, but they give you several addresses to maintain when one already does the job. If you've already submitted a batch of feed URLs and they show Success, they won't hurt anything. Adding /sitemap.xml and removing the extras simply leaves you with less to check.

The size limits are also not a concern for a typical blog. Google's limit is "50MB (uncompressed) or 50,000 URLs" per sitemap, far beyond the 800-URL pages we saw.

Should You Change robots.txt on Blogger?

Probably not. Blogger generates a robots.txt for you. Here is the one served by testing.googleblog.com:

User-agent: Mediapartners-Google
Disallow:

User-agent: *
Disallow: /search
Disallow: /share-widget
Allow: /

Sitemap: https://testing.googleblog.com/sitemap.xml

That already tells crawlers where the sitemap is, so pasting a custom version only to add a Sitemap: line gains you nothing. Blogger does offer a custom robots.txt option under Settings → Crawlers and indexing, and this is where sitemap problems tend to get created: a copied snippet replaces the working default, and a stray rule blocks something you wanted crawled. If you've turned it on and aren't sure why, compare your file with the default above, or check individual URLs using our guide to testing a robots.txt file.

The setting that matters more sits under Settings → Privacy: per Blogger's help page, Visible to search engines needs to be on. To hide individual posts, use the No index toggle in the post editor rather than a site-wide rule. The sitewide custom robots header tags are easy to set too broadly.

Why Search Console Says "Couldn't Fetch" on Blogger

Blogger hosts the file for you, so the usual suspects on self-hosted sites (caching plugins, firewalls, a bad server config) mostly don't apply. Work through these instead:

  1. The URL is wrong. Open the exact address you submitted. A typo or an old blogspot address on a blog that has moved is the simplest explanation.
  2. The property doesn't match. See the property note above, and check whether your blog redirects to a different version of the address.
  3. A custom robots.txt blocks it. Paste the sitemap URL into URL Inspection and run a Live test to see what Google gets.
  4. The blog isn't public. A blog restricted to invited readers, or one with Visible to search engines turned off, is the first thing to rule out if you changed privacy settings.

If the URL loads and the live test passes, you may just be looking at timing. Google says it retries a failed fetch a few more times, so give a brand-new submission a day or two before changing anything. The full diagnosis, including how to read the live test panel, is in sitemap could not be read. Some Blogger tutorials blame timeouts in the default sitemap or a "display bug," but Google's documentation doesn't confirm either, so treat them as guesses and go by the live test.

Search Console Warnings That Are Normal on Blogger

Blogger's URL structure produces a few statuses in the Page indexing report that look like problems and usually aren't.

Blocked by robots.txt on /search/label/... URLs. The default robots.txt disallows /search, which covers label pages and on-site search results. Your posts aren't affected. Those label pages also didn't appear in the /sitemap.xml we checked, so there's no conflict for you to fix.

Alternate page with proper canonical tag on ?m=1 URLs. Blogger's mobile address adds ?m=1 to a post's URL. On the post we tested, that version carried a canonical tag pointing at the clean URL, which is the correct setup. Our guide to alternate page with proper canonical tag explains why this status usually needs no action.

Crawled or Discovered, currently not indexed. This one is a real signal, but it has nothing to do with the sitemap. A sitemap gets URLs in front of Google, and Google is explicit that listing a URL doesn't guarantee it will be crawled or indexed. If the sitemap reads Success and posts are still missing, go to Google not indexing all your sitemap URLs. For a post you just published, start with why your new blog post isn't showing up.

What to Check After Submitting

A Success status tells you Google read the file, not that readers can find your posts. What goes in a sitemap matters less on Blogger than on other platforms, because you can't edit it, and most of the sitemap best practices people debate are handled for you. If you've also run a blog on another platform, our WordPress sitemap guide shows how differently that setup behaves.

The more useful check comes a couple of weeks later: are new posts collecting impressions? Traffic Monitor works with any site connected to Search Console and shows clicks and impressions per post, updated daily, so a post that never gets picked up stands out. You can connect your blog with read-only access. If you're trying to see where those posts rank, we also compared the options in our Blogger rank checker guide.

Blogger Sitemap Checklist

  • Open /sitemap.xml on your blog's exact address and confirm it lists your posts.
  • Submit sitemap.xml, plus sitemap-pages.xml if you have static pages.
  • Skip generators and atom.xml batches unless you have a specific reason to use them.
  • Leave custom robots.txt off unless you know what you need it for.
  • Confirm Visible to search engines is on under Settings → Privacy.
  • Ignore /search/label/ blocks and ?m=1 alternate pages in the Page indexing report.

Track your blog rankings automatically

Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.

Start free →