Put WordPress in Maintenance Mode the Right Way
A maintenance page is more than a message: it's the right HTTP status so you don't wreck your SEO, plus access control so you can keep working. Here's how.
You need to redo a design, migrate content, or fix something visitors can see—so you want to show a tidy “we’ll be right back” page while you work. Simple, right? Except the message is the easy part. Do maintenance mode carelessly and you can quietly damage your SEO, lock yourself out of your own site, or let Google index a placeholder as your homepage. Doing it right is about the response your server sends and who’s allowed past it. Here’s the proper way.
The essentials
- The HTTP status matters more than the message: temporary downtime should return 503, not 200.
- The module has four modes: Maintenance (503) and Coming Soon (503) hide the site from search engines and seal off the REST API; Staging (200) and Development (200) answer 200, leave the REST API reachable, and show the site to whitelisted roles and IPs only; everyone else gets the holding page.
- Access control: administrators always get through; whitelist other user roles and IP addresses, with an optional login link.
- Build the page with no code: headline, message, logo, background and text colours. The countdown timer and email capture are part of Coming Soon mode, described below.
- Three reminders—a badge in the admin bar, a dashboard-widget signal and a warning on the module page—stop the classic mistake: finishing work and forgetting the site is still hidden.
Why does the HTTP status code matter so much?
The HTTP status code matters because search engines read it, not just your text: a 503 (“service unavailable”) tells Google the downtime is temporary and your rankings survive it, while a 200 (“all good”) invites Google to index your holding page as real content. That applies to a live site under repair and to a site that isn’t launched yet. Two situations, and getting the code wrong hurts you:
- Temporary downtime (a live site you’re updating): the right response is 503 Service Unavailable, which tells Google “this is temporary, come back later”—so your rankings survive the outage. Send a 200 and Google may index your “we’ll be right back” text as real content. This is Google’s own advice for planned downtime, and its guide to temporarily pausing a site adds a time limit: a 503 for one or two days, and “a few days at most” for a whole site.
- A site that isn’t launched yet: this is the one most guides get wrong. A pre-launch “coming soon” page should also return 503, not 200. A 200 invites search engines to index the placeholder as your finished site; a 503 says “not ready—check back,” which is exactly what you mean.
That’s why this module sends 503 for both Maintenance and Coming Soon, complete with a Retry-After header—the header MDN recommends with every 503 to say when to come back—and seals off the REST API (the /wp-json address other software uses to read your content) while a 503 mode is active. Two things still pass, and you should know it: requests to admin-ajax.php, which logged-in work depends on, and files in your uploads folder, which the web server hands out directly without asking WordPress—so a direct link to an image or a PDF keeps working.
How do you enable maintenance mode properly?
To enable maintenance mode properly, activate the Maintenance module in Blaminhor Essentials, pick one of its four modes, and it sends the correct HTTP status automatically—503 for temporary downtime, 200 for a preview; only whitelisted people see the real site. Then design the holding page in plain fields and whitelist the roles and IP addresses that keep live access.
This is not the screen WordPress shows during its own updates. That one comes from a .maintenance file in the site root, which core stops honouring ten minutes after it was written—a safety net for updates, not a tool you can style or control.
The Settings tab: pick the mode—which sets the right HTTP status for you—then fill in the holding page’s title, headline and message. Design and Access have their own tabs.
Choose the mode
Select Maintenance, Coming Soon, Staging or Development. The correct HTTP status (503 or 200) is sent automatically, so you never have to think about it.
| Mode | HTTP status | Search engines | Use for |
|---|---|---|---|
| Maintenance | 503 | Hidden (temporary downtime) | Updating a live site |
| Coming Soon | 503 | Hidden (not yet launched) | Warming up before a launch |
| Staging | 200 | Holding page, noindex | A client reviewing work |
| Development | 200 | Holding page, noindex | Your team testing features |
Design the page (no HTML)
Set a headline, message, logo, background colour and text colour to match your brand—just fill in fields. In Maintenance mode you can announce an estimated end time, shown to visitors and sent to crawlers as the Retry-After hint. You can also drop in a contact or signup shortcode if you already use one.
Control who gets through
- Whitelist roles — administrators always get through (their checkbox is ticked and locked); add Editors or any role that needs live access.
- Whitelist IPs — let your office’s public IP see the real site without logging in (one exact address per line; behind a proxy such as Cloudflare, the server sees the proxy’s address, not yours).
- Login link — optionally show a link to log in straight from the maintenance page. When the Hide Login module is active, the link is withheld automatically so your secret login address never appears on a public page.
What makes a good free coming soon plugin for WordPress?
A good coming soon page hides the unfinished site with a 503, tells crawlers when to come back, and collects emails without a second plugin. The Coming Soon mode of this module does exactly that—countdown, Retry-After matched to your launch date, built-in email capture with CSV export—and the whole setup, with real screenshots, is in how to set up a WordPress coming soon page without hurting SEO.
When should you use it?
Use Maintenance mode for any change visitors could see half-done on a live site—a redesign, a content migration, a database cleanup, a clean-up after a hack. Use Coming Soon before a brand-new site launches, and Staging or Development to share work in progress with a client or your team without the public or search engines seeing it.
- A major theme or design change on a live site (Maintenance).
- Migrating content or restructuring URLs (Maintenance).
- A database update or cleanup (Maintenance).
- Cleaning up after a hack (Maintenance), while you follow the hacked WordPress recovery steps.
- Before launching a brand-new site (Coming Soon).
- Sharing work in progress with a client or your team (Staging / Development).
What does maintenance mode done right come down to?
Maintenance mode doesn’t need to be complicated—but it does need to be correct: the right HTTP status so you don’t harm your SEO, access control so you can keep working, and a reminder so you don’t leave it on. That’s the whole job, and it’s what this module handles. Pair it with a backup before any risky change and you can work behind the curtain with confidence.
Maintenance is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.
– blaminhor
FAQ
Why is my WordPress site stuck in maintenance mode, and how do I get out?
The classic cause: an update failed halfway and left a .maintenance file in your site root. WordPress ignores that file on its own ten minutes after it was created, so the built-in screen usually clears itself; if it doesn't, delete the file over FTP or your host's file manager. That's separate from the Maintenance module, which you simply toggle off from the dashboard.
How do I enable maintenance mode without a plugin (.maintenance file)?
WordPress creates a temporary .maintenance file automatically during updates; you can place your own in the site root with a one-line PHP snippet to trigger the same screen. But it's bare—no styled page, no access control, no way in for yourself—and WordPress stops honouring it ten minutes after the timestamp it contains. A module gives you a styled page, access control and no expiry.
How do I let myself see the site while it's in maintenance mode?
Whitelist access. Administrators always get through the Maintenance module; you can add other roles, and whitelist specific IP addresses so a whole office sees the live site without logging in. There's also an optional login link on the maintenance page, withheld automatically when the Hide Login module keeps your login address secret.
What's the difference between maintenance, coming soon and staging modes?
Maintenance (503) is temporary downtime on a live site; Coming Soon (503) is a not-yet-launched site—both are hidden from search engines and both seal off the REST API. Staging and Development modes are preview environments for clients or your team: they return 200, leave the REST API reachable, show crawlers a noindex holding page, and let only whitelisted users see the site.
Will maintenance mode hurt my Google rankings?
Not if you return the right status. A 503 tells Google the downtime is temporary, so it holds your rankings and comes back later. The danger is a page that returns 200: Google may then index your placeholder as real content. The Maintenance module sends 503 automatically, so this stays a non-issue.
How long can I safely leave my site in maintenance mode?
A 503 with a Retry-After header is fine for hours, even a day or two—Google's own guidance is to use it for a site disabled for one or two days, and warns that a whole site down for longer than a few days starts losing standing in Search. Keep maintenance windows short, and never forget to switch it off once the work is done.
Comments