Patryk

Redirect any “not found” (404) page to homepage with 301 (SEO) redirect code + Google Analytics (utm_source=404&utm_medium=Redirect&utm_campaign=404)

PRyC WP: 404 to Homepage 301 redirect

Redirect any "not found" (404) page to homepage with 301 (SEO) redirect code + Google Analytics (utm_source=404&utm_medium=Redirect&utm_campaign=404)

snakefoot

WordPress 2.3 now includes validation of the permalink URL when using Apache web server, 
but if using IIS then this plugin is still relevant.
Permalink Validator helps Search Engine Optimization (SEO) as it prevents duplicate 
contents on your WordPress blog:
<ul>
<li>Adds trailing back-slash if missing (Can also be done with <a href="http://www.alistercameron.com/2007/01/12/two-wordpress-plugins-you-dont-need-and-shouldnt-use/" rel="nofollow ugc">htaccess</a> or <a href="http://cephas.net/blog/2005/07/11/trailing-slashes-iis-and-f5-big-ip/" rel="nofollow ugc">isapi_rewrite</a>).</li>
<li>Adds or removes www prefix according to your permalink structure (Can also be done with <a href="http://andybeard.eu/2007/04/the-ultimate-wordpress-htaccess-file.html" rel="nofollow ugc">htaccess</a> or isapi_rewrite).</li>
<li>Forces a correct 404 page instead of showing an empty search result when using an invalid URL</li>
<li>Works only on post, pages and categories. Archives based on date (Daily, Monthly, Yearly) and search-result-pages should use noindex. Feed and trackback pages should be added to the robots.txt.</li>
<li>Fixes pagination for WP on IIS.</li>
<li>Fixes trailing slash for pages and categories on WP 2.2 when not having trailing slash in post permalink structure.</li>
</ul>
WordPress it very forgiving when supplying an URL that doesn’t match the 
actual permalink to a post or a page. This is caused by WordPress using some 
very greedy wp_rewrite_rules, which accepts almost any URL as valid.
This means that multiple URLs could be used to reach the page, which search engines 
sees a duplicate content and leads to penalty.
For example it will accept the following permalink URL as valid:
<blockquote>
http://example.com/post/hello-world/2
</blockquote>
Even though the official URL is this:
<blockquote>
http://example.com/post/hello-world/
</blockquote>
Permalink Validator makes a hook to template_redirect, and then adds some 
extra validation of the URL supplied before actually calling the 
theme-templates.
<h3>Version History</h3>
Version 0.8
<ul>
<li>Fixed PHP Warning: strpos() [function.strpos]: Empty delimiter</li>
<li>Converted the PHP file from UTF8 to ANSI (Removed special BOM character in file beginning)</li>
</ul>
Version 0.7
<ul>
<li>Permalink Validator will not perform redirect of POST server request</li>
</ul>
Version 0.6
<ul>
<li>Fixed a redirection bug introduced in 0.5 when the front page is a page of posts</li>
</ul>
Version 0.5
<ul>
<li>WordPress 2.3 includes permalink validation (canonical urls) when using Apache, so this plugin should now only be used with IIS</li>
<li>Added support for HTTPS urls</li>
<li>Added support for special IIS installations where PATH_INFO and SCRIPT_NAME is the same</li>
<li>Added small hack to exclude pages from validation (One is required to edit the source to use it)</li>
<li>Added detection of the plugin <a href="http://vapourtrails.ca/wp-keywords" rel="nofollow ugc">Jerome’s Keywords</a></li>
</ul>
Version 0.4
<ul>
<li>Better guessing of a proper REQUEST_URI</li>
<li>Finds the proper REQUEST_URI when using isapi_rewrite</li>
<li>Finds the proper REQUEST_URI when using IIS Mod-Rewrite</li>
<li>Improved validation as it nows expects a proper REQUEST_URI (Guess Apache is now supported)</li>
</ul>
Version 0.3
<ul>
<li>Fixes trailing slash for pages and categories in WP 2.2 when using a post permalink structure without ending slash.</li>
</ul>
Version 0.2
<ul>
<li>Added support for static front page.</li>
<li>Added detection of integrated <a href="https://bbpress.org/" rel="nofollow ugc">BBPress</a>.</li>
<li>Checks that WordPress has been started before adding hooks</li>
</ul>
Version 0.1
<ul>
<li>Fixes REQUEST_URI for WP on IIS, which also fixes pagination.</li>
<li>Handles permalink structure with or without index.php.</li>
<li>Handles default permalink structure using only post-id.</li>
</ul>
<h3>Testing Procedures</h3>
For each of the different permalink structures:
<ul>
<li>Default permalink structure (Using query string)</li>
<li>Permalink structure with index.php </li>
<li>Permalink structure without index.php (Using ISAPI_rewrite)</li>
<li>Permalink structure ending with .html</li>
<li>All the above in a sub-directory</li>
</ul>
Tries the following pages:
<ul>
<li>Front page and paged</li>
<li>Static page</li>
<li>Post page</li>
<li>Category page and paged</li>
<li>Front page as static page (WP 2.2+)</li>
<li>Front page as post page (WP 2.2+)</li>
</ul>
<h3>Contributors</h3>
<ul>
<li><a href="http://fucoder.com/code/permalink-redirect/" rel="nofollow ugc">Scott Yang</a> for giving me the idea and the example of to how make this plugin.</li>
<li><a href="http://www.articulate.com/blog/" rel="nofollow ugc">Gabe Anderson</a> for giving me the initiative to release this plugin.</li>
</ul>

Permalink Validator

Validates the URL used and if not matching the official permalink then it issues a HTTP 301 or HTTP 404 message.

PRyC WP: 404 to Homepage 301 redirect vs Permalink Validator