Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

How to Make a WordPress Site Private

How to Make a WordPress Site Private

Short answer

To make a WordPress site private, set single pages to Private or Password Protected, or install a login-wall plugin such as My Private Site and turn on its privacy setting so logged-out visitors are sent to the login page. WordPress core has no whole-site privacy switch, and the search engine visibility setting does not block visitors.

Key takeaways

  • WordPress core has no whole-site privacy switch, so a plugin is needed to force a login for the whole site.
  • Private pages are visible only to Administrators and Editors, even to visitors who guess the URL.
  • Password protected pages show a prompt and need no WordPress account, only the password.
  • The Discourage search engines setting only asks search engines not to index the site and blocks nobody.
  • My Private Site has 20,000+ active installations and redirects logged-out visitors to the login page.
  • Uploaded images and files can still be opened by direct URL on most private sites.

What does it mean to make a WordPress site private?

A private WordPress site hides its content from logged-out visitors and shows it only to people who log in.

WordPress has no built-in switch that locks a whole site behind a login. WordPress.org states that hiding a whole blog from public view “is not part of the core WordPress product” as of November 2026.

You can still get there in three ways: hide single pages, password-protect single pages, or add a plugin that forces a login for the whole site. Each method blocks a different amount, so pick the one that matches your goal before you change anything.

Which method should you pick first?

Pick per-page privacy for one or two pages, a password for shared pages, and a login-wall plugin for the whole site.

The table below compares the three main methods. A fourth option, “Discourage search engines” in “Settings → Reading”, is not privacy at all, so it is listed only to warn you away from it.

MethodWhat it hidesWho can see itBest for
Private page or postOne page or postAdministrators and Editors onlyInternal pages for staff
Password protected pageOne page or postAnyone with the passwordSharing a page with a client
Login-wall pluginThe whole siteLogged-in users onlyIntranets, family sites, staging
Discourage search enginesNothingEveryoneNot privacy; it only asks search engines not to index the site

Time needed is about 5 minutes for a single page and about 15 minutes for a whole-site plugin. You need an Administrator account for every method below.

How do you make one page or post private?

Open the page, change its visibility to Private, and save it.

Private content is published but hidden from the public. WordPress.org says private posts "are automatically published but not visible to anyone but those with the appropriate permission levels (Editor or Administrator)". A visitor who guesses the URL still cannot see the content, and the page does not appear in post lists.

  1. Go to “Pages → All Pages” or “Posts → All Posts” in the dashboard.
  2. Open the page or post you want to hide.
  3. In the settings sidebar, find “Status & Visibility” and click the link next to “Visibility”.
  4. Select “Private”.
  5. Click “Update” or “Publish” to save.

The status changes to “Privately Published”. Only Administrators and Editors can read private posts, because WordPress.org lists read_private_posts and read_private_pages as capabilities held by those two roles.

Authors, Contributors and Subscribers cannot see them. WordPress has 6 pre-defined roles in total: Super Admin, Administrator, Editor, Author, Contributor and Subscriber, according to WordPress.org's Roles and Capabilities page.

If your site has more than one Editor or Administrator, note that they can see private posts in the edit screen and can even make them public again. WordPress.org warns about this directly on its content visibility page.

How do you password-protect a page or post?

Choose “Password Protected” in the same visibility menu, type a password, and save.

A password-protected page shows its title and a password prompt to visitors. WordPress.org says a visitor "must enter the password in the box in order to see the content of the post or Page".

Anyone with the password can read it, and they do not need a WordPress account. That makes this method a good fit for sharing a draft with a client or a price list with a small group.

  1. Open the page or post in the editor.
  2. In the settings sidebar, open “Status & Visibility” and click the link next to “Visibility”.
  3. Select “Password Protected”.
  4. Type a password in the box that appears.
  5. Click “Update” or “Publish”.

Use a password that is long and hard to guess, and send it through a separate channel from the page link. Do not reuse a password you use elsewhere. If the password leaks, change it in the same menu and the old password stops working at once.

How do you hide a site from search engines?

Tick “Discourage search engines from indexing this site” in “Settings → Reading”, then click “Save Changes”.

This setting sends a request to search engines, not a block. WordPress adds a noindex, nofollow meta tag to every page and turns off the built-in XML sitemap when the box is ticked.

Search engines may still list pages they already know about, and any visitor with a direct link can still open every page. Treat this as a way to keep a new site out of search results while you build it, never as privacy.

For a stronger result, pair this setting with real access control from the sections above. If you run a staging or client preview site, a login-wall plugin is the safer choice. You can read how to set up a staging site for WordPress so unfinished work never sits on a public URL at all.

How do you make the whole site require a login?

Install a login-wall plugin such as My Private Site, then turn on its privacy setting.

My Private Site is a free plugin on WordPress.org that "makes your WordPress site private so only logged-in users can see your content", with one click to restrict all posts and pages and send logged-out visitors to the login screen.

