by Peter Hardy-vanDoorn 4.9 (24 reviews)

Maintenance Redirect

Name: Maintenance Redirect
Rating: 4.9 (24 reviews)
Author: Peter Hardy-vanDoorn

Display a maintenance mode page and allow invited visitors to bypass the functionality to preview the site.

Maintenance Redirect ranks #1,949 among WordPress.org plugins with 10,000+ active installations, is #73 of 1,518 in the Performance category, a 4.9/5 rating from 24 reviews, and was last updated May 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 6.9 (Current: 7.1)

v2.2.1 Current Version v2.2.1

Updated 3 months ago Last Update on 21 May, 2026

Refreshed 8 hours ago Last Refreshed on

#73 of 1,518 in Performance Top 5% by installs Downloads -23.1% this week

View on WordPress.org

Rank

#1,949

-1 this week

Active Installs

10K+

-25.8%

KW Avg Position

0.6 better

Downloads

210.9K

+6 today

Support Resolved

— No change

Rating

98%

Review 4.9 out of 5

4.9 (24 reviews)

Next Milestone 20K

Total Progress 34.1%

10K+ 20K+

528

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

Upgrade to Pro

Need 6,592 more installs to reach 20K+

Rank Changes

Current #1,949

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.9

24 reviews

Overall 98%

21 (88%)

3 (13%)

0 (0%)

Support Threads Overview

Resolved

Unresolved

Total Threads

Resolved

Unresolved

Resolution Rate

Security History

Source: WPVulnerability

1 known vulnerability on record · 0 in the last 24 months · checked 1 week ago

Sep 16, 2024

Maintenance Redirect [jf3-maintenance-mode] < 2.1.0

CVE-2024-45453 · Fixed in v2.1.0

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.2.1
Last Updated: May 21, 2026
Requires WP: 6.1+
Tested Up To: 6.9
PHP Version: 7.4 or higher
Author: Peter Hardy-vanDoorn

Support & Rating

Rating: ★ ★ ★ ★ ★ 4.9
Reviews: 24
Support Threads: 1
Resolved: 0%

Keywords

coming soon developer maintenance maintenance mode redirect

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,752

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Wordfence Security - Firewall, Malware Scan, and Login Security

Speed Optimizer - The All-In-One Performance-Boosting Plugin

1M+ installs

#43

WP Fastest Cache - WordPress Cache Plugin

1M+ installs

#47

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

View all Performance plugins

TL;DR

AI summary of the plugin's readme

This plugin is for designers and developers who need to preview sites with clients before public launch or temporarily hide a WordPress site during major updates. It solves the problem of controlling site access during maintenance by displaying a maintenance page while letting invited visitors bypass it.

Bypass access for administrators
Enable/disable without losing settings
200 OK or 503 header options
IP address bypass list
Cookie-based access keys
Email access key links
Custom HTML maintenance page
Redirect to static HTML page

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[] = ""; 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.