craigsimps

This is a super-simple plugin which will turn WordPress’ default <code>/?s=query%20terms</code> into <code>/search/query+terms/</code> if you have pretty permalinks enabled.
This is something which I have been placing into a theme include or in a core functionality plugin until recently, but it makes sense to separate this functionality out into an individual plugin so it can be switched on and off independently.
The plugin has no administrative interface or control panel. Activation turns it on, deactivation turns it off. Once activated, performing a search using the standard WP search widget should give you a much nicer search URL.

Simple Search Rewrite

Redirects search results from /?s=query to /search/query/, and converts %20 to +.

cartpauj

Shortcode Redirect sends visitors from any post or page to another URL. No settings screens, no database tables — just drop it in where you need it.
There are two ways to use it, and both produce the exact same front-end output.
1. The Redirect block (new in 1.1.0)
In the block editor, add the Redirect block from the Widgets category. The block sidebar exposes three simple fields:
<ul>
<li>Destination URL — where the visitor should end up</li>
<li>Seconds to wait — how long to pause before redirecting (<code>0</code> = immediate)</li>
<li>Show “redirecting” message — toggle the visible “Please wait…” line on or off</li>
</ul>
The editor shows a live summary of what the block will do, e.g. “Redirects to https://example.com — after 3 seconds · message shown”. No shortcode syntax to memorize.
2. The classic shortcode
Paste into any post or page:
<pre><code>[redirect url='https://example.com' sec='3']
</code></pre>
Shortcode attributes:
<ul>
<li><code>url</code> — destination URL (required)</li>
<li><code>sec</code> — seconds to wait before redirecting (optional, default <code>0</code>)</li>
<li><code>show_message</code> — set to <code>false</code>, <code>0</code>, <code>no</code>, or <code>off</code> to hide the “redirecting” message (optional, default <code>true</code>, new in 1.1.0)</li>
</ul>
Example with all three:
<pre><code>[redirect url='https://example.com' sec='5' show_message='false']
</code></pre>
Same output either way
Block or shortcode, the front-end renders the same single <code><meta http-equiv="refresh"></code> tag (plus the optional one-line message). No JavaScript. No server-side redirect. No third-party tracking. Existing <code>[redirect]</code> shortcodes from earlier versions continue to work unchanged.
<h4>Features</h4>
<ul>
<li>Block editor support — native “Redirect” block (new in 1.1.0)</li>
<li>Classic shortcode — <code>[redirect]</code> works exactly like it always has</li>
<li>Optional delay — choose how many seconds to wait before redirecting</li>
<li>Silent mode — hide the “redirecting…” message for a clean, blank-page redirect (new in 1.1.0)</li>
<li>Lightweight — a single PHP file plus a small block; no settings, no tables, no dependencies</li>
<li>Backwards compatible — upgrading from 1.0.x is drop-in</li>
</ul>

Shortcode Redirect

Redirect any post or page — with a native block or a classic shortcode. Optional delay. Optional "redirecting" message. Zero configuration.

Simple Search Rewrite vs Shortcode Redirect