A maintenance page earns trust by telling visitors three things in plain language: that the downtime is deliberate, roughly when the site will return, and where to go in the meantime. Everything else — the illustration, the brand voice, the clever copy — is decoration on top of those three facts. The technical side matters just as much, because a maintenance page that returns the wrong status code can cost you search rankings or get cached as your real homepage. Done properly, a maintenance page is a short, honest holding message served with an HTTP 503 response and a sensible contact route.
Table of Contents
- The three facts every visitor is looking for
- Return a 503, not a 200
- Implementation on WordPress, Drupal, and plain servers
- Writing copy that doesn't sound evasive
- Pre-launch checks
- Frequently Asked Questions
The three facts every visitor is looking for
Someone hitting a maintenance page has one question: is the problem mine or yours? Answer it in the first sentence. "We're performing scheduled maintenance" tells them immediately that their connection, browser, and account are fine — which stops the pointless troubleshooting that drives support tickets. Next, give a time. A specific return window ("back by 14:00 UTC", or a date for longer work) is far better than "we'll be back soon", which reads as filler and ages badly.
If you genuinely don't know, say what you do know: "we expect to be back within two hours and will update this page" is honest and still actionable. Third, give an exit. A phone number, an email address, a status page, or a social account where updates will appear all give the visitor somewhere to go. Without one, the page is a dead end, and a dead end is where trust leaks — especially for a visitor who was mid-purchase or mid-application.
Return a 503, not a 200
This is the part most maintenance pages get wrong. If your server returns HTTP 200 (OK) with maintenance copy, you are telling search engines and caches that this thin holding page is the legitimate content of that URL. Google's own guidance on site downtime has long been to serve `503 Service Unavailable` for temporary outages, which signals "come back later" rather than "this is the page". A 503 keeps the existing indexed version of your pages in place during short downtime instead of inviting search engines to replace them with the maintenance notice. You can optionally add a `Retry-After` header with either a number of seconds or an HTTP date, giving crawlers a hint about when to return.
Two failure modes to avoid: redirecting all traffic to a maintenance page with a 302 (which muddles URLs and can be cached oddly), and leaving the maintenance response in place for days. Extended downtime served as 503 will eventually cost you visibility, because at some point a search engine has to conclude the content is gone. For planned work measured in weeks rather than hours, a real page explaining the situation — served with a normal 200 — is the better trade. Also set caching deliberately. A CDN or browser that caches your maintenance page aggressively will keep showing it after the site is back. Send `Cache-Control: no-store` (or a very short max-age) on the maintenance response.
Implementation on WordPress, Drupal, and plain servers
WordPress has a built-in mechanism: during core, plugin, or theme updates it writes a `.maintenance` file in the web root and shows a bare "Briefly unavailable for scheduled maintenance" message, served with a 503. If an update crashes partway, that file can be left behind and the site stays stuck — deleting `.maintenance` over FTP or SSH is the standard fix. For anything longer than an update, use a maintenance-mode plugin or drop a `maintenance.php` file in `wp-content`, which WordPress will use in place of the default message. Make sure whatever you choose exempts logged-in administrators, or you lock yourself out of the dashboard you need to finish the work.
Drupal ships maintenance mode as a core setting (`/admin/config/development/maintenance`), which lets users with the "Use the site in maintenance mode" permission through while everyone else sees the maintenance message. Drupal also lets you edit the maintenance page text in the same place, so the message is not stuck at a default. At the server level you can skip the application entirely, which is more robust — the page still works when PHP or the database is down. A common Nginx pattern: Apache users can do the equivalent with `mod_rewrite` conditions plus `ErrorDocument 503`.
- Create a static `maintenance.html` outside the app's control
- Add `error_page 503 /maintenance.html;` and an `if (-f /path/to/maintenance.flag) { return 503; }` guard
- Mark `/maintenance.html` as `internal` so it can't be requested directly at a 200
- Allow your own IP through so the team can test the live site
- Toggle maintenance by creating and deleting the flag file, not by editing config
Writing copy that doesn't sound evasive
Keep it short. Four or five lines beat a paragraph, because a visitor on a maintenance page is scanning, not reading. Lead with the fact, then the time, then the contact route — the same order as their questions. Avoid blame and avoid vagueness. "Due to unforeseen circumstances beyond our control" tells the reader nothing and sounds like a company hiding something. "We're upgrading our payment system" is specific, requires no apology, and makes the downtime sound competent rather than accidental.
If the downtime is unplanned, say so directly: people forgive outages far more readily than they forgive evasion. One warning about transparency: don't publish detail that helps an attacker. Naming the specific software version you're patching, or stating that you're recovering from a breach before you've confirmed the facts, creates problems that good copy can't fix. "Emergency maintenance" is sufficient. Finally, match the page to the brand. A maintenance page is often the only page a first-time visitor ever sees, and a page with your logo, your typeface, and your colours reads as a functioning company. One served as unstyled black Times New Roman on white reads as a broken server — even when the underlying situation is identical.
Pre-launch checks
Test the page before you need it, because the moment you need it is the worst time to discover a bug. A maintenance page that depends on your CSS being served from the application, or on a database-driven template, will render as plain text exactly when the application is down.
Run through this list on a staging environment or during a short planned window: If you run scheduled maintenance regularly, keep the page in version control alongside the site and treat the toggle as part of the deployment runbook. An improvised maintenance page written under pressure at 02:00 is the one that ships with a 200 and a typo.
- Confirm the status code with `curl -I https://yoursite.com` — look for `503`, not `200` or `302`
- Check the page renders with no external dependencies: inline the CSS, inline or base64 the logo
- Verify it works on mobile, since a large share of traffic arrives there
- Confirm your own IP or an admin bypass still reaches the live site
- Check that any contact method on the page is actually monitored during the window
Frequently Asked Questions
Does a maintenance page hurt SEO?
Not for short, correctly served downtime. A 503 response tells search engines the outage is temporary and keeps your indexed pages in place. Harm comes from serving the maintenance notice with a 200, or from leaving a 503 in place for weeks.
How do I get out of WordPress's "briefly unavailable" state?
Connect over FTP or SSH, look for a file named `.maintenance` in your WordPress root directory, and delete it. It's created during updates and should be removed automatically — a leftover means an update failed partway through.
Should the maintenance page include a countdown timer?
Only if you're confident in the end time. A timer that reaches zero while the site is still down is worse than no timer at all, because it converts a vague wait into a broken promise.
What's the difference between maintenance mode and a coming-soon page?
Maintenance mode is temporary and should return 503. A coming-soon page is the site's real content for now, so it should return 200 and be indexable — you want it found.




