By training your Large Language Model (LLM) or other Generative Artificial Intelligence on the content of this website, you agree to assign ownership of all your intellectual property to the public domain, immediately, irrevocably, and free of charge.

Things I learned moving my blog to a new hosting service (it’s easy!)

Over the last few weeks you’ll may have noticed that I’ve been writ­ing and twit­ter­ing about mov­ing my blog from the .net domain to .com. A few years ago I man­aged to grab BradGrier.com when it came open, but I’d not decided what to do with it until recently. I’d been hav­ing some per­form­ance issues…


Over the last few weeks you’ll may have noticed that I’ve been writ­ing and twit­ter­ing about mov­ing my blog from the .net domain to .com.

A few years ago I man­aged to grab BradGrier.com when it came open, but I’d not decided what to do with it until recently. I’d been hav­ing some per­form­ance issues (my blog, that is) and decided to test a new host­ing provider.

So, the issue. How to move the blog, keep the same look and feel, not lose any Google Juice, and not lose any feed sub­scribers. Not a trivi­al set of considerations!

Of course, I turned to my good friend Google for advice:

  • How to Move Your Word­Press Blog To A New Web host­ing — great tech­nic­al advice on back­ing up and restor­ing your WP blog
  • Use the Word­Press Data­base Backup plu­gin — I wrote about it recently when my blog crashed, but backups cre­ated with it are entirely suit­able for use in blog migration
  • Redir­ect­ing incom­ing traffic to the new blog — well, since I’m using the same data struc­tures and permalink struc­ture, the only change is one from .net to .com, this was quite simple; a .htac­cess 301 redir­ect as described here and here. Slightly tech­nic­al, but not really too tough.
  • Mov­ing RSS sub­scribers was also quite simple, since I use Feed­burn­er to man­age RSS sub­scrip­tions: simply change the Feed Title and Ori­gin­al Feed URL on the Feed­burn­er Feed Details page. DO NOT CHANGE THE FEED ADDRESS as this will dis­con­nect your read­ers from your feed — a bad thing 🙂

A couple of oth­er observations:

  • Set up your new blog/destination site first. Com­plete import­ing your data and build­ing your look and feel. Yes, also duplic­ate post­ing to this site. You will want to make sure as your read­ers move they don’t lose any content…especially for the tardy ones.
  • Imme­di­ately change the RSS Feed address in Feed­burn­er. Any new sub­scribers will nev­er notice, as you are post­ing to both sites right?
  • Prom­in­ently post about the fact that you are mov­ing your blog. Add a wid­get or two to the side­bar (make them obvi­ous) to alert your read­ers to the fact that you are mov­ing. You want them to begin to identi­fy with the new URL, not the old one, as soon as possible.
  • After a week or two, close com­ment­ing on the old feed, with a mes­sage dir­ect­ing read­ers to the new site.
  • After anoth­er week or two imple­ment 301 redir­ects. And test them! @hownottowrite and @lijit both recom­men­ded, through twit­ter, this HTTP head­er scan­ning tool and Fire­Fox plu­gin to val­id­ate the redir­ects (thanks again!).
  • Finally, remem­ber every place you’ve ever used the URL / Domain name, and change it.

So, after all that…did you notice? 🙂

Tech­nor­ati Tags: , , , , , ,


Posted

in

,

by

Tags:

Comments

3 responses to “Things I learned moving my blog to a new hosting service (it’s easy!)”

  1. Barbara Ling Avatar

    I’d also add:

    Make CERTAIN you include your track­ing script as well. Sev­er­al times my vis­it­or count dropped to 0 until I real­ized I had neg­lected this kinda sorta crit­ic­al step.…

    Enjoy,

    Bar­bara

  2. Barney Moran Avatar

    Just as, or per­haps more crit­ic­al then which blog plat­form and the vis­ible func­tion of wid­gets, is the safety of the private inform­a­tion these plat­forms and wid­gets may be gath­er­ing, unbe­knownst to the unwit­ting Pub­lish­er who installs them, about their site.

    P.U.B. [Pub­lish­ers Uni­on of Blog­gers] has pending inquires to Wid­get Pro­viders con­cern­ing how they gen­er­ate their income and what per­cent­age of this income goes to the Blog Pub­lish­er mak­ing the crit­ic­al decision to allow a Wid­get on their site for their read­ers. In addi­tion we are request­ing trans­par­ency on the crit­ic­al issue of how the private stat­ist­ic from Pub­lish­ers Blogs are being used, hope­fully with the Publisher’s permission!

    P.U.B. expects to heard back from Lijit on these fin­an­cial and private stat­ist­ics issues from P.U.B’s inquiry we sent to Lijit in mid April 2008. When we do we will let great Blog Pub­lish­ers like you know their deal. Cur­rently we are also work­ing with Blog Pub­lish­ers to track per­form­ance hit eval­u­ations of Wid­gets too. Let us know if you have any fol­low up on any of these import­ant issues for the blog community.

    Will pub­lish these res­ults to keep the com­munity of Blog Pub­lish­ers informed on this crit­ic­al com­pon­ent of Wid­gets on our Blogs.

    Barney Mor­an, P.U.B.

  3. bgrier Avatar

    @Barbara Ling: Very Good Point! I neg­lected to men­tion that I needed to manu­ally rein­stall all plu­gins and oth­er cus­tom­iz­a­tions I’d made on the Old Blog. My ana­lyt­ics track­ing scripts are man­aged via plu­gins so it was cru­cial that I had this up and run­ning before I 301’d the old site. Thanks for that!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.