How to Put WordPress in Maintenance Mode

What WordPress Maintenance Mode Does

Maintenance mode shows logged-out visitors a holding page with an HTTP 503 status while the site stays editable for administrators. The 503 tells search engines the downtime is temporary, so pages are not dropped from the index the way a 404 would drop them.

Use it for a theme switch, a plugin audit, a database change or a redesign that moves navigation. Skip it for a single post edit: the site does not need to go dark while you type.

How to Put WordPress in Maintenance Mode With a Plugin

Install one maintenance plugin, open its settings, switch the mode on and write the message. Stay logged in, then check the page in a private window before you start the real work.

1. Go to Plugins → Add New, search for maintenance mode, and install a plugin with recent updates. Activate one only.
2. Open its settings, switch the mode on, and set the message and the expected return time.
3. Turn on the 503 option if the plugin has one; it tells search engines the page is temporary.
4. Keep your admin session open, then open the site in a private window. The holding page should appear there and the normal site in your tab.
5. Do the work, turn the mode off, and check the private window again.

Do not run two maintenance plugins; both try to own the same screen and the second one usually wins without telling you. The account this runs on is covered on WordPress hosting in India.

How to Enable Maintenance Mode Without a Plugin

Create a file named .maintenance in the WordPress root, the folder that holds wp-config.php, containing <?php $upgrading = time();. The site then shows the default maintenance page to visitors until you delete that file.

1. Open File Manager in the hosting panel and go to the folder that contains wp-config.php.
2. Create a new file named .maintenance, with the leading dot.
3. Paste one line and save: <?php $upgrading = time();.
4. Open the site in a private window; the default maintenance message should appear.
5. Delete the file when the work is finished.

A snippet in functions.php can do the same and show a custom message with a 503, but a syntax error there locks you out of the dashboard. Test theme-file edits on a WordPress staging site first.

Why You Still See the Live Site or a Stuck Maintenance Screen

Logged-in administrators always see the live site, which is the point of maintenance mode, so test in a private window or a second browser. If every visitor sees the maintenance message long after an update, a failed update left the .maintenance file behind.

During an automatic update WordPress creates .maintenance in the folder that holds wp-admin. Delete that file in File Manager and reload; the site returns at once. Do not delete wp-config.php, and do not rename the wp-admin folder.

If the site returns a 503 with no maintenance page, the cause is elsewhere; fixing a 503 error covers PHP, database and proxy causes.

What the Maintenance Page Should Say

Say what is happening, when the site will be back and how to reach you if it is urgent. One sentence, one time and one email address is enough, and a countdown timer only helps when the end time is known.

• What — "We are updating the site and it will be back shortly."
• When — a time, not "soon".
• Contact — one email address for urgent orders.
• Brand — your logo and colours, so the page does not look like an error.

Coming soon is a different page: it runs before launch and can stay up for weeks. Maintenance mode is for a live site that is briefly unavailable.

How to Turn Maintenance Mode Off and Check It Worked

Switch the plugin off or delete the .maintenance file, then load the site in a private window and confirm the real homepage returns with a 200 status. Clear the cache if the holding page persists.

1. Turn off the plugin toggle, or delete the .maintenance file.
2. Purge the hosting cache and any CDN cache.
3. Open the homepage in a private window; the real page should load.
4. Check the response in DevTools, Network tab; it should be 200, not 503.
5. Open one inner page and confirm it loads too.
6. Log in and confirm the dashboard is unchanged.