To make one WordPress page private, open Pages, edit the page, change its visibility to Private, and save with Publish (new pages) or Update (existing pages). In the Block Editor, the setting is in the right sidebar under Status & Visibility (sometimes labelled Visibility); in the Classic Editor, it is in the Publish box.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Private is different from password protection. Private pages are for authenticated WordPress users with the required role, while password-protected pages show a form that anyone with the shared password can use.
As an Amazon Associate I earn from qualifying purchases.
What a private WordPress page actually does
WordPress pages are public by default. The page-visibility setting gives you three choices:
| Visibility | What a visitor sees | Who authenticates | Typical use |
|---|---|---|---|
| Public | The page can be viewed normally. | No login required. | Ordinary website content. |
| Private | A logged-out visitor cannot view the page, even when the visitor knows its URL. It is also omitted from ordinary public article lists. | A WordPress account with permission to view private content. | Internal notes, drafts for a privileged team, or information for editors and administrators. |
| Password Protected | The page remains published but displays a password form. | Possession of one shared password. | Sharing one page with people who do not have WordPress accounts. |
WordPress.org describes the private option as “Only visible to site admins and editors.” In the default permission model, Editors and Administrators can see private content after logging in. A private page is still published inside WordPress; its public visibility is restricted rather than its existence in the dashboard.
#1 Best Overall
Editors and administrators can find private pages in the Pages list, edit them, and make them public. On a site with several privileged users, treat a private page as restricted internal content, not as a confidential vault.
Before changing visibility
- Confirm the scope. The instructions below protect one page. Core WordPress does not provide a built-in switch that makes an entire site private or creates arbitrary user-by-user rules.
- Check your role. An Administrator, an Editor, or the page’s Author can change a page’s visibility or password in the documented workflow. A user with a more limited role may not see the control.
- Identify the editor. The Block Editor and Classic Editor put the control in different panels. Use the procedure that matches the screen you see after opening the page.
- Decide who needs access. Private uses WordPress accounts and role permissions. If your readers are external people who should not receive dashboard accounts, password protection may fit better.
Make a page private in the Block Editor
Use these steps for the modern WordPress editing screen with blocks and a right-hand settings sidebar.
- Sign in to the WordPress dashboard with an account allowed to edit the page.
- Open Pages and select the page you want to restrict. For a new page, choose Add New Page and create the content first.
- In the editor, open the right sidebar if it is collapsed. Select the Page settings tab if the sidebar is showing block-level settings.
- Find Status & Visibility. Depending on the WordPress version or screen layout, the control may simply be labelled Visibility.
- Click Edit beside the current visibility, which is normally Public.
- Select Private. Read the confirmation prompt if one appears and confirm that you want to make the page private.
- Save the change. Click Publish for a page that has not been published before, or Update for an existing page.
The selection is only a pending editor change until you save it. Leaving the editor, closing the browser, or navigating away before clicking the appropriate save button leaves the previous visibility in place.
What to expect after saving
The page remains in your WordPress Pages list and remains available to users who have the necessary role. A logged-out visitor should not be able to read it by following a menu item, a search result, or a guessed direct URL. If you are still logged in as an administrator or editor, you may be able to open it yourself; that does not mean the page is public.
Make a page private in the Classic Editor
The Classic Editor uses the older editing layout and its Publish box.
- Log in to the WordPress dashboard and open Pages.
- Click the page title to edit it, or create a new page.
- Locate the Publish box, normally on the right side of the editing screen.
- Find the Visibility line, which usually says Public, and click Edit.
- Choose Private and confirm the prompt.
- Click Publish for a new page or Update for an existing page.
Do not confuse the page’s status with its visibility. A page can be published in WordPress while still being private to the public; the visibility choice is what controls whether ordinary visitors can read it.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsHow to verify that the page is private
Verification is useful because administrators and editors have access that logged-out visitors do not.
- Copy the page URL after saving.
- Open a separate browser window, a private-browsing window, or a browser in which you are not signed in to the site.
- Paste the URL and load it.
- Confirm that the content is not displayed to the logged-out session. Then sign in with an account that should have access and verify that the page is available there.
When testing, use the same site address and URL that visitors will use. A successful view while you are signed in as an Administrator or Editor only proves that your account has the required permission.
Private versus password-protected: which should you choose?
Both settings keep an ordinary visitor from immediately reading the page, but they solve different access problems.
Rank #4
| Decision point | Private | Password Protected |
|---|---|---|
| Authentication | A person signs in to a WordPress account with the required role. | A person enters one shared page password. |
| Logged-out view | The page content is hidden; knowing the URL is not enough. | The page is published and presents a password prompt. |
| Administrative control | Access follows WordPress roles and account permissions. Editors and Administrators can manage the page. | Access follows possession of the shared password. Anyone who learns it can use it. |
| Best fit | Internal content for an authenticated WordPress team. | A single page shared with people who should not receive WordPress accounts. |
| Password limit | No page password is used. | The documented WordPress workflow limits the password field to 20 characters. |
Password protection is not individual user authentication. WordPress stores the password in a browser cookie after a successful entry, so that browser does not have to ask for it on every visit. That convenience does not identify each person or prevent the password from being shared.
Examples
- Use Private for a page containing instructions that only your site’s Editors and Administrators should read.
- Use Password Protected when a client or event attendee needs to open one page but should not be given a WordPress dashboard account.
- If different people need different permissions, neither a single shared password nor the default private setting provides a complete per-person policy. You need a more specialized access-control arrangement.
Who can change the setting and who can see the page?
The documented workflow permits an Administrator, Editor, or the page’s Author to change its password or visibility. Viewing private content follows the site’s role capabilities; WordPress’s standard documentation identifies Editors and Administrators as the roles that can see private pages and posts.
These are two separate questions: a user may be able to edit a page without being able to view every private page on the site, and a person who can view a private page may also be able to change its visibility if their role grants editing rights. Check the role assigned to the account rather than assuming that every logged-in user has access.
Best Value
Troubleshooting when the page is still public
The visibility control is missing
- Make sure you are editing a page, not viewing the public page or editing an individual block.
- In the Block Editor, open the right sidebar and select the page-level settings. Look for Status & Visibility or Visibility.
- In the Classic Editor, look in the Publish box and expand the Visibility row.
- Ask an Administrator to check your role. Only an Administrator, Editor, or the page’s Author can change the setting in the documented workflow.
The option was selected but visitors can still read the page
- Return to the editor and check whether the current value actually says Private.
- Click Update for an existing page or Publish for a new one. Selecting a value without saving does not change the live page.
- Test the URL from a logged-out browser. A signed-in Editor or Administrator can still see a private page, so test accounts matter.
The page disappeared from a public menu or list
That is expected for private content. It is not intended to appear in ordinary public article lists. Keep the page private and give authorized WordPress users the dashboard route, or change the visibility back to Public if ordinary visitors are supposed to find it.
A colleague cannot open the private URL
Ask the colleague to sign in with the WordPress account that should have access, then retry the URL. If access still fails, an Administrator should verify the account’s role and whether the page is actually private rather than simply unpublished or still awaiting a save.
Recommended Free Tools
When one private page is not enough
Core WordPress handles visibility page by page or post by post. Official WordPress guidance says that hiding the entire blog or restricting it to selected users is not part of core and generally requires a plugin or server configuration.
Choose a whole-site or membership solution when the requirement is broader than one page, such as:
- making every page unavailable to logged-out visitors;
- creating member-only sections with different access levels;
- allowing selected individual users rather than every Editor or Administrator;
- restricting content by subscription, group, or other business rule.
Before installing an extension or changing server rules, verify that it supports your current WordPress and PHP setup, that its access model matches your roles, and that its support and pricing are acceptable. A site-wide control can also hide login, registration, media, feeds, or other endpoints differently from a single page, so read its documentation and test with both authorized and unauthorized accounts.
Quick Recap
A practical decision checklist
- One page, WordPress team only: choose Private.
- One page, outside recipients with no accounts: choose Password Protected, understanding that the password is shared.
- Several pages or the entire site: use an appropriate access-control plugin or server-level configuration; core page visibility is not a whole-site policy.
- Different access for named individuals: plan for account-based access control rather than distributing one page password.
- After every change: save with Publish or Update, then test from a logged-out browser and an authorized account.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
