The fastest way to put a WordPress site in maintenance mode is a maintenance or "coming soon" plugin that shows visitors a holding page while you keep working behind the scenes. WordPress doesn't ship a one-click maintenance toggle in the block editor, so for most sites a small plugin is the right tool, not a workaround.
Reach for maintenance mode before big changes: theme switches, major plugin updates, or a redesign you don't want visitors to see half-finished. If you're already using a staging site for the actual work, you may not need maintenance mode at all, since visitors never see staging. Maintenance mode matters most when the changes have to happen on the live site itself.
The plugin approach
A maintenance plugin intercepts every front-end request and shows a holding page instead of your normal site, while leaving wp-admin reachable so you can keep working. Two solid free options:
- SeedProd has a drag-and-drop page builder for the holding page itself, if you want something branded rather than a plain notice.
- WP Maintenance Mode is lighter: a simple on/off toggle plus a basic message editor. Good if you just need visitors blocked out without designing anything.
To install either: go to wp-admin → Plugins → Add New, search for the plugin name, click Install, then Activate. Both add a settings page under Settings in the sidebar. Turn maintenance mode on there, edit the message if you want, and save. Visitors now get the holding page; you can still log in and edit normally.
Whitelisting your own access
Most maintenance plugins automatically exempt logged-in administrators, so you see the real site while everyone else sees the holding page. Check this setting before you rely on it, especially if you need to preview the front end as a visitor would see it. Some plugins have a separate "bypass" option, like a secret URL parameter or IP whitelist, for exactly that case.
Setting the right HTTP status
A maintenance page should return a 503 Service Unavailable status, not a normal 200. This tells search engines "temporarily down, check back later" instead of "this is now the page's content," which protects your rankings during short outages. Reputable maintenance plugins handle this automatically. If you're writing a custom maintenance page yourself rather than using a plugin, this is the detail that's easy to miss and costly to get wrong, since a prolonged 200 response on a maintenance page can get the underlying page devalued or dropped from search results.
Don't leave maintenance mode on for more than a day or two. Search engines tolerate short 503 windows without penalty, but an extended one starts to look like the site actually is gone.
Before you flip the switch
Maintenance mode protects visitors from seeing a broken page. It doesn't protect your data. If you're about to do anything risky, a theme change, a major plugin update, custom code, take a backup first. Backing up your WordPress site covers what's already running automatically on Flashcloud hosting and how to trigger an on-demand backup before you start.
For anything bigger than a quick tweak, staging is usually the better tool. Maintenance mode hides the live site while you edit it live, which still carries risk if something breaks mid-edit. Staging lets you make the change on a separate copy first and only push it once it's verified. See Using WordPress staging for that workflow, particularly if the site sells anything, since a broken checkout during a live edit costs real orders.
After you turn it off
Once your changes are live, go back to the plugin's settings page and switch maintenance mode off. Load the homepage and a couple of key pages yourself to confirm the site looks right before you consider the job done. If the site felt slow before you started and that wasn't the reason for the maintenance window, My WordPress site is slow covers the caching and plugin-weight checks worth running next, since Flashcloud's cache stack handles the server side but plugin and image weight are still on you.
If your maintenance page won't turn off, is stuck showing to logged-in admins too, or you're not sure why a 503 is affecting how a page ranks, open a ticket from Support in the portal. It's real people, not a bot, and they can look at the specific install with you.