How I moved back from self-hosted to WordPress.com

Vittore Carpaccio - The Ordination of St Stephen as DeaconA year ago I moved my site from a local New Zealand host back to the WordPress mothership. The goal was to make life simpler. That worked: at least for now.

The move wasn’t technically difficult, there are things to watch:

1. Permalinks. These are not customisable with wp.com. You’re stuck with the WordPress format. I’ve no idea if this is good or bad for search engine optimisation. I don’t care.

2. If you worry about search, the trick is to switch format a couple of weeks before making the move, otherwise Google gets confused. I started on this path, but the rest of my preparations went so quickly the new format was only in place about five days before the switch.

A year later Google Webmaster Tools tells me traffic is still looking for those old format links. The lesson here is if you think you may switch to WordPress’s host in the future, start using the permalink format now.

3. I moved the domain name. There was no control over the time this happened, it happened at 11pm so I was effectively offline for about nine hours – this may not bother you. I don’t know how many people saw a dead site, in those days it would have been around 100 visitors. Any damage is fixed now. Another time I’d need to rethink how I’d do this.

4. I paid extra for WordPress.Com’s custom design and used my own twenty ten child template. It didn’t look great, so I had to switch to a new template – this was the trickiest part of the process and I still don’t have it perfect. A year later I’ve shut all the custom stuff down and have a stock WordPress theme. Dammit, this is THE stock theme. People come to my site for words – I can use pictures to make it look better.

5. Originally there was zero flexibility over the iPad and smartphone templates – this was almost a deal breaker for me. A year on and the problems are largely solved thanks to a responsive theme.

6. There are a few minor irritations. Mainly lack of design flexibility. I wanted a simpler life, so I’ll just have to put up with them.

7. On the plus side, the .com site is seven times faster than my hosted site, requires almost zero maintenance, has barely gone offline in a year, gets more accidental traffic and is free. The downside is I’m less in touch with WordPress coding – something I think journalists ought to get used to. To get around this I’ve built a couple of other sites.

5 thoughts on “How I moved back from self-hosted to WordPress.com

  1. I had been wondering whether I should go to a hosted blog at some stage, I think the key point is that our blogs are about words. Of course .com is largely free unless you license a custom design. I haven’t found a need as yet.

    Like

    • The simple answer is you need to go hosted if you want to run advertising – trust me that simply isn’t worth it until you see around 10,000 page impressions a month. I know, I’ve been down that path. You also need to be hosted to run ecommerce elements on your site – although simple stuff like pointing people to your books on Amazon is doable.

      And running a hosted site gives you infinite flexibility over how your site looks – for what that’s worth. I’d do it if I was a designer.

      Otherwise stick with the free service. Maybe spend money on customisation features and definitely get a proper web domain.

      Like

  2. Great blog post!

    I took the decision to move back from a self-hosted WP install when I realised that wordpress.com had features that were missing in the self-hosted package, including the ability to automatically share posts on publication, The community is a big plus too. I have a dev background so like you I missed the coding side, but like you, I’ve built and maintain some other WordPress sites that don’t fit into a typical set up.

    Like

  3. Pingback: Why I use WordPress.com not WordPress.org | Bill Bennett

Comments are closed.