P
by dbhynds 1 (0 reviews)

Protected Site

The Protected Site plugin blocks incoming traffic from accessing a blog or a specific blog in a network by requiring visitors to log in to WordPress.

Protected Site ranks #22,541 among WordPress.org plugins with 40+ active installations, is #1,201 of 4,514 in the Security category, a 1/5 rating from 0 reviews, and was last updated Jul 7, 2011. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 3.1 (Current: 7.1)
vtrunk Current Version vtrunk
Updated 15 years ago Last Update on 07 Jul, 2011
Refreshed 15 hours ago Last Refreshed on
#1,201 of 4,514 in Security Top 50% by installs No update in over a year
View on WordPress.org
Rank
#22,541
No change
Active Installs
40+
-4.8%
KW Avg Position
N/A
No change
Downloads
7.9K
+3 today
Support Resolved
0%
No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 50

Total Progress 0%
40+ 50+
14,026
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 10 more installs to reach 50+

Rank Changes

22,425 22,466 22,508 22,550 22,591 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026
22,376 22,523 22,670 22,816 22,963 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026
Current #22,541
Change
Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026
0 10 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026
Downloads
Growth
Peak

Upgrade to Pro

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

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Protected Site

It provides an additional layer of privacy for WordPress blogs. Currently, the only available privacy setting in WordPress is: "I would like my site to be visible to everyone, including search engines (like Google, Bing, Technorati) and archivers." Protected Site allows you to prevent any incoming traffic to your blog unless the user logs in to WordPress as a valid user for that blog.
The Protected Sites plugin has a variety of uses. For example, a web developer can use it to prevent traffic to blogs while their still in development. The site admin can provide a usernames and passwords to the client, designer and other developers working on the project. This allows them to browse the blog and keep track of progress as it is being developed. This allows them to provide feedback throughout the development process, minimizing the need for time-consuming tweaks down the road. Clients can even begin adding content to the site, so that it's ready to go the day the site launches. All the while, the site remains private to all outside traffic.
To protect a site from incoming traffic, simply install and activate the plugin on that site. Once activated, all traffic to the site receive a message alerting them that they must log in to view the page. Once logged in to WordPress, the user will be redirected to the page they were attempting to access and can navigate throughout the site at will. To un-protect a site, simply deactivate the plugin. This plugin is also compatible with a WordPress Network. Activating it on an individual site within a network only protects that site. To activate it on all sites and protect the entire network, choose "Network Activate" in the "Network Admin" section.
By adding an action that overrides the get_header(); function. When get_header(); is called in the template, it runs a function that generates the "Login Required" message, then kills the function. In order to work properly, get_header(); should be the very first code in your template. Otherwise, and code before the get_header(); function will make it into the source code for your page. This means that if you open the and tags, then link a CSS stylesheet, the "Login Required" message will inherit this style. To prevent this, ensure that your header.php file contains the tag.

More plugins by dbhynds

Sign In / Register

You need to sign in or register to use this feature.