12 May 2009, Posted by admin in Whitehat, 2 Comments
I’m not sure how many of you are aware, but WordPress defaults to 302 redirects. This is, for the most part, not a good thing. You’ll probably find this affecting you most when you have people linking to both http://yourdomain.com and http://www.yourdomain.com. If you’re using WordPress’ default 302s, then you won’t get the link juice from the URL that’s being redirected.
This is a bad thing.
I discovered WordPress’ love for 302s just after I wrote the post on how to make your own URL shortener in WordPress so if you’re using this (awesome) method of shortening your own URLs, then make sure your redirects are using 301s instead of 302s. Mine weren’t, and it made Google pretty much throw up.
How Can You Tell If WordPress Is 302ing Posts?
You can either run a server header checker and search for a URL on your domain that you know will redirect – usually something like either the www or non-www version of your domain. I also highly recommend the Live HTTP Headers Firefox plugin, because it’s awesome. Run that, browse around, and it’ll show you the server headers.
How do I make WordPress 301?
As far as I’m aware there’s no way to change this in the WordPress dashboard normally, but the very nice people at Urban Giraffe have made a WordPress redirection plugin which fixes it. Activate the plugin and it’ll automatically make the 302s become 301s. It also lets you do a whole lot of other stuff, which is all useful.
Apparantly Platinum SEO Pack will let you manage redirects too, although I’ve not tried it out yet.
Why Does WordPress Do This?
I really, really don’t know. But honestly, other than this, WordPress is the best. Let’s never fight again WordPress.
(Flickr image from Eric M Martin)