Originally published: June 14, 2022 · Last updated: August 16, 2026
Maintenance mode is useful when a WordPress site is temporarily unavailable because of planned work. It should communicate a short interruption clearly, not become a permanent layer hiding a broken production site.
WordPress itself already uses a maintenance mechanism during some core, theme and plugin update operations. For longer planned work, you may need a more deliberate maintenance page or staging workflow.
WordPress already has a core maintenance state
During certain updates, WordPress can create a temporary maintenance file and return a maintenance response while files are being changed. WordPress core’s maintenance handling can return HTTP 503 and a Retry-After header while that state is active.
This is intended for short update windows. If the process is interrupted and the maintenance file is left behind, the site can appear stuck in maintenance until the stale state is cleared.
Use staging for routine design and development
Changing a template, rebuilding a page or testing a plugin usually should not require taking the public site offline. A staging environment lets you work on a copy, test the result and deploy only when the change is ready.
Maintenance mode is better reserved for changes that genuinely require temporary production downtime, such as certain migrations or data operations.
A maintenance page should answer four questions
Visitors do not need the technical story. They need:
- confirmation that the interruption is temporary;
- a concise explanation when useful;
- an alternative contact method if the site supports important services;
- a realistic indication of when to try again if you know it.
A branded page can reassure visitors, but clarity matters more than animation or a complicated countdown.
Do not promise a return time you cannot support
A countdown creates a strong expectation. Use one only when the maintenance window is genuinely controlled. If the task may overrun, a broader status message is safer than repeatedly resetting the timer.
Keep administrators able to inspect the site
A useful maintenance system should let authorized administrators or developers preview the real site while ordinary visitors see the maintenance page. Test that access path before beginning the work.
For client reviews, a staging URL is often cleaner than creating exceptions on a production maintenance page.
Think about HTTP status, not only appearance
If the actual site is temporarily unavailable, a maintenance response should communicate temporary unavailability rather than pretending the maintenance page is an ordinary permanent page. WordPress core’s own maintenance handling uses HTTP 503 for this reason.
The exact implementation depends on the hosting and maintenance tool, so verify the response instead of assuming a visually correct page is technically correct.
Do not use maintenance mode as a security boundary
A maintenance or coming-soon page is primarily presentation and availability control. It should not be treated as protection for confidential content, a substitute for authentication or a replacement for a proper firewall and access policy.
Maintenance mode does not replace backups
Before risky work, create a recoverable backup. Maintenance mode only changes what visitors see while the work happens. It does nothing to help you recover a database or damaged file.
Test the site before reopening
Before disabling maintenance mode, verify the critical paths:
- homepage and key templates;
- navigation;
- forms and email delivery;
- login and account functions;
- checkout or booking where applicable;
- analytics or tracking changes;
- mobile layouts;
- caches and CDN behavior.
Then remove the maintenance layer and check the public site again as a logged-out visitor.
Coming soon and maintenance are different states
A coming-soon page is normally used before a site launches. A maintenance page represents a site that exists but is temporarily unavailable. They can use similar tools, but the message and search implications are not identical.
For an established site, do not leave a generic coming-soon page in place for weeks while public URLs and search traffic disappear behind it.
A practical maintenance workflow
- Decide whether production downtime is actually necessary.
- Create and verify a backup.
- Prepare the maintenance message and contact path.
- Confirm administrator access.
- Enable maintenance only when work begins.
- Make the planned change.
- Test critical functionality.
- Disable maintenance promptly.
- Verify the live site and monitoring afterward.
The practical rule
Maintenance mode should be short, informative and operationally boring. Use staging for work that can happen away from production, keep a recovery path, and make the temporary state technically as well as visually clear.
Official reference: WordPress core maintenance function documentation.