Pages

Wednesday, January 27, 2010

Migration tool overview

Last week's announcement mentioned a migration tool we will be releasing in February, and a number of people have asked what it will do. In this post, I'll give a summary of the functionality, and then answer questions in the comments.

The goals of this tool are straightforward. It will:
  • ensure that visitors to your FTP blog are redirected to your blog's new home
  • avoid having pages from both sites end up indexed in search engines
  • preserve PageRank from your existing site to your new URL
  • update your Blogger settings so that future posts publish automatically
  • identify any necessary changes you need to helps you through each one
The tool provides a wizard-style interface which walks you through each of the four steps of the process:
  1. Backup your blog. Blogger supports full blog backup/export today, and before we kick things off we want you to have a full copy of your blog.
  2. Next, the migration tool asks you where you want to publish the blog once it's hosted by Blogger. This could be at a subdomain of your current domain (if you currently publish to www.yourdomain.com/blog/, you might want the blog to reside at blog.yourdomain.com), or if you don't own the domain you're publishing to, it might just be a Blogspot URL. If you pick a subdomain, we'll instruct you how to update your DNS settings so that the CNAME properly points to Google's servers.
  3. Once your blog is available at the new URL, we will write a final post to the FTP blog instructing users to the new URL, and we will then update your existing FTP pages by adding two pieces of information to each page on the blog: one is called a rel="canonical" link, which tells Google that the "canonical" location of the page is no longer the FTP URL but the new Blogger-hosted URL. The other piece of info is a refresh line, which tells the browser to redirect the visitor from the page they're on to the canonical URL after a short pause. Now that rel="canonical" supports moving content across domains, this is the path that Matt Cutts recommended we use to ensure that we could simply redirect all traffic from the FTP URL to the new URL. (More on rel="canonical" here, and more on refresh here.)
  4. Finally, we validate that the FTP URLs resolve to the new URLs — we just pull a couple of randomly selected blog posts and verify that they properly resolve to the new URL.
Most users will be able to use this tool to minimize the disruption of migrating off of FTP. Once done, you will continue to publish from Blogger — except that instead of watching as multiple files get uploaded to your webserver, your post will be immediately visible on the web and all archives pages are rebuilt automatically.

Some users will want to exercise more control over the process — we're also building a checklist to help identify all of the things you'll want to make sure you cover in manually moving your site off of FTP. More on that in a later post.

