This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung
Indexing
What status code does a website send in maintenance mode?
With 503 (Service Unavailable). The standard HTTP provides this code for temporary overload and scheduled maintenance, and Google advises for a short shutdown: an explanatory page with the status 503 instead of the content. If the maintenance page 200 sends, Google processes its text as content of your pages; if it sends 404, the addresses are considered removed. This includes a short duration and an exception for the robots.txt.
503 tells the crawler to come back later
RFC 9110 describes 503 as a response from a server that is unable to handle the request due to overload or scheduled maintenance, and that expects it to settle down after a while. With the Retry-After header, the server can suggest how long a program should wait; Google recommends setting them with an estimate. Google responds to 503 as it does to other server errors: it lowers the retrieval rate, keeps indexed addresses in the index first, and gradually increases the retrieval rate once the server responds with a 2xx code. As long as a page sends 503, Google cannot refresh title, description and structured data.
One to two days are planned, a few days the extreme
Google calls the period itself: If you urgently have to shut down the website for one or two days, send an explanatory error page with 503. This condition should not last longer than a few days, because otherwise it has clear consequences in the search. The reason is in Google’s overview of the status codes: Addresses that persistently provide a server error, Google removed from the index. For the return after a complete removal, Google does not mention a fixed time and no way to speed it up. Overnight or weekend maintenance is within what 503 is intended for. A renovation over weeks needs a different plan.
The robots.txt continues to respond as usual
One exception is Google specifically: The robots.txt should not send a 503 during maintenance, because this blocks all crawling. A maintenance desk that places the maintenance page above each address also hits this file; ask if yours does. Also unsuitable for a break are a robots.txt, which locks everything, a noindex on all sides or the codes 403, 404 and 410. According to Google, they all lead to addresses being removed from search.
Who closes longer, leaves the website online and turns off the purchase
For a longer break, such as company holidays or delivery stops, Google recommends that you leave the website accessible and restrict only the function: switch off the shopping cart, show an indication on all pages, adjust availability and opening times in the structured data. Switching off the shopping cart does not change the visibility in the search according to Google. So the pages remain in the index, and customers read when it goes on. If the website still has to be off the net longer, Google advises a homepage as a placeholder, which answers with status 200 and can be found in the search.
- Before maintenance: Prepare maintenance page with reason and expected end and check that it sends 503.
- During maintenance: call your-domain.at/robots.txt. The file must appear as usual.
- After maintenance: Call homepage and two subpages and check status 200.
- You can see the status of the maintenance page in the browser: F12, tab network, page reload, first entry. There must be 503.
- WordPress sends during an update of itself 503 with the header Retry-After: 600 and the indication that the website is not available for a short time.
- Write on the maintenance page what is going on and when the website is back. Google already recommended its own 503 page with this information in 2011.




