Blogger will now let you use your own domain names with New Blogger blogs (as Kirk spotted, and since announced in Blogger Buzz). This isn't available for old Blogger blogs.
For example, in my case, after my blog is switched over to New Blogger I could set things up to use http://www.consumingexperience.com instead of http://consumingexperience.blogspot.com for this blog.
They call this feature "custom domains" or "custom domain names". UPDATE: if you can, I'd suggest you switch to a custom domain ASAP - see this post on why, plus details of my experiences with drops in search engine rankings after I moved to a custom domain on Blogger.
Custom domains versus FTP publishing
Using custom domain names is not the same thing as FTP publishing, which has been available on Blogger for some time. The FTP option lets you use Blogger as your blogging tool - but, instead of publishing to Blogger's Blogspot.com, you keep your blog webpages on a server owned by an external third party host, and you can use your own domain name with your blog (an example of a blog using FTP publishing via Blogger would be Nancy White's Full Circle blog).So what's the difference? Well, with custom domain names you can, as with FTP, use your own domain name for your blog (e.g. in my case consumingexperience.com) - but Google/Blogger will continue to host your blog webpages on their servers and you can continue to publish to your blog in the usual way rather than using FTP.
In other words, with custom domains on New Blogger you can:
- hosting - still keep your blog webpages hosted for free on Blogger's servers
- blogging software - still use familiar ol' Blogger as a free blogging system to publish and edit your blog, as before (including fast publishing, access control etc) - and now, in addition
- own domain name - use your own domain name/URL for your blog, instead of http://yourblogname.blogspot.com
- images - but note that images of over 400px won't then display on your blog (although Blogger thumbnails and other thumbnails of less than 400px will still display in posts, and could link to the full size image) (see the Blogger help page on this)
- (UPDATED) use Layouts and widgets - see this - but you can't with FTP.
Blogger have provided full setup instructions for a custom domain name on your blog, including how to change your Blogger settings, plus links to setup instructions for common domain registrars. (You would normally need to change settings with both services.)
Will changing your blog's domain name affect its Google PageRank i.e. your ranking in Google searches or with other search engines?
One good thing is that Blogger say "Your original Blog*Spot address will automatically forward to your new domain. That way, any existing links or bookmarks to your site will still work", and "Your old Blog*Spot address will forward to your new custom domain, so the switch will be seamless for your readers." I assume this will work for links to individual post pages as well as the main blog homepage.EDIT FOR UPDATE: at first I was concerned about the impact of a change to a custom domain on a blog's Google PageRank. With a normal type of domain name change, Google say a 301 redirect should help with search engine crawlers, and also, to help preserve your blog's ranking, that you should find out who links to your blog and ask them to change their links to point to the new URL too. I have a feeling the latter may not be very practicable and others may not bother to change their links if they're automatically getting redirected anyway.
I'm not clear how it will work, and I am the first to say I really don't know enough about all this. Kirk says "But instead of just a redirect, it appears Blogger will host the dns for the domain you select, and route it to your blogspot blog". I assume that's even better than a 301 permanent redirect from your previous Blogspot.com URL, but it would be great if Pete, Lexi or someone else from the Blogger team would confirm the position and the impact on PageRank of changing to a custom domain from a Blogspot blog.
Kirk has kindly clarified what he meant. What he was trying to get across is that your old Blogspot address would be given a 301 redirect to your new domain, while your new domain's (or subdomain's) DNS would be hosted at Google / Blogger. Most likely your new domain wouldn't SHOW any Pagerank for a bit. But that's misleading, as what is public Pagerank and what is the actual internal Google PR isn't the same. For an example, see
So basically what it should come down to is, your old Blogspot URL will be 301 redirected to your new domain. Your new domain probably won't SHOW any pagerank for a bit, but internally at Google it will start to soak in your Blogspot URL's Pagerank (which is all that really matters)... and even then, most of your content will still be indexed at your old Blogspot URL, with it's old Pagerank. All that should even out, as the indexed content is gradually spidered in at your new domain etc., although there might be some lag in what you see for the new domain's Pagerank through toolbars etc... as they only get info when Google releases their public rankings.
This is confirmed by another Googler, Adam Lasnik: "Proper use of 301s (old-page to equivalent-new-page, not all-old-pages to new-root page) generally results in an appropriate flow of PageRank and related stuff to the new domain". Kirk has also verified from checking the response headers for a Blogspot blog that switched to a custom domain that Blogger do do an "old page to new page" 301. You request a permalink on a Blogspot blog, and get the 301 to the same page on the new domain. As a page to page 301 redirect seems to be the only way to preserve links from old Blogspot permalink to new domain permalink it appears that Blogger is doing it correctly, and (to quote Kirk) that Pagerank love should follow.
So as Kirk says you shouldn't expect any real problems from using a new custom domain, other than the panic of not SEEING the Pagerank immediately at your new domain. Blogger has it setup correctly that things should transfer over fine. There always could be a temporary blip whilst things reshuffle, but anything major seems unlikely.
Some might say that your own domain name is a lot more professional and, longer term, the sooner you change your domain name the more time you will have to let it absorb the old blog's PageRank, under the new domain name. Plus, the PageRank you build up by continuing to blog under the new name will of course be associated with the new domain name, so it won't be affected if in future you decide to change hosts and use servers other than Google's for your blog.
Myself, I'll probably bite the bullet and change over as soon as I can (it really doesn't cost much these days, see below). But that won't be for a while as I have a large blog.
UPDATE: I moved to a custom domain, and it was scary. See this post on the impact of the change to a custom domain on my blog's traffic and PageRank.
Getting your own custom domain name
You can of course only use the custom domains feature if you have your own domain name. How do you buy one for your blog?Blogger have provided a list of domain registrars you could try, though you don't have to buy your domain through them - you can use any registrar you like, including a local registrar if you don't live in the USA.
GoDaddy are listed first. This is not surprising as they're well known, cheap, popular, and - probably most significantly - as Google had announced in December, they recently teamed up with Google to enable users of Google Apps for Your Domain to buy domains through Google for US $10 a year on signing up for Google Apps for Your Domain.
Google Apps for Your Domain?
Google Apps for Your Domain was launched in beta in August 2006 and enables organisations who have their own domains (or, now, who buy a domain name through Google) to use Gmail web email, Google Calendar shared calendaring, Google Talk instant messaging and the Google Page Creator webpage creation tool for that domain, in an integrated way, for all the organisation's members or staff. For free (during the beta period), with everything hosted on Google's servers, automatically configured to work with those services, and managed via web browsers - no extra software or hardware required.There seem to be some good features for domains bought via Google, e.g. private domain registration (so your details aren't publicly associated with that domain on WHOIS).
So I wonder if it's worth considering whether to buy the domain name direct through GoDaddy, or via Google as part of getting Google Apps for Your Domain?
Because as far as I can see, there's nothing to stop a blogger getting Google Apps for Your Domain, including buying a domain name, thereby getting the advantages of Google Apps (so that they could e.g. manage email sent to their own domain, like ownname@owndomainname.com, via the familiar Gmail Web interface) - but then setting things up to use Blogger rather than Page Creator for that custom domain, given that Google say you will have full DNS/domain management control for any domain bought through them.
(I'm not fond of Page Creator, the way it currently is - insufficient "power user" control, truncates long filenames if you upload your own files instead of using their built in webpage creator, won't let you upload usable favicon .ico files even though they're in my view essential for any website, etc etc.)
Now I haven't tried doing that yet myself, but it looks like a possibility to me. I'd be interested to know if anyone's done it successfully. I certainly plan to have a go once I've more time, probably next weekend now.
GoDaddy direct, or Google Apps for Your Domain for your domain name?
Leaving aside the mechanics of how to get Blogger to work with a domain name bought via Google Apps (which as I said I'm not sure about), there seem to be pros and cons to both options: namely, buying your domain name direct through GoDaddy, or through Google Apps.Cost. One factor is of course cost. For a single domain name, GoDaddy seems to be cheaper, but if you add the private registration fee then there's little difference, at the moment anyway. However, GoDaddy often have a multiplicity of special offers, e.g. if you buy lots of domain names in bulk, there can be a discount. (You might want to buy up variations of your blog names as I have, e.g. in my case consumingexperience.com, aconsumingexperience.com, theconsumingexperience.com). The price can also vary depending on whether you're buying a year's registration, or more than 5 years' worth, etc. And you can get private domain registration if you buy direct from GoDaddy too.
A minus from a consumer/usability viewpoint is that GoDaddy's offers are hard to figure out, with some inconsistencies or contradictions on the site. In particular it's not at all clear whether and when you can combine several different types of offers on their website. I spent a happy few hours (not!) hitting the Back button, opening lots of browser windows, trying out different combos.
The good news, although it wasn't at all obvious at first, was that - when I tried it, anyway - when I got to the final checkout page, it did finally list my domains and whether certain options (e.g. privacy) were included, or if not their cost. I wish they'd provide that info originally, e.g. it seemed I'd have to pay for email as an extra when I tried via the "bulk registration" page, but on another page it said it was free as part of the package. It's also not clear whether you have to manually pick certain options during the purchase process to get them for free under a special offer, even though they seem to be labelled as chargeable.
The moral is that you need to figure out exactly what package you want, then try different routes in to your desired package, from different parts of their website, and see if they make a difference to the final pricing and features.
Tip: for non-US residents, you can choose to see the pricing in currencies other than US dollars, if you prefer. It's up to you whether you want the conversion to your local currency to be done by GoDaddy or your credit company, really.
Simplicity. As mentioned, it's not clear what you do or don't get as part of your domain name purchase, with GoDaddy (email, etc), and what has to be selected and paid for as an extra. Though you could probably figure it out from the final page, or after the event! At least with Google Apps you know what you're getting, much more clearly: Gmail-type email, etc, for free. Which may be worth the (probably) slightly greater cost, if you're only buying a single domain.
You pays your money and you takes your choice...
Tags:
