WordPress maintenance mode: fix it and plan it well

What is WordPress maintenance mode?

Think of maintenance mode as a temporary sign on your storefront. Someone arriving from Google or an ad needs to know whether you are still open and how to contact you. Explain the interruption without making a technical task look like a closed business.

• Automatic update notice

  WordPress creates a .maintenance file in the installation root during updates and normally removes it afterward. This is part of the update process, rather than a page you need to design in advance.

• Planned maintenance page

  You deliberately show a brief notice while a live change makes normal use unreliable. Give it an owner, a realistic window and a way for customers to call or email.

• A screen that will not clear

  An interrupted update, a separate maintenance plugin or cached content can leave visitors seeing a notice. Identify which layer is serving it before changing unrelated settings.

The automatic screen says: Briefly unavailable for scheduled maintenance. Check back in a minute. WordPress troubleshooting documentation explains the root file and its removal after a failed upgrade.

For a reliable WordPress website, keep inquiries, bookings and sales available, with a recovery route when updates go wrong.

How to fix WordPress maintenance mode

If an update is still running, let it finish and avoid launching another update from a second tab. If it has failed or stopped and the notice remains, use the host file manager or SFTP, a secure connection to your site's files. You do not need a working WordPress dashboard to reach that file.

1. Step 1

   Confirm that the update has stopped

   Check the update result and hosting activity, or ask the host to confirm no upgrade process is active. Record the component being updated and any error so the next action addresses the failed change.

2. Step 2

   Preserve a recovery point

   Find the backup taken before the update and confirm access to it. Save a current files-and-database snapshot separately before repairs, especially when orders or inquiries have arrived since that backup.

3. Step 3

   Open the correct WordPress root

   In the host file manager or SFTP client, locate the folder containing wp-admin, wp-content and wp-includes. Enable hidden-file display because .maintenance starts with a dot; confirm the domain if your hosting account contains several sites.

4. Step 4

   Delete only the leftover .maintenance file

   Once the update has stopped, remove that exact file from the installation root. Leave wp-config.php, .htaccess and the WordPress folders in place, then check the public site and dashboard in a fresh browser session.

5. Step 5

   Finish or roll back the failed update

   Check the affected component's version and the host error log. Complete a compatible update or restore the affected component with qualified help; if database changes occurred, use a coordinated recovery plan that preserves newer business records.

6. Step 6

   Verify the visitor journey

   Clear the relevant caches after the repair and check the site while logged out. Test contact delivery, booking or checkout as applicable, and watch for recurring errors before closing the incident.

WordPress normally ignores the marker once its timestamp is ten minutes old, as documented in WordPress's maintenance-mode check. A longer-lasting notice can involve caching, a plugin, the host or another active update, so do not keep deleting files blindly.

If .maintenance is absent, ask the host to identify the response source and check intentional maintenance settings. Share the URL, screenshot, start time and recent update, without emailing passwords.

WordPress maintenance mode or staging?

Use a maintenance page when a short live operation would expose unreliable behavior, such as a checkout change or final migration. Prepare copy and redesigns on staging, an isolated copy where customers are unaffected.

Follow our WordPress updates guide for the backup, staging and update workflow. Protect staging from public access and disable real payments, customer email and integrations there, so a test order does not become an actual charge or customer notification.

WordPress maintenance mode and Google

The visible notice and the server response need to agree. For a short outage, use HTTP 503, meaning temporarily unavailable, with a Retry-After header giving a best estimate of when to try again. A header is information sent with the page, even though visitors do not see it.

HTTP/1.1 503 Service Unavailable
Retry-After: 600
Cache-Control: no-store

HTTP/1.1 200 OK

We are temporarily closed for maintenance.

Google's HTTP status guidance says server errors reduce crawling and persistent errors can remove URLs from the index. A 503 is therefore a short interruption signal, not a way to preserve visibility through a long closure.

