When Jason pointed out an article by Blog Bloke which claims to be the best way to set up your Blogger custom domain, I popped over to take a look at the differences. Indeed Blog Bloke's solution is a very good method to use: this ensures both your www and non-www url both point to your blog quite easily, whereas my preferred method requires a little more customization to perform the same function. Both methods have their advantages and drawbacks, as I shall explain here.
As Blog Bloke points out, many Bloggers who have set up their custom domain do not redirect visitors to their non-www address (eg: http://myblog.com) to their www address (eg: http://www.myblog.com), instead leaving their "parked" page in place, which can be quite frustrating for visitors who forget to add that www in the address bar, not to mention off-putting!
Both Blog Bloke and I agree that it is useful to have redirection in place for your non-www url, though our solutions are slightly different.
Amanda's Custom Domain Method
I use GoDaddy as my domain provider, and my method for setting up your domain with GoDaddy requires three steps:
- Set up your custom domain by changing the CNAME records and the settings in your Blogger dashboard.
- Activate your free hosting account
- Upload a redirect page, which redirects visitors to your www blog url.
While this may seem like a lot to do in order to ensure all visitors to your URL actually get to your blog, I do have good reason for doing things this way. When you set up a redirect page at your non-www url, you can explain that your blog is located at www.myblog.com to ensure bookmarks are correctly formed. Most importantly, when you activate your free GoDaddy hosting, you can utilize this space to host images, scripts and files on your own domain.
Blog Bloke's Custom Domain Method
Blog Bloke's method ensures you only need to set up your custom domain. He advises that you don't change the CNAME records, and instead utilize the "A" records and domain forwarding to ensure your custom domain name points to your Blog*Spot URL. This is a much simpler and cleaner method, and ensures that your non-www automatically redirects visitors to your www domain.
However, this method means you cannot create an informative redirection page, and makes the use of your hosting space a little more complicated as you would need to set up sub-domains in order to make your hosted files accessible. Nonetheless it is a good method, and from what I have read this does work effectively.
Which method should you use?
This depends entirely on your own preferences, but here is some advice to help you decide for yourself:
- If you want a quick and easy method, go for Blog Bloke's method. For this, you don't need to set up your hosting account or create and upload a redirect page to ensure all visitors get to your blog.
- If you want to provide info about your URL, and make good use of the free hosting space available to you, you may wish to consider my method instead. Fair enough, it does take a little longer to set up, and requires a little more effort, so it may not be the ideal solution for everyone.
Why not let me know which method you prefer to use by leaving your comments below?
Technorati Tags: godaddy | set+up | blogger | custom+domain
6 Comments:
A few months ago after I read your post on this topic, I wrote my own:
http://www.ifitfeelsgooddoit.com/2007/07/how-to-set-up-custom-domain-with.html
At the time, I couldn't find anyone else that listed the exact same solution.
I am not sure which method to use, because I am not very internet-savvy when it comes to setting up a custom domain, redirect page, etc.
Both solutions sound like good ways to do it. I just need to figure out which one would be best for a person who does not know much about this process. I probably will be able to get it together. Your tips are helpful, and they alway work so everything should be fine.
If you use the A records method will that preclude setting MX records for mail delivery?
I currently use Google Apps (standard) to handle my mail, Sites (non-Apps) for my web site, and Blogger for my blog. I'd love to put them all together but individually each of these services out-features anyone who offers all three. I wish Google would allow domain aliases in Apps for Sites (like it does for e-mail), integrate Blogger into Apps (via Sites or separately) and share layouts between Sites and Blogger (if necessary).
I am thoroughly convinced in this said post. I am currently searching for ways in which I could enhance my knowledge in this said topic you have posted here. It does help me a lot knowing that you have shared this information here freely. I love the way the people here interact and shared their opinions too. I would love to track your future posts pertaining to the said topic we are able to read.
Thanks for taking the time to discuss this, I feel strongly about information and love learning more on this. If possible, as you gain expertise, It is extremely helpful for me. would you mind updating your blog with more information
Your post really helped me to understand this. It has great details and yet it is easy to understand.That's what i was looking for. I will definitely share it with others.Good job ..
Post a Comment