We will update this FAQ file for questions pertaining to the upcoming shut-down of FTP on Blogger. Please see the blog for the latest news/updates on the migration from FTP to custom domains.
  • Will I lose any data?
    • No. All blog posts continue to be stored in Blogger’s system, and will always be available through the UI.
  • Does this include SFTP?
    • Yes.
  • How much do Custom Domains cost?
    • It is free to host your content on Blogger.
    • To purchase a domain name for your blog, visit Settings->Publishing from your Blogger Dashboard.
  • But I need FTP. Can’t you extend it beyond March 26? Why can’t you let the current users continue to use it?
    • No, we can’t. Update, 2/12: We have extended the deadline to May 1. Details here. For a variety of reasons, we made the decision that we will no longer support FTP. Upcoming changes in Google’s infrastructure will render our current approach inoperable, and rewriting the FTP interface to work with the changes did not make sense given the relatively small number of users relying on FTP today relative to the total userbase.
  • My current blog relies on server-side extensions, scripts, or other external functionality that Blogger doesn’t support. Will Blogger support PHP code, server side includes, or other similar features?
    • In those implementations, no. But Blogger’s support for OpenSocial Gadgets and the growing number of third-party gadgets built to work with Blogger provide many opportunities to add to your blog's functionality. If there’s a gadget you want and don’t see, let us know – we often work with engineers and developers who are looking to build gadgets that users want. 
  • I don’t like the Blogger Navbar. Can I turn it off?
    • Yes, details for disabling the navbar are here. Keep in mind, however, that disabling the navbar hides your blog from “Next Blog,” a key tool used by readers to discover new blogs. We also have a number of features tailored to the navbar in the months ahead – we hope that it adds to, rather than detracts from, your use of Blogger.
  • Can I leave Blogger instead of going to Custom Domains?
    • Yes. While we hope we’ve made the transition as straightforward as possible, you can convert to a different Blogging platform. Take your Blogger export file – many platforms can import that directly. If that doesn’t work, Google’s Data Liberation Front has a number of converters to assist in the migration to another platform.
  • Do I have to redirect my old URL to the new URL?
    • No, but if you don’t then you’ll split your blog’s audience and run the risk that they don’t find all of your new content.
  • Why can’t I keep publishing at a sub-directory?
    • The way the system is set up, blogs must be hosted at a discrete domain.
  • How long will this take?
    • The migration tool should make transitioning from FTP to a custom domain take less than an hour (not including DNS changes); if you choose to do it manually, it will vary depending on the size of your blog and the changes to your setup you make. (See Kent Newsome's blog post about his migration, where he concludes that "I can tell you that the process of moving to a Blogger Custom Domain was pretty easy.")
  • If I redirect to *, am I stuck on Blogspot forever?
    • No. You can always update your blog to a Custom Domain, and we will redirect your requests to your Custom Domain.
  • My old FTP host is dead, can I update the old files to redirect traffic?
    • No. 
  • How do I create a CNAME?
    • Our help file for creating a CNAME is here.
  • What about URLs like Will the migration tool support them?
    • Yes. Using rel=canonical, we will redirect the homepage of the blog to your blog's new homepage (at either your custom domain or your chosen URL), and all other pages (individual posts, archives, label pages) will redirect to their equivalent at your new URL.
  • Do I have to move my entire domain to Blogger?
    • No. We will host your blog, other content hosted at your domain can stay as is. The blog's URL must be unique, however. So the blog may be at, while the rest of your site lives at
  • We have three blogs at Can they share a custom domain?
    • No. Each blog requires a unique URL.
  • Will comments migrate?
    • Yes.
  • Are classic templates going away?
    • Not at this time, no. We do provide a mechanism for upgrading from classic templates to Blogger's more modern Layouts (which support drag and drop design, gadget support, and simpler editing of HTML and CSS), but you are not required to upgrade at the time you migrate from FTP publishing.
  • Can I host at, or does it need to be (Naked domains)
    • You cannot host a naked domain with Google, though you may point your domain's A records at our IP addresses so long as both the naked domain ( and the non-naked domain ( are served by us. More on this here.
  • What about archives and label URLs?
    • The migration tool will support redirecting existing label and archives pages to their new counterparts.
  • Will FTP blogs on Windows servers be able to be redirected?
    • Yes. The migration tool will rely on rel=canonical and meta refresh to redirect http requests, which is not dependent on your server configuration.
  • Missing Files Host: will it work for new files, or only old files?
    • It will work for all files hosted at the URL you manage, regardless of when they were uploaded.
  • What if my site is already, can I simply change the CNAME to point to Blogger?
    • Yes. But note that previously uploaded files will no longer be served, unless you configure a secondary CNAME and set up Blogger's missing files host. You will need to migrate manually, as the migration tool will not set up missing files host settings automatically.
  • Can blog and non-blog content share the same domain?
    • No. Blogs must be at unique URLs.
  • Is there an SEO penalty when moving sites?
    • Not with the approach we're using with the migration tool. Other approaches - .htaccess, for instance - are generally safe as well.
  • Will e-mail to Blogger still work?
    • Yes.
  • Are any other file transfer protocols going to be supported in the future?
    • No.
  • My template reference CSS files hosted on my current domain. Will it still work when my blog is hosted by Blogger?
    • Yes.
  • What does this cost?
    • It's free.
  • Will we still support commenting on old FTP blogs should they decide to leave the blog as is?
    • No. You should either look into a third party commenting system that runs independent of Blogger (Disqus, Intense Debate, or Echo are three options that work with Blogger) if you intend to leave the blog as is but want the comments to continue to work.
  • Will we redirect the traffic automatically to the new blog?
    • Yes.
  • Will the page rank and analytics be carried over to the new blog?
    • Pagerank will flow to the new blog; Google Analytics code that is in your template will remain (and continue to gather impressions).
  • My comments are missing after migration.
    • There may be a slight delay of up to a couple hours as the comments are replicated across our storage layers; no data is lost and all comments will display within a couple hours.
  • Can I just start from scratch?
    • Yes. If you don't want to redirect visitors from your current blog to its new location, you can simply leave your current blog alone and ignore the migration alert in your dashboard. Start a new blog on Blogger (either are your domain or on and you're all set.
  • Does Blogger support all domains with Custom Domains, or just .com?
    • Any valid domain name can be hosted by Blogger.


  1. What about accesing blogs in countries where google is blocked? Presently I can update my blog from China, from Iran, from Afganistan, from Cuba, from . . . (fill in blocking country here) without having to 1) obtain 2) utilize proxy software.

    Uploading pictures to a blog from Picasa through a proxy is hell, when it can be coaxed to work. Most of the time it just fails. Is there a solution for this?

    An idea just occured to me - would it be possible to expand Picasa to publish the blog via FTP/SFTP? That would at least give some access to google tools and keep sites available around the world.

  2. As a user moving one of my blogs to WordPress I have needed to switch to a domain (for the WordPress import) and switch back after. The link to switch back has been removed, but I figured you can still do it by hacking the URL. I thought I would mention it here to save you the time it took me.

    The URL is where XXXXXXXX is the, well, blog ID. I have more details on my blog at and will have a write-up of my migration notes and scripts there when I have finished.

  3. @Santiago: No, Picasa cannot publish the blog via FTP/SFTP. Re: dealing with proxies, we published a post on our Open Source blog last week about the Tor project which may be of some use.

  4. This comment has been removed by the author.

  5. Here's another TIP, no warranties, for advanced users:

    The first thing you'll want to do after migration is fix any links INTO your site that are hard-coded in your template. Otherwise, people at the new site will be clicking back to your old site and having to be redirected again. (For the same reason, in the longer term, you'll want to find and fix links going from one blog post to another within your site.)

    But you should consider fixing the template links BEFORE you migrate, so that in the old site they point directly to the new site. You'd do this and re-publish just before you start the migration, because after the migration you won't be able to FTP publish again.

    The links in the template -- like the one to your "About" page and other important posts and pages -- are very important for two reasons: One, they are the links visitors are likely to click before they realize they're still on your old site. Two, if you fix them in the template and republish, you'll be fixing them on every page of your old site.

    Notes: (1) Back up your template first. (2) Fix the template and republish just before migration - late at night or early in the morning most probably. (3) Hover your mouse over the all changed links and check your work before you migrate. (4) You'll have to carefully figure out what the new URL for each link is going to be. Exporting the blog and importing into a temporary Blogspot blog may be of some help. (5) While you're doing all this, it can't hurt to go ahead and add another link to "GO OUR NEW SITE" in an obvious place, say at the top of the sidebar.

  6. I don't understand the instructions on how to set up a missing files host. I read this:

    In Blogger's Custom Domain options, enable the Missing Files Host and input ""

    OK, that's done. But how do I upload images to Is that what I'm supposed to do? How do I get the images to show up now? I'm confused and the documentation is not clearing it up for me.

  7. @Matt Ruby: This post explains the Missing Files Host in full detail. You need to ensure that you enable a CNAME for "files" to point to your host's IP address for this to work.

  8. I clicked to begin the migration process about three days ago, and the page has been stuck in the more of "preparing your blog" this whole time. I can't seem to get past this step. My blog is very large and dates back to 2001. Is there some accommodation or assistance for this situation?

  9. @Mary Forrest: Please report specific issues here.

  10. I don't use ftp as far as I know. So, why I have this message when I enter the blog? My blog is . What should I do?

  11. @Ailton: Sounds like our alert was a bit over-zealous in its notification. If your blog publishes to you're fine. You're not affected by this process at all.

  12. When I move my existing blog from to, how will it affect my settings in Windows Livewriter (WLW)? - Apart from changing the blog-home-page within WLW, what else would need to be tweaked?

  13. @Steve - you should set up a test blog to see how WLW is affected.

  14. If I have old ftp blogs that I don't plan on updating but that I don't want to go away (because they get some traffic) can I just leave them how they are instead of going through all of this?

    What I'm asking is this necessary if we are not going to be making new blog posts or changing the blog template?

  15. @Josh: Yes. As noted here, you do not need to do anything.

  16. For All Users of the Portuguese Language

    I'm Brazilian and I did the migration of my blog, successfully, to a Custom Domain. All users of the Portuguese Language can read a step by step in the post The Process of Migrating the Blog Step by Step.

    Hope that helps.

    Para Todos os Usuários da Língua Portuguesa

    Eu sou brasileiro e fiz a migração de meu blog, com sucesso, para um Domínio Personalizado. Todos os usuários da língua portuguesa podem ler um passo a passo em meu post O processo de migração do blog passo a passo.

    Espero que ajude.


  17. can I set it up so that the blog is at, while the rest of my site lives at I have only seen .com domains mentioned not .de etc.

  18. I'm using the custom template and have my blogs matched to my site design. Converting to the new template layouts makes it very difficult to match the same look and feel, so I would like to continue with the custom template.

    I can't find any way to turn off the Blogger toolbar in the custom template and my site is now aligned to the left rather than centered and now looks out of place compared to the rest of the site.

    Can we make it an option to remove the search bar and allow the blog to be centered as well?

  19. All my comments did not migrate. What can I do – repeat the migration? Will that double entrys? Thanks for helping.

  20. Can I just start my blog over again at I have a domain (; I keep my blogs in my own html files there, with my own blog archive. The Google files that get filed on my domain site are actually redundant.

    Can I shut down my current Google Blogger FTP blog (Liberal Christian Commentary) and re-start it from scratch on the new system?

  21. My pictures no longer show up on my blog. When I click on them, I get a DNS error. I migrated my web site from ftp to a new Google blogspot site. Is there a step I missed?

  22. @Ken: Disabling the navbar is addressed above in the FAQ.

    @Matt: Comments may take up to a few hours to migrate to the new blog (it's a data replication issue) but no data is lost and they will show up.

    @Sea Raven: Yes, you can start from scratch. No need to delete the blog from Blogger, just start a new one. (Or, if you want to preserve everything in one place, click "settings | publishing | switch to blogspot" and your entire blog moves over.

    @Chris: Please report specific problems here.

    @Backstreeter: Yes, you can host domains with us.

  23. @Ken: Disabling the navbar is addressed above in the FAQ.

    That is for the new layout templates. I'm not using those templates. I need a solution to disable the navbar in the old template. The option for disabling the navbar was available before I migrated and now it's not.

  24. @Ken - That should work regardless of which template system you use. There is no option to disable the navbar in the Blogger UI (as there was with FTP); CSS will hide the navbar from view.

  25. I made a CNAME change for my subdomain (in an established domain) about four hours ago. The new URL is already listed under Settings>Publishing but says "The DNS record for your domain is not set up correctly yet," and the Hosted by Blogger image does not appear in the migration utility. How long should I need to wait?

  26. It depends on the registrar; some set their nameservers to only update a few times per day, so it could take a few hours.

  27. I apologize if this question has been answered. There are a lot of comments and it is taking me a long time to sort through them.

    I've successfully move my blog over from an FTP sever to a address. The redirect works and everything is fine.

    My question is this: how long do I need to keep my old blog live and accessible for the redirect. Will it still appear in the search results? What about links to the old posts? Does the original site need to remain for the traffic to be redirected?


  28. @Adam: glad the migration went smoothly. You should see the Google index update pointers to your new URLs (at within a few days. Once that happens, it's up to you about how long you want to keep the old pages up: if you want to delete them, you can certainly do so, and just risk leaving behind visitors who click on external (i.e., non-search) links to your blog. You might consider setting up a custom 404 page on your webhost so that in the event that someone does land on a non-existent page, you can still direct them to the new blog URL.

  29. My current FTP blog is already on a unique subdomain. Ideally, I would forward this subdomain to Blogger and not have any content for it on my own server anymore.
    But I suspect the new Blogger hosted blog would not have perfectly identical pagenames etcetera, or would it? Would all incoming links still work if I would change the cname for this subdomain?

  30. @Michiel: Yes, all URLs to posts would be identical. I have a post drafted that I will publish later today or first thing tomorrow that will detail the steps necessary to migrate to the same URL, that should help make sure you cover your bases.

  31. Question for Rich:

    Currently we publish our blogger blog(s) via FTP to our own server to a password protected area or our site as it is not public. Will this no longer be possible?

  32. I apologize in advance for coming at you with a third problem already, but this process is as frustrating as hell for me. Since I started the migration but haven't been able to finish confidently, I haven't been able to republish anything on my blog. There is a comment I haven't successfully moderated. Would it be possible for you to undo the "in progress" of my migration status, so I can start fresh? If you could, that would be immensely helpful for me.

  33. @Brian Please file bug reports/specific issues with migration at the Issue Tracker so we can monitor them there. Thanks.

  34. Looks like I need the same help as Brian Sorgatz (i.e. can you guys roll back the migration so that I can start fresh when I have more time to deal with this?) In reading Rick's response, above, he says "file bug reports/specific issues with migration at the Issue Tracker so we can monitor them there". HOW DO I DO THAT?

  35. @Jim: No it will no longer be possible to publish via FTP to your remote server. Blogger has the ability to restrict access to blogs (via Settings | Permissions)

  36. @Stephen: As noted here, please use the issue tracker for posting specific questions relating to the migration.

  37. Hi Rick. Can I avoid the whole 'cname' requirement and just move my blog ( to a blogspot address? If I do, what do I do about links to files that are held at, for example,



  38. @Steve: Yes you can, and links to files on your domain will not be affected.

  39. Count me as a member of the confused. As far as I know, my blog is "hosted" at blogger - - the template, the posts,comments, etc. However, some of the pictures, pubs, etc. in the template and in my posts are located on our own web server, and are reached by hyperlinks on the blogspot blog. To complicate matters, I don't use blogger's custom domains, but own the domain name which is registered at The domain is set up with forwarding with masking to Where does this set up leave me in the migration process? Thanks to all who can help!

  40. @Bob: You are not using FTP to publish. Blogs hosted on are not using FTP.

  41. @Rick - thanks for the amazingly quick reply. Just so I can sleep better, I gather the issue of the shutdown of FTP for blogger doesn't affect me?

  42. Ever since I switched from FTP hosting, my blogs haven't been working properly. Right now, they're both throwing up DNS errors when I try to hit them (from my home or my phone).

    Blogs are located here:

    I talked with my web host, and they same the CNAME is pointed to the correct place ( This makes sense, because the blogs do work every once in awhile. When I hit the root domain ( works fine, so I know it's not a problem with my web host. Any ideas what I need to try to get this migration to work properly?

  43. Please file specific issues relating to the migration at the Issue Tracker here.

  44. Currently I have two versions of my blog: for English and for Russian. Is it possible to migrate them to and respectively? Or am I bound to create two sub-domains: i.e., and Or, probably, there is a better solution, isn't there?
    Thank you.

  45. @Alex: You would need to either create two blogs, or create one blog and use labels to differentiate English posts from Russian posts, then use links to those labels to surface English-only and Russian-only posts.

  46. Thanks Rick!
    Currently I have two separate blogs (English and Russian; both FTP-published). Is it possible to "merge" them into a single blog (custom domain) during the migration (to switch to "labeling" approach)?

  47. @Alex: Sure. Just export the posts from one blog, and import them into the other. Might want to do a test to make sure everything behaves as expected before you do this on live data.

  48. Rick: I still have not seen any suggestions on how best to preserve RSS subscribers. I assume that for anyone who now subscribes to my feed, the feed will simply stop working upon migration. (No, I don't use feedburner.) Is there a way to redirect the feed automatically? If not, can I tell them in advance what the new feed will be? Will the feed address be

  49. I have migrated my blogs (new and while retaining my old domains and feed settings. Everything seems to have gone well, EXCEPT that my RSS feeds on feedburner (EuropeanPensions and CaptainsLog) don't seem to work anymore. Trying to insert the new original feed results in the following error message: "An error occurred connecting to the URL: unknown protocol: feed" HELP!

  50. Rick

    Can you please send me the link to the migration tool, I am pulling my hair out trying to find it

  51. @Insignia Creative: if you do not see an alert in your Blogger dashboard with a link to the tool, you are not impacted and do not need to use it.

  52. @Chris: Please post specific issues with the migration to the issue tracker.

  53. @Bob: The migration tool writes a final post to the old blog URL (both the site and the feed), and provides the new URL in that post, which directs users to the new address.

    The only way to automatically redirect users from the server is to use .htaccess (contact your webhost to see if .htaccess is supported on your server); otherwise you'll need your users to update their subscription by taking the new URL from the final post mentioned above.

  54. @Rick, I have actually just resolved the matter, it was a most embarrassing triviality: On feedburner, I pasted feed://... instead of http://...
    Sorry about taking your time!

  55. my ISP does not accept for the CNAME setup, they require a numeric IP address. Can you provide the numeric IP address for thanks

  56. @CivilGuy - that's actually not possible, we periodically change our IPs. CNAMEs routinely point to a machine name; if your registrar will not accept that you'll need to have another provider handle your DNS. (They *should* - there's no reason not to.)

  57. Hi,

    Our initial page for our website ( is actually our blog, for ease of updating. We're worried that if we establish a custom domain or subdomain to migrate our blog onto, our users won't see our webpage or our blog.

    Our expert (who set up our site initially) is out of the area for the next several months, so we're trying to accomplish this migration on our own but have very little technical knowledge. Is there any assistance that you would be able to provide?

    Thanks much.

  58. @Cudahy Family: This post is a step-by-step procecss for migrating from your current setup to custom domains, while keeping your current URL. That should be what you need.

  59. I have about 100 blogs to convert! Some are being used daily, others not so much but we'd still like to convert them. If I dont get to converting them all by the deadline I understand my blogs will go static but can I still use the conversion tool after May 1st?

  60. @Earthwatch: No, FTP publishing is being disabled effective May 1, and the migration tool depends on being able to publish via FTP to work.

    That said, we will provide you with the ability to download a ZIP file containing the full archives of your blog, with the rel=canonical and meta refresh code included, so that you'll be able to migrate after 5/1 (just not using the migration tool - you'll have to manually upload the old files yourself).

  61. Hi, I did the migration and it got stuck on the third step (it's been exactly two weeks now). The blog is there in the new blogspot url, ready to use, but all the comments had gone!
    could you tell me what happenned or how can i fix it? thank you!

  62. I currently use some Javascript of my own, but suggests that Blogger is going to discontinue support for full template customisation. Is that true?

    Basically I'm thinking Blogger is planning to discontinue full customisation/javascript usage, the same way FTP was discontinued after a similar sort of comment in a blog post (a straight-up early announcement would have been better).

    Basically what I'm asking is whether we're about to migrate into further lockdowns/feature discontinuation. FTP went from a post saying it was kinda hard, to a total discontinuation as though that first post was an announcement. So I'm left thinking this latest aside about javascript means "we're going to switch that off but we aren't simply saying so".

    Would really appreciate any information on this topic.

  63. Rick,

    I've migrated 1 blog to a subdomain:

    It's working fine.

    The second blog redirects to in error but the CNAME (vacationrentals) and DATA ( are both correct: is currently bringing up the TLD and not the blog page, which is still visible at

    The migration progress page stopped at Publish.

    Any suggestions?

  64. If I haven't migrated yet, shouldn't my old blog still function normally until the end of the month? I have not been able to post anything in at least a couple of weeks. The posts hang at "Publishing your blog is taking longer than expected...." forever.

  65. Hi Rick,

    I have a question about traffic. Once we migrate our ftp blog ( to a subdomain ( will we still receive the traffic/unique visitors? Or will that traffic go to Blogger since it's hosted on Blogger?

    Thanks in advance

  66. I'm in dire need of a migration for dummies version of this info. I don't know what a cname is much less an aname. My e-commerce site was set up by someone else. She created a custom template for the blog and connected it to my e-commerce site.

    If I use the migration tool and follow all the steps, will the new blog exist in the same place that it is now on my website or are there additional steps I need to take once I finish with the migration tool? I'm sorry to be so dense...but I just don't get this. I need very basic steps to follow. I've watched the video and it doesn't have enough detail for me.

    One other thing...I clicked on the wrong button on the first page of the migration tool and did not back up my files yet. I can't seem to get back to that page in order to do the backup. Is there any way to do that now?

  67. So, is there ANY possible way to have multiple blogs on the same page anymore? Now that Custom Domains do not support PHP includes, are there any options left?

    I am using a completely custom template, so gadgets are not an option (though I'm not even sure there is a gadget so such a thing).

  68. I have finally migrated one of my blogs and several images do not appear on the blogspot site...Help...

  69. my old blog URL:
    New custom domain:

    I've gone through the migration, but I had CSS in the custom template that links to my server (ie. inc, top, images, etc.)
    These are not linking correctly. Above it says this will not be a problem, but it has been. Help!

  70. Perhaps it's just me not understanding, but when I exported our FTP-blogger site, and then imported into a non-FTP blogger, the author of all the posts changed to just me (Joseph), when the majority of the posts are by someone else (mostly my wife) -- is there a way to preserve the authorship?

  71. Hi Rick, I am thoroughly confused about what to do. I've tried posting to comments a few times in the last several weeks but my question never gets posted. Please bear with me...

    I publish my blog via FTP at
    My image files are located at images.

    I currently have the custom domain pointing to

    I also have an empty Blogspot address:

    When I got to the "publish to a new URL" section on the migration tool, I typed in "thehappy-project" in the option. I then got a "Sorry, this blog address is not available" message.

    What am I doing wrong and what is the best option for me?
    I am not attached to the address but want to continue using the domain

    Would it be easiest to import (instead of migrate) the blog over to and point my domain to it? Do I still need to create a CNAME?

    If there's a better option, will you please tell me what I am supposed to do at the "publish to a new URL" page of the migration tool? Like I said, I am not attached to keeping the url.

    Please help I am lost. :-(

  72. @Amparo: If you've already secured a blog at a blogspot address, then it will not be available to switch to during migration (since a blog is already hosted at that address). Delete the blog at if you want to move your FTP blog there.

    If you are moving to Blogspot you do not need to configure a CNAME.

  73. @Joseph: Add your wife as author to the blog before importing the files.

  74. @ABE Representative: Make sure the CSS URL is absolute ("") instead of relative ("/css/stylesheet.css"). If that doesn't help, feel free to file a ticket with our Issue Tracker and our support team will look at it.

  75. @Jeff: For images not displaying, it's possible that either the path to the images is relative (i.e., /images/foo.jpg) instead of absolute (; if that's the case, you can add an HTML parameter to your template that defines the base URL so that relative image calls are converted to absolute. Do a Google search for HTML base href if you're not familiar with this.

    If that doesn't help, file a ticket with the Issue Tracker and we can look into it.

  76. @Team OPHIR: No, as indicated on this page and elsewhere - each blog needs a unique URL.

  77. @Heart's Desire: Your blog will likely get a new URL; while the migration tool is designed to be relatively simple (and will take care of redirecting your visitors from the old blog URL to the new URL), you may want to get some assistance from someone who understands the ins and outs of website maintenance so you have help available if you need it.

  78. @Wow! - The hits will be going to our servers, since the content is hosted by us. You can still track the visits by using Google Analytics or another analytics package.

  79. @indigo: Yes, FTP publishing is still working. If you have not migrated, it's likely a problem authenticating to your FTP host; please verify with them that they are not blocking Blogger.

  80. @Jay: Please file a ticket with our Issue Tracker so our support team can take a look.

  81. @200OK: The FTP announcement is not a lock-down on our part, but a response to the disproportionate engineering and support time FTP was taking relative to usage. More details are here.

    Auto-pagination is not a feature shut-down - Blogger never had a "feature" that allowed users to create HTML pages that were 200 screens long. In evaluating our performance, we noticed that some users were creating (either deliberately or not) pages that were unnecessarily long, and we imposed sensible limits on how those pages are formed now.

    To answer your broader question: our goal is to keep Blogger the premiere free, simple and powerful blogging platform that it is. As last month's template designer announcement shows, we are absolutely committed to not just allowing but encouraging users to express themselves and customize their site as much as they like. And while I have no plans to change Blogger's support of third party code embedding, we will likely help users understand the tradeoffs they're making when they embed that code - how it affects performance, page loads, etc.

  82. @SrKaito: If you're still experiencing problems with the migration tool, please file a ticket with our Issue Tracker and our support team will take a look.

  83. For me, the biggest limitation of having my blog hosted at Google is not having access to robots.txt because Google-hosted robots.txt files disallow indexing of tag files (Disallow: /search). Having control of my robots.txt file was a critical part of my decision to self-host.

    I certainly hope, now that self-hosting is no longer an option, that Google will loosen some of the restrictions on Google-hosted blogs - especially allowing us to make our own choices about robots.txt.

  84. @Rick: thanks for the response. Does Blogger plan to allow hosting of CSS, JS and template-related image files? It would make sense to keep all files together on the same host/infrastructure and remove the dependency on "missing files" hosts.

    Also a separate question... post-migration the only way to disable the NavBar to hide it with CSS, meaning the site still has extra http requests etc. With FTP we simply had an "off" option which avoided those pitfalls. With the recent announcement about page speed, every last bit helps - could that simple "off" option be reinstated?

  85. @200ok: Yes, we're looking at making that an option. (Though the current latency hit is measured in single to low-double-digit milliseconds, so it shouldn't be noticeable.)

    We do not at this time have plans to host arbitrary javascript or CSS, but it's a popular request and it's on the list to be reconsidered as other initiatives wrap up. Nothing around the corner though.

  86. Greetings,

    I have four blogs in addition to my homepage that publish to sub-directories at my web host:

    Am I going to be able to migrate all of them separately and keep them separate?

  87. We have a number of blogs that are not active but remain up as archives and are used quite a lot. I'm assuming that these will remain albeit not able to update; there just won't be any replacement blog. Am I right?

  88. Hello and thank you for the helpful tools and information you've provided for migrating from FTP blogs to your new setup. Currently, on my dashboard it says across the top that I have one or more blogs operating on the old FTP blog system and I need to migrate them. When I click on the Start Migration Now button it takes me to the FTP Migrate Page but there are no blogs listed under the header to migrate. Am I missing something?

  89. @Shane: No, you're not missing anything. This is a bug on our side - it means that one of the blogs in your account at one point (may even be a deleted blog) was using FTP. We originally wrote the code to alert users to be very broad so we didn't miss anyone; unfortunately, in a few cases it meant we alerted some users like you who don't have any current FTP blogs.

    You can ignore the alert, your blogs are fine.

  90. Hi Rick, my blog ftp server is while my blog url is

    Can I still use the advanced setup: moving from www to www at to preserve my current blog url


  91. @Rena: The instructions have nothing to do with your FTP server, they are focused on the URL itself. If your blog is currently publishing at and you want to keep that, the instructions are valid.

  92. I migrated my blog but I now have a message on both the old and new one that says. "This blog has moved". Now I understand why for the old location, but for the new!

    Do I delete just this and carry on or wil that delete it for both versions and screw up the re-direct.

    PS I posted this in the error log (blogger-ftp-migration-tracker) weeks ago and all I get is a "This is fixed" when it isn't and I still don't know what to do) That was back on 11 April.

    also I have others to transfer and am concerned I am running out of time.

    2) I now have two blogs (the old and new ones) but clicking on entries in the old one
    does not transfer me to the new one but mereky to the old entries in the old blog.

    If I am on the old page and click on one of the entries I still land on an
    old blog entry rather than the sub-domain, ie It does not re-direct me to the new blog.

    This all started when the verify FTP gave the message ""We were unable to verify that the
    migration completed. You can either manually verify that your FTP blog's
    pages include "rel=canonical" and "meta refresh" by viewing the source code
    of your pages in your browser or you can click "Retry Update" and re-do the

    I re-tried this three times but still the same error.

    Now I don't trust the migration tool

  93. @Phil: Please file a new ticket (feel free to add links to prior issues/posts). The comment threads are not the best place to address specific questions concerning individual blog migrations. I'll make sure the support team follows up on any outstanding issues, and will chime in with any additional info needed concerning your specific migrations.

  94. correct me if I'm wrong but by leaving the blog alone (the files are on my host) it will still work except I cannot post there. My plan is that I exported the files over to wordpress and will make a final post saying the new blog is {new url} and change the Blog Home Page link to the new url. But people who have my old blog domain name will still see a working site, and will see links to the new one.

  95. @Soo Do-nim: yes, that will work.

  96. Rick - I've convert over to using a custom domain, but I have two issues, perhaps related.

    I've noticed that a new STYLE block has now been inserted into my HEAD block that imports the following CSS file:

    and additionally sets the following style:

    div.b-mobile {display:none;}

    I believe this CSS is related to the navbar, which I don't want to see. As suggested in the FAQ I have already added a style override for the #navbar-iframe id. However, the rest of the CSS settings are messing with my layout by eliminating a nice padding I had around things, and seems to be the cause of other layout ugliness.

    The second problem is that for some reason in Firefox, my Google Ads no longer display (they do display in IE 6).

    You can see this for yourself by comparing the new custom domain version,, against the old, still accessible version I used to FTP to my web site at

    How can I eliminate the 697174003-classic.css import, or am I going to have to muck with CSS (my worst nightmare) to try and override every setting???

    Thanks in advance.

  97. @Daniel: You can just put a <style> tag right before the </head>.

    You'll want:

    html body {
    padding: // whatever;

    body #header {
    margin-top: 0;

  98. Hi Rick. I have already moved my blog (which used FTP to my own domain) to Word Press. My content is still here on blogger... will it be removed? or is it safe to leave here? Do I need to do anything else?

    btw... my (few) readers have been finding me and commenting just fine... so I think I've done it correctly.


  99. @Deb: The content will remain until (if) you choose to delete it.

  100. Hi Rick,
    Can I force the migration tool to migrate the same blog once again? But to a different location this time?

    I migrated my blog to succesfully, but I changed my mind (I didn't like the resulting URLs). Now I would like to migrate to in advanced style migration, I guess.

    Please show me the way to do so - I have deleted subdomain 'sub' already but kept the ZIP from migration and copies of the entire blog by FTP.

    I'm in a sort of nowhere land right now which doesn't feel very comfortable...

  101. @Coen: File a ticket in the issue tracker to have your migration status reset and publishing state set back to FTP. You may encounter some challenges for a period of time as search engines discover the current pointers to URLs that no longer exist, but it should work itself out in a few weeks.

  102. OK ... I'm not getting this at all. First of all there seems to be conflicting instructions between:

    "To create the CNAME, pick a name for this backup domain ("files" is a popular choice) and point it at your webhost's IP address."


    "To create a CNAME record for your domain with the DNS, associating your domain with:"

    So, when(/if) I create a CNAME record do I put the IP of my hosted site or in the "Please specify a fully-qualified domain name, or @ for" field at my web host?

    Secondarily, since I have five blogs at published via ftp to sub-directories (as well as the root)... well I don't even know how to ask the relevant question.

    I have a blog at ... I'm guessing I create a CNAME like but I don't know where to point this and then I don't understand how this will:

    1)relate to the creation of a custom domain in the blogger settings interface
    2)impact the other four blogs.

    The #2 above confuses me because in your examples you use "" to point to what seems to be the root of my hosted site. How can I have five different blogs that all point to the root of my hosted site?

    Another thing that may or may not complicate this is that, as it stands now, pair networks, my host, has it set so that and just go to the same thing. It seems to me that part of what this migration assumes is that there are no 'naked' domains. That 'files' is just standing in for 'www'.

    To further complicate matters it is not clear if I need to set set up actual sub-domains at my domain registrar or just create CNAME records at my web host.

    Is there any way you can help me understand how to ask the proper questions here? And am I making it clear about my issue with having five different blogs that exist in sub-directories at my web host?

  103. @sitenoise: Let's say you intend to move your blog to "". You will need to create a CNAME that points "blogger" to "" If, on the other hand, you are hosting with us, you'll need to update the CNAME for "www" to point to ""

    The explanation for "" is in the event that you need to use a Missing Files Host (this is documented here), then you will be setting up a second CNAME, and it needs to point at your webhost. See the aforementioned post for specifics.

    Each blog will need its own unique URL, which will be a CNAME.

    Check with your registrar to see whether they or your webhost is hosting your DNS files; whoever is hosting the DNS is who you need to set up the CNAME with.

  104. At my Blogger blog publishing definitions there is an option that asks the Blog Filename. Mine is "blog.html" for several years, because the site´s mainpage is "index.html".

    At the custom domain definitions will I have the Blog Filename option? If not, is there any hope before migrating to Wordpress? Tyvm

  105. Ok I´m changing my blog´s url to (previously

    My host service already did this and its working:
    CNAME "blog" to ""

    During the migration I had to go with the manual process because the I couldnt accept the redirect offered the migration tool ( to, because my old blog´s url is The has an index.html file which is my site´s homepage (not the blog), so I had to choose not redirect.

    In terms of SEO what will be the impact of this migration?
    SHould I redirect 301 the old url ( to
    Should I change and ask to change internal and external links?
    Will Blogger and Google redirect it too?
    Would the automatic migration tool had assumed that the correct redirect should be ' to' and not ' to'?


  106. PS: I noticed that my favicon disappeared after the migration.

    I pointed a sub-sub-domain as a missing files host but the problem remains.

    The code is like this: link rel="shortcut icon" href="/favicon.ico" /

    Any clues?

  107. @ty yes, the migration tool properly understands that /blog.html redirects to /index.html. If you're having specific issues post-migration please file a ticket in the issue tracker.

  108. @ty As far as SEO advice, we spoke with the search quality team to ensure that there would be no penalty in using the approach outlined in the migration tool. You are of course free to use other methods, which are often well-documented and the results of which are generally well-known. Beyond that, I do not feel comfortable giving specific SEO advice.

  109. I'm having a little problem here...

    I have a domain and hosting with Strato, a famous internet hosting provider here in Spain (And other places of Europe). The problem is that Strato doesn't let me modify CNAME or anything like that. I can only create NS-Records, A-Records, MX-Records or SPF-Records. What should I do?

    Thanks in advance.

  110. @Sandor: Unfortunately the only way to host a domain with Blogger is to modify the CNAME, which is a standard DNS configuration. I'd be surprised if a large webhost/registrar did not allow that modification - it's quite common. That said, if you want to stay with Blogger you can either register a new domain through us (and all configuration options are taken care of automatically) or you can host the blog on Blogspot.

  111. Whoa, thanks for the quickness answering me :)

    I gave a call to Strato and their tech support told me that they don't allow any modification of the CNAME. Only the A-Record is allowed, and it won't make the trick.

    Looks like I'll have to recover my old account on Blogspot. Thank you very much for your time and attention :D

  112. hmm ... I've been trying for a couple days now to post an entry that says I won't be updating my blogs because Google has discontinued ftp publishing, and they just won't publish. It gives me the notice that things are "taking longer than expected would I like to click here and keep waiting."

    Is ftp publishing supposed to be still operational?

  113. It's my understanding that the migration tool redirects all your old pages so that there's little lost when people have linked to your old pages.

    Unfortunately, the migration tool makes me do things "manually" since I'm switching to a new domain name. I'm fine with that, but concerned that none of my old pages will be re-directed. Are my fears well-founded?

  114. @sitenoise Yes, it's functional until midnight PDT (GMT -0700) tomorrow.

  115. @Doug: Your best bet to get the benefit of the migration tool would be to migrate to Blogspot, then after a few days update the publishing settings to point to the custom domain. That way the old pages will point to Blogspot, which Blogger will 301 redirect to the new domain. It's a bit of a hack, but it will work and it avoids you having to do manual redirection work on your end.

  116. What if I want new blog post images hosted on my server? How do I do that? I know that Picasa has a limit on the amount of images that can be stored on there. I also know that there is an upgrade option but then I am just shelling out even more money to host my images. Ideally, I'd like all of my images stored in one place. A server seems more reliable. If I was to move all of my past images to Picasa, does that mean I have to manually repost each blog entry so that the photo is uploaded to Picasa??

  117. @Amparo: No need to move past images, and you can continue to upload images directly to your server (via FTP or however you want to communicate with your server), then insert the images via hyperlink into the Blogger post editor.

  118. Hi Rick,
    I think that I might have done the wrong thing. I moved my blog (which used to be: to

    I have the custom domain pointing to the blogspot address. I would like the domain to be hosted with blogger so that it is no longer pointing to the blogspot address.

    How do I do this? I know that you have probably explained it already but I've read so many posts that I am confused. I'm not tech savvy and some of the jargon is lost on me.

    Will I have to to re-migrate my blog? Do I have to create a new CNAME?
    By the way, I have not posted anything new since I've migrated my blog to the blogspot address.

  119. @Amparo: Go to "settings" then "publishing" and follow the instructions to switch to a custom domain. You will need to update the CNAME settings on your domain.

  120. Hi Rick,

    I now publish as

    I plan to use

    I'm open to a blogspot address, if necessary as per my questions below.

    1. Are there any special issues with podcasts? (Feedburner does my podcast feed).

    2. My template is very customized, which I paid someone to do. Is there a way for that customized template to migrate over?



    PS: I posted this once, and it didn't appear, so I'm trying again.

  121. @Jack: 1: No. 2: The template will continue to work as coded.

  122. Thanks for your quick reply, Rick.

    By waiting until after May 1, did I lose anything?

    For one thing, it seems I now have to download a zip and manually upload via ftp my modified old files, while before the wizard did that automatically?

  123. @Jack: Other than needing to do the download/unzip/upload manually, you didn't lose anything.

  124. Good to know. It's great having you there Rick. When I actually do this tomorrow afternoon CA time, I hope you'll be around if any problems arise. (PS: I tried on IE8 and Firefox, but couldn't subscribe by email so I'd know when there's a response. Got a "An error occurred while contacting the server" message).

  125. Rick,

    I have not yet performed the FTP Migration process of my Blog. My blog is currently set up as: '' in which '' is currently configured as a 'Subdomain' pointing to ''. That Subdomain has folders and files that contain all of my current blog uploaded images, archives, blog posts, and more.

    I would like to keep my blog at '' when I do the FTP migration.

    The instructions state that if I want my blog at '', I must make a CName Record of that '' and point it to Google (

    If '' is already a Subdomain with all the associated blog files, images, atom.xml file, and other files - how do I keep '' as my blog place when I can’t make it the CName to point to Google?

    Because, as I see it, if I change it from the 'subdomain' folder to the CName Record pointed to Google, it can't contain the current blog files, images, atom.xml file, and other files that currently run the blog. Help.

  126. @Lewa: In that case, you'd use the missing files host to handle cases where requests for files in the /blog/* path 404 (because we don't host them), and we can then redirect requests to those files to a backup domain (like

  127. Hi Rick Klau,
    I have read the instruction on transferring the blogs to domain name. I got the part where I would transfer to I am looking for an answer for: How can I make to
    I have been looking for this answer everywhere. Nothing yet. May you can help me.

  128. @Solver777: If you're publishing to you are not using FTP and are not affected. If you want to switch from to a custom domain, go to settings | publishing | switch to a custom domain. You cannot publish to /myblog when hosting with Blogger.

  129. How do I find my blog's IP address?
    I need to be able to read my blog's atom.xml file ( from my main site ( My main site is behind a firewall, so I will have to create a firewall rule to allow incoming data from a specific IP address.
    Are Google's IP addresses static? Can I be sure that if I set up a firewall rule with a particular IP address, Google won't go changing it every once in a while?

  130. @Maureen: Our IP addresses are not static, though they do not change terribly often. How do you plan on publishing to your domain?

  131. @Rick: We used to publish via FTP but have now migrated to a blogger hosted subdomain using the CNAME method.

    We have a PHP script at our main domain which parses the atom.xml file to extract a summary of the latest post and create a link on our home page. I have discovered that resolves to which is itself a CNAME pointing to which resolves to

    If I put that IP address into my firewall rule, everything works OK. But for how long?

  132. @Maureen: Sounds like it will work until the IP address changes on our end. As I said earlier, that's not terribly often - so you should be fine.

  133. Would I be safer by using a netblock such as Most of your blogger IP's seem to be in that range.

  134. @Maureen There's no guarantee that a future IP would remain in the same block. Given that the changes are infrequent, your best bet is to simply keep an eye on it and if it stops working, it's likely a result of the config (which is then a simple change).

  135. It has occurred to me that the method I use could be useful to those who are unable to migrate to a custom domain or subdomain, or who cannot add the CNAME to their DNS.

    The method requires PHP with fopen enabled. The blog can be migrated to blogspot and a PHP script could read and parse the XML file, and create the blog pages using a locally hosted template and CSS file.

    I'll do a bit more research/work on this and publish a full solution if it all works out OK.

  136. I had a blog on an FTP and haven't done anything with it until now. I see that things are done differently, but can't use the Migration Tool. When I go to my Dashboard, it shows I have no blogs to migrate, but won't let me make a new one. Do I need to set up a new account, and if not, how do I go about posting a new blog with this present setup?

    Thank you for answering my question.

  137. @Abigael - What do you see when you click on "settings | Publishing"?

  138. I don't have a "Publishing" tab...just 'Email & Mobile' and 'Permissions'.

  139. I have it set so that we update our blog site by sending an email, so I am just discovering that FTP is no longer available. The only time I've had to use the FTP is if I needed to change the template, or if for some reason the email update didn't work. So right now I need to do both these things, but realize I have a lot more work to do! But I'm getting dizzy trying to read all these posts and figure out which solution is appropriate for me. Here's my scenario. I cannot change my url. I have the blog on our own servers here at my office, at the following url: What are my options?

  140. @UW: Unfortunately there is no way for Blogger to publish to that URL on an ongoing basis. If you could set up a CNAME in the domain record for (like then you could continue to use Blogger; otherwise, you'll need to look into an alternative publishing platform (WordPress is a popular option). Also recommend updating the e-mail address that is connected to your Blogger account - we sent e-mails announcing this move starting in January to every e-mail address we had for all users w/FTP blogs in their account.

  141. Thanks for responding, Rick. So this CNAME - which I take as a subdomain? - if I set one of those up, then I can continue using blogger, you say. Then the updates would be done how?
    Thanks, Linda

  142. You will need to convert your blog from FTP publishing to custom domain publishing; the FTP Migration Tool walks you through that process. (Click 'start migration' on the message on your dashboard.) Each step is explained, should be straightforward.

  143. Thanks again, Rick. Now, if the powers that be don't want a sub domain, then my other choice is to go to WordPress? And then the whole blog will be on WordPress and have nothing to do with Blogger? Or will it still integrate.

  144. If you can't do a subdomain, then you would need to change blog apps to continue to update the site. Blogger would no longer be involved in the updating of the site.

  145. Thanks again, Rick! One more question. If they let me go with the sub-domain, would we still be able to update the blog via email?
    Thanks, Linda

  146. @UW - yes, you certainly will.