PiotrPress

Clearcode

<p>This plugin allows you to create simple redirect requests to another page on your site or elsewhere on the web.</p>
<p>Redirects format is similar to the one that Apache uses. The <code>From</code> field should be relative to your website root. The <code>To</code> field can be either a full URL to any page on the web, or relative to your website root.<br />
From: <code>/old-page/</code> To: <code>/new-page/</code><br />
From: <code>/old-page/</code> To: <code>http://example.com/new-page/</code></p>
<p>To use wildcards, put an asterisk <code>*</code> after the folder name you want to redirect.<br />
From: <code>/old-folder/*</code> To: <code>/redirect-everything-here/</code></p>
<p>You can also use the asterisk <code>*</code> in the <code>To</code> field to replace whatever it matches in the <code>From</code> field.<br />
From: <code>/old-folder/*</code> To: <code>/some/other/folder/*</code><br />
From: <code>/old-folder/*/content/</code> To: <code>/some/other/folder/*</code></p>


CC-Redirects

This plugin allows you to create simple redirect requests to another page on your site or elsewhere on the web.

<p>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.</p>
<p>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.</p>
<p>.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.</p>
<h3>Quick Links</h3>
<p><a href="https://github.com/nk-crew/redirect-txt" rel="nofollow ugc">GitHub</a></p>
<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>
<p>Open <code>Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Redirect.txt</code> and provide a list of URLs here. Here is an example of available syntax:</p>
<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>
<p>The same rules without comments:</p>
<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.

CC-Redirects vs Redirect.txt