New: ShopBar Theme — faster, lighter, refreshed

See what's new
WordPress

Can I Hide My WordPress Site While Editing? Yes, Here’s How

Editor Team

Spiracle Themes

11 min read

Yes — you can hide a WordPress site while you edit it, and you can do it in about two minutes with a maintenance-mode plugin. What matters far more than the plugin is the HTTP status code it sends, because that is the difference between protecting your rankings during a redesign and quietly telling Google your site is a “coming soon” placeholder.

A hidden site should return 503 Service Unavailable with a Retry-After header. A 503 tells Google the page exists but is temporarily unavailable, so indexed URLs stay in the index. A “coming soon” page that returns 200 tells Google this is your real content — and for a redesigned homepage, that is the version it may keep.

Key takeaways

  • Use a 503, not a 200. Google’s own documentation says 5xx responses make crawlers slow down and preserve indexed URLs, but that persistently failing URLs are eventually dropped from the index.
  • WordPress core’s built-in maintenance mode is for upgrades only — the .maintenance file stops working after 10 minutes.
  • If you only need to keep yourself working while the public sees nothing, password protection or an IP allowlist is lighter than maintenance mode and keeps the site technically live.
  • Do not hide the site for weeks. A few days of 503 is recoverable; a month of it is how pages fall out of the index.

The four situations people mean by “hide my site”

What you are doing Right approach Status code
Editing one page or post Nothing — save as draft and preview —
Redesigning the whole site live Coming-soon / maintenance plugin 503 (or 200 on a single coming-soon URL)
Client review before launch Password protection or a staging site 200 behind auth
Migrating hosts or moving domains Maintenance mode plus DNS change 503 with Retry-After

Most people searching for this are in the first row and do not need to hide anything: WordPress already lets you edit a published page without changing what visitors see until you press Update. If you are unsure which of your pages are live, publishing and unpublishing draft pages covers the mechanics.

Why the status code decides whether hiding hurts you

Google’s crawling documentation is explicit about server errors. For 5xx responses it states that crawlers temporarily slow down, that already-indexed URLs are preserved in the index but eventually dropped, and that any content received from a URL returning a 5xx is ignored. It adds that URLs which persistently return a server error are removed from the index.

Read that as a countdown, not a guarantee. A 503 for a two-day redesign is fine — Google keeps the URL, slows the crawl, comes back later. A 503 held for three weeks is indistinguishable from a broken site, and the pages start dropping.

The opposite mistake is more common and more damaging. A “coming soon” plugin set to return 200 presents a single page with a logo and a newsletter form as your site’s content. If it stays up while the site is rebuilt inside, Google may index the placeholder; if it is applied site-wide, every existing URL now returns the same thin page, which looks like you deleted your content and replaced it with a holding page.

The practical rule: 503 for maintenance, auth for review, and never a 200 placeholder on URLs you want to keep.

Option 1: core WordPress maintenance mode (and why it is the wrong tool)

WordPress has a built-in maintenance mode, and it is not a “hide my site” feature. Core checks for a file called .maintenance in the WordPress root. If that file exists and was created less than ten minutes ago, WordPress serves a message — “Briefly unavailable for scheduled maintenance. Check back in a minute.” — with a 503 status and a Retry-After: 600 header. The file is written automatically during core, plugin and theme updates, then deleted.

The ten-minute window is the point: it exists to cover an in-progress update, not a day of editing. Create the file manually and your site un-hides itself after ten minutes. Recent WordPress versions also made this path more correct — as of the 7.2 changelog entry in core, the 503, no-cache and Retry-After headers are sent before a custom maintenance.php drop-in loads, so a drop-in no longer has to set them itself. On older versions, a custom drop-in that forgot those headers would return a 200.

If you want the no-plugin route anyway, add wp-content/maintenance.php with your holding page markup and create an empty .maintenance file. You will still need a cron job or a manual refresh to recreate .maintenance before it expires — at which point a plugin is the simpler answer.

Option 2: a maintenance or coming-soon plugin

These do the job properly: they serve a template, usually with a countdown or email capture, and most let you keep the site visible to logged-in administrators. Install figures below were pulled from WordPress.org in October 2026.

Plugin Active installs Rating Last updated Best for
Coming Soon Page, Under Construction & Maintenance Mode (SeedProd) 600,000 98% (4,699) 29 Sep 2026 Best-rated; drag-and-drop page builder for the holding page. Free tier; paid from $79/year (Basic), $199 (Plus), $399 (Pro) at list price
WP Maintenance Mode (Colorlib) 400,000 86% (874) 29 Oct 2026 Free, simple, countdown and subscriber capture
Maintenance 1,000,000 88% (869) 16 Aug 2026 Largest install base; free tier plus paid extensions
Password Protected 300,000 88% (142) 26 Oct 2026 Different job: keeps the site live but behind a password
Coming Soon Page 8,000 84% (83) 2 Feb 2026 Only tested to WordPress 6.9 — skip on a 7.x site

Generic setup, whichever you pick

  1. Install and activate. Most plugins activate in a “disabled” state so you are not locked out — check the toggle.
  2. Set the mode: maintenance (503 to everyone) or coming soon (a single page, usually reachable at the normal URL).
  3. Exclude administrators, or better, allowlist your own IP so you see the real site while the public sees the holding page.
  4. Write the page. A logo, one line of explanation and an email field outperforms a generic “we’ll be back soon” screen.
  5. Verify with curl -I https://yoursite.com that the status is 503 and that Retry-After is present. Do not trust the plugin’s own preview.

That last step is the one people skip. Several maintenance plugins return 200 by default because the holding page is a real WordPress page — which is exactly the case where Google may index the placeholder.

If you use Elementor

