Put WordPress maintenance mode, the temporary update screen, behind a 503 status and noindex tag. That pairing tells crawlers to retry later and leave the screen out of search results. Visitors see a short notice while you update themes, plugins, or designs. Crawlers handle that notice differently than browsers, so the server response matters more than the words on screen.
Table of Contents
- Why does a maintenance page show in search results?
- How does a 503 status protect you?
- How to set up maintenance mode safely?
- What to check before going live again?
Why does a maintenance page show in search results?
A maintenance page served with a 200 OK status looks like a normal page to crawlers. They can store its headline and show it for your address. Many simple coming-soon layouts cause this problem.
They hide your content visually but still return 200, which invites storage in results. A brief test rarely causes lasting harm. A 200 notice left for days can replace your real titles and descriptions in results.
How does a 503 status protect you?
A 503 Service Unavailable status signals a brief outage. It asks crawlers to come back later without storing the current screen. Add a Retry-After header with a short wait, such as a few hours.
It spreads out return visits and lowers load from repeated crawl attempts. Pair the 503 with a noindex tag in the maintenance template. If a crawler renders the screen despite the status, the tag gives a second keep-out signal.
How to set up maintenance mode safely?
Choose a method that sends 503 by default. WordPress core does this during automatic updates, and many dedicated maintenance tools do the same. Do not rely on the Reading setting that discourages search engines.
It applies site-wide and often stays on after launch when forgotten. Do not block the maintenance page only with robots rules. A blocked page can still appear as a bare address when other sites link to it.
- Turn on maintenance and pick a simple template without links or feeds
- Set the response to 503 and add a Retry-After interval of a few hours
- Add noindex to the maintenance template and keep it out of menus
- Allow admin access so you can work and preview while visitors see the notice
What to check before going live again?
Preview the maintenance address while logged out. Confirm the server returns 503, includes Retry-After, and serves the noindex tag. Admin views often bypass maintenance, so a logged-in check can hide mistakes.
Remove maintenance as soon as work ends and load two or three key pages. Confirm each returns 200 and shows full content without a site-wide noindex tag. Keep downtime short when possible. An outage stretching for many days can lose visibility even with a correct 503, so use a staging copy for long rebuilds.
