Skip to main content

Custom Domain Publishing, And Naked Domains

We see several problems weekly, which relate to custom domain redirects.
My domain root isn't working!
How do I get my naked domain to redirect to my blog??
Generally, we'll investigate, discover an apparent Google server problem in the original publishing sequence, and recommend recycling of the domain.

Sometimes, the solution is simpler - but we may not get to the simple solution, immediately.

In some cases, the BlogSpot and "www" aliases are working just fine - the only problem is, as the blog owner implied, with the domain root (aka "naked domain") redirect setting.

Note that successful use of the redirect requires the correct DNS setup, which should not be described as "optional".

If you are familiar with the principle of Occam's Razor, you'll understand the final solution.
Check the redirect option.

Start with the "Blog Address" setting in Settings - Basic.

Click on "Edit".

And, there it is.

Here, "Redirect to".

For many domains, one would expect "Redirect to".

Blogger lets us choose whether or not we want the domain root to redirect. With this domain, I used "Redirect to" - but one might generally expect "Redirect to".

If we don't choose the redirect, though, we don't get the redirect - and our readers (and the search engines) may suffer.

Perversely, some of our readers, depending upon what browser they are using, may, nevertheless, see the redirect. And right now, you may need to use an alternate option to setup the redirect.

You may also want to consider how the search engines index the domain root and "www" alias.


Dear Chuck,

Can you PLEASE help me with a Custom Domain issue I am having? I have posted several times in the Blogger Forums but NO ONE is responding to my posts!

I recently purchased a Custom Domain through Blogger. During this process, I lost the data (links to external sites) in 18 Blog Roll Widgets on my sidebar. The loss occurred during the migration - the 72 hour transition period completed days ago - and the data is just gone.

The widgets themselves remain on my template - just the data is gone.

I need to know if there is a way to recover this data or if it is lost forever and I just need to rebuild from scratch.

My latest unanswered letter in the Blogger Forum is at this link:

Thank you for any assistance you can provide. I LOVE your blog and have used your posts to help me plan out this migration. It is the one blog I recommend to all of my Blogspot friends!

New Site:

Old Site:

I'm on IE8 in the US
Natasja said…
Thank you so much for helping me out :)
Kati Michelsson said…
Thank you! This was very helpful. I'm so grateful that I got my problem fixed with the help os this.
Aproko Admin said…
Thanks to you sir. Very grateful user here.
Cebu Nomads said…
Thank u so much.. this was thw problem i was facing for 2 days.. i am hosted under 1and1. My previous blog was then followed the directions to changes some Cname by creating subdomain I was excited that i forgotten the check box to redirect to ... ur simple tip really made my life easy... i was seeing error 404.. now it is resolved.. im ready to roll...
Cameron Smith said…
Cheers mate, such a simple way to fix my problems.
You rock!

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: