Skip to main content

Is A Sitemap Useful, For A Blogger Blog?

Occasionally in Blogger Help Forum: How Do I?, we see evidence of confusion and doubt.
Do I really need a sitemap, for my blog?
This question, when asked, may help us to design our blogs better.

WikiPedia defines a sitemap as
a list of pages of a web site accessible to crawlers or users
Classically, a sitemap is a visual index, to help the people viewing a static website, to easily identify and access a specific article in the website.

A sitemap provides an alternate index, to a non Blogger website.

Most websites are static, with a hierarchically accessed, single structure. A well designed sitemap allows people and crawlers to more efficiently locate specific articles (pages or posts), in a static website.

Most Blogger blogs provide much more than a hierarchical, single, static structure. By default, a Blogger blog links posts dynamically, using several alternate indexes.

  • Archives (posts listed hierarchically, by date).
  • Labels (posts listed hierarchically, by topic).
  • Extended main page (posts listed sequentially, by "Newer Posts" / "Older Posts").

Any blog, which provides one or more of these features, serves as its own sitemap - for viewer access to posts. Static pages are accessed only when necessary - and content published in pages is not intentionally sitemapped.

For crawler access, the options are simpler.

  • Archives (posts listed hierarchically, by date).
  • Extended main page (posts listed sequentially, by "Newer Posts" / "Older Posts").

Label searches, which use a different URL structure from the base blog design, are not used for indexing a Blogger blog.

If you look at the main page of a typical blog, you can follow the "Newer Posts" / "Older Posts" links from page to page, repeatedly - and eventually, see every post in the blog. With a new blog, with few posts, and predominantly "first visit" viewer traffic, the main page makes a passible sitemap. For an older blog, with many posts, and more "repeat" viewer traffic, the main page makes a less efficient sitemap.

For crawlers, which will generally follow a limited number of links within any single blog or website, the main page makes a still less efficient sitemap. Most blogs with any appreciable search engine reputation, however, only need new posts indexed by the crawlers - as older posts are already indexed, and remain in search engine cache.

Google recommends using a sitemap, if at all possible.
Using a sitemap doesn't guarantee that all the items in your sitemap will be crawled and indexed, as Google processes rely on complex algorithms to schedule crawling. However, in most cases, your site will benefit from having a sitemap, and you'll never be penalized for having one.

Blogger provides a good, default gadget which serves as a sitemap, on most blogs - the Archives index. Look in the sidebar of this blog, about halfway down, for the "Contents" gadget.

The Archives index is an HTML based gadget, which produces a set of hierarchical, date structured links, exhaustively enumerating each post in the blog. It's an ideal structure, for search engine bots (crawlers) to follow. If your blog includes this accessory, that's probably sufficient for indexing.

Blogs which contain one or more complementary features can provide search engine access, organically.

  • Well written, regularly published posts.
  • The standard Archives gadget.
  • The standard "Newer Posts" / "Older Posts" links.

Both the Archives, Labels, and "Newer Posts" / "Older Posts" links are subject, on some blogs, to customisation. A blog with Javascript driven Archives, Labels, and / or custom pagination ("Newer Posts" / "Older Posts") gadgets may not provide easy crawler access. This also affects blogs which use dynamic templates. If you tweak your blog extensively, you may want to consider these issues.

There is one special case where a sitemap is always needed. Any time the URL of your blog is changed - whether to a new BlogSpot URL, or to a non BlogSpot custom domain - prompt re indexing, under the new URL, is a necessity to regain search engine reputation. A robust sitemap set, which directly references all posts in the blog, helps the crawlers to re index each post, under the new URL, much faster.

Other than that special case, a blog with standard, well designed, features may not actually need a sitemap. If the blog does need a sitemap, Blogger provides automatically generated sitemaps for both dynamic pages ("posts") and static pages ("pages").


The "L" Spot said…
Thank you for this information. It certainly cleared some confuse I had regarding sitemap in Blogger.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: