Some solutions, more problems

Through liberal use of RedirectMatch, I’ve solved some link issues caused by my shift from Blogger to WordPress, but I still have several other problems.

I have solved the problems of redirecting from /journal and removing the .html extension by using 301 RedirectMatch. It was really a matter of trial and error, especially getting the .html extensions to go away without affecting, but I think I managed it. If you see any weird behaviors or post links that don’t work, let me know. (Of course, I still haven’t solved the problem of Blogger’s post links not including the articles a, an, and the.)

I became aware of two new problems while using Google’s cached search results to test my settings: archive pages and “label” pages. Blogger archive URLs were formatted like /2004_07_01_archive, while WordPress’ are the much nicer /2004/07/. Similarly, Blogger keywords/tags, called labels, had page URLs formatted like /labels/travel, while WordPress’ tag pages are /tag/travel/. I think I can write a couple more RedirectMatch statements to fix these problems.

I do wonder if all the RedirectMatch-ing is going to hose my server. Is there another way I should be doing this? I guess in time search engines will map the new addresses for all the posts, and then I can remove the redirect expressions…right?

So now my issues are:

  • Removing the articles (a, an, the) from WordPress URLs
  • Redirecting old archive page URLs [done]
  • Redirecting old label page URLs to tag URLs [done]
  • New: Replacing spaces with dashes in tag links
  • Changing image links from Blogspot to my server*

* Update: I had thought that the images were all on my server already and I just needed to change the links. It turns out that all images uploaded after November 3, 2009 are saved to Blogspot and do not exist on my server. So I will need to upload those images and then change the links…manually.