Recommended Free Tools
To unpublish a WordPress site safely, back it up first, then choose the least destructive option that matches your goal. Set a WordPress.com site to Private when only you and approved users should see it, use Coming Soon when visitors should see a temporary holding page, make individual pages private or password protected when only part of the site must disappear, and use staging for a substantial rebuild. If the site is being retired, archive the content and handle old URLs before deleting anything.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Privacy settings, password protection, search-engine suppression and deletion are different operations. A site can be inaccessible to ordinary visitors while its old pages remain in search results, and a temporary Google removal does not erase the underlying content. The steps below keep those distinctions clear.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsChoose the right kind of “unpublished”
“Unpublish” can mean several different things. Decide what visitors, editors and search engines should be able to do before changing a setting.
| Goal | WordPress action | What visitors experience | Search implication | Reversible? |
|---|---|---|---|---|
| Pause the whole site for approved users | WordPress.com: Dashboard → Settings → Reading → Site Visibility → Private | Only you and logged-in users you approve can view it | Ordinary visitors and search crawlers cannot view the private site | Yes |
| Show a temporary public message | Enable Coming Soon mode where it is available | Visitors see a holding page instead of the working site | Depends on the mode’s configuration | Yes |
| Hide one page | Edit the page and change Visibility to Private | Only Editors and Administrators can view it | Private pages do not appear in feeds or search | Yes |
| Share one page with selected people | Edit the page and choose Password protected | Readers must enter the page password | Access control and indexing are separate; check the page’s search settings | Yes |
| Keep the site human-accessible but ask search engines not to index it | Settings → Reading → Discourage search engines from indexing this site | Anyone who has the URL can still visit | Search engines are asked not to index it; the request is not guaranteed | Yes |
| Redesign without risking the live site | Work on a staging copy and sync after testing | Production remains live while work is tested | Protect staging from indexing | Yes |
| Retire the site permanently | Archive your files, then empty or remove the installation through your host or multisite tools | The site becomes unavailable or its content is removed | Use temporary removal only for urgency; return 404/410 or relevant redirects for permanent handling | Usually difficult or destructive |
For a temporary maintenance window, Private or Coming Soon is normally safer than deletion. For a rebuild, staging is safer than repeatedly taking production offline. Delete only when you have a verified archive and no need to restore the installation.
#1 Best Overall
Back up before changing visibility or deleting anything
Make a complete copy before unpublishing. WordPress maintenance guidance, updated June 9, 2024, recommends keeping backups both on the website host and on your computer: “Make it a part of your regularly scheduled maintenance to backup your site, both on the website host server and on your computer.”
What to preserve
- Database: posts, pages, comments, users, settings and plugin data.
- Uploaded media: images, documents, video and other files in the uploads area.
- Themes and plugins: active and inactive copies, including custom code.
- Configuration: environment variables, rewrite rules, domain and email settings, and any host-specific configuration you need to recreate the site.
- Content exports: an export from WordPress gives you an additional, portable copy of posts and pages.
Keep one copy on the host and another on a computer or other offline storage. A USB flash drive for WordPress backups can be the computer-side destination, but use enough capacity for the complete backup and protect the drive because it may contain personal data and credentials.
Verify the backup instead of assuming it worked
- Check that the backup has a recent timestamp and a plausible file size.
- Confirm that the database dump, media directory and custom theme or plugin files are all present.
- Open a few exported files and images from the computer-side copy.
- If your host provides a restore test or staging restore, use it before making destructive changes.
- Record where the backup is stored and which date it represents. For a rebuild, keep a specifically labelled copy made immediately before the production-to-staging or staging-to-production sync.
Make an entire WordPress.com site private
WordPress.com’s Private setting is the clearest choice when the site should remain intact but ordinary visitors should not see it. WordPress.com states: “The Private setting makes your site visible only to you and logged-in users you approve.” The current path documented by WordPress.com is:
- Sign in to the WordPress.com dashboard.
- Open Settings.
- Select Reading.
- Under Site Visibility, select Private.
- Save the change if the dashboard presents a save button, then test the site in a logged-out browser window.
Use a logged-out or private browser window for the test; an administrator session can make a private site appear available when it is not. Give approved collaborators their own logged-in access rather than sharing your administrator credentials.
Return the site to public visibility
When maintenance is complete, return to Settings → Reading → Site Visibility, select the public option and save. Check the home page, a representative post, contact forms and any membership or checkout flows before announcing that the site is live again.
Use Coming Soon for a temporary public holding page
Coming Soon mode is appropriate when visitors should know that the site exists but should not browse the unfinished version. It presents a temporary holding page while authorized users continue working. Availability and exact controls depend on the WordPress.com plan or the tools provided by a self-hosted installation, so confirm that the mode is enabled for your site before relying on it.
Write a useful message on the holding page: explain that maintenance is in progress, provide a return date only if you can meet it, and include an alternative contact method when visitors may need assistance. Test both the public view and your logged-in editing view. A holding page is not the same as a permanent search removal; old URLs may still be known to search engines until you handle them separately.
Unpublish one page instead of the whole site
If the rest of the website should remain live, change the individual page’s visibility.
Private page
- Open the page in the WordPress editor.
- Find the page’s Visibility setting in the document or publishing panel.
- Select Private.
- Update or publish the change.
- Open the page while logged out to confirm that ordinary visitors cannot view it.
Private pages are limited to Editors and Administrators and do not appear in feeds or search. Check menus and internal links after changing visibility so visitors are not sent to a page they cannot open.
Password-protected page
- Open the page and locate Visibility.
- Select Password protected.
- Set a strong, unique password and update the page.
- Test the page in a logged-out window and share the password only through an appropriate channel.
Password protection controls who can read the page; it is not a substitute for a site-wide private setting or a search-removal process. If the content must not be exposed at all, use Private visibility or remove the content and configure the URL appropriately.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Discourage search engines while keeping the site public
WordPress provides a setting for cases where people should still be able to visit the site but you do not want to encourage indexing:
- Open Settings.
- Select Reading.
- Enable Discourage search engines from indexing this site.
- Save the setting.
This is a crawler and indexing request, not a security boundary. WordPress.com warns: “Please note that not all search engines may respect this setting.” Anyone with the URL can still access a public site, and a search engine may retain a previously indexed result for some time. Do not use this option for confidential information; use access control instead.
The behavior of this setting changed in WordPress 5.3, according to a 2019 Make WordPress Core developer note. If you are managing an older or customized installation, confirm what your version and theme actually output before assuming that the setting has the desired effect.
Rebuild on staging instead of taking production apart
A staging site is a separate copy used to test a redesign, updates or content changes while the production site remains available. It is the safest choice when the work is substantial or may need several rounds of testing.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Create the staging copy. Use the staging facility supplied by your host or workflow, and include the database, media, theme and plugin files.
- Protect staging access. Require authentication or another access restriction, and configure it so search engines are not invited to index the copy.
- Test the rebuild. Check navigation, responsive layouts, forms, logins, media, redirects, email delivery and any integrations that matter to your site.
- Take a pre-sync backup. Preserve production immediately before copying changes back. This is your rollback point.
- Sync only after review. Confirm the destination and the direction of the sync. A mistaken direction can overwrite newer production data.
- Verify production. Test the home page, important URLs, forms and administrative access. Keep the pre-sync backup until you are certain that no data was lost.
WordPress.com documents restoring production from a backup taken before a sync if data is lost. Treat that backup as part of the change plan, not as an optional extra.
Permanently retire or delete a WordPress site
Deletion is different from unpublishing. It can remove files, database records and media in a way that is difficult or impossible to reverse. Preserve and verify the archive before proceeding.
Self-hosted installation
The exact deletion control belongs to your hosting environment. After confirming the backup, remove or empty the WordPress installation through the host’s documented control panel or server procedure. Record the domain, database name and filesystem location first so you do not target the wrong installation, especially when several sites share one account.
WordPress multisite
WP-CLI exposes separate operations for multisite sites, including:
Rank #4
wp site privateto make a site private.wp site archiveto archive it.wp site deactivateto deactivate it.wp site emptyto remove the site’s content.wp site deleteto delete the site.
Use the site ID or URL required by your command and verify it before running anything. The documented wp site delete example requires confirmation, and the operation is destructive. Do not treat the confirmation prompt as a backup; it only confirms that you intend to proceed.
Keep an archive after retirement
Store the verified backup, the final domain and URL list, and a note explaining why the site was retired. If legal, tax, customer-support or editorial records must be retained, keep those records separately from the live WordPress installation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Remove old pages from Google results
Taking a site offline does not automatically erase search results. Search access and site access are separate problems.
Use Search Console’s Removals tool for urgent, temporary suppression
Google’s Search Console Removals tool can hide a URL from results in about a day. The block lasts about six months, so it is a temporary measure while you make the underlying change. It does not permanently delete the page, prevent every crawler from accessing it, or remove copies held elsewhere.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use the tool when a result needs to disappear quickly, then make the result permanently obsolete by changing the page’s availability or URL response. If the content is still reachable, the temporary block can expire and the result can return.
Make removal permanent
For content that should no longer exist, remove or update it and ensure the URL returns an appropriate response. A retired URL with no replacement should return HTTP 404 or 410. A URL that has a genuine replacement should redirect to that relevant replacement. Do not redirect every unrelated retired page to the home page; that gives visitors and search engines a misleading destination.
Best Value
Handle URLs during a domain move or redesign
Before unpublishing, export a list of important URLs and decide what each one should do. This prevents broken links and accidental loss of pages that still have a useful successor.
| Old URL situation | Recommended result | Why |
|---|---|---|
| The same content now has a new URL | Redirect the old URL to the new URL | Visitors and search engines reach the correct successor |
| The content was replaced by a closely related page | Redirect to that relevant replacement | The destination answers the old URL’s intent |
| No replacement exists | Return 404 or 410 | Clearly signals that the resource is gone |
| The page should be hidden temporarily while work continues | Use Private, Password protected or Coming Soon as appropriate | Preserves the content while access is controlled |
Keep redirects pointed at the most relevant destination and test them after the change. A redirect plan is especially important when a rebuild changes page slugs, category paths or a domain.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Troubleshoot common outcomes
Visitors can still see a supposedly private site
- Test while logged out; an administrator session may bypass the public restriction.
- Confirm that you changed Site Visibility, not only the search-engine setting.
- Check whether a cached holding page or a third-party copy is being shown.
- Verify that collaborators are using approved accounts rather than a public link.
The page vanished from navigation but still appears in Google
Removing a menu link does not remove a URL from search. Use the appropriate access or HTTP response, and use Search Console’s temporary removal tool when the result must be hidden quickly.
The site is private, but a collaborator cannot open it
Confirm that the collaborator is logged in to the account approved for the private site. Private visibility is not the same as a shared password; each approved user must meet the site’s login requirement.
A staging copy is appearing in search
Protect the staging site with access control and review its indexing configuration. Do not leave an unrestricted development copy online while expecting a request to discourage indexing to act as a security barrier.
A sync overwrote newer production content
Stop further syncing, identify the last known-good production state and restore from the backup taken immediately before the sync. Compare the restored site with the staging copy before attempting another transfer.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A deleted URL was redirected to the wrong place
Replace the redirect with a genuinely relevant successor, or return 404/410 when no successor exists. Sending unrelated pages to the home page creates a poor visitor experience and does not accurately describe the old resource.
Quick Recap
A safe unpublishing checklist
- Write down the intended outcome: temporary pause, public holding page, page-level restriction, search suppression, rebuild or permanent retirement.
- Create and verify a complete backup, with one copy on the host and another on a computer or offline storage.
- Record important URLs and decide whether each should be restored, redirected or retired.
- Choose the least destructive visibility change that meets the goal.
- Use staging for redesigns and keep a pre-sync rollback copy.
- Test the public view while logged out and test approved-user access separately.
- If retiring the site, remove or update content and configure 301-style relevant redirects or 404/410 responses as appropriate to the URL’s future.
- Use Google’s Removals tool only as a temporary suppression step when a result needs to disappear quickly.
- Delete or empty the installation only after the archive, URL plan and recovery path are confirmed.
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.
