How to Put Your WordPress Site in Maintenance Mode Without a Plugin
Every WordPress site needs downtime now and then. Maybe you are redesigning the homepage, running a batch of plugin updates, or migrating to a new theme, and you do not want visitors landing on a half-built page. Maintenance mode solves this by showing visitors a friendly “we will be right back” message while you work behind the scenes.
Most tutorials reach for a plugin first. That works, but every plugin you install adds code to maintain, potential conflicts to debug, and one more thing that can break during updates. For something you might use a few times a year, a plugin is overkill. WordPress has maintenance mode built into its core, and with one small code snippet or a single file, you can enable a clean, branded maintenance page with zero plugins.
This guide shows you two no-plugin methods: a functions.php snippet that gives you a custom maintenance page with your own message and styling, and the .maintenance file method that WordPress itself uses during core updates. Both take under five minutes. Pick the one that fits your situation.
If you like this no-plugin approach, you will also like our guide to limiting login attempts without a plugin, which hardens your login page with pure code the same way.
Method 1: The functions.php Snippet (Recommended)
This method hooks into WordPress and shows a custom maintenance page to everyone except logged-in administrators. You keep full access to the site and the dashboard while visitors see your message. It is the most flexible approach because you control the HTML, the styling, and even the HTTP status code.
Add the following to your child theme’s functions.php file. If you are not using a child theme yet, create one first, because edits to a parent theme’s functions.php are wiped out on the next theme update. Our things to do after installing WordPress checklist covers child theme basics among other launch essentials.
// Enable maintenance mode without a plugin
function vtg_maintenance_mode() {
// Let admins keep working while visitors see the message
if ( current_user_can( 'edit_themes' ) || wp_doing_ajax() || wp_doing_cron() ) {
return;
}
// Send the correct HTTP status so search engines know this is temporary
header( 'HTTP/1.1 503 Service Temporarily Unavailable' );
header( 'Retry-After: 3600' );
?>
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>We'll be right back</title>
<style>
body {
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
background: #f5f7fa;
color: #1a1a2e;
display: flex;
align-items: center;
justify-content: center;
min-height: 100vh;
margin: 0;
text-align: center;
}
.wrap { max-width: 560px; padding: 2rem; }
h1 { font-size: 2rem; margin-bottom: 0.5rem; }
p { color: #555; line-height: 1.6; }
.logo { font-size: 3rem; margin-bottom: 1rem; }
</style>
</head>
<body>
<div class="wrap">
<div class="logo">⚙</div>
<h1>We'll be right back</h1>
<p>We're giving our website a little tune-up. Please check back soon, we expect to be done within the hour. Thanks for your patience!</p>
</div>
</body>
</html>
<?php
die();
}
add_action( 'template_redirect', 'vtg_maintenance_mode' );What this snippet does, line by line:
- The admin bypass: anyone who can edit themes, meaning administrators, skips maintenance mode entirely and browses the site normally. AJAX and cron requests are also excluded so background tasks keep running.
- The 503 status: the snippet sends HTTP 503, which tells search engines the downtime is temporary. Google will not drop your pages from the index over a short maintenance window with a proper 503. The
Retry-Afterheader politely suggests when to come back. - The branded page: the HTML between the PHP tags is a complete standalone page. Swap the gear character for your logo, rewrite the message, adjust the colors to match your brand, and it looks like a deliberate part of your site rather than an error.
To take the site live again, simply remove or comment out the snippet. Visitors immediately see the normal site. Nothing to deactivate, nothing left behind in the database, which is the whole point of skipping the plugin.
Customizing the message
The example above is intentionally generic. For a real maintenance window, be specific: say what is happening and when you expect to finish. “We are upgrading our store checkout and will be back by 3 PM” beats “site under maintenance” every time. If you collect emails, add a simple contact link so visitors can reach you. Keep the page lightweight, no external fonts or scripts, so it loads instantly even if your server is under strain.
Method 2: The .maintenance File (Quick and Built-In)
WordPress core already knows how to do maintenance mode. Every time you update WordPress itself, it creates a file called .maintenance in your site’s root directory, shows a plain “Briefly unavailable for scheduled maintenance” message, and deletes the file when the update finishes. You can trigger this same behavior manually.
Create a file named exactly .maintenance in the root folder of your WordPress installation, next to wp-config.php, with this content:
<?php
$upgrading = time();
?>The moment this file exists, WordPress shows its built-in maintenance message to all visitors. When your work is done, delete the file and the site is live again. That is the entire method.
The trade-off is control. The built-in message is plain and unbranded, and unlike Method 1, it blocks everyone including administrators from the front end, though you can still access /wp-admin directly in most cases. Use this method for short, simple jobs like running updates, and use the snippet method when you want visitors to see something polished.
Stuck in maintenance mode? If a core update fails halfway, WordPress sometimes leaves the
.maintenancefile behind and your site stays stuck on the maintenance message. The fix is simple: connect via FTP or your host’s file manager, delete the.maintenancefile from the site root, and the site comes back immediately.
Which Method Should You Use?
- Use the functions.php snippet when the work will take more than a few minutes, when you want a branded message, or when you need to keep browsing the front end as an admin while visitors see the notice.
- Use the .maintenance file for quick jobs under 15 minutes where a plain message is fine, like running plugin updates or a fast theme switch.
- Use a plugin only if you need extras like countdown timers, email capture forms, or scheduled maintenance windows. For a simple “be right back” page, code wins.
Maintenance Mode and SEO: What to Know
The biggest SEO risk of maintenance mode is sending the wrong HTTP status. If your maintenance page returns a 200 OK status, search engines may index the “we will be back soon” text as your page content. If it returns 404 or 500 errors for days, rankings can slip. The 503 status in Method 1 exists specifically to avoid both problems: it tells crawlers the outage is temporary and to check back later.
Google’s own guidance for site maintenance confirms that a 503 with a Retry-After header is the correct approach, and you can read the details in the Google Search documentation on handling site maintenance. Keep maintenance windows as short as you reasonably can, and never leave a site in maintenance mode for days.
Testing Before You Go Live
Before announcing that the site is back, test in a private browser window where you are not logged in, so you see exactly what visitors saw. Click through the homepage and a couple of key pages, submit a test form if you have one, and confirm the 503 headers are gone. If you are new to the WordPress admin area and want to get comfortable navigating settings after the work is done, our WordPress dashboard walkthrough for beginners is a good next read.
Frequently Asked Questions
Will maintenance mode hurt my Google rankings?
Not if done correctly. A short maintenance window that returns HTTP 503 tells Google the downtime is temporary, and rankings are unaffected. Problems only arise from long outages or wrong status codes, so use the snippet in this guide and keep the window brief.
Can I still access wp-admin during maintenance mode?
With the functions.php snippet, yes, administrators bypass maintenance mode completely and can use both the front end and the dashboard. With the .maintenance file method, the front end is blocked for everyone but /wp-admin usually remains accessible.
How do I get my site unstuck from maintenance mode?
If you used the snippet, remove it from functions.php. If WordPress is showing its built-in maintenance message after a failed update, delete the .maintenance file from your site root via FTP or your hosting file manager. The site returns instantly.
Is it safe to edit functions.php directly?
It is safe if you use a child theme and back up the file first. A typo in functions.php can cause a white screen, so always keep a copy of the original and edit through FTP or the file manager rather than the built-in theme editor, which offers no undo.
Do I need a plugin for a countdown timer on my maintenance page?
Not necessarily. You can add a simple JavaScript countdown to the HTML in the snippet. But if you want email signup forms, social links, and scheduled windows, that is the point where a dedicated maintenance plugin becomes worth installing.
What is the difference between maintenance mode and coming soon mode?
Maintenance mode is for existing sites going down temporarily; it returns 503 to tell search engines to come back. Coming soon mode is for sites that have not launched yet; it typically returns 200 with a teaser page. Use the right one so search engines interpret your site correctly.
One Comment