Moving My Static Site to a WordPress site

  • SubscribeToday!

6 users commented


A few comments

1. Why not set up the dev server on a local box? You can change your windows host file and your apache virtual host settings so that resolves to the local site on your computer. When dev is done, you move it and reset the windows host file. You can create a simple script to do this in one click for 1-second changing back and forth; I usually just use example.loc (for local) but that might not work with a lot of rewrites.

2. Why aren’t you just rewriting the URLs (no 301) just a rewrite so you can keep the old URLs? A simple rule to strip off the .html and wouldn’t you have what you want?

said Tom Lambert on December 16th, 2008 at 1:00 am

Good points, but I think I have good ripostes…

The first point was using a local server. Setting up Apache is OK, but I was told many years ago that putting MySQL on a windows box was asking for disaster. That may not be the case now, but in any event I had third party developers working on the WordPress theme and transferring the content, so it made sense to do it on the web server itself as the designers were remote anyway.

The second point… as I say… I SO tried to keep the old urls with a rewrite hack, but the previous urls ended in .htm and even when I implemented the hack, WordPress insisted on adding a trailing slash… (.htm/). I didn’t pick up on this until it went live and by then there was duplication issues all over the place.

It’s nearly all sorted now. Traffic yesterday is down about 12% on the previous highs, but now I have been messing with some of the content and Descriptions, this may be because my traffic is getting more targeted, not worse. Certainly my sales have doubled now. Trebling them will need more work, but all in all a success.

I would recommend making the move from a static site to a CMS based one to others in the same boat, but you really do need to know what you are doing. Nerves of steel and most importantly the ability to react very quickly on the days following the switch. Something is going to go wrong… you just need to be able (or pay someone else to be able) to spot the problems quickly enough.

said Dixon Jones on December 16th, 2008 at 9:36 am


How nice of WP to help you out like that. I don’t think I quite understood what you were saying there the first time.

>>MySQL on a windows box

I don’t know about a production site, but I’ve mirrored tons of MySQL DBs to Windows, and ones a lot bigger and more cumbersome than the typical WP database. I’ve never had a problem since MySQL 3.??? (so many years). Some things (MySQL but also PHP scripts in general) can be surprisingly slow, but since you’ll typically only have one concurrent request….

Anyway, I’ve rarely had a problem with building on Windows and rolling out to *nix. I get it running. FTP everything over to a dummy directory (, upload the DB, and then just change the directory names. If I don’t like it, change the names back and test some more.

said Tom Lambert on December 17th, 2008 at 6:33 am
said AussieWebmaster (AussieWebmaster) on January 3rd, 2009 at 12:47 am

thanks for the useful info
i would wanna try wordpress soon

Yours sincerely,

said don on January 21st, 2009 at 2:55 am

I would suggest to go by the wordpress way. You can create a new WP based site and add all the data, pages, posts in a default manner. Then simply edit .htaccess file and tell about permanent redirect like this

Redirect 301

i hope this is easier without messing up anything. Moreover, i think www or non www is a personal choice but its wise to stick with any one of these option and not both. Google or other search engines might treat both of them as separate sites.

said Katie @ Women Magazine on November 9th, 2010 at 7:29 am

Leave a reply

Categories Archives Who’s saying what

Recent Posts Recent CommentsBadges
View additional information about through Majestic SEO Site Explorer.