codecide

MetaRedirect is a lightweight module that allows any post to be redirected to a URL address stored in a custom (meta) field. You can use MetaRedirect in cases where your posts need to act as pass-through for other web destinations, either internal or external. This plugin does not have any side-effects and uses a minimal amount of resources.
The module can be disabled from the settings page. Important: If you leave the Enabled box unchecked, the plugin will have no effect at all.
You can configure MetaRedirect to use any custom field to hold the value of the target URL.
You can set up the redirection to either permanent (301), or temporary (302). Using the former setting, the client browsers or search engines that hit your post’s page will remember the redirection and perform it automatically the next time they visit your post. If you use a temporary redirection instead, those clients will request the redirection anew. In other words, only use Permanent (301) redirections if you are sure that the target will never change.
You can further configure the redirection’s trigger to be permanent or provisional. A permanent trigger will enforce the redirection automatically. A provisional trigger will only perform the redirection when a preset query parameter (see below) is found in the requested URL. For example, if you set the trigger parameter to jump, the post’s URL will be redirected if, and only if, it contains “?jump”, otherwise nothing will happen.
The trigger parameter is a string used to trigger provisional redirections (see above). URL parameters appear after the question mark (“?”) in the URL. Though query parameters typically consists of key/value pairs separated by an equal sign (e.g., key=value) the MetaRedirect provisional trigger only requires the key to be present (the left side of the =) and will ignore any associated value.
Finally, you can set the redirection to append custom URL parameters to the target These additional parameters need to be URL-encoded key/value pairs; the parameters will be merged with the original URL seamlessly.
<h3>Roadmap</h3>
<ul>
<li>Redirection tracking report </li>
<li>Redirected posts listing page</li>
</ul>
<h3>Donations</h3>
None needed.

MetaRedirect

MetaRedirect is a lightweight module that allows any post to be redirected to a URL address stored in a custom (meta) field.

fullworks

Alan Fuller

WPVibes

Easily redirect WordPress 404 error pages to the homepage or any other page. The plugin supports permanent redirects (HTTP response status code 301) and temporary redirects (HTTP response status code 302). The plugin will redirect 404 error pages to the homepage when you activate it by using the 301 permanent redirects.
To configure it open <code>Dashboard >> Settings >> General Settings and scroll down to the bottom.</code>
Note Permalinks have to be enabled in <code>Dashboard >> Settings >> Permalinks</code> in order for the 404 Redirect to work properly.
<h3>New Feature</h3>
<ul>
<li>404 errors can be logged with this plugin so you can examine what pages may be missing.</li>
</ul>
Redirect 404 Error Page is very useful for themes with an ugly, uninformative 404 server error page that can’t be changed without missing code and set to still return 404. Simply create a new custom 404 error page and activate the plugin – problem solved!
It’s also beneficial in situations when a lot of content has been removed from the site. For those situations, create a new page explaining what happened and simply configure Redirect 404 to use that page.
It is an ideal plugin for missing page redirection.

Redirect 404 Error Page to Homepage or Custom Page with Logs

Redirect the 404 error page to the homepage or any other page with logs. Supports permanent (301), temporary (302) redirects & not found (404).

MetaRedirect vs Redirect 404 Error Page to Homepage or Custom Page with Logs