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


so what should be done? have blog at or

Popular posts from this blog

Adding A Link To Your Blog Post

Occasionally, you see a very odd, cryptic complaint I just added a link in my blog, but the link vanished! No, it wasn't your imagination.

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Add A Custom Redirect, If You Change A Post URL

When you rename a blog, the most that you can do, to keep the old URL useful, is to setup a stub post , with a clickable link to the new URL. Yo! The blog is now at!! Blogger forbids gateway blogs, and similar blog to blog redirections . When you rename a post, you can setup a custom redirect - and automatically redirect your readers to the post, under its new URL. You should take advantage of this option, if you change a post URL.