Its WordPress.org page lists 20,000+ active installations and an update dated 1 September 2026, with a rating of 4.5 out of 5 from 82 reviews, checked November 2026.

  1. Go to “Plugins → Add New” in the dashboard.
  2. Search for “My Private Site” and click “Install Now”, then “Activate”.
  3. Go to “My Private Site → Site Privacy” in the dashboard menu.
  4. Tick “Enable Privacy” (listed as “Enable login privacy” in some versions) and save.
  5. Open your site in a private browser window and confirm you land on the login page.

The plugin also offers an option to block unauthenticated access to the WordPress REST API. Turn that on too, because the REST API can expose post titles and content to logged-out requests even when pages are hidden. You can add extra two-factor authentication to WordPress so stolen passwords alone do not open a private site.

How do you give people access to a private site?

Create a user account for each person and give them the Subscriber role.

Subscribers can log in and read the site, and WordPress.org says the Subscriber role has just the “read” capability, so they cannot edit anything. Do not hand out your Administrator login, and do not leave “Anyone can register” turned on unless you want strangers to create accounts.

  1. Go to “Users → Add New”.
  2. Enter a username and email address, then pick a password or let WordPress generate one.
  3. Set “Role” to “Subscriber”.
  4. Click “Add New User” and send the person their login details separately.

Check “Settings → General” first: the “New User Default Role” setting controls the role given to anyone who registers on their own. Set it to “Subscriber” so a self-registered account never gets editing rights by accident. You can learn more in the guide on how to add users in WordPress.

Learn WordPress has a User management lesson that walks through the 5 main roles and what each one can do in the dashboard.

From the command line, WP-CLI can create users too: its home page lists wp user for creating, updating and resetting passwords.

What stays public on a private site?

Uploaded files such as images and PDFs can still be opened by anyone who knows the direct URL.

This is the most common surprise with login-wall plugins. My Private Site states in its limits that it "won't restrict images and other media and text files directly accessed by their URL", because files in wp-content/uploads are served by the web server before WordPress runs.

The same applies to private pages: the page is hidden, but an image attached to it is not.

Do not upload contracts, medical records, or other sensitive files to a private WordPress site and assume the login wall covers them.

For files that must stay secret, keep them off the public web server or protect the uploads folder at the server level with HTTP authentication. You can also protect wp-admin with HTTP authentication as an extra layer in front of the dashboard.

How do you check that the site is really private?

Open the site in a private browser window while logged out, and try the homepage, a post, and a media file URL.

A private window has no login cookie, so it shows what a stranger sees. Run these 4 checks:

  • The homepage redirects to the login page or shows a holding page.
  • A post URL shows the login page, not the post.
  • A search engine query for site:yourdomain.com shows no new pages after a few days.
  • A direct image URL still loads, which confirms the uploads limit above.

Also test with a Subscriber account to confirm that real members can read the site after logging in. If a page still shows while logged out, check that its visibility is Private, that the plugin is active, and that no caching plugin is serving a stored copy of the page to visitors.

What mistakes should you avoid?

Do not confuse “Discourage search engines” with privacy, and do not assume uploads are hidden.

The 5 mistakes below cause most private-site failures:

  • Using “Discourage search engines” as the only protection, which blocks nobody.
  • Making a page Private and expecting Authors or Subscribers to read it, when only Editors and Administrators can.
  • Sharing one Administrator login with a whole team instead of creating Subscriber accounts.
  • Uploading sensitive files and assuming the login wall hides them.
  • Forgetting to turn off self-registration, which lets strangers create accounts.

Re-check the site after every plugin update, because an update can reset a setting or clash with a caching plugin. A 5-minute logged-out check once a month catches most problems early.

Frequently asked questions

Can I make my whole WordPress site private without a plugin?

No. WordPress core lets you hide single posts and pages, but it has no setting that locks the whole site behind a login. You can set each page to Private or Password Protected by hand, or install a login-wall plugin such as My Private Site to cover the whole site at once.

Who can read a private WordPress page?

Only Administrators and Editors can read private pages and posts. Authors, Contributors and Subscribers cannot see them, and logged-out visitors cannot see them even with the exact URL. Editors and Administrators can also see private posts in the edit screen and change them back to public.

Does the Discourage search engines setting make my site private?

No. It adds a noindex, nofollow tag and turns off the built-in XML sitemap, which asks search engines not to list the site. Any visitor with a direct link can still open every page. Use it only to keep a new site out of search results while you build it.

Are images private on a private WordPress site?

Usually not. Files in the uploads folder are served by the web server before WordPress runs, so a login-wall plugin cannot check who is asking. Anyone with the direct file URL can open an image or PDF. Keep sensitive files off the public server or protect the uploads folder at the server level.

What user role should I give members of a private site?

Give them the Subscriber role. Subscribers can log in and read the site, and their only default capability is read, so they cannot edit posts, change settings or install plugins. Set the new user default role to Subscriber in Settings, General so self-registered accounts never get more access.

Sources

  1. Set blog content visibility (Block Editor) WordPress.org
  2. Roles and Capabilities WordPress.org
  3. My Private Site WordPress.org
  4. Logging In WordPress Developer Resources
  5. User management Learn WordPress
  6. WP-CLI WP-CLI

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.