Skip to main content

Aliasing Of Non Root Custom Domain URLs Ended

Since the beginning of the Google Custom Domain option, the ability to publish a blog to "", and optionally have Blogger associate "" with "", has been an assumed feature in custom domain publishing.

Similarly, the ability to publish to "", and optionally have "" as an association, was an assumed, if slightly less popular option.

Long ago, I discovered an oddity in the association, previously accepted as a feature.

Aliases for non root domain URLs were inconsistent, when provided.

If you were to publish your blog to "", you would get the option to "Redirect to". However, if you were to publish your blog to "", you would get the option to "Redirect to".

In cases where there was another Blogger blog already published to "", and "Redirect to" had been selected, this would produce a disruption in the domain content.

I don't think that this confusion is coincidental to the addition of two level Top Level Domains, to the custom domain publishing support structure.

Indiscriminate alias use could lead to database corruption.

Another disaster was observed when people intentionally publishing to "" - or to "" - were presented with the Redirect option. Naively deciding "Why not?", and selecting the redirect (even with no DNS address having been setup to for the aliased host), the blog owner would later see the infamous "Another blog ...." (now "Key already exists ...").

Blogger finally stopped providing aliasing of all non root domain URLs.

In 2010, when considering this potential for disaster, and oddity - and observing that the need to publish to "" is relatively unpopular (at least 99% of all custom domains involve publishing to "") - Blogger decided to discontinue support for aliasing non root custom domain URLs.

This means that both "" and "" are now completely separate URLs - with no aliasing possible.

You can, when publishing, redirect the domain root to any non root URL.

Right now, if you were to publish "" to "", then publish "" to "", you may find the option to "Redirect to" - in spite of having previously selected "Redirect to".

If this is the case for your domain, then you may have to revisit the Publishing settings for "", and again select "Redirect to".

I suggest only aliasing the domain root to the "www" host, for consistency.

My recommendation - if you want a stable domain - is that you publish to the "www" host - that you only alias the "www" host and domain root - and that you never combine a Blogger blog and a website, using the "www" host and domain root, together.

Schizophrenia And Non Root Custom Domain URLs
Aliasing Of Non Root Custom Domain URLs Ended


Deepika said…
so what should be done? have blog at or

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: