Lorixen.
EN

Coming Soon and Maintenance Pages That Do Not Hurt Your SEO

Short answer: A maintenance page should return the HTTP status 503 Service Unavailable, along with a Retry-After header that says when to come back. That tells search engines the outage is temporary and that the real pages will return. A page that says "under maintenance" but returns a 200 status looks like a normal page, and search engines may index it or treat your real pages as changed. Keep the outage short, check the status code before you go live, and avoid leaving a holding page up for weeks.

Why the status code matters more than the message

Visitors read the words on the page. Crawlers read the status code first. A 200 response means "this page is fine, here is its content", so a maintenance message with that status can be stored as the content of your URL. If that happens to your homepage or your product pages, search engines may show the holding message in results, or drop the real pages while the placeholder is up.

A 503 response means "the service is temporarily unavailable". Search engines understand this as a short interruption. They retry later, and they avoid replacing your indexed pages with the placeholder.

What a correct response looks like

The response needs two parts: the 503 status, and a Retry-After header. The header is either a number of seconds or a date. For a one-hour update, the header is:

HTTP/1.1 503 Service Unavailable
Retry-After: 3600
Content-Type: text/html

The body is the page the visitor sees. Keep it simple: say the site is being updated, give an estimated return time if you know it, and offer a way to contact you for urgent matters.

Check the status before you launch the page

A common error is a plugin or a host panel that shows a friendly page but sends a 200 status. Check the real response before you rely on it:

  1. Open a terminal and run curl -I https://www.example.com/. The first line of the reply should show 503.
  2. Look for the Retry-After line in the same reply.
  3. If you have no terminal, open the browser's developer tools, go to the Network panel, reload the page and click the first request to see its status.
  4. Check an inner page too, such as a product or article, because some systems only change the homepage.

If the status is 200, the page is not working as a maintenance page, whatever it looks like on screen.

Ways to put a maintenance page up

  • A content management plugin. Many WordPress maintenance plugins send a 503, but some do not. Test each one before you use it on a live site.
  • A hosting control panel. Many hosts offer a maintenance mode switch. Ask the support team whether it returns 503 with Retry-After.
  • An edge rule. A rule at your CDN or proxy can return the 503 response before the request reaches your server. This works well during a server migration, because it keeps the holding page separate from the code you are changing.

Pick one method, test it, and write down the steps so the next update is faster.

Keep the window short

Google's own guidance on planned downtime says a 503 is for temporary issues. For a short update, such as an hour or an evening, the risk is small. For longer work, the page can start to affect how often Google crawls your site, and a site that stays unavailable for several days may see pages drop out of results. Plan the work in a window, finish it, and bring the site back.

If a rebuild will take weeks, do not keep the live site under a holding page. Build the new version on a separate address, block it from search with a noindex instruction, and switch over when it is ready.

Brand-new sites that are not ready

A new domain that is still being built has no indexed history to protect. Here a coming soon page can return 200, but it should carry a noindex instruction, not be linked from anywhere, and not appear in a sitemap. Once the real site is ready, remove the noindex and submit the sitemap.

What to check after the work

  • The homepage and two inner pages return normal content with a 200 status.
  • The sitemap loads and lists the pages you expect.
  • Search Console shows no new server errors in the Crawl or Page indexing reports over the next few days.
  • Any redirects you added during the work still work.

Telling visitors what to expect

The maintenance page is also a customer touchpoint. Say what is happening in one plain sentence, such as "We are updating our booking system", and give the expected return time as a range, not a promise. If customers need to reach you during the work, provide a phone number or an email address that the page can display without relying on the broken parts of the site.

Avoid jokes or long apologies. Visitors who arrive during an outage want to know whether to come back and when, and a short, clear page answers both questions.

FAQ

Will a short maintenance window hurt my rankings?

A brief outage with a correct 503 response is unlikely to cause lasting harm. The risk grows with length and with the use of 200 status pages.

Should I add noindex to the maintenance page?

For a planned outage on a live site, the 503 status is the signal you need. Noindex is more useful for a staging or coming soon site that should never appear in results.

Can I use a 302 redirect to a holding page?

It is better to avoid it. A redirect to a holding page can be treated as a change to the address, and it does not clearly say the outage is temporary.

How do I know Google has seen the outage?

Check the Crawl stats and Page indexing reports in Search Console after the work, and look for a spike in server errors. A spike that clears within a few days is normal.

If you would like us to set up a correct maintenance response for your next update and check it against the live site, tell us when the work is planned.

Sources

WhatsAppBook a call