michaeltyson

Leon Stafford

Save your visitors from unhelpful 404 errors!
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.
See the <a href="http://michael.tyson.id.au/smart-404" rel="nofollow ugc">Smart 404 homepage</a> for more information.
<h3>Template tags</h3>
<code>smart404_has_suggestions</code>
Returns true if there are some suggestions, false otherwise
<code>smart404_get_suggestions</code>
Retrieve an array of post objects for rendering manually.
<code>smart404_suggestions</code>
Draw a list of suggested posts.
Pass the parameter “list” to render suggestions as a list.
<code>smart404_loop</code>
Query posts for use in a Loop. Eg:
<pre><code><?php smart404_loop(); ?>
<?php while (have_posts()) : the_post(); ?>
 <h2><a href="<?php the_permalink() ?>"><?php the_title(); ?></a></h2>
 <?php the_excerpt(); ?>
<?php endwhile; ?>
</code></pre>
Note that the loop will not display pages correctly, as it is not built to support them. It is recommended that if you use 
a loop like that above, do not enable searching of pages.
<code>smart404_get_search_terms</code>
Retrieve an array of search terms used to populate the suggestions list, for use with contextual highlighting, etc.
For support and latest source code, please visit https://github.com/leonstafford/smart-404

Smart 404

Automatically redirect to the content the user was most likely after, or show suggestions, instead of showing an unhelpful 404 error.

With Redirect.txt, you can provide a simple list of URLs and their destinations with no post-creation bloat, no limitations, and just a simple editor.
There are many good redirect plugins that have been developed for years and have a strong code base. But we don’t like the idea of creating separate posts/entries for each redirection rule. We simply need to add, remove, and manage redirects in a simple and bulk way.
.htaccess and nginx configs are OK, but we don’t want to edit configs placed somewhere in server directories; we want to open our admin panel and add redirects easily. We also don’t care about wrong config configurations, which will stop your server.
<h3>Quick Links</h3>
<a href="https://github.com/nk-crew/redirect-txt" rel="nofollow ugc">GitHub</a>
<h3>Features</h3>
<ul>
<li>Path redirects</li>
<li>Full URL redirects</li>
<li>Post ID redirects</li>
<li>RegEx redirects</li>
<li>Redirect logs</li>
<li>404 logs</li>
</ul>
<h3>Usage</h3>
Open <code>Tools → Redirect.txt</code> and provide a list of URLs here. Here is an example of available syntax:
<pre><code># The links below will automatically use 301 redirects.
/hello: /new-hello

# Support for custom status
# To make 301, 302, 303, 307, or 308 redirects, use a code like this:
308: # All redirections below will use 308 redirect status.

# Support for post ID's
# Redirect from post with ID 1 to post with ID 8:
1: 8

# Support for external redirects:
/external: https://google.com/

# Support for RegEx redirects (automatically detected when the string starts with ^):
^/news/(.*): /blog/$1

# You can use as many comments as you want to categorize your links better.
</code></pre>
The same rules without comments:
<pre><code>/hello: /new-hello

308:

1: 8
/external: https://google.com/
^/news/(.*): /blog/$1
</code></pre>

Redirect.txt

Manage 301 & 302 redirects easily. No posts creation bloat, just a simple list.

Smart 404 vs Redirect.txt