A Blogger XML sitemap is a machine-readable file that lists every post and page on your Blogger blog so search engines can find, crawl, and index them. The best part: Blogger creates it for you automatically. You do not need a plugin, a generator, or a single line of code.
In this guide, you will learn where to find your Blogger XML sitemap, how to submit it to Google Search Console and Bing Webmaster Tools, and how to fix the most common errors. If you want the general background first, read our guide to what an XML sitemap is and why it matters.
In this guide:
- What Is a Blogger XML Sitemap?
- Does Blogger Automatically Generate an XML Sitemap?
- How to Find Your Blogger XML Sitemap
- How to Submit Your Blogger Sitemap to Google Search Console
- How to Submit Your Blogger Sitemap to Bing Webmaster Tools
- How to Check That Your Sitemap Is Working
- Common Blogger Sitemap Errors and How to Fix Them
- Custom Robots.txt and Sitemap Settings in Blogger
- Blogger XML Sitemap Best Practices
- Frequently Asked Questions
What Is a Blogger XML Sitemap?
An XML sitemap is a file written in XML (Extensible Markup Language) that gives search engines a complete list of the URLs on a website. Think of it as a map of your blog: it tells Google and Bing which posts and pages exist, so they do not have to discover them only by following links.
Each entry in a Blogger XML sitemap includes the URL of a post or page and the date it was last modified (lastmod). Google uses the last-modified date to decide when to re-crawl a page. Google ignores the priority and changefreq values, so do not worry about them — that is confirmed in Google’s own sitemap documentation.
A sitemap does not guarantee that a page will be indexed or ranked. It is a hint, not a command. Google still decides which pages to index based on quality, uniqueness, and usefulness. But without a sitemap, new and updated posts — especially on a young blog with few backlinks — can take much longer to be discovered.
Does Blogger Automatically Generate an XML Sitemap?
Yes. Every Blogger blog gets an XML sitemap automatically, whether it uses a free blogspot.com address or a custom domain. There is no setting to switch on and nothing to install. Blogger builds the file from your published posts and pages and updates it whenever you publish, edit, or delete content.
Here are the Blogger sitemap URLs you need to know:
- Posts sitemap:
https://yourblog.blogspot.com/sitemap.xml— this is the main sitemap and the one you submit to search engines. - Pages sitemap:
https://yourblog.blogspot.com/sitemap-pages.xml— this lists your static pages (About, Contact, and so on). - Custom domain: replace the blogspot address with your domain, for example
https://www.yourdomain.com/sitemap.xml.
If your blog has more than 500 posts, Blogger splits the posts sitemap into pages of 500: sitemap.xml?page=1, sitemap.xml?page=2, and so on. You still only submit the main sitemap.xml — it works as an index that points search engines to each page.
Important: there is no sitemap-posts.xml file on Blogger. If you see that address in an old guide, ignore it. The two real addresses are sitemap.xml and sitemap-pages.xml.
How to Find Your Blogger XML Sitemap
Finding your Blogger XML sitemap takes less than a minute:
- Open your blog in a browser and go to your home page, for example
https://yourblog.blogspot.com. - Add
/sitemap.xmlto the end of the address so it readshttps://yourblog.blogspot.com/sitemap.xml, then press Enter. - Check what you see. Your browser should display an XML document listing your post URLs with their last-modified dates. If you see the list, your sitemap exists and is public.
- Check your static pages too by opening
https://yourblog.blogspot.com/sitemap-pages.xml. - Check your robots.txt file at
https://yourblog.blogspot.com/robots.txt. It should contain a line such asSitemap: https://yourblog.blogspot.com/sitemap.xml, which points crawlers to your sitemap.
If the sitemap address shows an error page instead of XML, first check the spelling of the address and make sure you are using the current domain of the blog (the blogspot address or your custom domain, not both). If the blog is set to private, the sitemap will not be reachable — see the errors section below.
How to Submit Your Blogger Sitemap to Google Search Console
Submitting your Blogger XML sitemap to Google Search Console is how you tell Google the sitemap exists. Before you start, your blog must be verified as a property in Search Console. If you have not done that yet, add your blog as a URL-prefix property and verify it with the HTML tag method: copy the meta tag Search Console gives you, then in Blogger go to Theme → Edit HTML and paste it directly after the <head> tag.
Once your blog is verified, follow these steps:
- Open Google Search Console and select your blog’s property.
- In the left menu, go to Indexing → Sitemaps.
- Under “Add a new sitemap”, type
sitemap.xml— just that part, not the full address. Search Console already knows your domain. - Click Submit.
- Check the status. The sitemap first shows as “Pending” while Google fetches it, then changes to “Success” once it has been read. The table also shows how many URLs were discovered.
- Optional: submit the pages sitemap too by repeating the steps with
sitemap-pages.xml.
What happens next? Google will crawl the URLs in your sitemap over the following days. Submission does not guarantee indexing: Google treats a sitemap as a hint and still chooses which pages to index. You can follow progress in the Indexing → Pages report, which shows how many of your pages are indexed and why others are not.
For an important new post, you do not have to wait for the sitemap crawl. Paste the post’s URL into the URL Inspection tool at the top of Search Console and click Request indexing.
How to Submit Your Blogger Sitemap to Bing Webmaster Tools
Google is not the only search engine worth submitting to. Bing also powers Yahoo search results, so a few minutes here covers more than one search engine.
- Open Bing Webmaster Tools and sign in with a Microsoft, Google, or Facebook account.
- Add your blog — or, faster, use the “Import from Google Search Console” option, which copies your verified sites over in one click.
- In the left menu, click Sitemaps.
- Click “Submit sitemap” and enter the full sitemap address, for example
https://yourblog.blogspot.com/sitemap.xml. - Click Submit and check that the sitemap appears in the list with a “Success” status.
As with Google, submit the pages sitemap (sitemap-pages.xml) as well if you want your static pages covered.
How to Check That Your Sitemap Is Working
After submitting, check these three things:
- Sitemaps report status: In Google Search Console, go to Indexing → Sitemaps. A healthy sitemap shows the status “Success”, a recent “Last read” date, and a “Discovered URLs” count that roughly matches your number of published posts.
- Pages report: In Indexing → Pages, you can see how many of your submitted URLs are actually indexed and read the reasons for the ones that are not.
- The sitemap itself: Open
yourblog.blogspot.com/sitemap.xmlin your browser. You should see your latest posts at the top of the list. If a post you published recently is missing, check that it is published (not a draft) and not blocked by a noindex setting.
Check back monthly. A sitemap that worked when you submitted it can break later — most often after a custom domain change or a change to your robots.txt settings.
Common Blogger Sitemap Errors and How to Fix Them
“Couldn’t fetch” in Google Search Console
This is the most common Blogger sitemap error. It means Google tried to read your sitemap and failed. Check that you submitted the right address (including the correct domain — blogspot or custom), that the blog is public, and that your robots.txt does not block the sitemap. Then wait a few hours and resubmit. Temporary fetch failures often clear on their own.
Sitemap shows zero URLs or “Sitemap is empty”
First, open the sitemap address in your browser. If it lists your posts, Google may simply not have finished processing it yet — give it a day or two. If the browser also shows an empty file, your blog may have no published posts yet, or the posts may be set to draft.
404 Not Found
A 404 means the address is wrong. Double-check the spelling — it is sitemap.xml, not sitemap.xml.html or sitemap-posts.xml — and make sure you are using the blog’s current domain.
Your posts are not indexed after submission
A sitemap helps Google discover pages, but it does not force indexing. Check the Pages report in Search Console for the reason (for example “Discovered — currently not indexed” or “Crawled — currently not indexed”). Common causes are thin or duplicate content, pages blocked by noindex, or a very new blog that Google has not crawled deeply yet. Publishing useful content, adding internal links between posts, and requesting indexing for key posts through URL Inspection all help.
Your Blogger XML sitemap stopped working after a custom domain move
When you connect a custom domain, your blog’s address changes, so the old blogspot sitemap address no longer applies. Add the new domain as a property in Search Console and Bing Webmaster Tools, verify it, and submit the sitemap under the new domain: https://www.yourdomain.com/sitemap.xml.
Custom Robots.txt and Sitemap Settings in Blogger
Blogger’s default settings are enough for most blogs, but you can take more control under Settings → Crawlers and indexing in your Blogger dashboard. (Older guides call this section “Search preferences” — that name is no longer used.)
- Custom robots.txt: Turn this on only if you need rules beyond the default. If you do, include a line pointing to your sitemap:
Sitemap: https://yourblog.blogspot.com/sitemap.xml. Never add a rule that blocks/sitemap.xmlitself — that would stop search engines from reading it. - Custom robots header tags: These let you add a
noindextag to archive or search pages, for example. Use them carefully: a page with a noindex tag will not be indexed even if it appears in your sitemap. - Third-party sitemap generators: Tools such as the Blogger sitemap generator from Slickplan can build a sitemap for you, but for a standard Blogger blog they are unnecessary — Blogger already generates one. Consider a generator only for special cases, such as an image sitemap.
Blogger XML Sitemap Best Practices
- Do not resubmit after every post. Your Blogger XML sitemap updates automatically when you publish, so Google will pick up new posts on its next crawl.
- Resubmit only when something changes — after a custom domain move, after fixing a sitemap error, or if the Sitemaps report shows a problem.
- Keep the blog public. Under Settings → Privacy, “Visible to search engines” must be on, or your sitemap cannot be read.
- Link between your posts. Internal links help Google discover and value your content; a sitemap alone is not a substitute for good internal linking.
- Use URL Inspection for important posts instead of waiting for the next sitemap crawl.
- Check the Sitemaps report monthly so a broken sitemap does not go unnoticed.
Key Takeaways
- Blogger automatically generates an XML sitemap — no plugin or manual work is needed.
- The main sitemap is at
yourblog.blogspot.com/sitemap.xml; static pages live atsitemap-pages.xml. - Blogs with more than 500 posts get paginated sitemaps (
sitemap.xml?page=1,?page=2), but you still only submit the main sitemap. - Submit
sitemap.xmlin Google Search Console under Indexing → Sitemaps, and in Bing Webmaster Tools under Sitemaps. - A sitemap helps search engines discover your content; it does not guarantee indexing or rankings.
- Most errors come from a wrong URL, a private blog, a robots.txt block, or a custom domain change — all are quick to fix.
- Check your sitemap status regularly and resubmit only when something has changed.
Conclusion
Generating a Blogger XML sitemap is not a task you have to do — Blogger has already done it for you. Your job is the easy part: find the sitemap at yourblog.blogspot.com/sitemap.xml, submit it to Google Search Console and Bing Webmaster Tools, and check the status from time to time.
Do that today, and your new posts will have the best possible chance of being found and indexed quickly. Then keep publishing helpful content — the sitemap opens the door, but the content is what earns the ranking.
Frequently Asked Questions
Does Blogger automatically create an XML sitemap?
Yes. Every Blogger blog automatically has an XML sitemap at yourblog.blogspot.com/sitemap.xml (or yourdomain.com/sitemap.xml on a custom domain). You do not need to install anything or write any code — just verify the address works and submit it to Google Search Console.
What is the Blogger sitemap URL?
Your main Blogger sitemap is at yourblog.blogspot.com/sitemap.xml. Static pages have their own sitemap at yourblog.blogspot.com/sitemap-pages.xml. If your blog has more than 500 posts, the posts sitemap is split into pages such as sitemap.xml?page=1 and sitemap.xml?page=2.
Do I need to submit my Blogger sitemap to Google?
Strictly speaking, no — Google can find your sitemap on its own, and Blogger notifies Google when you publish. But submitting it in Search Console is free, takes a minute, and gives you status reports and error alerts you would not otherwise see. It is the recommended step for every Blogger blog.
How long does it take for my pages to appear in Google after I submit a sitemap?
There is no fixed timetable. Google treats a sitemap as a hint and crawls and indexes pages on its own schedule, which depends on the blog’s age, authority, and content quality. New blogs usually take longer than established ones. If a specific post matters, use the URL Inspection tool in Search Console and click “Request indexing” rather than waiting.
Why does Search Console say “Couldn’t fetch” for my Blogger sitemap?
The most common causes are a wrong sitemap address, submitting the sitemap under the wrong domain (for example the blogspot address after moving to a custom domain), a blog set to private, or a robots.txt rule blocking the sitemap. Check each of these, then wait a few hours and resubmit.
Can I customize which pages appear in my Blogger sitemap?
Not directly. Blogger’s default sitemap includes all public posts and pages, and you cannot remove individual URLs from it. To keep a page out of search results, set it to draft or add a noindex tag using the custom robots header tags under Settings → Crawlers and indexing.







