WP Plugin to automatically create 301s?

Redirection

Thanks for the quick response Brian.

I had a look at Redirection - it's definitely an awesome plugin, but I don't think it's quite what I'm looking for - this one you still have to manually configure each 404 to a 301 right? It doesn't automatically step in if a 404 occurs, it only logs it, and then AFTERWARDS you can setup a 301 for the 404s that it logged.....

....or did I just not read it's features correctly?

Oh and I am aware it can create 301s automatically if a post URL changes, however I'm thinking more along the lines where external links have been pointing to a URL that was never part of the Wordpress install (ie in a previous life the domain was in plain HTML), so obviously there is no "record" of the old URL.....

Are you looking at something that does this dynamically on the fly? If so, I can't think of anything that does this.

Hi Rus

Yes, that's exactly what I'm thinking. Is it even possible?

Whether you do it via a plugin or in your .htaccess file, you will need to know the old URL in order to have it re-directed if the old URL is not on your site.

Redirection (or any other plugin) will only know about URLs in the current site.

Cheers,

Martin.

hmm. Is there a way to programatically tell WordPress that if it's about to serve up a 404 page, to redirect the user then?

The issue is that we have no idea what a lot of the old URLs are, so we want to be proactive, and try and "stomp them out" without having to just monitor error logs over a few months.

How to Redirect a Web Page Using a 301 Redirect

You've just redesigned some pages of your web site. The
pages have high search engine rankings that you don't want
to lose. How can you safely redirect web site traffic from
your old pages to the new pages without losing your
rankings? You can do this by using a " 301 redirect "

What is 301 redirect?

301 redirect is the best method to preserve your current
search engine rankings when redirecting web pages or a web
site. The code "301" is interpreted as "moved permanently".
After the code, the URL of the missing or renamed page is
noted, followed by a space, then followed by the new
location or file name. You implement the 301 redirect by
creating a .htaccess file.

What is a .htaccess file?

When a visitor/spider requests a web page, your web server
checks for a .htaccess file. The .htaccess file contains
specific instructions for certain requests, including
security, redirection issues and how to handle certain
errors.

How to implement the 301 Redirect

1. To create a .htaccess file, open notepad, name and save
the file as .htaccess (there is no extension).

2. If you already have a .htaccess file on your server,
download it to your desktop for editing.

3. Place this code in your .htaccess file:

redirect 301 /old/old.htm http://www.you.com/new.htm

4. If the .htaccess file already has lines of code in it,
skip a line, then add the above code.

5. Save the .htaccess file

6. Upload this file to the root folder of your server.

7. Test it by typing in the old address to the page you've
changed. You should be immediately taken to the new
location.

Notes: Don't add "http://www" to the first part of the
statement - place the path from the top level of your site
to the page. Also ensure that you leave a single space
between these elements:

redirect 301 (the instruction that the page has moved)

/old/old.htm (the original folder path and file name)

http://www.you.com/new.htm (new path and file name)

When the search engines spider your site again they will
follow the rule you have created in your .htaccess file.
The search engine spider doesn't actually read the
.htaccess file, but recognizes the response from the
server as valid.

During the next update, the old file name and path will be
dropped and replaced with the new one. Sometimes you may
see alternating old/new file names during the transition
period, plus some fluctuations in rankings. According to
Google it will take 6-8 weeks to see the changes reflected
on your pages.

Other ways to implement the 301 redirect:

1. To redirect ALL files on your domain use this in your
.htaccess file if you are on a unix web server:

redirectMatch 301 ^(.*)$ http://www.domain.com
redirectMatch permanent ^(.*)$ http://www.domain.com

You can also use one of these in your .htaccess file:

redirect 301 /index.html http://www.domain.com/index.html
redirect permanent /index.html http://www.domain.com/index.html
redirectpermanent /index.html http://www.domain.com/index.html

This will redirect "index.html" to another domain using a
301-Moved permanently redirect.

2. If you need to redirect http://mysite.com to
http://www.mysite.com and you've got mod_rewrite enabled on
your server you can put this in your .htaccess file:

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^example\.com
RewriteRule ^(.*)$ http://www.example.com/$1 [R=permanent,L]

or this:

Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTP_HOST} ^domain\.com$ [NC]
RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]

Tip: Use your full URL (ie http://www.domain.com) when
obtaining incoming links to your site. Also use your full
URL for the internal linking of your site.

3. If you want to redirect your .htm pages to .php pages
andd you've got mod_rewrite enabled on your server you can
put this in your .htaccess file:

RewriteEngine on
RewriteBase /
RewriteRule (.*).htm$ /$1.php

4. If you wish to redirect your .html or .htm pages to
.shtml pages because you are using Server Side Includes
(SSI) add this code to your .htaccess file:

AddType text/html .shtml
AddHandler server-parsed .shtml .html .htm
Options Indexes FollowSymLinks Includes
DirectoryIndex index.shtml index.html

Frequently Asked Question:
What's the difference in using a 301 redirect versus a meta redirect?

Meta Redirect
To send someone to a new page (or site) put this in the head of your
document:

<meta http-equiv="refresh" content="10;
url=http://mynewsite.com/">

Content="10; tells the browser to wait 10 seconds before
transfer, choose however long you would like, you can even
choose 0 to give a smoother transition, but some (really
old) browsers aren't capable of using this so I'd suggest
putting a link on that page to your new site for them.

With a meta redirect the page with the redirect issues a
200 OK status and some other mechanism moves the browser
over to the new URL. With a 200 OK on both pages, the
search engine wants to index both the start page and the
target page - and that is a known spam method (set up
10,000 domains full of keywords for the search engines to
index then meta redirect the "real visitor" after 0 or 1
seconds to the "real site" ) so using it gets you
penalized.

The 301 redirect simply issues a Permanently Moved message
in the HTTP header which tells the search engine to only
index the target URL.

Conclusion: The safest way to redirect old web pages to the
new pages or old web site to the new web site and keep the
same search engine rankings is to use the 301 redirect. It
will also pass on the page rank from your old site to your
new site.

I use this "Smart 404" for Wordpress


"Instead of quickly giving up when a visitor reaches content that doesn't exist, make an effort to guess what they were after in the first place. This plugin will perform a search of your posts, pages, tags and categories, using keywords from the requested URL. If there's a match, redirect to that content instead of showing the error. If there's more than one match, the 404 template can use some template tags to provide a list of suggestions to the visitor."

Yeah I've looked at that plugin as well. It still doesn't fit what I'm looking for.

It seems all the plugins out there are all retrospective. At this stage I'll presume that's because there is no way to create some sort of redirect on the fly, which sucks, because I think it would be an incredibly useful plugin to have....

Someone just referred me to Link Juice Keeper. It's a little dated, so it looks like it may not be compatible with WP 3.0, but looking at the coding, it's pretty small, so I'm guessing it wouldn't take much to update this. Wishing I could code....