Elementor has its own Maintenance Mode under Tools ? Maintenance Mode, where you can pick an existing page as the holding page and choose the mode. It is convenient if Elementor already runs the site, but it applies at the Elementor level, so confirm the response code the same way. Block-theme users have a similar built-in option through a “Coming Soon” template in the Site Editor, which is cleaner because it does not need a plugin at all.

Option 3: password protection or an IP allowlist

If the goal is “let me work without the world watching”, this is the better fit and it is the option most guides skip. The site stays fully live and indexable — only the people without the password see a prompt. For a client review, or for editing on a live site where you cannot afford any downtime, it is strictly better than maintenance mode.

Options, in order of weight:

  • Password Protected (300,000 installs, 88%, updated 26 October 2026) — a single password for the whole site, with an option to exempt logged-in users.
  • Hosting-level basic auth — most managed hosts offer a one-click “password protect this site” or staging environment. This sits in front of WordPress entirely, so it also blocks bots hitting wp-login.php.
  • IP allowlist — the most surgical option if you have a static IP. Everyone else gets a 403; you get the site. Worth it during a launch week.

The trade-off: a password wall is not “under construction” messaging, and it does nothing for SEO because Google hits the wall too. That is fine for a day, and not fine for a month — if the site needs to be hidden from the public for that long, take it down properly and put a 503 holding page up instead.

Keeping your own access while the site is hidden

Three ways, in order of reliability:

  1. IP allowlist in the plugin — you see the real site, everyone else sees maintenance. Best for testing the redesign as a visitor would not, but it is the least fragile.
  2. Administrator bypass — most plugins let logged-in admins through. Convenient, but it breaks the moment a caching layer serves the maintenance page to everyone, including you.
  3. A staging copy — if the work is a redesign, do it on a staging site and leave production alone entirely. This is the only approach with zero risk of a 503 window, and it is what most hosts now make trivial.

If you are also preparing a move while the site is hidden, exporting the site before you start is cheap insurance.

Troubleshooting

“Briefly unavailable for scheduled maintenance” will not go away

A stale .maintenance file is sitting in your WordPress root — usually left behind by an update that timed out. Delete it via FTP or your host’s file manager. If you cannot get into wp-admin, that is the only fix; the message is served before WordPress finishes loading plugins.

The plugin is active but visitors still see the real site

A full-page cache is serving the old, cached HTML before WordPress runs. Purge the cache — host cache, Cloudflare, and any plugin cache — then test in a private window. This is the single most common reason “maintenance mode is not working”.

Google indexed the coming-soon page

It returned 200, so it was crawlable. Fix the status code first (most plugins have a setting), then request removal of the placeholder URL in Search Console if it is being served on your real URLs. Expect the old pages to return once Google recrawls and sees a 503 or the real content.

I locked myself out

You probably enabled maintenance mode without the admin bypass. Reach the site with ?bypass=1 if your plugin supports it, otherwise rename the plugin folder via FTP — the site comes back instantly, and your settings are preserved.

The site is hidden but the admin bar shows a cached copy

You are seeing a cached page from the object cache or the browser. Hard-reload, or test with curl -I, which bypasses caches that respect no-cache headers. If curl shows 200 while the browser shows the maintenance page, the problem is client-side.

Frequently asked questions

Can I hide my WordPress site while editing without a plugin?

Yes, but the built-in route is limited. WordPress core only offers the .maintenance drop-in, which expires after ten minutes and is designed for updates. You can pair it with a custom wp-content/maintenance.php file for your own markup, but you will need to recreate the .maintenance file to keep it active. For anything longer than a single update, a plugin or password protection is more practical.

Does hiding my site hurt SEO?

Not if you use a 503 and keep it short. Google’s documentation says 5xx errors make crawlers slow down and preserve already-indexed URLs, but URLs that persistently return server errors are eventually removed. A few days of 503 during a redesign is routine; several weeks is where pages start dropping. Avoid 200-status placeholder pages on URLs you want to keep.

What is the difference between maintenance mode and coming soon mode?

Maintenance mode means “the site exists but is temporarily unavailable” — typically a 503 with a Retry-After header, applied to the whole site. Coming-soon mode is a launch page, aimed at visitors who have never seen the site, and is often served with a 200. Use maintenance while you work on an existing site, coming soon when you are launching something new.

Will visitors see the maintenance page if they are logged in?

Only if the plugin’s administrator bypass is enabled — most have it on by default. Note that the bypass relies on a cookie, so a page cache configured to ignore cookies can serve the maintenance page to logged-in users too. If that happens, allowlist your IP instead.

Can I hide just one page instead of the whole site?

Yes — set that page to draft, or password protect it individually in the block editor’s page settings. That is almost always what people actually need: a single page under construction, with the rest of the site live and ranking. Hiding the entire site to work on one page costs you far more than it protects.

How long can I leave a site in maintenance mode?

Days, not weeks. Google keeps indexed URLs through short 5xx periods, but its documentation is clear that persistent server errors lead to removal from the index. If a project will take longer than a week, either build it on staging, or keep the site live and hide it behind a password instead.

What to do now

Pick the situation honestly: editing a page needs no hiding at all, a redesign needs a 503 maintenance window measured in days, and client review needs a password rather than a wall. Whichever you choose, run curl -I against your homepage and confirm the status code before you tell anyone the site is hidden.

If hiding the site is part of a longer handover or care arrangement, what a WordPress maintenance plan actually covers is the next thing worth reading.

Written by

Editor Team

Content Specialist at Spiracle Themes

We are a team of WordPress enthusiasts passionate about creating beautiful themes and helping users build better websites.

Leave a Reply

Your email address will not be published. Required fields are marked *