How Do I Put WordPress Into Maintenance Mode?
Why the HTTP Status Code Matters
Search engines interpret HTTP status codes as meaningful signals about a page's state — a 503 clearly communicates "temporarily unavailable, check back later," while a normal 200 status showing generic maintenance content (or worse, a 404) can be misread as the actual, permanent state of that URL, risking it being deindexed or deprioritized if the maintenance period is long or the signal is missing entirely.
Getting Maintenance Mode Right
- A dedicated maintenance mode plugin handles the 503 status code correctly by default, alongside providing a properly designed, branded maintenance page rather than a generic placeholder.
- WordPress's own core "under maintenance" mode (which activates briefly and automatically during a core update) does return a 503 correctly, but isn't meant for extended manual use — a dedicated plugin is the right tool for planned, longer maintenance windows.
- Allowing specific IP addresses through (so the development/support team can still access and test the site while maintenance mode is active for everyone else) is a common and useful plugin feature worth using.
- Including an estimated return time or a way to be notified when the site is back is a good practice for visitor experience, beyond just the technical correctness of the status code.
Setting Up Maintenance Mode Properly
- Use a dedicated maintenance mode plugin that correctly returns a 503 status code.
- Allow specific IPs through for the team working on the site during the maintenance window.
- Design a proper, branded maintenance message rather than a generic default.
- Disable maintenance mode promptly once work is complete, rather than leaving it active longer than necessary.
Need a properly configured maintenance workflow for planned updates? See WordPress bug fix.