Skip to main content

FTP Publishing Is Long Over

Some Blogger blog owners have been confused about the role of FTP, in the Blogger world, for some time.

Here's yet another instance where Blogger is different from many other website hosting services, on the Internet.

With many website hosting services, you develop (and even debug / test) a website offline, then upload it to the hosting service, using File Transfer Protocol. That's what FTP is - a network protocol for moving files from computer to computer. And a website is a bunch of files.

Blogger provides an online development and test environment. With Blogger, you create your entire website using Post Editor and accompanying utilities ("Settings", "Template Editor", etc). When you're done, your website is there, hosted in Google. No need for using FTP, to upload a website, after you created it.

Until last year, the term "FTP" referred to a procedure for hosting Blogger blogs outside the Google naming / server space.

In 2010, even that option ended.

The option of publishing a Blogger blog, to a non BlogSpot URL, as
is over. Now, your only option is
using custom domain publishing.

Custom domain publishing uses DNS referral, to associate a "domain" (non BlogSpot) URL to a Blogger blog. All Blogger blogs are now published to a BlogSpot URL, initially.

All Blogger blogs have a BlogSpot URL - and some processes, like account / blog recovery, or abuse review requests, require the BlogSpot URL.

You may be able to simulate specific addresses, such as "", using properly constructed custom redirects - but a Blogger blog cannot actually be published as "".

Part of the procedures provided by Blogger, to help blog owners survive the process of migrating their FTP published blogs back to Blogger / Google hosting, included a feature called "Missing Files Host". This let the blog owners leave key portions of their Blogger blogs hosted on the remote (non Google) server, and publish only new content in their blogs, newly hosted by Blogger / Google.

It's possible that some blog owners, the lucky ones for whom The Migration went seamlessly, are ignoring it as a significant event - and are seeing it as a mere "bump in the road" of their Blogger life (and FTP Publishing was bumpy, for many). Some blog owners may continue to tweak their (non Google hosted) websites using utilities provided by the hosting service, and may be using their (formerly Blogger published, now non Google hosted) websites as static content.

Having ignored the migration, these Blogger blog owners may be confused about why their Blogger published new posts don't show up in their non Google hosted website.

Blogger blog owners who publish web content hosted on non Google servers may wish to think about migrating the remainder of their websites to Blogger / Google hosting. At least, some blog owners may reflect that we are approaching the one year anniversary of the end of FTP Publishing.

>> Top


Nanook said…
I've come to rely on Google for too much. I knew that "Do no evil" would go out the window the day they went public.

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: