nerdismftw.com

Define allowed routes for your website, all other routes will return a 404 error. Permalinks will be overruled.
Login, Backend routes and local files (like wp-login.php) are always available to prevent a lockout.
Also delete all your page caches after enabling to prevent unwanted routing behavior.
Use cases:
<ul>
<li>Absolute control over all permalinks</li>
<li>Prevent unwanted search engine indexing</li>
<li>Be sure no custom post type adds unwanted permalinks</li>
<li>No frontend needed</li>
</ul>
Important:
<ul>
<li>The routing overrules permalinks and works like a whitelist. Only correct entered routes will go through. You should test the routing before using on production environments</li>
<li>Be careful using several routing- or redirect plugins at the same time</li>
<li>Do not forget to delete all your page caches after enabling/disabling the routing to prevent unwanting routing behavior</li>
</ul>
Behaviour:
<ul>
<li>The used protocol (HTTP or HTTPS) will be ignored</li>
<li>GET params will be ignored</li>
<li>Routes are case sensitive</li>
</ul>
Syntax / Wildcards:
<ul>
<li>The route / allows the index page (Check the checkbox \”Allow index page\”)</li>
<li>Wildcard * allows a single term with an arbitrary value (e.g. category//page/)</li>
<li>Wildcard ** permits all possible combinations of terms (e.g. category/**) This wildcard is only allowed at the end of a route</li>
<li>Wildcards are only allowed as complete terms. Correct: /foo//bar/** Wrong: /foo/ba/test**</li>
</ul>

Allowed Routes

Define only allowed routes for your website. Permalinks will be overruled. Wildcard Support.

Joan Rodas

Sirvelia

Custom Page Routes

Add custom routes easily, without needing to manually update permalinks

Allowed Routes vs Custom Page Routes