villdev

This plugin extends WooCommerce’s built-in “Coming Soon” functionality by allowing you to whitelist specific pages that should remain accessible even when your store is in coming soon mode and set to apply to the entire site.
Important: This plugin only works when WooCommerce’s “Coming Soon” mode is enabled AND configured to “Apply to entire site” (not just store pages).
Perfect for: 
* Keeping terms of service and privacy policy pages accessible 
* Allowing contact pages to remain available 
* Maintaining access to important information pages 
* Creating exceptions for legal compliance requirements
Key Features: 
* Simple checkbox interface to select pages/posts 
* Search functionality to quickly find pages 
* Works seamlessly with WooCommerce’s coming soon mode 
* No configuration needed – just activate and select pages 
* Lightweight and efficient with built-in caching
How it works: 
1. Enable WooCommerce’s “Coming Soon” mode in WooCommerce > Settings > General 
2. Important: Set it to “Apply to entire site” (not just store pages) 
3. Go to Settings > Coming Soon Whitelist 
4. Check the pages you want to remain accessible 
5. Save your settings
The plugin automatically integrates with WooCommerce’s coming soon system and only affects the pages you’ve specifically whitelisted.
<h3>1.0.0</h3>
<ul>
<li>Initial release</li>
<li>Simple checkbox interface for selecting pages/posts to whitelist</li>
<li>Smart detection of WooCommerce Coming Soon mode status</li>
<li>Built-in caching for optimal performance</li>
<li>Full WordPress and WooCommerce compatibility</li>
<li>Translation ready</li>
</ul>
<h3>1.0.0</h3>
Initial stable release. Clean installation with all core features included.

Coming Soon Whitelist

Allow specific pages to remain accessible while WooCommerce's "Coming Soon" mode is active site-wide.

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.

Coming Soon Whitelist vs Allowed Routes