roehler

<p>BasisRedirects helps you create and manage redirects (301/302/307/308) with an intuitive admin UI.<br />
Includes bulk tools, CSV import/export, analytics, and a link scanner to find broken links.</p>
<h3>External services</h3>
<p>This plugin’s optional Link Scanner feature can make outbound HTTP requests. There is no single third‑party API used; requests go directly to the destination sites you choose to scan.</p>
<ul>
<li>What service: Direct HTTP requests via the WordPress HTTP API (wp_remote_head/wp_remote_get) to the URLs you select. The scanner may also fetch each target host’s robots.txt (e.g., https://your-domain.example/robots.txt) to respect crawl rules.</li>
<li>What data is sent: The destination URL is requested with a user agent of “BasisRedirects-LinkScanner/1.0” and standard HTTP headers. No personal data is sent by the plugin. You control which hosts and paths are scanned (by default restricted to your own site; you can change this in the scan settings).</li>
<li>When: Only when an administrator starts a scan or enqueues URLs on the Link Scanner admin page. If you do not use the Link Scanner, no outbound requests are made by this feature.</li>
<li>Terms/Privacy: Requests are made directly to the destination sites you choose; their respective Terms of Service and Privacy Policies apply. The plugin itself does not send data to any third‑party service provider. WordPress (the platform) privacy policy: https://wordpress.org/about/privacy/</li>
</ul>


BasisRedirects

Manage URL redirections with bulk management, import/export, logs, analytics, and a link scanner.

<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.

BasisRedirects vs Redirect.txt