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 errorsUse the post’s Visibility setting. Choose Private to remove a post from public feeds and search and limit it to Editors and Administrators; choose Password Protected to leave the post live while locking its content; or choose Draft to unpublish unfinished work. Password-protected posts can still appear on the homepage and archive pages, so hiding those listings requires a query customization or a compatible plugin.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Choose the right hiding method first
“Hide” can mean several different things in WordPress. You might want to keep a post available to your editorial team, let a small audience read it with a shared password, remove an unfinished post from the public site, or keep a protected post live while removing its title from indexes and archive loops. These are different controls, and selecting the wrong one can leave a title visible or make the content inaccessible to the people who need it.
As an Amazon Associate I earn from qualifying purchases.
| Method | What visitors see | Listing and search behavior | Direct URL | Best fit |
|---|---|---|---|---|
| Private | Only logged-in Editors and Administrators can view the post. | Removed from feeds and search. | Unavailable to other visitors. | Internal notes, editorial drafts that must remain in WordPress, and staff-only material. |
| Password Protected | The title remains reachable; the post content requires the password. | May still appear on the homepage and archive listings by default. | Anyone with the password can open it. | Limited-audience announcements, previews, and shared reading rooms. |
| Draft | The post is unpublished and visible only to logged-in users with editing permission. | Does not appear as a public published post. | Not publicly viewable as a published post. | Unfinished or superseded work that should not be live. |
| Listing exclusion | The post remains live under its existing visibility setting. | A query customization or plugin can remove it from selected loops such as the homepage and archives. | A password-protected post can still open at its direct URL. | Keeping a protected post available while removing its discoverability in lists. |
Make a WordPress post private
Private status is the clearest way to keep a post inside the WordPress editorial area. It does not merely hide the body from a visitor; it restricts the post to users with the appropriate WordPress role.
Block Editor steps
- In the WordPress dashboard, open Posts and select the post you want to hide.
- In the editor’s settings sidebar, open the Status or Visibility control. It normally shows Public.
- Select Private and confirm the change when WordPress asks whether to make the post private.
- Click Publish for a new post or Update for an existing one. The setting is not applied until you save that change.
Classic Editor steps
- Open the post and find the Publish box.
- Next to Visibility, click Edit, select Private, and confirm.
- Click Publish or Update.
Editors and Administrators can see private posts in WordPress. Other logged-in roles and anonymous visitors cannot. A private post is removed from public feeds and search, making this status suitable for internal production notes or a review that should not be discoverable.
#1 Best Overall
Password-protect a post without unpublishing it
Password protection keeps the post published but places a password gate in front of the content. The post title can remain reachable, and anyone who knows the password can read the protected material.
Set the password
- Open Posts in the dashboard and edit the post.
- Open the Status or Visibility panel and change Public to Password Protected.
- Enter a password in the field WordPress displays. Use a separate password from your administrator login and share it only with the intended readers.
- Click Publish or Update to save the setting.
Visitors who reach the post are asked for the password before the protected content is shown. This is useful when the post should remain a functioning URL for a group of readers but should not be open to everyone. It is not an identity check: every person who receives the password has the same access.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What password protection does not hide
WordPress can still expose the post’s title in homepage and archive listings by default. A reader may therefore learn that the post exists even without seeing its body. If the existence of the post is itself confidential, password protection alone is the wrong setting; use Private, an unpublished draft, or an access system that also restricts the surrounding listings.
Save the post as a draft
A draft is the appropriate choice when the post should not be live at all. Draft status is not an access layer for a finished article: it simply leaves the post unpublished. Only logged-in users who have editing permission can work with it in the dashboard.
- Open the post in the editor.
- Click Save draft in the editor, or change the status in the Publish panel to Draft and save.
- When the article is ready, select Publish and review its visibility before making it public.
Use a draft for an unfinished game review, an embargoed announcement that has no approved audience yet, or a post that has been replaced and should no longer be published. Use Private instead when colleagues need a stable, non-public post to review or reference.
Hide a password-protected post from the homepage and archives
Changing a post to Password Protected does not automatically remove it from every WordPress loop. The default home and archive queries may continue to output its title and excerpt. To remove those entries, you need to alter the query or install a plugin that explicitly supports the post type and listing locations you use.
Use a query customization
A common approach is to alter the main front-end query with the pre_get_posts hook so it requests posts with an empty password. The following pattern targets the main homepage and archive queries:
add_action( 'pre_get_posts', function ( $query ) {
if ( is_admin() || ! $query->is_main_query() ) {
return;
}
if ( $query->is_home() || $query->is_archive() ) {
$query->set( 'post_password', '' );
}
} );Place custom code in a site-specific plugin or a child theme rather than editing a parent theme. This pattern is general WordPress code and should be tested against the active theme, custom post types, pagination, and any page-builder queries before use. A theme can build a secondary query that bypasses the main loop; those queries may require their own handling, sometimes through a posts_where filter. Test while logged out and in a private browser window so an editor session does not make a hidden post appear to be public.
Check every place your theme lists posts
- Homepage main loop and any featured-post block.
- Category, tag, date, author, and search archives.
- Related-post widgets and “latest posts” sidebars.
- Custom landing pages that use their own query.
- Feeds or APIs that your theme or another service consumes.
Removing a post from one loop does not guarantee that another loop is filtered. Decide which surfaces must be clean and test each one after deploying the change.
Use a plugin when you need listing controls without custom code
Plugins can provide a user interface for hiding protected content from listings, but they differ in scope. Confirm that a plugin supports posts, not only pages, and check its current WordPress compatibility before enabling it on a production site.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →WP Hidden Password Protected Pages
This plugin is described as hiding password-protected pages from listings while leaving the direct URL usable. Because its name and documented purpose focus on pages, verify post support before relying on it for a blog post. If it does not alter post queries on your site, it will not solve a post appearing on the homepage.
Private Password Posts
This plugin is intended to hide private and password-protected posts on the front end. A listing for it reported testing up to WordPress 6.0.11, so treat compatibility as a check you must perform against your current WordPress version, theme, and other plugins rather than as a guarantee. Test archive pages, search, feeds, widgets, and direct URLs after activation.
Password Protected
Another plugin named Password Protected extends protection to areas such as categories and partial content. That broader scope can help when hiding a whole section rather than a single post. Review its settings carefully so you do not lock more of the site than intended, and verify that the version you install supports your current WordPress release.
Plugin selection checklist
- Does it support posts, pages, or both?
- Does it remove titles from the homepage, archives, search, feeds, and widgets, or only from one location?
- Does a direct URL still open, and is that the behavior you want?
- Does it preserve pagination and category counts correctly?
- Is it compatible with the WordPress version and theme running on your site?
- Can you disable it safely and restore the original listing behavior?
Understand the security limits
WordPress visibility settings are editorial controls, not a complete data-loss-prevention system. Do not place highly sensitive information in a post merely because it is private or password protected.
A hidden URL is not a security boundary
Anyone who has a direct URL can reach a hidden post unless login rules or server-level restrictions also block access. Password protection limits the content to people who know the password, but the password can be forwarded. Listing exclusion reduces discovery; it does not revoke the URL.
Custom fields may remain exposed
Custom-field data attached to a protected post is not automatically protected. A theme, widget, API response, or custom template can print that data separately from the locked post body. Audit templates and integrations if a field contains information that should not be public.
Editors and Administrators have elevated access
Other Editors and Administrators can see protected content in the WordPress editor without entering the visitor password. Password protection is therefore suitable for controlling readers, not for separating content from trusted site staff.
Save the change before testing it
Visibility changes take effect only after you click Publish or Update. If you change the setting and navigate away, the old status remains active.
Troubleshoot a post that is still visible
The title still appears on the homepage
Check whether the post is Password Protected rather than Private or Draft. Password-protected posts may remain in default listings. If the status is correct, inspect whether the homepage uses a secondary custom query; update that query or use a plugin that filters the relevant loop.
The post appears in an archive or search result
Review each archive type separately. A filter that handles the homepage may not handle category, tag, author, date, or search queries. Clear any page cache after changing code or plugin settings, then test while logged out.
Best Value
The post opens without a password
Confirm that the post’s visibility is actually Password Protected and that the change was saved. Check whether a custom template is displaying the content outside the normal post output. Also review whether you are viewing an editor screen; Editors and Administrators can access protected content in the dashboard without the visitor password.
A custom field is visible even though the body is locked
Inspect the theme template, shortcode, widget, REST integration, or page-builder element that outputs the field. Protect or remove that separate output; changing the post visibility alone does not cover custom-field data.
You cannot convert many password-protected posts at once
WordPress core does not provide a bulk switch from Password Protected to Public. Change posts individually, or use a purpose-built workflow only after confirming that it handles the exact status transition safely. Back up the database and test on a staging copy before making a large change.
Practical choices for a video-game site
Internal review of a game article
Set the post to Private when only Editors and Administrators should see an unfinished review, fact-checking note, or publishing checklist. It will not enter public feeds or search.
Early access for selected readers
Use Password Protected when a publisher, tournament organizer, or invited community needs to read a preview while the post remains a live URL. Remove it from homepage and archive loops if revealing the title would spoil the announcement.
Unreleased announcement
Keep the post as a Draft until the release timing, assets, and copy are approved. This avoids exposing a public URL before the announcement is ready.
Free tools Windows power users keep installed
One-click scans. No signup required.
Staff-only reference page
Use Private for a recurring internal reference such as review-code logistics or editorial standards. If the information is confidential beyond the WordPress staff, use stronger account or server controls rather than relying on post visibility.
Quick Recap
Final decision guide
- Choose Private when visibility must be limited to Editors and Administrators.
- Choose Password Protected when the content should remain live for anyone who has a shared password.
- Choose Draft when the post should be unpublished until it is ready.
- Add a tested
pre_get_postscustomization or compatible plugin when a password-protected post must disappear from homepage and archive listings. - Audit direct URLs, custom fields, widgets, feeds, search, and custom queries whenever the content has meaningful confidentiality requirements.
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.