Google's temporary closure guidance recommends Retry-After, keeping robots.txt accessible and limiting functionality when possible. Avoid leaving a whole-site maintenance page up for days; keep useful information available while longer work continues on staging.

A coming-soon page introduces a new site or business before launch; a maintenance page pauses an existing experience. For a prelaunch page you want indexed, provide real information and return 200. Keep unfinished staging content private, and avoid replacing every established URL with the same launch message.

Choose a WordPress maintenance mode plugin

Many options exist in the WordPress.org plugin directory. Verify status codes and cache behavior on your hosting setup, beyond the visual preview. Your host or existing tools may already provide a suitable control.

• Verify the public response

  Ask whoever configures the page to check a real logged-out request. Confirm 503, Retry-After and the expected notice on the homepage and another public URL, after any CDN or page cache.

• Define who can get through

  Editors may need to preview the normal site while customers see the notice. Check the actual access rules, including customer accounts, instead of assuming all logged-in users should bypass it.

• Keep contact usable

  Check that the message fits a phone, the call and email links work and the promised contact route is staffed. Avoid a form that depends on the same system currently being repaired.

• Make removal predictable

  Record how to switch the page off and how to regain access without the dashboard. Assign someone to verify reopening from outside the administrator's session.

These are acceptance checks, not features promised by every plugin. Test before the maintenance window and avoid overlapping maintenance tools that could show different versions to different visitors.

How to put WordPress in maintenance mode

A small site plugin can demonstrate the essential behavior: let signed-in users through, send logged-out page visitors a temporary response and avoid storing that response in caches. Have your maintainer install and test it on staging first. Owners do not need to edit PHP to specify these requirements.

<?php
/* Plugin Name: Short Maintenance Window */
add_action('template_redirect', function () {
    if (is_user_logged_in()) {
        return;
    }
    nocache_headers();
    header('Retry-After: 600');
    wp_die(
        'Short maintenance. Please try again soon.',
        'Maintenance',
        ['response' => 503]
    );
});

This example handles ordinary front-end page requests and allows every signed-in user, including customer accounts, to bypass it. It does not block APIs, background jobs, login or every payment callback, and it cannot intercept HTML already served by a CDN. A store may need coordinated restrictions at the host and application layers.

The default core screen already uses 503 and Retry-After, as shown in WordPress's maintenance response. Check custom replacements separately, because their output can differ.

Before a WordPress website maintenance window

Schedule around customers, ad traffic and bookings. Agree who can authorize rollback, when to report if work runs over and which checks must pass before reopening.

A maintenance notice does not secure a compromised site. If you see unknown administrators or unexpected files, use the WordPress security checklist and involve the host before reopening a potentially unsafe customer journey.

What to say on a maintenance page

Tell customers what they can still do, when they should check again and where to get help. Use a time zone and a specific next update if completion is uncertain. Keep the wording calm, especially when a booking or payment has already been attempted.

We are making a short update to our website.
Online [booking/orders] is temporarily paused.
Next update: [date, time and time zone].
Need help now? Call [number] or email [address].
If a payment appeared to fail, contact us before
trying again so we can check its status.

Replace the placeholders and remove sentences that do not apply. Confirm existing orders or appointments before calling them unaffected, and avoid a countdown that resets on every visit. Give a reliable next update rather than an unsupported reopening promise.

For agencies managing a client's outage

Give the client a separate operational note: what is unavailable, what is confirmed, who is working on it and when you will report again. Keep file paths, credentials and internal errors off the public notice. Maintain one agreed contact so different staff members do not make competing changes.

Remove the page and prove the site works

An administrator may see a working site while logged-out customers still get cached maintenance HTML. Verify a new visitor's experience and the systems behind the page.

Use the recurring WordPress maintenance checklist to keep recovery, forms and update reviews on the calendar. If you prefer one team to own those checks, our WordPress maintenance service combines staged updates, backups, security and monitoring with a clear written scope.