by Peter Hardy-vanDoorn
4.9 (24 reviews)
Maintenance Redirect
Display a maintenance mode page and allow invited visitors to bypass the functionality to preview the site.
Compatible with WP 6.9.4
v2.2.1
Current Version v2.2.1
Updated 1 month ago
Last Update on 10 Feb, 2026
Refreshed 6 hours ago
Last Refreshed on
Rank
#2,023
—
No change
Active Installs
10K+
—
No change
KW Avg Position
N/A
—
No change
Downloads
211.3K
+18 today
Support Resolved
100%
—
No change
Rating
98%
Review 4.9 out of 5
4.9
(24 reviews)
Next Milestone 20K
10K+
20K+
537
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 6,688 more installs to reach 20K+
Rank Changes
Current
#2,023
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.9
24 reviews
Overall
98%
5
21
(88%)
4
3
(13%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 0 of 0| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| No keyword data available yet. | ||||
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Support Threads Overview
Resolved
Unresolved
1
Total Threads
1
Resolved
0
Unresolved
100%
Resolution Rate
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.2.1
- Last Updated
- Feb 10, 2026
- Requires WP
- 6.1+
- Tested Up To
- 6.9.4
- PHP Version
- 7.4 or higher
- Author
- Peter Hardy-vanDoorn
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.9
- Reviews
- 24
- Support Threads
- 1
- Resolved
- 100%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,714
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#953
WP-Sweep
100K+ installs
#285
Nginx Helper
100K+ installs
#290
SSL Insecure Content Fixer
100K+ installs
#302
Frequently Asked Questions
Common questions about Maintenance Redirect
This plugin is designed to block only the normal display of pages in the web browser. It will not effect any other calls to WordPress, such as the Rest API. This means that services such as the PayPal and Stripe integrations in WooCommerce, for example, are still able to function for testing WooCommerce stores. It also means that all of the usual WordPress REST endpoints are active. If you wish to completely lock down your site's data then you will need to find an additional solution to block those calls.
There is a filter which allows you to programatically bypass the redirection block: wpjf3_matches This allows you to run pretty much any test you like, although be aware that the whole redirection thing runs before the $post global is set up, so WordPress conditionals such as is_post() and is_tax() are not available. This example looks in the $_SERVER global to see if any part of the URL contains "demo" function my_wpjf3_matches( $wpjf3_matches ) { if ( stristr( $_SERVER['REQUEST_URI'], 'demo' ) ) $wpjf3_matches[] = "<!-- Demo -->"; return $wpjf3_matches; } add_filter( "wpjf3_matches", "my_wpjf3_matches" ); Props to @brianhenryie for this!
By default, Maintenance Redirect uses the manage_options capability, but that is normally only applied to administrators. As it stands, a user with a lesser permissions level, such as editor, is able to view the admin side of the site, but not the front end. You can change this using this filter: wpjf3_user_can This filter is used to pass a different WordPress capability to check if the logged-in user has permission to view the site and thus bypass the redirection, such as edit_posts. Note that this is run before $post is set up, so WordPress conditionals such as is_post() and is_tax() are not available. However, it's not really meant for programatically determining whether a user should have access, but rather just changing the default capability to be tested, so you don't really need to do anything other than the example below. function my_wpjf3_user_can( $capability ) { return "edit_posts"; } add_filter( "wpjf3_user_can", "my_wpjf3_user_can" );
Yes, there is no problem when using access keys. However, using the IP address whitelist is now a little more problematic as, due to an over-zealous security researcher, I have been forced to drop the support for testing the http X-FORWARDED-FOR header which supplies the original IP address rather than the proxy IP address. This is unfortunate as it means that you will have to whitelist the proxy's IP address rather than the end-user's address.