228 comments:

  1. I have about 40 blogs with Blogger.com and FTP Publishing is the only way to make my content accessible to visitors from China. Is it possible to get a desktop publishing software like livewriter to help us updating self-hosted blogs without merging to Blogger.com platform? Thanks!

    ReplyDelete
  2. I happened to convert my FTP blog to a subdomain of my personal domain earlier this month, prior to this annoucement.

    Will the conversion tool be OK with maintaining that subdomain?

    ReplyDelete
  3. @wordpress Livewriter only helps with the creation of the content, it doesn't handle the publishing of the content to a remote server. Since Blogger.com remains blocked in China, you'll likely have to move blogging platforms.

    @Jeff C: Yes, the migration tool will be just fine with a subdomain. If you are uploading files to the same subdomain, you will likely need to go the "advanced" route however, so that you don't orphan those files when Blogger starts hosting that URL. We'll be sharing more info about how to handle that shortly.

    ReplyDelete
  4. I have a high number of images hosted on my blog (which is one of the main reasons I FTP rather than use custom domain - some DNS issues that i'll now have to figure out are another).

    Anyways, since we're being forced to move to blogger hosted and not our own sites am I now going to have to pay for increased image storage in Picasa? Or will I be forced to limit the nubmber of images I can have in my blog (which kinda defeats the purpose of a photography blog)

    ReplyDelete
  5. and I realize that i can host the images on my server and link them to blogger but that adds steps to my workflow and makes it much more cumbersome to create blog posts..

    ReplyDelete
  6. You can keep those images on your domain. If your current URL is www.thekloeppings.com, you could have Blogger host the blog at blog.thekloeppings.com and keep all of your files at www.thekloeppings.com - not only would all current URLs continue to work, but you'd also continue to be able to upload and store them there.

    You're of course free to use Picasa, but if you are happy with your current setup there's no reason to change.

    ReplyDelete
  7. I'm not worried what what's up there. I see your solution for that and they'll remain on my servers and will work. However, what i liked most about the previous set up was being able to insert the images from the blogger platform and have the uploading to the FTP done for me as part of the publish process....now i have to add an extra step or two to upload the images to my servers, find the links, and then create the blog in blogger. Takes a formerly 5 min process to 15 at least (until I can develop some type of automation).

    I use Picasa for my other blog but it too is image heavy and has already started to fill up my free storage limit. Putting both on there will surely push me over the limit a lot faster than it would have before and would require me to buy additional storage (which i'm not inclined to do since i'm already paying for storage on my own servers)

    I understand why you guys are doing this - i'm in the software industry too and know that you can't please everyone but I'm just bummed that the ease I once saw in publishing images to my blog is going away and that I either have to pay for that ability or adapt some other way of publishing my blog.

    ReplyDelete
  8. Okay stupid questions time.
    1- what is FTP
    2- how do I know if my blog is using it.

    I only got my first computer in May 2009, so it is all new to me and I don't have a clue what you are talking about, but I know I don't want to loose my blog.

    Help!!!!

    ReplyDelete
  9. @Lia: FTP is "file transfer protocol", and it's a way of publishing a blog to another webhost. If your blog is at http://someaddress.blogspot.com/ then you are not using FTP.

    You can also check your blog's "Settings" and look under "Publishing" - it will tell you if you're using FTP.

    ReplyDelete
  10. @Rick Klau,
    the overview is great.Hope that it will also include some option to move the FTPed images onto Blogger + Picasa. It would be much useful if you guys help the FTP users to move the blog completely from their servers rather than hosting the images on their own hosts and moving the blog alone to the google servers. It would be much useful if the images published on the blog(and stored on users host) can be moved to Picasa albums and the image links in the posts gets updated accordingly.

    ReplyDelete
  11. @Aneesh - We will not be modifying the location of images at this time. We wanted to build a tool that would work for everyone (or nearly everyone) and had as few moving parts as possible to minimize disruption and potential for errors.

    ReplyDelete
  12. @Rick Klau - thanks for the confirmation. and nice to see this dedicated help blog and the support you offer in migrating to custom domains.

    ReplyDelete
  13. I'm still confused. After migrating off FTP, will the custom domains be free or do we bloggers have to pay to use it?

    Also, I have two blogs that has .blogspot.com/ at the end. I know I'm not using FTP, which I checked, and I have the Blog Readers set to Anybody. However, my question is, will I be able to continue using them after March 26th?

    Thanks

    ReplyDelete
  14. I am working on migrating my ftp to custom domain & I wouldl like to host 2 different blogs
    Example.

    blog1.domainname.com
    blog2.domainname.com

    When I try to update the CName using Godaddy for each subdomain to point to ghs.google.com it will only allow me to point 1 subdomain to this because it says the ghs.google.com is already being used?

    How can I have 2 blogs with same domain?

    ReplyDelete
  15. @Native New Yorker: There is no cost for custom domains (other than whatever you pay your registrar to register the domain). Your blogspot.com blogs will not be affected at all.

    @Chad: You can have as many subdomains as you want. You should probably follow up with GoDaddy support to make sure that there isn't a configuration option preventing you from properly setting up multiple subdomains.

    ReplyDelete
  16. Hello, I'm slightly confused.

    I don't own the domain I use, I was given space as a subdomain to use for whatever I wanted. Do I have to contact the owner or can I do this on my own?

    Also, will I have to start directing people to a new address? or is there anyway to keep the same address?

    My template pulls images and a css file from my domain-will I still be able to use this after migration?

    Thanks in advance!

    ReplyDelete
  17. Hi Rick,

    I just got my first email about this, and I'm a bit unsettled. I'm hoping you can answer a couple quesitons to ease my mind.

    I'm a 10-year Blogger user, own my own domain name (www.bradleysalmanac.com) and keep all my content on a Readyhosting server, where I use FTP to manually transfer images and audio. I use Blogger to FTP my posts onto this server.

    After reading a few posts here, I'm still unclear on something: It's vital that I keep my blog URL at www.bradleysalmanac.com, and that I'm able to continue to use my hosting provider and keep my content there. Will I be able to do this after converting away from FTP blogging? When I write new posts, I'll still need to point to images and audio files that I manually upload to my provider space.

    I don't see my particular setup mentioned in any of the example cases. I truly hope Blogger's abandoning of us longtime FTP users doesn't result in my having to migrate to another platform. I still wear my blogger hoodie with pride ;).

    ReplyDelete
  18. @Rick Klau: So here is my situation, my Blog is published on a custom domain www.miss-sly.com (purchased through Blogger) which stopped working since Sunday.

    I am able to login into my Blog and update/edit everything in it, but once I click VIEW BLOG, I get an error: Site not found.

    Possible solutions: 1)can switching back to blogspot.com resolved this?
    2) Will I lose all my Blog content by doing so?

    Any help? Anyone?

    ReplyDelete
  19. Oh! I forgot to mention that I started out with a blogspot address, then switched to ftp. Will my old blogspot address be a factor here?

    ReplyDelete
  20. Hi;

    My blog is at http://domain.com/me/blog/

    Other content, going back a dozen years hangs off of domain.com.

    Given that Google isn't offering a generalized hosting service I don't think I have anything to migrate to.

    Or am I misunderstanding?

    ReplyDelete
  21. I'm definitely confused and a bit worried about privacy. I FTP to my server that has a robots.txt setup to block all search engines. A couple of years ago, I tried to switch off of FTP but was horrified to see posts also cross-posting to an equivalent blogspot site. It took a lot of back-and-forth to take down the latter and switch back.

    If I go through this migration process (which is still not clear to me -- where exactly will my posts reside?), how can I keep bots from crawling over years of posts?

    ReplyDelete
  22. Pardon the questions from a non-techie: First, I tried to export my blog to my computer but it didn't work. what do I need to know?

    Secondly, my blog is on www.artnbarb.com, which is thru GoDaddy. I don't really understand how to set up a subdomain - if this is indeed what I need to do.

    ReplyDelete
  23. @Romana1 - You will have to contact the owner of the subdomain if you wish to continue publishing to that URL; if you want to direct people to a new URL, you can pick a new one and start using that.

    @Brad - Glad you like your hoodie! :) Your setup sounds similar to mine, where I host lots of files at www.rklau.com (not managed by Blogger). I keep my blog at a subdomain (tins.rklau.com), with pointers to the files at www.rklau.com. In your case, you have two options: (1) setup a redirect so that www.bradleysalmanac.com redirects to blog.bradleysalmanac.com, or (2) have Blogger host www.bradleysalmanac.com, and then create a "backup" subdomain (like files.bradleysalmanac.com) that Blogger can point to if we get requests for files we don't host. (Pete describes our "missing files host" support here.) Hope that helps.

    @Miss SLY - Not related to FTP, have you started a thread in our forums? One of our super users can help you out there, and I'll make sure our support team takes a look.

    @Lee - We're proposing that you can host the *blog* at a subdomain (blog.mydomain.com) while leaving the rest of your content in tact.

    @C - We have a setting in your blog's dashboard that controls whether or not your content is indexed by search engines. Set it to 'no' and you're all set.

    @Barbara - Can you be more specific? What didn't work? GoDaddy-specific instructions are here.

    ReplyDelete
  24. Okay, I just want to keep my Url (which is my name) How do I start this transfer to the Custom
    blog (which will use my Url as is, right?) Some one helped me set up this complex FTP system, so I'm not exactly technical! Can you give us a step by step instruction? And how to get all my data
    on blogspot?

    ReplyDelete
  25. @bevjackson That's exactly what the migration tool will do; it will be available in a couple weeks. We wanted to get the announcement out ASAP so that people who needed to make alternative arrangements had time; but if you're planning to do what we outline above, you can just wait until it's available.

    ReplyDelete
  26. I'll check out the GoDayy instructions, As for the xml file, I thought I'd have a (readable) copy of my entire blog on my hard drive, but when I tried to open the file I got this message:

    The XML page cannot be displayed
    Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.


    --------------------------------------------------------------------------------

    XML document must have a top level element. Error processing resource 'file:///C:/Users/Barbara/Documents/blog-02-02-2010.x...

    ReplyDelete
  27. @Barbara The backup file is an XML document which contains your blog's settings, posts and comments. It is not a copy of your blog intended to be viewed on your hard drive. (The migration tool will, among other things, give you a Zip file which *is* a formatted copy of your blog.)

    ReplyDelete
  28. I have been using Blogger for four years and started using FTP last year. It was like one of the best thing I have ever came across since, well, Google.

    My blog is currently published to http://blog.ping-yui.net/ and I have a large number of visitors, so I am concerned about all the moving around and redirecting.

    Will be really glad if you keep us updated.

    ReplyDelete
  29. If you are using the ftp for a blog that is already located on another domain will you be able to post at the same address or do you need to get a subdomain? mine is set up like this bbbb.com/bb.htm. is that any good or do you need to create a new location like this example blog1.domainname.com .

    ReplyDelete
  30. Sorry, but this is a disaster for me. Static pages limited to just 10? Quite useless!

    My site Doodlecat.com has many, many more pages than that, and the home page is powered by Blogger to allow easy and frequent updating by me & co-authors.

    So, will blogger be able to host my site as you suggest - for free? I suspect not.

    My other site, a club, not only uses Blogger for the home page, but the web space provider provides email and newscast facilities for the domain as well. Will Blogger do this? I guess that's a 'no' too.

    So, what I have now is a major piece of my sites' functionality being removed, and no reasonable alternative.

    Not happy. Not happy at all.

    And the solution is ... ?

    ReplyDelete
  31. @Dave Each blog needs to publish to a unique URL. If your blog publishes to bbbb.com, then you won't be able to "share" that URL with other publishing platforms. blog.bbbb.com is probably a better answer.

    ReplyDelete
  32. I have no idea waht any of this means.

    I run three blogs (two personal, one for someone else). I log in to blogger, create a post then publish it, which ftp's the info onto the proper site. How am I meant to update my site without ftp? I have no intention of changing my hosting company or my url so what do I do?

    ReplyDelete
  33. @Rick Klau I am an Internet Marketing Director with over 50 blogs that publish FTP style. This is going to cost me a lot of time and money to migrate all these over.

    Do you recommend I wait for the migration tool? That only gives me 2 weeks or so to move them all.

    Also, is there anyway to keep the templates we have now? The reason we chose blogger in the first place was because we could make them look exactly like the rest of our site.

    ReplyDelete
  34. I was just thinking that it's time to redesign my website, but I've paid for hosting & my domain for a two year period. It sounds like from reading this that after ten years of using blogger to publish to my site I will need to select another service that allows me to publish to the hosting space I've purchased. I see no reason to migrate my website when there are plenty of other publishing options out there now.

    ReplyDelete
  35. One thing I'm trying to understand that I don't seem to see addressed in the FAQs -- my blog isn't just a blog, I have numerous subsites attached to it. The blog appears as my homepage, but it leads to a number of other sites that aren't blogger published. These are hosted on a service that I pay for. So if I bring my blog over to a Custom Domain and reset the DNS for the site's homepage, is it possible to maintain those subsites where they were? I'm a little concerned about breaking my site entirely.

    ReplyDelete
  36. @Stampers In order to continue using Blogger to update your blog, you'll need to publish to a URL we host. That can be your current domain, a subdomain off of that domain, or a Blogspot URL. You do not need to change your hosting provider (you can still use them for hosting other content).

    @Ad Trends - The migration tool will give you a month to migrate, which should be plenty of time. You're of course welcome to start ahead of that - setting up CNAMEs could be in place ahead of the migration tool, which will save you time and make things update instantaneously.

    ReplyDelete
  37. I publish my blog (www.garylynch.net) to my own server for a number of reasons but one of the most important reasons is it enables me to embed server-side script in my template and posts to allow me to do things that I wouldn't otherwise be able to do. I use Blogger for this, rather than installing some other local installed system, as it means I don't have to get bogged down in maintaining the blogging platform that manages the blog. This I clearly cannot migrate so my question is, can anyone recommend a good blogging platform that does allow me as much free control?

    Cheers
    Gary

    ReplyDelete
  38. If we have to migrate our blogs to a new domain or subdomain, how will this impact searches? will each page on our old sites have a redirect to the new site? Search engine placement is a critical issue.

    ReplyDelete
  39. @Rick Klau
    Sorry of my question wasn't FTP related...I have started a thread in the help forum and have yet to hear from someone. And there other ppl with the same issue, thank you to look into this: Thread is located here.

    http://www.google.com/support/forum/p/blogger/thread?tid=18e258e11a102080&hl=en

    ReplyDelete
  40. @John As stated above, using rel="canonical" is how Google knows that the content has moved. Searches will be unaffected - they'll simply update to find the new URLs.

    ReplyDelete
  41. Thanks very much for your quick reply, however I think I'm more confused now than when I started!

    You say "a url that we host" but you don't host a url, do you? My url is provided by my hosting company and you say that I can continue to use my hosting company for "other content."

    What, exactly, is goingo to change if I can still host my blog with my current hosting company?

    ReplyDelete
  42. My position is similar to Stampers ... and I'm confused too!

    ReplyDelete
  43. OK, I converted one of my blogs - but I'm finding that I've lost control over the URL names of archive pages. I used to specify the shortest name possible:

    http://37.9timezones.com/2006_03_01_.htm

    , but now I have to accept this:

    http://37.9timezones.com/2006_03_01_archive.html

    1) Is there any chance of getting back that control?

    2) Also, is there any chance of getting back subdirectories? I used to be able to visit the archive page by typing in this:

    http://9timezones.com/37/2006_03_01_.htm

    Your engineers have heard about the concept of "backwards compatibility," right? It sounds like you folks have pretty well screwed us FTPers. I thought your motto had something to do with not being evil...

    ReplyDelete
  44. @Alan The migration tool is being built to address the moving of archives pages (as well as individual pages). We won't be changing the current directory structure on the hosted side, no. As far as backwards compatibility goes, that's exactly why we're investing the time to build out the migration tool - to ensure that we preserve as much traffic as possible.

    ReplyDelete
  45. I'm confused, too--and I can't believe that this announcement was rolled out before the migration tool was ready. Seems you guys should have had that tool ready sooner to release it simultaneously with the announcement (so that we don't have three weeks of fretting about this and then only a month to implement the migration).

    So my blog is www.phoebeeating.com. It seems like the best thing to do, in order not to have lots of broken links to subpages, would be to host the blogspot blog at blog.phoebeeating.com, and then have www.phoebeeating.com redirect to blog.phoebeeating.com, yes? And I should be able to copy my template over and turn off that hideous navigation bar? (Yes, I know--you want us to keep it. Free advertising for you guys. But no way I want that emblazoned across my home page.)

    ReplyDelete
  46. Rick, your documentation says: "only .5% of active blogs are published via FTP," like that's an insignificant number. But I can just imagine how many millions of blogs are represented by that .5% - and how many millions of bloggers you're going to p*ss off. We FTPers are the active ones - the blogspot set tends to create blogs and then wander off in search of the next shiny toy. But we are the guys and gals who blog month in, month out. And you're forcing us into becoming your sworn enemies. If you Googlers want to maintain your reputation, you need to work a little harder at that "not being evil" thing.

    ReplyDelete
  47. @Rick Klau I want to make sure I clearly understand this so I can make a decision as to what I have to do with my 7 blogs(one I've had for nearly 10 years) with Blogger.

    All of them are set up the same way - I use my blog as the index.html and the rest of the pages on my site are built off the blog template.

    In order to continue to do this, I will need to create a sub domain for my blog(okay, no problem) and then publish to it from Blogger? Is this what is necessary?

    I know how to create a new subdomain but I have no idea how I go about having you guys host it. I've used blogger for many years to do this stuff because they made it easy so you have to understand this is bit of a bad, unexpected divorce.

    Would I then have to redirect my domain (www.citrus953.com) to the sub domain so that I could retain the format of having my blog as the front page?

    Like I said, I used blogger because I have limited knowledge and it made it easy for me to do the things I wanted to do. Will it be possible for me to continue to do what I'm doing with my 7 blogs? (Basically, using blogger for the front page to integrate with the rest of the basic site and it's pages)

    And who gets the dog?

    ReplyDelete
  48. This is just ridiculous. I *don't want* a blog.vijaypadiyar.in kind of structure. I want to retain my existing www.vijaypadiyar.in/blogs/ structure. Damn you, Blogger!!

    ReplyDelete
  49. Any idea what will happen to our RSS feeds that exist on our old URLs (I happen to have a www.domain.com/blog that will likely need to change to blog.domain.com)? Will they contain some sort of notification that the new RSS feed will be located at blog.domain.com/atom.xml?

    ReplyDelete
  50. My club's website homepage includes an embedded blog that looks just like it's part of the site. I can handle changing from www.clubsite.org/blog to blog.clubsite.org following your instructions and by using the migration tool. My question is: will I still be able to display the blog within the site's homepage? Currently the page is in php and this line: causes the blog to display I think. Please bear in mid that I didn't develop the site although I am capable of day to day maintainance. If this include doesn't work is their another way to drop the blog onto a webpage, with the css formatting still working as well?

    ReplyDelete
  51. @Chris Sounds like your site is iframing the Blogger content, which will continue to work just fine.

    @Ka Wai Your best bet for the feed is to switch to FeedBurner so that you can later redirect readers to whichever feed you want; alternatively, you can post to the blog informing your subscribers that they will have to update their subscriptions.

    @Matty You've got it right. You can wait for the migration tool to walk you through the changes (which will also help redirect traffic from the old URLs to the new ones). The only thing you'll need to do is input your new URL and configure the CNAME (which the tool will provide guidance about how to do that) in your domain configuration. Everything will continue to work as it does today.

    ReplyDelete
  52. I already have a custom domain name since 2006 what am I supposed to do now???

    ReplyDelete
  53. Thanks for your answer but I don't know what iframing is. In my last post I tried to paste in a line of php code which didn't appear in the post. The relevant bit is a php include statement, relating to /blog/blog.html which is the relative address of the blog in its current location. Will this just need to be updated, or even not changed at all after I migrate to a custom domain name?

    ReplyDelete
  54. Rick

    Read the posts. Many of us are not technical which is why this suited us perfectly. All you say is wait for the migration tool. It's appalling you announce this and yet you are not ready to offer any help. Whatever the whys and wherefores, that's appalling management and communications. You're losing touch with your market.

    ReplyDelete
  55. I already publish to a subdomain - blog.funkyj.com

    Does this process mean I will have to create another subdomain and the migration tool will redirect there?

    ReplyDelete
  56. @Admin I'm answering hundreds of comments, and we're answering them as fast as we can on Twitter as well. I'm sorry you feel we're losing touch, we're trying very hard to accommodate our users.

    We've been given a hard internal deadline for infrastructure that's being decommissioned - when that decommissioning happens, we lose our ability to publish via FTP. We've been working to get a plan in place to accommodate the many non-technical users. Would I have liked to have the tool done before making this announcement? Of course. But the timing was just not possible - we announced as soon as we knew the plan, and are working furiously to get the tool done and in users' hands so that they can migrate seamlessly.

    ReplyDelete
  57. @FunkyJ No, you can continue to publish to that subdomain, you'll just update it so that it points to us. I'll publish a post shortly that explains how that will work.

    ReplyDelete
  58. I shouldn't complain about a service I get for free.. but this is pathetic. You announce a migration, but the tool to do it is three weeks away, and the reason given is that for some reason Google can't support FTP any more. I didn't realise that Google was a Mom and Pop operation being run from the spare room.

    Yes, I get it for free. But I'm also an enterprise customer of Google and this sloppiness seems to run deeply within the organisation.

    Shape up.

    ReplyDelete
  59. This comment has been removed by the author.

    ReplyDelete
  60. Right, well I'm not having a blog.something.com address and I'm not having my files hosted on blogger so I suppose I'll be moving over to Wordpress, and I'm betting I won't be the only one. Good going, guys.
    I know it's not your fault, Rick, but even you have to admit this is a terrible business decision.

    ReplyDelete
  61. Rick -- Thanks for answering so many questions. I'd like to be perfectly clear so I can decide whether I need to move my blog to another provider.

    I own my own domain and host my blog at mydomain/weblog/

    I need to maintain this structure. I need all the rest of my site to remain exactly as it is, hosted with my webhost

    To be perfectly clear, are you saying I can create a subdomain such as mydomain.myblog and repoint only the subdomain mydomain.myblog to Google's services? or do you require that the entire domain be repointed? The latter is out of the question.

    Thanks for any clarification.

    ReplyDelete
  62. @Carolyn Let's say you own carolyn.com and your blog is currently publishing to carolyn.com/weblog/. In order for Blogger to host your blog (and assuming you don't want us to host www.carolyn.com, which we can do but I believe you don't want), you will need to create a subdomain - like weblog.carolyn.com. That will leave everything else at www.carolyn.com alone. Does that help?

    ReplyDelete
  63. @Conrad This comment is my best effort at explaining what we're doing and why (and my acknowledgement that this is problematic for some users); it's not an easy decision but as product manager I believe it's the right one for the Blogger platform.

    ReplyDelete
  64. I am pretty sure there is a much easier solution than what you are proposing.
    Possibly a simplified blogger based admin tool that could be uploaded/added to a hosting site to avoid FTP.
    Mine already has one by a competitor, so it might just be easier to migrate to it and drop the blogger tags.

    ReplyDelete
  65. Hi Rick,

    As much as I appreciate your addressing all of our questions, and putting time into this migration, I'm afraid Google's incomprehensible decision to abandon this part of their userbase has me looking at other options. I simply don't have the time or expertise to deal with the migration.

    Was there ever any discussion about charging a nominal fee for FTP service instead of just dumping it? I'd gladly pay.

    At this point a migration to another tool strikes me as a better way to maintain control of my blog, vs. forcing me to restructure my site. I looked at my provider's site and can find no easy way to set up a subdomain (and it looks like it will cost me money to do so). I can pay for one, but then it looks like I have to point to a subdirectory of my site? That doesn't seem to relate to this process at all, so I'm even more clueless.

    I've been trying to think of an appropriate way to mark the 10th anniversary of my blog on Blogger this month... I certainly didn't think it would involve considering a move off of Blogger entirely. Sigh.

    ReplyDelete
  66. I happen to own the domain I use with FTP. Will I be able to keep using that domain after the FTP phase-out by using the migration tool?

    ReplyDelete
  67. I have several blogs I'll need to migrate. Can you tell me:

    1. Will our blogs lose their organic search results once migrated or will they remain the same?

    2. Will images migrate over to the new functionality or will the blog look differently?

    3. Is the migration going to be a simple process or will we need to hire someone to do it?


    Thanks for your help with this. Anna

    ReplyDelete
  68. "Don't be evil"... just be really really annoying!

    My domain hoster does not support CNAME management which I think is required in the absense of FTP. So now I'm going to get hit with a bill to change hosters.

    Thanks Google!

    ReplyDelete
  69. @Rick: Thanks. Although, I'm still confused by this change, I will wait and see what will happen on the 22nd when the tool is release. I just hope I do not have to update my blogspot.com sites to a custom domain, because I can't afford it.

    ReplyDelete
  70. Hey Rick: Can you help me with this question, which I'm sure I'm not the only one facing this dilemma.

    1. I have a domain hosted with BlueHost.
    2. I use Blogger FTP to publish to that EXISTING domain.

    Q: If I switch to Custom Domain publishing, will I still be able to use Blogger to publish to www.domainname.com or will the URL HAVE TO be changed to blog.domainname.com??

    Q2: Using Custom Domain, can I still use the Classic Template just as I do now in Blogger or will I HAVE TO upgrade to Blogger New Template?

    Q3: Can you please provide the Google NameServers to use for changing the DNS settings with a web host? For example, with BlueHost, I need two name servers, which are generally something like ns1.google.com; ns2.google.com - Are those the correct DNS names (not IPs, b/c it must be a NAME server)? If not, can you please tell us the nameserver names to use?

    Q4: Will publishing via Custom Domain PRESERVE path names (such as domain.com/labels/label-name.html and domain.com/11/2009/pagename.html) ??

    Q5: Will I lose Google search engine rankings and page rank as result of this change?

    Q6. Does Google offer hosting service that will make this transition easier and/or support PAID FTP publishing? If so, where can I find that information. If not, why not?

    PS - I can't buy a new domain via Blogger Custom Domains because I only want to use the existing domain - www.domainname.com - but it's confusing if switching to Custom Domain
    Thanks for your help - I'm sure many people have same questions, I just haven't been able to find verifiable information about this.

    ReplyDelete
  71. By the Way, for a company with as much money and resources as Google has, this is a very poor decision.

    AT LEAST Google should have offered a fee to keep FTP publishing - this is a huge headache and let down to all of us who publish via FTP and don't have the means, time, etc. to make the changes. I would have paid for FTP hosting - crappy decision and I URGE GOOGLE to re-evaluate this decision and AT LEAST offer FTP publishing as an ALTERNATIVE to Custom Domain.

    ReplyDelete
  72. Hey Everyone:

    I think we need to band together.

    Join me on Twitter for user 'keepftp' to pressure Google to keep FTP publishing - OR to at least keep FTP publishing and charge a fair fee ($20 annually?) - This decision by Google is going to cost many of us much more than that in lost customers, readers, time to migrate, trouble-shooting, branding, search engine positions, etc.

    Join me at http://twitter.com/keepftp - and leave messages and Retweet.

    I will use your support and messages to send to Google to ask that they NOT discontinue FTP publishing.

    I will also be creating a Blog to advocate Google NOT discontinue FTP publishing - OR offer us some sensible alternative rather than a 'migration tool' that won't even be available until next month.

    Right now, as you may know, Google plans to discontinue FTP publishing on Blogger on March 22 - maybe we can band together and get Google to reconsider this disastrous decision.

    Thanks!
    Join at:
    http://twitter.com/keepftp

    ReplyDelete
  73. Working through the Q's & A's.
    Correct me if I'm wrong please.
    I have 2 blog's that I bought dot com names for. These I take it are OK. No changes necessary. Not FTP.

    My 3rd blog is hooked to my site (FTP) so it needs to be moved.
    Your "migration tool" will do this for me?
    Will I need to do anything to my site so the links there can still find my blog?

    ReplyDelete
  74. @Native New Yorker: If your URL is *.blogspot.com, you are *not* publishing via FTP and are not affected by this announcement.

    @Googe: Answers to your questions:

    If I switch to Custom Domain publishing, will I still be able to use Blogger to publish to www.domainname.com or will the URL HAVE TO be changed to blog.domainname.com?

    A: You will still be able to use www.domainname.com. "www" is just one of the CNAMEs on your domain, so if you want to host www.domainname.com on Blogger, point "www" to "ghs.google.com" in your domain config.

    Q2: Using Custom Domain, can I still use the Classic Template just as I do now in Blogger or will I HAVE TO upgrade to Blogger New Template?

    Yes, you can still use the classic template.

    Q3: Can you please provide the Google NameServers to use for changing the DNS settings with a web host? For example, with BlueHost, I need two name servers, which are generally something like ns1.google.com; ns2.google.com - Are those the correct DNS names (not IPs, b/c it must be a NAME server)? If not, can you please tell us the nameserver names to use?

    Help doc is here.

    Q4: Will publishing via Custom Domain PRESERVE path names (such as domain.com/labels/label-name.html and domain.com/11/2009/pagename.html) ?

    The migration tool will handle redirecting label and archives pages, yes. If you manually convert, you will need to implement the redirection manually.

    Q5: Will I lose Google search engine rankings and page rank as result of this change?

    The migration tool, as documented above, will use rel="canonical" links in your HTML pages, which is how you tell Google that the page has a new location. rankings/pagerank will be preserved.

    Q6. Does Google offer hosting service that will make this transition easier and/or support PAID FTP publishing? If so, where can I find that information. If not, why not?

    No, we do not support a paid option. We're not turning FTP off because it's not generating revenue, we're turning it off because we are unable to continue evolving the platform as we were investing disproportionate resources in supporting a declining number of users and sites.

    ReplyDelete
  75. Well, this whole matter makes me very sad. Like so many people here I have my blog integrated into my site (which predates blogger by 4 years).

    I have been using Blogger for 6 years and I always loved the way I could have my blogs blend in with the whole look-and-feel of my site. Sometimes I was jealous of the people who had their blogs hosted at blogspot and got all the cool tools etcetera, but I COULD not move because there is more to my site than only a blog. And I did not WANT to move, because I wanted to stay in control of my data.

    Now it looks like the decision has been taken out of my hands: I am being FORCED to move, even though the same problems continue to exist. I admit I will be able to make things WORK again, but I will be losing traffic and I will have to put in a lot of effort. And still, after the dust has settled down, it will not be the same it was:
    * I will be forced to register about ten subdomains. (And keep those forever.)
    * My users will have to get used to new URLs.
    * My site will have to host tricks to redirect the traffic to the new location. (Forever.)
    * Unexpected problems will pop up. (For a long time.)
    * My setup will have added complexity, resulting in more possibility for mistakes and errors. (Forever.)
    * My data will be out of my hands and future changes to my setup will be hindered. (Forever.)

    I agree with the above posters that the 0.5% of blogger users who use FTP must include a lot of the long-timers: faithful, active bloggers that have a far greater impact in the blogosphere than gazillions of blogspot one-day flies. These people are hurt by this move.

    I don't really expect a big corporation like Google to listen to reason, so I see little chance of this move not taking place. I also don't expect moving to another platform, like WordPress, would be painless to me.

    So I will go ahead and try to move one of my "lesser" blogs first. Then I will be able to see what the results are and decide whether I will move the rest too or change to a "roll-my-own" setup.

    But -- @Rick_Klau -- here finally comes my question: Will I be able to evaluate the results after moving one of my blogs by hand, or will there be changes that are beyond my control until the migration tool becomes available?

    By the way Rick, I don't envie your position, having to explain all this to the bloggers. And you do it in a great way. Thanks for that!

    ReplyDelete
  76. @Evelien I'd suggest setting up a test blog and do a test run of the migration, which will let you verify everything before you do it for real. You can always import the export file into a test blog, import the template, etc. and then try the migration out.

    Thanks for your kind words!

    ReplyDelete
  77. @Rick: Thank you very much. I now very much understand what's going in here.

    Good luck

    ReplyDelete
  78. @Rick Klau:

    I can appreciate the problem that you are facing in regards to FTP connectivity. I'm in a fortunate situation where our dozen blogs are already self-hosted on a subdomain that is dedicated exclusively to those blogs. The proposed transition is fine for us in general. However I would like to offer one additional issue for your team to add to your user concerns list and an alternative solution for the situation:

    Issue: Our other sites draw from the blogs via RSS files to populate the 'Whats News' column on many of our pages. Because this is generated on the server side, and the RSS feed is coming from within our own network, the page response hit is negligable. I'm guessing that sub-10 milisecond response times for the RSS feeds are not available through ghs.google.com. I suppose I will need to create a caching version of the RSS reading function. Do you have any suggestions for doing this with Classic ASP or PHP?

    Alternate Solution: Spin off the .5% of users who still need the FTP functionality into a 'Blogger Classic' platform that provides the continued functionality, but 1) no longer allows for new accounts, 2) no longer gets new features. If this would be possible to spin out to a volunteer group of users who would provide the on-going hosting of the otherwise frozen toolset, perhaps you can offer that up to your users.

    ReplyDelete
  79. I am leaving blogger.. as a loyal user since 2003 this is a bonehead move.
    I am not moving to blog.domainname.com
    plus what if I DON'T want google hosting EVERYTHING..
    wtf..

    Hello WordPress goodbye Blogger.

    ReplyDelete
  80. @mblind
    if you are currently having an FTP blog at www.yourdomain.com then there is no need to move to blog.yourdomain.com (Rick had mentioned this in some previous comments)

    If you are using www.yourdomain.com on FTP you can continue using the same using Custom Domain and if you wish you can host your images on your own servers

    ReplyDelete
  81. Hi Rick,

    I am so impressed that google has taken the initiative on this issue. I've wracked my brain for about 2 years now on how I could migrate my blog from ftp to the new blogger and this migration method is certainly a sound plan.

    I've always worried about losing pagerank by changing from ftp to the new blogger. The other problem was the canonical issue and you seem to have addressed that too.

    My hat's off to Google for once again addressing the concerns of their customers (us bloggers) to help and once again make the experience better for the end user.

    Can't wait to migrate and use the Layout method.

    Thank you,
    Mark

    ReplyDelete
  82. Will the google API for blogger still work? I have a lot of custom scripts in my blog and not big on wordpress. If the api's still work I can make my blog still work where it is. Also will there be a way to keep the content in the google cloud from showing up at all on the Internet?

    ReplyDelete
  83. Hi Rick,

    I forgot to ask this other question.

    After reading this post and comments, I logged into my cpanel and created a subdomain for my blog.

    I did not change anything, my blog has always been an ftp blog located at http://www.mississauga4sale.com/blog/ and when I created the subdomain blog.mississauga4sale.com then browsed to http://www.blog.mississauga4sale.com/ my blog appears! What causes this? I did not change any of the DNS settings in my cpanel or anything, all I did was create the subdomain blog for my domain mississauga4sale.com

    How did the system resolve mississauga4sale.com/blog to blog.mississauga4sale.com to my blog?

    Thanks again,
    Mark

    ReplyDelete
  84. Hi Rick,

    Sorry, one more question. I think this is obvious, but need to know.

    I should wait for the migration tool to be published in mid February before I do anything, correct?

    As well, will my new blog at blog.mississauga4sale.com be automatically under the Layout format rather than the Template format? And if so, then I can add widgets and such to my blog? If so, this will make me very happy!

    Thanks
    Mark

    ReplyDelete
  85. Hi Rick, if I must host my files on blogspot, how do I use php commands (that work correctly now because I host the files on my domain)? when I published to blogspot the php commands stopped working. Am I missing a step? Example php statement:

    ReplyDelete
  86. Hi,

    So far, I seem to be reading a lot about sub-domains, my blog publishes to the root domain. Can I still keep this setting with the changes, or will I have to create a sub-domain?

    Actually, I have 2 FTP blogs, 1 is already on a sub-domain and the other root domain(different domains). On both blogs, I host images and videos on my own domains and will want to continue to do so.

    How does this all affect my blogs? Also will this transition affect google search rankings? I have had the #1 position for over a year now, so obviously, a bit concerned, if I have to change from root domain to sub-domain.

    ReplyDelete
  87. @Storm
    yea you can continue using the same sub-domains and root domain but you will have to create additional subdomains to move the hosted images and videos. hope my tuto will help you..

    ReplyDelete
  88. when will be the migration tool be ready?

    ReplyDelete
  89. I echo the comments of those who say the 0.5% of users are probably hardcore (and thus probably account for more than 0.5% of traffic). And yes, I've had a site that predated Blogger. But fine, if I have to be moved, I'll move.

    But @Rick, I am a bit confused by your wording in step #2 of your post. I publish my blog at my current domain (www.dsng.net), no /blog/ or subdomains. I presume Custom Domains allows me to continue to publish at my domain, and doesn't impose a subdomain structure on me?

    ReplyDelete
  90. thanks Aneesh! Rick was getting a bit confusing(with the hosted by blogger vs pointing) ur tuto, makes it much clearer!

    Just a couple more questions:

    1. Seeing as my root level domain will now technically be pointing to a google server, does this mean that, should google(for whatever reason) decide to abandon the whole blogger thing, or be hacked and down for days, my blog would not be accessible?

    2. In the case of blogs currently publishing to a sub-domain, do I have to create an additional sub-domain, or can I just copy files to a root level folder eg "www.abc.com/uploaded_images/" and use that as the missing files folder?

    3. If I decide, this is all a bit too much and prefer to maintain control over my blogs(as I am sure some people will do), will moving blog platforms(to WP for instance) affect google search rankings?

    4. Will I finally be able to have the "older posts" and "newer posts" links with this move? A major annoyance in the current system, which had me considering WP for my larger blog.

    I use both WP and Blogger, for various reasons and definitely would like to leave at least one of my blogs with blogger, but this must be explained to people in clear terms like Aneesh's tuto. There appears to be some confusion with "hosted by blogger" and pointing etc. People need clear, concise, easy to follow directions.

    Rick, I don't envy your job right now, so I know you are doing the best you can.

    ReplyDelete
  91. Rick,

    I feel a lot of people here are getting confused/anxious about this process and the blog is not clearly spelling out what people need to do to continue using blogger with minimal angst.

    I think at this point a clearly written chart or FAQ is in order

    Although may of the steps will be the same, people are starting from different places. "I already have a domain, I update the news section of my existing site using blogger, etc etc"

    A clear set of instructions or FAQ's covering these issues will likely make everyones lives a little less stressed and avoid you having to re-answer the same questions endlessly.

    ReplyDelete
  92. @Steve Agreed. Been busy trying to address as many specific questions as possible today, didn't have time to take a step back. Doing that tomorrow. Thanks.

    @Storm Your questions:

    1. Seeing as my root level domain will now technically be pointing to a google server, does this mean that, should google(for whatever reason) decide to abandon the whole blogger thing, or be hacked and down for days, my blog would not be accessible?

    Yes, you will be hosting with us. The last survey I'm aware of that ranked blog hosts gave Blogger strong marks, and our internal reporting over the last year suggests that our uptime has actually improved. But yes, we are asking you to host on our servers (for free).

    2. In the case of blogs currently publishing to a sub-domain, do I have to create an additional sub-domain, or can I just copy files to a root level folder eg "www.abc.com/uploaded_images/" and use that as the missing files folder?

    This is best answered in the blog post I'll be writing (see my comment to Steve), but in general you're right - the missing files host will take care of you.

    3. If I decide, this is all a bit too much and prefer to maintain control over my blogs(as I am sure some people will do), will moving blog platforms(to WP for instance) affect google search rankings?

    I can't speak to what the migration will be to another provider, but my experience moving from WordPress to Blogger was relatively painless in terms of search rankings; you'd probably need to use .htaccess redirection to preserve links and inbound traffic, and you'll also want to configure WordPress's permalinks to match Blogger's permalink structure (which is doable). But that's beyond the scope of what I can promise.

    That said, our migration tool *will* address preserving pagerank and overall indexability of your content (as outlined in the actual post above), should you choose to stay with Blogger.

    4. Will I finally be able to have the "older posts" and "newer posts" links with this move? A major annoyance in the current system, which had me considering WP for my larger blog.

    Yes. And much, much more. Basically all feature development over the last 3-4 years has been focused on our own environment, which meant we were unable to offer FTP users any significant new functionality in that time. Most users familiar with FTP are pleasantly surprised at how much more capable Blogger is when publishing to Blogger servers; Kent Newsome's experience last week is one example of that.

    ReplyDelete
  93. My biggest problem is I embed a lot of PHP in both my template and my posts. I could probably get away with removing the PHP from the template but for the posts I use it to do such things as read in tables from csv files etc. One solution may be that instead of inserting PHP code in my posts I change the PHP to output Javascript instead of HTML and use a < script src=http://www.domain.com/xxxx> tag. So my blog would be hosted with Blogger and my PHP still hosted by myself.

    Is this solution workable? can we embed script tags in posts when using blogger custom domains? Will Google still index the javascript generated content?

    thanks
    Gary

    ReplyDelete
  94. @Gary Yes, you can insert javascript in posts. While the Google crawler does read javascript, it does not execute and index the contents of the javascript.

    ReplyDelete
  95. Thanks for the rapid response Rick. When you say Google does not index the contents of the javascript, does that include where it'd simply be a single document.write that's outputting html?

    cheers
    Gary

    ReplyDelete
  96. Thanks for the prompt response Rick! Can't wait to read your blog post tomorrow.

    If the migration tool is going to do more than 301 redirects etc, then I'll wait 'til it is released.

    In the meantime(after I've read ur post), I'll test out this move on a smaller blog, one which I'm not too fussy about, in terms of search rankings etc. As with all my blogger blogs, I host my own images etc, so should be fairly straightforward and it is already on a sub-domain, doesn't have that many blog posts etc.

    Actually looking forward to playing around with this. All I need is an excuse and the closet geek comes out.

    Thanks!

    ReplyDelete
  97. This is sch a dumb corporate style move. I have been with blogger for over 5 years and push ftp to my own server. How much resources can it take to send XML to my server? I would pay you $10 a month for this.

    Will I lose any of my post URLs in this migration and will I have to change ANY of my URLs? If the answer is YES, then I am gone.

    ReplyDelete
  98. I don't see my earlier comment addressed, so forgive me for repeating it, but I need to understand how this is going to work.

    One thing I'm trying to understand that I don't seem to see addressed in the FAQs -- my blog isn't just a blog, I have numerous subsites attached to it. The blog appears as my homepage, but it leads to a number of other pages (subdirectories on my site) that aren't Blogger-published. These (and my blog) are hosted on a service that I pay for. So if I bring my blog over to a Custom Domain and reset the DNS for the site's homepage, is it possible to maintain those subdirectories where they were? I'm worried that if I assign the DNS to a Blogger address, I may be causing trouble for updating the rest of my site by FTP, or for accessing it.

    In case the example isn't clear, my homepage, containing the blog, is at http://www.mynonurbanlife.com/
    That links to several subdirectories, such as my genealogy pages at http://www.mynonurbanlife.com/familyhistory/genealogy.html and local history pages at http://www.mynonurbanlife.com/familyhistory/localhistory/localhistoryindex.html. I'm not sure that resetting the DNS won't screw things up for me, since I've never had a site that was hosted on different servers.

    ReplyDelete
  99. I am not computer savvy but have been using FTP since 2006 and know no other way to do it. I already have my domain and have 2 years paid hosting with GoDaddy. I tried to back up my blog with the export thingy and my computer has no idea what to do with the files and I do not know what to tell it to do (mac 0S)...Like I said NOT computer savvy. I just know how to upload things to my server and to link them in posts and in my template. I do not want to lose my domain but have no idea what any of this will mean to me. I need a step by step and many more details because pretty much none of this makes any sense to this admittedly computer-phobic-techno-dummy. PLEASE, PLEASE, Help me???

    ReplyDelete
  100. Oh and I think I have a similar set-up as the commentor just before me...my site is my blog. Capturethisphotography.com ...then I have tabs set up to go to other content stored on my server and as pages withing my blog.

    ReplyDelete
  101. The more I read the more confused I get. Please allow for FTP...seems there are at least a few of us who are in the same boat and would even be willing to pay for the FTP to remain the same....

    ReplyDelete
  102. Well, I have jumped through all the hoops and set up a test blog. It is supposed to be located at http://sandbox.eveliensnel.com

    However, when I try to access it, my normal homepage at http://www.eveliensnel.com shows up, not the front page of the test blog.

    Even when I add a new posting to force some output, and try to view it from the "Edit Posts" page "View" link (at http://sandbox.eveliensnel.com/2010/02/lets-force-some-output.html ) it does not show, I get a 404 error page instead.

    Is the server at ghs.google.com not up yet? When I try to ping that, I get a reply from ghs.l.google.com [74.125.77.121]

    ReplyDelete
  103. Are there any plans in place to allow FTP service if we are willing to pay for it? I host my site and blog on my own servers that I can manage and I have no intention of moving any content to some other servers hosted and managed by someone else. Without the FTP publishing I'll have to find a new way to publish blog/RSS content, but I'd really like to stick with Blogger and I'd be willing to pay for the service. How about a "premium" account or something?

    ReplyDelete
  104. Carl summarized my exact issue perfectly... that's the question I'd really like to see addressed clearly (either in the FAQ post or here).

    http://blogger-ftp.blogspot.com/2010/01/migration-tool-overview.html?showComment=1265196557092#c3741079269363347819

    ReplyDelete
  105. We have been using blogger since 2004 and this announcement is most troubling. How much trouble is ftp publishing really causing Google? Maybe you can charge users a fee and continue to support bloggers that still need to use ftp?

    Snip from Alard from another post.

    http://blogger-ftp.blogspot.com/2010/01/deprecating-ftp.html?showComment=1265211930426#c1543828611699838510



    I don't want to fragment my content, scatter my users onto multiple sites, fragment my web statistics, remove my blog from my robust on-site search capability, cause search engines to direct our traffic to other-than-our main site, screw up our URL pathing methodology, etc, etc, etc, etc, complicate our navigation and maintenance, and so on.

    ReplyDelete
  106. Well, I guess it's time to start blogging about this stupidity...

    http://9TimeZones.com/s/2010_02_01_.htm#G

    Google dumps "Don't be evil."

    [Re: Google's motto.]

    I just received an email from Google (which owns Blogger, the service that publishes this blog), and it contains a nasty bit of news: Google intends to shut down FTP (file transfer protocol) service sometime before the end of March.

    To the casual reader, this probably doesn't seem very earth-shaking. But for me, and millions of other FTP bloggers, this decision will cause major disruptions and precipitate a lot of unnecessary work on architecture, links, etc.

    And after all that effort, our blogs still won't work right.

    For example, if you've installed a link to a particular posting in this blog, it will probably generate an error message after March 26, 2010.

    I've published all of my blogs with FTP for the last six years, and the system has worked reasonably well. Google justifies this drastic FTP move saying that "only .5% of active blogs are published via FTP." Hm, .5% sounds like an insignificant number... but it actually represents millions of blogs.

    Google also complains that maintaining the FTP service "would require that we completely rewrite the code that handles our FTP processing." Aw, those poor overworked Googlers. Maybe they need to take a few days to: leave their dogs at home, step away from the foosball tables, and stop guzzling so many free sodas... then they might be able to actually do a little work for a change.

    I design free add-ons for Open Office Writer, an open-source word processor. I don't get paid for creating these Screenwright(R) extensions; I do it because I want to help other writers. There have been only 85,927 downloads to date, so my formatters don't serve nearly as many people as Google's Blogger does. But if I announced to my users that the next release versions of Screenwright(R) would not be backwards compatible, they would start calling for my head. And if I claimed that my reason for flouting this basic tenet of good software design was because I would need to "completely rewrite the code," there would be a lynching party on my doorstep in ten minutes flat.

    It sounds to me like Google needs to work a little harder at that "not being evil" thing.

    ReplyDelete
  107. And tweet: http://twitter.com/acbaird/statuses/8594384128

    #Google dumps "Don't be evil." (#Blogger discontinues #FTP after March 26.) #BloggerFail #GoogleFail #ftpFail #KeepFTP http://is.gd/7CNFy

    ReplyDelete
  108. @Gary Correct, it does *not* index content written by the javascript.

    @Global Status Reporter: Using the migration tool, your post URLs will be preserved.

    @Carl: You can keep www.mynonurbanlife.com where it is, and set up a subdomain for the blog. (blog.mynonurbanlife.com?) That will leave any files in subdirectories off of www.mynonurbanlife.com alone.

    @Laurie: The migration tool will be exactly what you're looking for: step-by-step guided walk-through to convert your blog.

    @Evelien: I'm seeing your test blog just fine, it was likely just a slight delay for your ISP to update the new DNS settings for you.

    @Nate: No, we are not considering a paid FTP option.

    ReplyDelete
  109. I cannot even figure out how to use the export blog thing to back up my blog now...and you expect me to have faith that the migration tool will be any better? Remember TOTALLY computer illiterate here. I do not even know what a sub-domain is or how to set one up. I only know how to upload onto my server and make folders of which there are a bazillion that are there that "came with it" when I first started using FTP.

    ReplyDelete
  110. Our current blog is at www.domain.org/blog.

    If we choose to create a CNAME (blog.domain.org), will this hurt our SEO?

    ReplyDelete
  111. Web logs issues? My current blog is at www.domain.org/blog and all traffic to both my blog and the rest of my site is captured in my web logs. This change will effect my logging and statistics capturing. How will this be handled if my webserver is no longer hosting and logging my blog pages?

    ReplyDelete
  112. @Dan: Your logs will not have visibility into our server activity. Site analytics tools like Google Analytics, SiteMeter, etc. will allow you the ability to track pageviews, but raw logs access is not something that will work in this environment.

    ReplyDelete
  113. Hi again Rick,

    In your answer to Carl, you said:

    "@Carl: You can keep www.mynonurbanlife.com where it is, and set up a subdomain for the blog. (blog.mynonurbanlife.com?) That will leave any files in subdirectories off of www.mynonurbanlife.com alone."

    My situation is the same as Carl's, but my biggest concern is not being forced to change my blog's URL from www.myblogname.com to blog.myblogname.com. I need to know if there is a way to do this without being forced to make that change.

    ReplyDelete
  114. The blog IS my home page, it's what's delivered when you enter my domain, so setting up a subdomain for it doesn't work, because that means I have to redesign it as a separate page. Not what I want.

    ReplyDelete
  115. What if I want to keep my blog data on my server and not yours? Can I have my blog moved to a me.blogspot.com address, and mirror it myself (pull from my server instead of push from yours) to my local server and continue to use my custom domain as it is currently configured?

    ReplyDelete
  116. I have not found anything about using a custom template. I maintain a blog for a client and have customized the sidebar with several links and photos. Will I still be able to customize the sidebar using the template tab as I have been doing? The blog also has a custom footer with links to the client's website, will that stay in place?

    Will this change the look of the current blog in any way? (my client is very particular about this)

    www.greenconsciousness.org

    ReplyDelete
  117. @sjhollist Not aware of a setup that would work the way you outline. Will share one if someone else documents such a setup.

    @sirius Your custom template will not be affected.

    ReplyDelete
  118. I've been on Blogger since the beginning ...Blog Spot before that... I flow the text though Blogger and directly upload (FTP) images to my domain...using Live Writer for the layout etc. It is great not having to maintain a data base and the security... But what is getting missed here is; IF you have a following in China (we have over 50% of our page views from there)...or IF you EVER want to have readers in China, migrating to a Google server will drop you off the internet for the largest potential audience in the world...

    ReplyDelete
  119. Hi Rick,

    I see you are very busy and I wrote here late last night, so you may have missed my 3 questions. I'll be succinct this time.

    Q1 - After reading this post and comments, I logged into my cpanel and created a subdomain for my blog.

    I did not change anything, my blog has always been an ftp blog located at http://www.mississauga4sale.com/blog/ and when I created the subdomain blog.mississauga4sale.com then browsed to http://www.blog.mississauga4sale.com/ my blog appears! What causes this? I did not change any of the DNS settings in my cpanel or anything, all I did was create the subdomain blog for my domain mississauga4sale.com

    How did the system resolve mississauga4sale.com/blog to blog.mississauga4sale.com to my blog?

    Q2 - I think this is obvious, but need to know.

    I should wait for the migration tool to be published in mid February before I do anything, correct?

    Q3 - Will my new blog at blog.mississauga4sale.com be automatically under the Layout format rather than the Template format? And if so, then I can add widgets and such to my blog? If so, this will make me very happy!

    Thanks again
    Mark

    ReplyDelete
  120. @Mark 1. Generally speaking, CPanel will alias a subdomain to point to a directory on your server. You'll want to follow the directions to ensure you're setting up a proper CNAME with your domain registrar (who may not be your webhost). More here. 2. Yes, we think we'll have just about everyone who wants to migrate to the new setup covered when the tool is available. 3. No, you won't be forced to upgrade to Layouts, but we make that a straightforward couple-clicks option.

    ReplyDelete
  121. I noticed in the above step 2, there was no mention of a how to migrate to a custom domain. I assume that will be an option to migrate your existing blog to corrrect?

    ReplyDelete
  122. @Rick OK, thanks Rick, good luck with the FAQ's and the launch, looking forward to finally using widgets! :-)

    Mark

    ReplyDelete
  123. Hi Rick

    I hope you will respond to my comment. I run a review website where I review products. The way I have been doing it is I would create a static page for the review which would stay on my host and then I link to it through blogger. I want to move over to using the custom domain. So what would be the best way of getting these files into blogger. I thought of going back and redoing them one at a time as a post. But I want the older ones not to show up as new posts. I guess I am just looking for the easiest way to transfer all the content to the new system. Any help would be greatly appreciated.

    Jason

    ReplyDelete
  124. ok...I had a lot of help and managed to do the switch over...but now only some of my posts work and some do not...I did everything as was told and it sort of works but many links are now broken. I have "previous / next" navigation under my images and many of them ar now broken. They were just fine prior to the change. Please help. I tried republishing some of those posts and still get: Page not found

    like this one: http://www.capturethisphotography.com/2009/11/bedazzled-II.html

    but not for this one: http://www.capturethisphotography.com/2009/11/bedazzled.html

    this is happening with many of my posts with apparently no rhyme or reason.

    ReplyDelete
  125. oh I should mention I have over 650 posts...so figuring out which ones are broken and which are not is daunting...also they do show up when I click "view post in the dashboard edit posting pane where it shows all the posts.

    ReplyDelete
  126. Oh and I can view them if I type files.mydomain.com So is it some issue with the redirect?

    ReplyDelete
  127. I'm running an FTP blogger account, which follows the http://www.mysite.com/blog format.

    In the interest of maintaining the blog within the structure of the site, could i set up the /blog directory as a 'virtual directory' and then point this to the new domain (http://myblog.blogspot.com)?

    Has anyone managed to integrate a Google hosted blog into their excisting site using virtual directories?

    Thanks,

    Marco

    ReplyDelete
  128. This is so frustrating...all the posts are there as I can check with this site: http://photos.vfxy.com/photoblogs/3972 by clicking on the image thumbs...but the previous / next is broken on many of them...gah what is going on?

    ReplyDelete
  129. @Rick when we switch from www.mydomain.com (FTP) to www.mydomain.com(Custom Domain), the previous archive and label pages are lost and many of the google indexed pages would give 404. So hope you people will do a fix in redirecting such urls to the corresponding new archive/label urls. Here are some google indexed pages which now give 404 after the migration. (results may get deindexed when you read this :)) - Google Search Result page

    ReplyDelete
  130. Aneesh figured out my issue...blogger is case sensitive so any of my links with caps are now broken...gonna be a LOOOONG time fixing that. :(

    ReplyDelete
  131. Does anyone out there know of another service, utility, or software package that generates an ALL-STATIC-PAGE-BLOG like BLOGGER does?

    Wordpress and other alternatives to bloger all seem to force one into a dynamic page paradigm, which for reasons too plentiful to explain here, is (for my purposes) another big loser.

    ReplyDelete
  132. we have 8 different ftp published and established sites and wanted to know if we can keep the same domain for example garagesalestracker.com/blogger/index.html
    Will we still be able to retain the domain name and just change the publishing process?

    ReplyDelete
  133. Well, I repointed the nameservers and that seems to work. I have no idea how to actually set a subdomain and nowhere does it tell me what should be put there, I guess a migration tool would be helpful. :(

    I guess I have to figure the last 2 years of work is just screwed and no I start from new. Whatever...

    Here is my real issue. I used to pull from RSS to post on my website as an update, and previously the entire post and photos would pull.

    Now all I get is a the Title and that is it.:(

    How can I fix this?

    ReplyDelete
  134. @Rick - I currently use FTP primarily becuase I use a lot of images. My Picasa albums quota is already full and none of those images are on my blog. I primarily post blogs from Picasa or from my mobile phone. Will I still be able to use Picasa to post blogs to custom domains and have my images automatically upload to my webserver? Would you guys consider maintaining at least a partial FTP integration that pushes images to my server while hosting the blog on blogger's? I don't want to pay for picasa space when I have a perfectly good webserver with gigs of space. thx

    ReplyDelete
  135. So when is this tool going to be ready? Or is it ready already and I am too stupid to find it?

    ReplyDelete
  136. @Rick, thanks for answering these comments personally, it's appreciated.

    I have been using ftp at matthewhunt.com/blog and I understand how to switch to custom domain at blog.matthewhunt.com, that's no problem.

    However, I'm not sure what to do about all the links in my blog posts. In many posts, I link back to other posts using the full URL, e.g. http://www.matthewhunt.com/blog/2010/01/aftenposten.html. After custom domain changeover, is there any way to modify all these links to blog.matthewhunt.com... without editing each post manually?

    ReplyDelete
  137. Well done Google - you certainly know how to upset your users.
    5% of Blogger blogs must be an awful lot of people!
    You have failed miserably to consider those of us who like to have a blog as a sub section of our main site!

    looks like I'll be switching to wordpress then
    - and Bing!
    bye bye!

    ReplyDelete
  138. im very very sad about this bad news blogger is giving to us. ftp publishing rocks very hard. i hope any other company activates something like that soon so i can use it. custom domains are not the same thing and they require differente soft-hard setting... i have more than 50 blogs working via FPT its a bad news for me,....

    ReplyDelete
  139. @Nodomutante - Agreed - this sucks very much - ftp publishing was the only thing that would allow any type of individuality - now all Blogs will all be basically the same page with different stuff turned on.

    ReplyDelete
  140. Ok... I LOVED FTP publishing, but alas, I understand Blogger's request.

    That said, I moved to a custom domain today to help out. Now, almost 3/4 of the images that were on my site (mypicsof.us) are broken links.

    I have no idea how to fix this.

    ReplyDelete
  141. @TC - The images are now hosted on your server and www.mypicsof.us is mapping to google and not to your server. So the images are unavailabe. To fix this you need to create a subdomain like images.mypicsof.us(uder your hosting panel) and move all files/images in your domian's root directory to this subdomain's root directory.

    You have already setup the missing files host.So this is the only thing left.

    ReplyDelete
  142. @GST as far as i know, you wont be able to preserve the urls. But you can host each blog at a separate sub-domain and the blogger migration tool will assist you in redirecting the old links to its new location

    ReplyDelete
  143. I want to be clear: I have an FTP blog on a hosting service with a simple domain. I want to keep the domain. You are saying that blogger can take over the domain, with only the wrinkle that the blog will become a sub-domain, i.e. blog.domain.com? Or are you saying that the hosting service will still have the domain, and we must create a subdomain that blogger will somehow know about and manage.

    I have second situation where the blog already resides on a subdomain, sub.domain2.com, and the first blog has many links to it. What happens there?

    It would be helpful to have the full documentation on the tool ASAP.

    ReplyDelete
  144. you can move www.yourdomain1.com(FTP) to www.yourdomain1.com (CustomDomain)

    you can move sub.domain2.com(FTP) to sub.domain2.com(Custom Domain)

    So it will preserve links.. hope it explains

    ReplyDelete
  145. right now I have blog is published to a path under a domain that I work with (i.e. www.mydomain.com/myblog

    I see that I can set up a custom domain if the address was http://myblog.mydomain.com...

    ...but will it be possible to have a custom domain that ends in a path, as in my current setup?

    ReplyDelete
  146. @Cory - custom domain can run only at your root domain(www.yourdomain.com) or at some subdomain(subdomain.yourdomain.com). It can't work the other way like www.yourdomain.com/blog. You can move the blog to some subdomain like blog.yourdomain.com and Blogger's migration tool will help you in redirecting www.yourdomain.com/blog and its pages to the corresponding ages on blog.yourdomain.com .

    ReplyDelete
  147. this is a complete joke

    google: think again. you are making a mistake!

    ReplyDelete
  148. i'm surprised to read on here how so many people who use google's ftp publishing are so languid about this.

    this is google imposing onerous new terms on its customers. we're the reason google is huge and powerful and this impositition appears to be the beginning of a new google.

    well, google, when you lose customer loyalty and go the way of AOL you can think back to decisions like this.

    ReplyDelete
  149. I have a question about redirecting my old blog post URLs:

    buzz.blogger.com advises sing .htacess:

    RewriteEngine On
    RewriteBase /
    RedirectMatch 301 ^/blog/(.*)$ http://blog.yourdomain.com/$1

    and this works for me, but the problem is that it also tries to redirect image files which are still stored at blog/images/. How can I modify it to ONLY redirect .html files, or to EXCLUDE these folders:

    blog/images
    blog/text
    blog/video
    blog/data

    ReplyDelete
  150. Hi.

    1. I already have my blog in a subdomain. The URL of my blog is http://blog.datamanagementsolutions.biz/dms.html. How do you recommend I should handle this?

    2. I use Windows Live Writer (sorry if that's a dirty word) to write and publish my blog posts, and I wish to continue to do so. Do you expect that will be possible?

    ReplyDelete
  151. I have been using FTP for 3 years and have over 1000 posts:

    1. A month of notice? This is not acceptable, respectful or even profesional. I only received notice one or two days ago.

    2. I will not change my URL.

    3. I will not let Google host my content on it's servers due to abysmal and abusive terms - the original reason for using FTP in the first place.

    So then, what options do I have to continue unaffected?

    ReplyDelete
  152. Blogger just lost another long-time user; I will not put all my critical content on servers outside my control.

    I refuse to believe that FTP service is an insurmountable burden to the Goliath tech company that is Google. "Equipment being decommissioned..." PLEASE.

    Commission some new equipment, then, and do FTP right from the ground up.

    Or, you know, be evil. Whatevs.

    I am moving on to another platform, which will be a giant headache, but at least what's mine will stay mine.

    ReplyDelete
  153. This comment has been removed by the author.

    ReplyDelete
  154. I have my own domain and ftp two blogs to two directories. E.g. me.com/familyblog me.com/newsblog
    If I understand things right I can migrate both to blogspot.com (e.g. me-familyblog.blogspot.com and me-newsblog.blogspot.com. But I cannot redirect back to me.com/familyblog and me.com/newsblog because directories are currently not supported by the migrate mechanism.
    Instead I have to redirect to a subdomain (e.g. familyblog.me.com and newsblog.me.com).

    That's do-able. But is there a reason why subdirectory redirects are not supported?

    ReplyDelete
  155. "Rick Klau said... @Admin We've been given a hard internal deadline for infrastructure that's being decommissioned - when that decommissioning happens, we lose our ability to publish via FTP. Would I have liked to have the tool done before making this announcement? Of course. But the timing was just not possible - we announced as soon as we knew the plan, and are working furiously to get the tool done and in users' hands so that they can migrate seamlessly."

    Thanks for replying, but the internal deadlines are set by Google, so that simply won't wash. If the tool isn't ready yet, then it may not be by Feb 22, so will you extend the deadline beyond March 26 if that's the case? I suspect we know the answer already. This is turning into a PR gaff on Google's part. Been quite a few of them lately, eh?

    ReplyDelete
  156. @Mathew Hunt
    Try this

    RewriteEngine On
    RewriteBase /
    RewriteRule ^blog/(images|video|text|data)/(.*)$ - [L]
    RewriteRule ^blog/(.*)$ http://blog.yourdomain.com/$1 [R=301,L]

    ReplyDelete
  157. Still no help here?

    I have a blog at www.birdmanblog.com that I used FTP publishing for. I have moved it to a Custom URL and the CNAME is setup and working properly.

    I set up a subdomain at find.birdmanblog.com and set up the Missing Files deal at that subdomain but all my photos are still not found and show a DNS error. (The 2 most recent posts do work, but they are after the change.)

    Any help or should I just go find another way to post my blog?

    ReplyDelete
  158. @Birdman,
    you have to create a subdomain find.birdmanblog.com from your hosting panel. Once you have created it, you have to copy the folder named uploaded_images from your old FTP publishing location to this new Subdomain's root folder. To explain it more clearly you image should be available at http://find.birdmanblog.com/uploaded_images/Spotlight-739955.jpg :) Once this is done, all your images will show up on your blog.

    ReplyDelete
  159. @aneesh

    As I previously stated, I did that and it does not work.

    ReplyDelete
  160. @birdman - if you had successfully created the subdomain and moved the folder to there, then the imgage url in my previous comment would be accessible but it is not.

    Did you change your domain's Name Servers? If you did then it would be the problem.

    ReplyDelete
  161. @aneesh

    I had to change the Domain's Name Severs per Blogger's directions?!?

    The FTP guidlelines were simple, this....not so much.

    ReplyDelete
  162. @Birdman -
    the blogger guys had actually asked you to create CNAME and A records, not to change the Name Servers. Are you sure that you changed it ?

    ReplyDelete
  163. @aneesh

    I'm sure it is not correct! LOL

    I sent Dotster Customer Service the directions and they helped change what was changed, which is obviously wrong. :(

    I am unsure how to create a CNAME or where, on CPanel on my server or On the Domain registry page?

    At least I know I have the info, just a matter of allowing the rest of the world to see it.

    BTW, thanks for your help so far!

    ReplyDelete
  164. @Birdman - actually you contacted the wrong guy..
    Doster is your domain registrar and if i am right you should have been using some other webhost. You should have asked your webhost and not your domain registrar :)

    Login to your Doster Domain Name Control Panel and provide your Hosts's Name Servers there.(your host will help you with the name servers) Once you have done that ask your host to create the CNAMEs and A Records for you.

    ReplyDelete
  165. @aneesh

    OK, I found that on CPanel.

    One last question and I think I'll be good. (OK 2)

    Should the find folder be in the HTML_Public folder or at the root? And does it only need the uploaded_images folder or everything?

    ReplyDelete
  166. @Birdman - it should be moved to the main directory of the subdomain it would probably be public_html/find .Images published via blogger are present in this folder(uploaded_images). so it would be enough. :)

    ReplyDelete
  167. I have about 10.000 posts in Blogger, but I can only export 5.000. Will the migration tool handle this?

    ReplyDelete
  168. The reason i chose blogger in the first instance, was because it allowed me to create a blog within my existing site structure.

    Will google apply the same weight to the inbound links which will now point to http://blog.site.com as those i have spent most of my time establishing for posts within http://www.mysite.com/blog?

    Will we be penilised for decreasing the number of pages from our existing domain? or even loose long tail term visibility?

    Can we introduce canonicalisation to the pages we're being forced to relocate or will we then be upseting google's spaming team?

    Though i can completely understand Google's needs to evolve, i feel some element of backwards compatibility (directory level custom domain) would be the minimum they could do for their existing users.

    Some detail on the effect this change will have on our exiting natural rankings would be most appreciated, even if to prepare us for the drop.

    ReplyDelete
  169. I manage 100 or so blogs for volunteers travelling abroad through my organization, Earthwatch. About 20 of them are new blogs and maybe a handful still use their blogs after travelling so I won't need to keep all of them but it would be nice. We publish via FTP and realize we will have to switch to custom domain. However, will I have to individually switch all these blogs if I want them to still function? Is there a way to use the tool you've created to switch a couple or all at once using the same protocal for each? Thanks.

    ReplyDelete
  170. very good question earthwatch, really. i have the SAME problem, i have to migrate 50 blogs and to individual domains?? i used to have them in different folders at the server...!! heeelp! thanks

    ReplyDelete
  171. I'm using a co.cc domain. Is there any way to make a co.cc subdomain (sub.domain.co.cc) and point that to blogger?

    ReplyDelete
  172. Very annoying. I guess we're getting what we paid for. Like I've got time to do this for 25 different blogs.

    How about giving us FTP people the old code that we can install on our servers and let us deal with our own technical problems?

    If not, I guess it's time to upgrade to Wordpress. Sigh.

    ReplyDelete
  173. What should be done for a client like: http://www.CoopersPick.com/blogs/nfl/ ??? change it to blogs.CoopersPick.com/blogs/nfl ???

    ReplyDelete
  174. does anyone know how i can integrate a php based wordpress blog into our existing .net based architecture?

    would a virtual directory do the trick?

    ReplyDelete
  175. LAME. Thanks for messing with your best users Google. Sounds more like a Microsoft move. I won;t go through THIS hassle, easier to find another company that doesn't alienate users for greed.

    ReplyDelete
  176. I'm a longtime Blogger user who started out using dotcomments for my commenting due to no comment support in Blogger at the time. Am I just going to lose all of my comments or is there any way to get them imported into my posts?

    ReplyDelete
  177. Hi,

    I am a little nervous about this whole migration thing, namely because I am finding it impossible to do a simple download of my FTP blog. When I follow through the standard steps, I download an XML file that is empty and is 0K in size. It is a pretty big blog, about 1600 posts.

    I have submitted this question to a couple of forums including blogger's but no specific help yet and none of the suggestions for other people have worked for me.

    ReplyDelete
  178. I think I have just found the answer!!!

    OpenSource .Net blogging platform.

    http://dotnetblogengine.net

    ReplyDelete
  179. No, the correct answer is for Google to leave FTP as an unsupported option for the 90% of the .5% who have NO problems with FTP (according to a post by a Google tech elsewhere on this blog).

    Please.

    ReplyDelete
  180. Hi all - just noting that the FAQ is updated, addressing a number of recent questions raised on this and other posts.

    ReplyDelete
  181. I currently use FTP to put my blog on my own website domain (jimoberst.com) on its hosting servers. I actually use it as a "what's new" page on my website. It is Watercolors by Jim Oberst at jimoberst.com/blog.html. It's fine with me to transfer this "page" to blogspot... I've reserved a new blog with the same name at "jimoberst.blogspot.com". What I'd like to do is just move all of my blog to this new blogspot place, and then I'll just steer people to it from jimoberst.com, and steer people to jimoberst.com from jimoberst.blogspot.com. This is what I do now, by including the blog page in my website page menu, and by having my website page urls on the blog page. Questions:
    1) I'm using an old template that I modified to contain these page urls and other things, and to make it look like the rest of my website. Will my "new" blog keep using that, or will I need to switch to a new "standard" template?
    2) Can I somehow just publish all my old blog posts to my new jimoberst.blogspot.com blog, and drop the old one? Essentially nobody goes to my old blog directly, only through my website, so I don't think I need to worry about all the "redirect stuff" you're talking about here... do I? Or, I could just "bounce" people from the old blog address to the new one.
    3) Above I see people talking about image storage. What's that about? Do I need to provide some separate place for image storage, or will blogger just store them for me?

    Thanks!

    ReplyDelete
  182. Many of my blogs are being published with a index.php and archive.php format. When the migration tool is ready, I hope it will support these php file types besides the htm and html file types for the automatic transfer to the new blog location.

    However, I use a lot of "php includes" files for menus within the blog(s) themselves. I suspect there is no way around using php includes within the new XML Blogger templates, Blogspot.com hosted, or "myowndomainname . com" custom domain name published by Blogger. Which I guess that means customizing lots of new templates and using other things like JavaScript for certain includes and/or custom CSS for various different dropdown menus. However, the php includes were very search engine friendly and JavaScript is not at all search engine friendly.

    Any ideas would be appreciated.

    Thank you.

    Regards,

    Jim W.

    ReplyDelete
  183. @Rick Klau. I am an newcomer to Blogger. I currently have a website but would like to incorporate a blog as my new home page. Since ftp is no longer an option, I have been following instructions and have created a CNAME for my site (blog.thefancybird.com). When creating the ANAME, the directions say to point to 4 IP addresses. My hosting/domain registrar only allows for 1. Will the be an issue?

    ReplyDelete
  184. thanks marcobarra, that is looking like my best bet out of this mess.

    ReplyDelete
  185. I'm missing just ONE step in changing over here. Moving a simple, non-photo-intense, blog from my domain's host to Blogger, all the DNS stuff makes sense, I know about .htaccess redirects, etc. etc. I'm just not seeing where in the process all the past posts that currently "live" on our Ixwebhosting site get transferred to Google so that all Kim's past postings are still accessible. The export/import tool seems to just deal with settings and info, how do I get the old postings moved?

    ReplyDelete
  186. I think I already know the answer to this question, but... My blog has some posts with images hosted on picasa (from before I was hosting on my own server via ftp) and some posts with images hosted on my own server. The MAIN problem is that the domain name I had lapsed and before I didn't renew it in time to avoid "minimum bid $1000!" Riiiiight... So, now I have a blog where 1/4 of the images point to picasa, and the other 3/4s point to a domain that no longer hosts the files! I have all of the files, but the links are all whacked out. To compound the problem, I used to host the blog at blog.myolddomain.com, but now I want it to be at www.mynewdomain.com... I am guessing that this is going to simply require a TON of work on my part, yes? No chance of shnazzy automated code reworking here? Thought so...

    ReplyDelete
  187. @metempsychosis: Your best bet would be to download a full backup of the blog (it's an XML file). With a text editor, do a search/replace for the image URL strings that are broken (img src=http://blog.myolddomain.com/...) and replace the broken strings with the new URL pattern (once you've registered the new domain). Then import the updated export file into a clean blog, and publish that to your new domain. That's the best I can think of given the situation you're in. (One silver lining: since you can't publish to the old URL, there's really no point in trying to redirect traffic from the old URL so you can just start clean at the new URL.)

    ReplyDelete
  188. I've seen some other people are having this problem, but I haven't been able to find a solution anywhere...

    I've used the missing file host to forward www.bensoncomics.com addresses to images.bensoncomics.com addresses.

    As you can see, it works with some of the links, like this one:

    http://www.bensoncomics.com/exists/exists01.htm

    But with others it doesn't work:

    http://www.bensoncomics.com/2010/02/bensonthanks.gif

    (If you replace the "www" with "images" in that second link, you'll see that the file is in fact there and should be viewable.)

    Anybody know what's going on with this?

    ReplyDelete
  189. @Rick Klau.my current blog page is at "www.yourdomain.com/blog" once migrated accross this will become "www.blog.yourdomain.com" How will this affect inbound links and internal link structure from non blog pages on the same domain?

    Can you also please clarify the insert image issue? (how will it differ from how it works right now)

    In an earlier comment you mention a "refresh" tag which will forward to new URL. Wouldn't it be simpler to do a 301 redirect?

    The May 6 extension is welcome news, but with loads of sites to migrate I'm keen to start sooner rather than later.

    ReplyDelete
  190. @The Editor: If you are migrating manually, it's up to you to handle redirects. .htaccess (using 301 redirects) is probably the most reliable answer. If you are using our migration tool, we will be using a combination of rel=canonical and meta refresh, as there was no way for us to guarantee that .htaccess would be available to us in all cases, and we needed to build a tool that would reliably work for all users.

    Re: non-blog pages on the same domain, you can either use the missing files host to address that, or use .htaccess to redirect those requests to valid URLs.

    Insert image integrates directly with Picasa, so images uploaded through that mechanism will be uploaded to your Picasa account

    ReplyDelete
  191. @bensoncomics: The 404 page I see when I connect to images.bensoncomics.com is being generated by Google, so I suspect that you've pointed the CNAME for images to us, when it should be pointing to your webhost.

    ReplyDelete
  192. Rick, I have still gotten no guidance on my problem exporting my current FTP blog: a blog with 1600 posts downloads as an empty xml file. I am getting nervous because others have been waiting for months for a fix.

    Poking around I notice that on the dashboard under Settings>Publishing it says this:

    You're publishing via FTP

    Switch to: • blogspot.com (Blogger's free hosting service) • Custom Domain (Point your own registered domain name to your blog) • SFTP (secure publishing on your ISP server)

    If I switch to blogspot.com, are my switch-over problems over?

    ReplyDelete
  193. I own my domain and won't have a problem creating a subdomain; however, for the past few weeks many readers have been complaining that my blog page won't load for them. This isn't a browser issue since these readers are using IE, Firefox, Safari, primarily. I've noticed that there are some new changes on Blogger, vis a vis image uploading, automatic time publishing, etc. Could there be a conflict here?

    ReplyDelete
  194. @Marilyn: If you're currently using FTP, then this can't be us. Likely your webhost.

    ReplyDelete
  195. Sorry but you have a huge flaw. The EXPORT tool doesn't work for large blogs. There are 200+ posts on your help forum and no working resolution. Posts are exported but the comments are not. (I've got over 800 posts, and 400 comments, 240 on one post). Only the 200 MOST RECENT comments are exported. It's really frustrating as I have a popular blog (yay) and have no way to back it up reliably in case your migration tool doesn't work (and I don't expect it to work based on what I've seen). I'm really wanting to bail on Blogger due to my ongoing frustration, and I can't even do that.

    ReplyDelete
  196. @Rev. CMOT: The export bug was confirmed by our QA team earlier in the week, and we expect a fix for it next week. Rest assured that we will not lock you in to staying on Blogger; if the problem persists beyond next week you can contact me directly (rklau at google.com) and I'll get one of our engineers to manually recreate the export file. (I don't expect we'll need that though, we're pretty sure we know what's causing the export problem.)

    ReplyDelete
  197. Rick,

    Note that my FTP blog has 1600 posts and exporting produces a completely empty xml file.

    http://tinyurl.com/avjvz/

    Had I but known what a monster this would turn into! :-)

    ReplyDelete
  198. When I export my blog (FTPd to my own site) by clicking "export blog" on the Basic page and then click DOWNLOAD, I get a zero KB download. What's up? This needs to work for me, and it isn't now!!!

    ReplyDelete