For this I use the beta version of the Wavr plugin, and a test wave I made:

The code to add the above wave is:

In this testwave I added the bot “easypublic@appspot.com”, which makes the wave public for you (I couldn’t get the “official” way of adding public@a.gwave.com to work).

You’ll need a Wave account to see the above; if you don’t, I currently have 2 invites to spare, just comment below.

In spirit of the site, here are some of the pitfalls of moving WordPress:

Getting search engines to redirect correctly

I set up the old site to return HTTP 301 – Moved Permanently by putting the following .htaccess file in the /wp folder:

This ensures that (most) search engines consider the new location as equivalent to the previous, and will – hopefully – make only the new location appear in search results.

All my WordPress pages are blank after the move!

Assuming you’ve followed the standard operating procedure for moving the blog, and all database entries are updated to the new path (I did this part manually, but the linked procedure seems OK), the most likely reason is that your plugins are still using the old path. If you can still re-enable the old path (in my case, I moved /wp to /wp-deactivated), go in to the admin panel and deactivate all plugins.

They can also be deactivated from the database, if you have no way of returning to the old installation:

When everything works again you can reactivate the plugins, and things should be back to normal.