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.

WebFactory

A perfect plugin for creating a new site from an old site or changing the domain name, and managing all of the redirects and broken URLs by using redirection.
Find the link to 301 Redirects in the main Settings menu. 
404 error log can be found on the same page, and on the admin dashboard.
301 Redirects plugin creates a new table in the WP database called ‘WP_PREFIX_ts_redirects’ that stores all of your redirect rules and redirections. On plugin deactivation the table is not deleted. When you delete the plugin then the redirection table is deleted forever.
Why is the 404 error log limited to the last 50 errors? 
By default, the 404 error log is limited to the last (chronologically) fifty 404 errors. Since the 404 log doesn’t use a custom database table for storage but rather an array saved in WP options, 50 is a safe number that ensures the 404 log works on all sites, that it doesn’t take up too much space in the database and that it doesn’t slow down the site. 
The code imposes no limits on the log size and you can easily overwrite the default limit by using the 301_redirects_max_404_logs filter or by using the following code snippet to raise the limit to 200:
<pre><code>add_filter('301_redirects_max_404_logs', function($log_max) { return 200; }, 10, 1);
</code></pre>
GDPR compatibility 
We are not lawyers. Please do not take any of the following as legal advice. 
301 Redirects does not use any 3rd party services or CDNs. It does create a 404 error log which saves the following info when a non-existing (404) page is opened: timestamp of the event, URL of the 404 page, user agent based on the user agent string from the user’s browser. No IP related data or any other identifiable user data is saved or processed. Based on that, we feel it’s GDPR compatible, but again, please, don’t take this as legal advice.

301 Redirects & 404 Error Log

Create & manage 301 redirects. Easily test redirects. Includes 404 error log.

Redirect.txt vs 301 Redirects & 404 Error Log