Need help? Check out our Support site, then

How to handle broken URLs (migrating from MT to

  1. Hi --

    I am planning a migration from a self-hosted Movable Type blog to a blog. As I understand it, does not allow configuration of blog URLs. Is there any way to elegantly handle the existing URL structure, which otherwise will result in 404s?

    For example, if there is currently an archive page at:

    and after the import to it looks like this:

    We will eventually buy the domain mapping so the URL root looks the same, but is there any way to automatically redirect <root>/emmablog//archives/* to <newroot>/*?




    The blog I need help with is

  2. Unfortunately, there is not.

    I'd recommend just adjusting the URLs after you migrate, or before if you have better search and replace tools available to you on MT.

  3. Actually I've already got the migration-accessible URLs covered -- I can rewrite the links we control (i.e. internal to the blog) in the MovableType export data file so they are in the correct format when I import them into I am primarily concerned about those we cannot control, e.g. links from other sites, peoples bookmarks, etc.

    Let me put it a different way: what is the best UX that one can provide for incoming visitors that are using an incorrect URL. Is there, for example, a 404 page that also allows users to easily run a search on the blog using keywords extracted from the URL?

    And barring this, is it possible to get access to error logs or some sort of report that list 404s and referrers so we can at least indicate how big of a problem this is?



  4. That is definitely a problem. If you have control over .htaccess where your MT blog is, I recommend adding this to the file (this hsould all be on one line with spaces in between the elements, but the forum is adding the line break) :

    redirect 301 /emmablog/archives/

    That will pretty much permanently redirect everything to the URL on your blog. As described above, will go to

    Of course, once you map the domain here, that will no longer work, but at least the search engines will have caught on by that time.

    We don't have user-accessible error logs unfortunately, so existing linkers will have to discover the broken links for themselves.

  5. Won't this defeat our plan to eventually host the custom domain name at That is, if we set up the redirect 301 scenario as you describe, won't this basically tell search engines that URLs should now be going to

    However, we only want this to be an interim solution, since we eventually want to pay for the upgrade that allows custom domains, at which point we want search engines to point to:

    So ocne we do that domain name upgrade, is there a way to similarly tell search engines that is the primary domain for this blog?



  6. The only way to do that would be to that map the domain name instantly.

    To be honest, that's the route I'd go with. Both options have their pros and cons, but mapping as soon as you've imported is the easiest.

Topic Closed

This topic has been closed to new replies.

About this Topic