Setup & site building · Guide
How to Hide Your WordPress Site From Public (Step by Step)

Short answer
Use a coming soon or maintenance plugin so visitors see a holding page while you work, or force a login so only users with accounts can see content. For staging sites, server password protection is strongest. The Discourage search engines setting alone does not hide anything.
Key takeaways
- WordPress core has no single hide site switch.
- Discourage search engines does not block visitors.
- Coming soon plugins show visitors a holding page.
- Force-login plugins suit intranets and client portals.
- Server basic auth is best for staging sites.
- Reverse every hiding step when you launch.
How do you hide your WordPress site from the public?
To hide a WordPress site from the public, put it behind a coming soon or maintenance page, require a login with a members-only plugin, or password protect it at the server, then block search engines as well.
There is no single hide site switch in self-hosted WordPress core. You pick a method based on who still needs access and for how long.
Building a new site, testing a redesign and running a private intranet each call for a different approach.
This table compares the main options.
| Method | Who can see the site | Best for | Blocks search engines |
|---|---|---|---|
| Coming soon or maintenance plugin | Logged-in users | New sites, short redesigns | Usually, with noindex |
| Members-only or force-login plugin | Any logged-in user | Intranets, client portals | Yes, if login is forced |
| Server password (basic auth) | Anyone with the password | Staging, dev, client previews | Yes |
| WordPress.com privacy setting | Invited users or logged-in owner | WordPress.com sites | Yes |
| Private pages | Admins and editors | Single pages, not whole sites | Yes, for those pages |
| Search engine visibility setting | Everyone | Not a hiding method | Only requests no indexing |
Does the Search Engine Visibility setting hide your site?
No, the Search Engine Visibility checkbox only asks search engines not to index the site, and anyone with the link can still visit every page.
You will find it under Settings > Reading as Discourage search engines from indexing this site. The Reading Settings documentation notes that it is up to search engines to honour the request.
Use it alongside one of the real hiding methods below, not instead of them. On its own it keeps the site out of most search results, but it does nothing to stop visitors.
Remember to untick it at launch. Forgetting this step is a common reason new sites never appear on Google.
How do you hide your site with a coming soon page?
A coming soon or maintenance plugin shows a single holding page to visitors while logged-in users see the real site, which suits new builds and redesigns.
Follow these general steps:
- Install a plugin such as SeedProd's Coming Soon Page plugin or a similar tool from the plugin directory.
- Choose coming soon mode for a new site, or maintenance mode for a live site under repair.
- Design the holding page with your logo, a short message and a contact or signup option.
- Enable the mode and save.
- Open the site in a private window to confirm visitors see only the holding page.
Coming soon mode tells search engines the site is not ready yet. Maintenance mode usually sends a 503 status so search engines come back later.
Our guide on how to enable maintenance mode in WordPress compares both modes in more depth.
If the holding page does not appear, see our guide on SeedProd coming soon not working.
How do you hide a WooCommerce store before launch?
Recent WooCommerce versions include a site visibility setting with a coming soon mode, so you can hide the store or just the shop pages without an extra plugin.
Look under WooCommerce > Settings for a Site visibility tab. You can usually choose between coming soon and live, and decide whether to hide only the store pages or the entire site.
Store managers and admins can still browse and test checkout while logged in.
To change the design of that holding page, see our guide on how to change the WooCommerce coming soon page.
How do you make the whole site require a login?
A force-login or members-only plugin redirects every logged-out visitor to the WordPress login page, so only people with an account can see any content.
This method suits intranets, internal documentation and client portals that stay private for good.
The typical setup is:
- Install a force-login or members-only plugin from the plugin directory.
- Activate it and review its settings for allowed pages, such as a public homepage.
- Create user accounts for everyone who needs access, with the Subscriber role for read-only access.
- Test in a private window to confirm the redirect works.
Check that the plugin also protects uploaded files if they are sensitive. Many login plugins protect pages but not direct links to images or PDFs in the uploads folder.
Files in the uploads folder are served directly by the web server, so a login plugin that runs inside WordPress never sees those requests. Anyone who has the direct file address can still open it.
For sensitive documents, use a plugin that stores files outside the public uploads folder, or add server rules that block direct access. Server-level password protection covers uploads automatically, because it sits in front of every request.
How do you password protect the site at the server level?
Server-level password protection, often called basic authentication or directory privacy, asks for a username and password before WordPress even loads.
Many control panels, including cPanel, include a Directory Privacy or password-protect folders tool. Select the folder where WordPress is installed, enable protection and create a user.
On Apache servers this uses an htpasswd file and rules in .htaccess. The Apache authentication guide explains how it works.
This is the strongest simple option for staging and development sites, because nothing reaches WordPress without the password. Search engine crawlers cannot get in either.
Be aware that basic auth can break loopback requests, cron jobs and some plugin features. Our guide on how to fix loopback request failed explains the side effects.
How do you hide a WordPress.com site?
On WordPress.com, go to the site's privacy settings and choose Coming Soon or Private, which hides the site from everyone except you and invited users.
Coming Soon shows visitors a placeholder page. Private requires visitors to log in and be invited.
The WordPress.com privacy settings guide explains each option and how to invite viewers.
If your site is private and you did not expect it, our guide on why your WordPress site is private covers the usual reasons.
Can you hide only some pages instead of the whole site?
Yes, set a page's visibility to Private or Password protected in the block editor, which hides that page without affecting the rest of the site.
Open the page and click the Status or Visibility option in the sidebar. Private pages are visible only to admins and editors. Password protected pages ask for a password you choose.
Password protected pages still appear in some lists and menus, so check your navigation.
To reverse it later, see our guide on how to change a page from private to public.
Should you use a staging site instead?
If you only need to test changes privately on a live site, a password-protected staging copy is usually better than hiding the live site from visitors.
Many hosts offer one-click staging. You build and test on the copy, then push changes live when they are ready.
Keep the staging site hidden with basic auth and search engine discouragement. Duplicate content from an indexed staging site can confuse search results.
Staging also avoids a common mistake: hiding a live site that already gets traffic and rankings. Even a few days behind a coming soon page can cost you visitors, orders and leads.
If you must take a live site offline, keep the window short and use maintenance mode rather than coming soon mode, so search engines know the downtime is temporary.
Our guide on how to set up a staging site walks through the process.
What should you do when you are ready to go public?
When you launch, turn off the coming soon or login plugin, remove server passwords, untick Discourage search engines and check the site in a private window.
Go through this list:
- Disable coming soon, maintenance or force-login mode.
- Remove basic auth from the hosting panel.
- Untick Discourage search engines under Settings > Reading.
- Clear every cache layer.
- Submit your sitemap in Google Search Console.
Google's guide to blocking indexing with noindex explains why leftover noindex tags can keep a launched site out of results.
Frequently asked questions
How do I make my WordPress site private without a plugin?
Use your host's directory privacy or password protection tool to add basic authentication to the site folder. You can also set individual pages to Private. Recent WooCommerce versions also include a built-in coming soon mode for stores.
Can people still find my site if I discourage search engines?
Yes. The setting only asks search engines not to index the site. Anyone with the address can still visit, and links from elsewhere can still lead people there. Combine it with a coming soon page or password protection.
Will hiding my site hurt SEO later?
Not if you hide it before launch and reverse every step afterwards. Problems come from forgetting to remove noindex settings or passwords. Use maintenance mode with a 503 status for short downtime on a site that is already ranking.
Can logged-in admins still see the real site in coming soon mode?
Yes. Coming soon and maintenance plugins usually show the real site to logged-in users with the right role, so you can keep building and testing while visitors see only the holding page.
What is the most secure way to hide a WordPress site?
Server-level password protection is the strongest simple method, because nothing loads until the visitor enters the password. For long-term private sites with many users, a force-login plugin with proper user accounts is easier to manage.
Sources
- Settings Reading Screen WordPress.org Documentation
- Privacy Settings WordPress.com Support
- Authentication and Authorization Apache HTTP Server Documentation
- Block Search indexing with noindex Google Search Central
- Coming Soon Page, Maintenance Mode by SeedProd WordPress.org
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


