Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Back up the site first, then choose the least destructive method that matches your goal. On WordPress.com, Dashboard → Settings → Reading → Site Visibility → Private hides the site from ordinary visitors while allowing you and approved logged-in users to work. Use Coming Soon mode for a public holding page, page-level Private or Password protected visibility for selected content, and Discourage search engines from indexing this site only when people may continue to visit the public site.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Unpublishing is not the same as deleting. Private and password-protected settings control access, a search-engine setting requests reduced indexing, and deletion removes the installation or its content. Keep a verified backup before changing any of these states.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Choose what “unpublish” should accomplish
There is no single WordPress unpublish switch. Decide whether you need to stop public access temporarily, conceal one page, keep the site reachable while reducing new indexing, rebuild it safely, or retire it permanently. The right choice determines what visitors see, what search engines can still fetch, and how easily you can reverse the change.
| Goal | WordPress action | Who can access the content | Search implication | Reversible? |
|---|---|---|---|---|
| Pause the entire site for approved users | Set Site Visibility to Private on WordPress.com | You and logged-in users you approve | Ordinary visitors and normal search discovery are blocked | Yes |
| Show a temporary public notice | Enable Coming Soon mode where available | Visitors see the holding page; authorized users continue working | Depends on the mode and its configuration | Yes |
| Hide one or several pages | Set each page to Private or Password protected | Private: Editors and Administrators; Password protected: people with the password | Private pages do not appear in feeds or search | Yes |
| Keep the site public but ask crawlers not to index it | Leave visibility Public and enable Discourage search engines from indexing this site | Anyone who has the address can visit | A request, not a guarantee; some search engines may ignore it | Yes |
| Redesign without risking the live site | Work on a protected staging copy and sync after review | Production remains live while the staging team works | Staging should be protected from indexing | Yes, if a pre-sync backup is retained |
| Retire the site permanently | Archive, empty, delete, or remove the installation through the host, as appropriate | The site becomes unavailable or its content is removed | Old URLs need a removal, redirect, 404, or 410 plan | Usually difficult or destructive |
If you are unsure, start with a reversible state. A private site or staging copy preserves your work while you decide whether anything should ultimately be deleted.
#1 Best Overall
Back up and verify everything before unpublishing
WordPress maintenance guidance updated June 9, 2024 recommends keeping backups on both the website host and your computer. Do this before changing visibility, syncing a staging site, emptying a multisite site, or deleting an installation.
What the backup must contain
- Database: posts, pages, comments, users, settings, menus, and plugin data.
- Uploads: images, video, audio, documents, thumbnails, and other files in the media library.
- Themes and plugins: active code plus any custom theme files or extensions that are not available from their original source.
- Configuration: hosting settings, environment values, rewrite rules, and any custom code needed to reconnect the site.
- Domain and email information: record where DNS and site email are managed before changing hosting or deleting an account.
Keep two independent copies
Store one copy on the host and another on a computer that is not dependent on the same hosting account. A USB flash drive for WordPress backups can serve as the computer-side copy, provided it has enough capacity, is encrypted when the data is sensitive, and is safely ejected and stored. A second computer, offline disk, or other independent location gives you another recovery path if the host account is closed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Verify the backup instead of assuming it works
- Check that the archive contains a database export and the complete uploads directory, not just a list of filenames.
- Confirm that the archive opens and that its file size is plausible for the site.
- Restore a copy to a staging environment when the site is important enough to justify a test restore.
- Write down the backup date, location, and the credentials or keys needed to restore it.
Do not proceed to deletion until you can identify a specific, readable backup and the person responsible for restoring it.
Make an entire WordPress.com site private
On WordPress.com, the documented path is Dashboard → Settings → Reading → Site Visibility → Private. WordPress.com describes this setting as making the site visible only to you and logged-in users you approve.
- Sign in to the WordPress.com account that owns the site.
- Open the site dashboard.
- Choose Settings, then Reading.
- Find Site Visibility and select Private.
- Save or confirm the change if the dashboard presents a confirmation button.
- Open the site in a private browser window or another browser session to confirm that an unapproved visitor cannot view the public pages.
Private mode is appropriate for maintenance, a paused personal site, client review, or a project that is not ready for public launch. It does not erase posts, media, themes, or settings. Return to the same Site Visibility control and choose the public option when the site is ready to reopen.
When Coming Soon is better
Use Coming Soon mode when visitors should receive a clear temporary message instead of a private-access notice. It is suited to a launch, short maintenance window, or redesign where you want a public-facing holding page while authorized users work behind it. Check the mode’s preview and make sure the message states what visitors need to know; availability and controls can vary by WordPress.com setup.
Coming Soon is not a substitute for a backup or a staging site. It changes what visitors see, but it does not create a safe workspace for major database or plugin changes.
Hide only selected pages or posts
If the rest of the site should remain available, change visibility on the individual page rather than taking the whole site offline.
- Open the page or post in the WordPress editor.
- Locate the Visibility setting in the publishing or document panel.
- Choose Private or Password protected.
- Save or update the content.
- Test the URL while logged out and then test it with the intended editor account or password.
A Private page is limited to Editors and Administrators and does not appear in feeds or search. Password protected content remains addressable, but the visitor must submit the password before the content is displayed. Use a unique password and share it only with the people who need access; page passwords are not a replacement for a user account with an auditable permission.
To republish the page, return to Visibility and select the public option. Check menus, internal links, XML feeds, and related-content blocks after republishing so the page is discoverable where you expect it to be.
Ask search engines not to index a site that remains public
When people must still reach the site, leave it Public and enable Discourage search engines from indexing this site under Settings → Reading. This is a crawler and indexing request, not an access control. Anyone with a link can still read a public page, and a search engine may ignore the request. WordPress.com explicitly warns that not all search engines may respect the setting. A 2019 WordPress 5.3 developer note also documents a change in how the discourage-indexing behavior is handled.
Use this option only for the right job
- Use it for a private-in-practice development site that must remain reachable by a small team, while understanding that the URL is not secret.
- Use it as an additional precaution on a staging site, together with access protection.
- Do not use it to protect client records, unpublished game builds, credentials, or other sensitive material.
- Do not assume it removes pages already copied into search indexes, caches, feeds, or third-party archives.
If a page must be inaccessible to the public, choose Private, Password protected, authentication at the host, or a site-wide private mode instead of relying on a no-index request.
Rebuild on staging instead of taking production apart
A staging copy lets you update themes, plugins, templates, and content while the production site continues serving visitors. It is the safest option for a redesign, a major game-news archive migration, or maintenance that could change the database.
- Create the staging copy. Clone the production files and database into a separate environment controlled by the same team.
- Protect staging access. Require login or another access control, and enable the site’s discourage-indexing setting as an additional signal. Do not treat the setting as the only barrier.
- Record the starting point. Take and label a complete production backup immediately before work begins.
- Test changes on staging. Check front-end pages, editor access, media, forms, search, menus, redirects, scheduled jobs, and integrations.
- Review the database direction. Decide which staging changes should move to production and which new production orders, comments, or user records must be preserved.
- Take a pre-sync backup. WordPress.com documentation describes restoring production from a backup taken before a sync if data is lost.
- Sync only after approval. Confirm the target site, the files and tables included, and the rollback backup before starting the operation.
- Test production immediately. Check representative URLs, login, media, forms, and the site’s visibility setting after the sync.
Staging is reversible because production remains available and the pre-sync backup provides a defined rollback point. A direct edit of the live database does not provide that safety.
Unpublish or retire a WordPress multisite installation
Multisite has site-level actions that are different from ordinary page visibility. WP-CLI exposes commands for making a site private, archiving it, deactivating it, emptying it, and deleting it:
Rank #4
| Command | Effect | Risk |
|---|---|---|
wp site private |
Changes a multisite site to private | Reversible visibility change |
wp site archive |
Archives the site within the network | Visitors lose normal access until it is unarchived |
wp site deactivate |
Deactivates the site | Operationally disruptive but generally reversible by an administrator |
wp site empty |
Removes the site’s content while leaving the site record | Destructive; verify the backup and target first |
wp site delete |
Deletes the multisite site | Destructive; the documented example requires confirmation |
Run a command only when you understand whether it targets the site record, its content, or both. Confirm the network, site ID or domain, and backup before approving an empty or delete operation. If the goal is a temporary pause, use a private, archived, or deactivated state instead of an irreversible command.
Permanently retire a standalone site
Permanent retirement is a sequence, not merely a visibility toggle:
- Export and verify the database, uploads, themes, plugins, and configuration.
- Decide whether the domain should redirect to a genuinely relevant replacement, remain registered but inactive, or expire under your registrar’s process.
- Remove or empty the WordPress installation through the host only after the archive is safe.
- Disable scheduled jobs, forms, transactional email, and integrations that should no longer run.
- Record the final URLs and the response each retired URL should return.
- Use the search-removal and URL-response workflow described below.
Deleting files does not automatically remove copies held by search engines, browsers, feeds, or third-party archives. It also destroys the easiest path to a later restoration, so treat host deletion as the final step, not the first.
Remove old pages from Google results
Changing access and cleaning search results are separate jobs. Google Search Console’s Removals tool can hide a URL from results within about a day, but the temporary block lasts about six months. It is useful for urgent suppression while you make the underlying change permanent; it does not erase the content from the web or guarantee that every search engine and cache will stop showing it.
Temporary suppression
- Open the property that contains the URL in Search Console.
- Use the Removals tool and create a new temporary removal request for the exact URL or appropriate URL prefix.
- Confirm the request and monitor its status.
- During the temporary window, change the source page so that the desired permanent response is in place.
Permanent outcomes
- Relevant replacement exists: redirect the old URL to the closely matching new page. Do not redirect unrelated retired pages to the homepage simply to avoid a 404.
- No replacement exists: return HTTP 404 or 410 for the old URL so crawlers can understand that the resource is gone.
- Content should remain available to selected users: require appropriate access control and keep the URL out of public navigation, while recognizing that access controls and indexing signals solve different problems.
After the permanent change is live, allow the temporary removal request to expire naturally or remove it according to Google’s workflow. The source response and access policy, not the temporary request, are what determine the long-term result.
Best Value
Common situations and the least destructive fix
“I need to work privately for a few days.”
Use WordPress.com Private mode or a protected staging site. A public site with discourage indexing is insufficient because visitors can still load the pages.
“Only a draft landing page must disappear.”
Set that page to Private or Password protected. Leave the rest of the site public so its navigation and search presence are not unnecessarily disrupted.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
“The site must stay online, but I do not want new search listings.”
Keep it Public and enable the discourage-indexing setting, then protect any sensitive pages separately. Treat the setting as a request that can be ignored.
“A redesign might overwrite orders, comments, or new posts.”
Use staging, document the database direction, and take a production backup immediately before syncing. Keep that backup until the live site has passed its post-sync checks.
“The site is gone, but Google still shows it.”
Use Search Console’s temporary removal tool for urgent suppression, then make the source URL return 404 or 410, or redirect it to a genuinely relevant replacement. Search-result cleanup can take longer than changing the site itself.
“I clicked delete but now need the site back.”
Stop making further changes and locate the verified database and file backups. Restoration depends on the host or network’s backup facilities and on whether the domain, database, media, and configuration were all preserved. This is why private mode, archive, or staging should be used for a temporary pause.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsQuick Recap
Final pre-unpublish checklist
- Have you stated the goal: pause, selected-page restriction, reduced indexing, staging, migration, or retirement?
- Is there a readable database and file backup on the host and another copy on a computer or independent device?
- Have you tested or at least inspected the backup contents?
- Did you choose Private, Coming Soon, Password protected, discourage indexing, staging, or deletion based on the required access level?
- If using staging, did you take a production backup immediately before sync and define what data must be preserved?
- If deleting or emptying a site, did you verify the exact network, domain, site ID, and command?
- For old URLs, is each one mapped to a relevant replacement or configured to return 404 or 410?
- Have you treated Google’s temporary removal window of about six months as a stopgap rather than permanent erasure?
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.
