Skip to main content

Blogger Magic - Changing Your Custom Domain

The process of changing one custom domain URL to another is similar to the task of changing the BlogSpot URL.

The risk of identity theft is not as great, when you change a custom domain. You will continue to "own" any previously used domain, even when unpublished - but the risk of technical error is just as real.

If you care about blog accessibility, you will plan this process, with some care.

Changing one domain, for another, requires careful planning.

A domain change involves world wide services. Neither you, Blogger Support, or your registrar / DNS host can control this process. Domain setup needs to be carefully verified, over a significant time span.

  1. Verify that the current domain addresses are proper - and correct if needed.
  2. Register the new domain.
  3. Setup the new domain, with proper DNS addresses.
  4. Give the new domain time to stabilise.
  5. Click on the "X", and publish the blog back to BlogSpot.
  6. Change BlogSpot URL, if desired.
  7. Disable HTTPS, if necessary.
  8. Publish the blog to the new domain.
  9. Redirect the domain root to the new published URL.
  10. Verify the blog, published to the new domain, is working.
  11. Re direct the old domain, to the new domain published URL.
  12. Re enable HTTPS, as required.
  13. Publicise the new domain.
  14. Update any owner added internal links.

Register the new domain.

Choose a registrar who can provide the necessary services - such as email, if that's important to you.

A properly chosen registrar won't be free. You are unlikely to get a free domain, that will be reliable.

Setup the new domain, with proper DNS addresses.

Just as important as a reliable registrar is a proper address complement. You need a reliable registrar, for a dependable domain - but even a reliable registrar won't necessarily understand what DNS addresses are needed, for a Blogger custom domain.

It's up to you, to ensure that your domain DNS addresses are properly setup. Nobody can do this, for you.

Give the new domain time to stabilise.

The DNS addresses need to propagate uniformly, through the worldwide DNS infrastructure. Having some computers able to access the domain, and others not, may lead to Google database corruption.

If the domain was used previously, you'll still have to wait - while any previous DNS addresses expire, from the many DNS servers, worldwide.

Click on the "X", and publish the blog back to BlogSpot.

If you wish to publish the blog to the new domain, it must be first published back to BlogSpot, using the Publishing wizard in the Blogger Settings - Basic dashboard page. Skipping this step may be another cause for database corruption.

Change BlogSpot URL, if desired.

Having prepared the new BlogSpot URL, now you swap the operational blog and stub blog URLs - if desired. This is the simple 1 - 2 - 3 swap that must be done in one uninterrupted 5 minute session, to reduce the risk of identity theft.

Publish the blog to the new domain.

Now, you see how well the DNS addresses are setup, and hope that the addresses have propagated uniformly. And be prepared to (possibly) verify domain ownership. This is what follows, when you click on the "X".

Redirect the domain root to the new published URL.

This is one of the more overlooked details, in the publishing process. Some people describe this as "optional". We see the results of treating the domain root to published URL redirect as optional, daily.

If you are publishing the blog to the primary domain host (which is normally the "www" alias), the domain root redirect is as necessary as publishing the blog to the new domain. If the domain will contain multiple hosts, you must choose which will be the primary domain host.

Verify the blog, published to the new domain, is working.

Test all 3 URLs - the BlogSpot URL, the domain root, and the "www" host - and ensure that all work. Use multiple browsers, multiple computers, and various online services.

Verify from multiple locations, using services like GeoPeeker, and What's My DNS. And do this over hours, if not days.

Be diligent and thorough, here - don't get caught, unaware, when your readers in another country contact you, complaining of the blog being offline.

Re direct the old domain, to the new domain published URL.

If you are retaining the old domain, at least temporarily, redirect it to the new published URL. This must be done using services provided by the DNS host / registrar, it's not a Blogger option.

If done properly, redirection from the old domain URL, to the new URL, will provide some initial search engine reputation, and traffic. This can't be done until the new URL is working - but should be started shortly afterwards.

Publicise the new domain.

As you did when you started the blog - and as when you published to the first custom domain, the blog needs to be re indexed under the new URL. Make the reputation of the new domain justify the effort involved in the above process.

Update any owner added internal links.

When you publish to a custom domain, all Blogger generated dynamic links - such as Archive and Label index gadgets, and Label links at the end of the posts - are updated, to point to the custom domain.

When you publish back to BlogSpot, all Blogger generated links are updated, to point back to the BlogSpot URL. When you publish to the new domain, the Blogger generated links are updated, to point to the new domain.

Owner added links are not updated, in either case. As when publishing from BlogSpot, all owner added links are the owners responsibility.


Mark Wallis said…
As an assembly language programmer I'm a little unsure of some of my words within web/blogger/internet but hopefully this is relatively clear;

I am trying to move my Custome Domain address from my OLD blog, to my NEW blog

My OLD blog's (blogger) address is:, reached by from, but would like it to point to the NEW blog here;

Can I - from within the; Blogger>Basic Settings page - simply delete the blog's redirection, and then (within my NEW blog's Blogger>Basic Settings page, add my Custom Domains address there, to show my NEW blog??

Thanks for any help!
Mark Wallis, England.

Chuck Croll said…
Hi Mark,

What you are asking about is Step 4 ("Click on the "X", and publish the blog back to BlogSpot."), followed by Step 6 ("Publish the blog to the new domain.") of the above procedure - the basic steps in changing the domain. The other steps - though less basic than steps 4 and 6 - are no less necessary.

If you want to walk through this, in detail, why not post in Blogger Help Forum: Learn More About Blogger? It's a lot easier to provide detailed help, in the online forums.

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: