Skip to main content

Custom Domains, And A Domain Cluster

More and more bloggers are publishing their blogs to non BlogSpot URLs, using custom domain publishing, thanks to improved setup and stability. And more bloggers are finding more questions to ask, about how to handle the details.

Before custom domain publishing, we had bloggers renaming BlogSpot published blogs. Then, we had them publishing to their custom domains. Now we have bloggers who wish to rename their custom domain published URLs, and even to publish blogs to multiple non BlogSpot URLs.
  • A single blog republished to a different domain.
  • A single blog published to one (primary) domain, with one or more secondary domains used as aliases.
  • Multiple blogs, each published to a different domain, in a domain cluster.

A single blog republished to a different domain is similar to republishing a custom domain published blog. Since the final custom domain URL (from step #3) won't be the same as the original custom domain URL, this will require planning similar to changing your BlogSpot URL. When complete, you will have one blog, addressable from a different domain URL.

A single blog published to one (primary) domain, with one or more secondary domains used as aliases, requires careful setup.When complete, you will have one blog, addressable from multiple domain URLs.

Multiple blogs, each published to a different domain, in a domain cluster, is a third possibility. This variation gives us the ability, for instance, to publish a blog in multiple languages. When complete, you will have multiple blogs, each addressable from a different - and mutually similar - domain URL.

Note that, in all 3 cases discussed above, we refer to different domains in the associated URLs. You can, just as easily, have different virtual hosts within the same domain.
  • "" and ""
  • "" and ""
  • "" and ""
would all be valid primary / secondary pairs. Note that
  • "" and ""
would not be a valid primary / secondary pair, because "" and "" are two halves of a host pair, when published to a custom domain.

>> Top


Alfredo said…
Hi, it may be a stupid question but it’s been bugging me for some time now, it’s about custom domains. Is it possible to use a single custom domain name to host an English version and a Spanish version? (Within Google)

Right now I’m using for English and a Blogspot account for the Spanish version it’s really not a big deal but I’d like to have something like or something to that effect. Is it possible? Or do I just have to buy another domain name?
Chuck said…
Hi Alfredo,

I explored the need for a multi-lingual published blog cluster, some time ago. Do you own ""? If so, publish " to "", publish " to "", and publish " to "".

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: