Does Website Downtime Hurt SEO? What Google Does

Farouk Ben. - Founder at OdownFarouk Ben.()
Does Website Downtime Hurt SEO? What Google Does - Odown - uptime monitoring and status page
Content

Short answer: a few minutes or even a few hours of downtime almost never hurts your Google rankings. Downtime that lasts more than a day or two can, because Google starts dropping pages it can't reach from its index. Planned maintenance done the right way, with a 503 status code, is safe.

Here's what actually happens, based on Google's own documentation and comments from its Search team.

What Google does when your site is down

When Googlebot tries to crawl a page and gets a server error (a 5xx status code such as 500 or 503) or a timeout, three things happen:

  1. Crawling slows down. Google treats server errors as a sign your server is struggling, so it crawls less to avoid making things worse. 429 (Too Many Requests) responses have the same effect.
  2. Pages already in the index stay there, for now. Your rankings don't change straight away. Google keeps showing the version of the page it already has.
  3. If the errors continue, pages start dropping out. Google's documentation says URLs that keep returning server errors are eventually removed from the index. Google's John Mueller has said that happens when errors persist for more than a day or two.

When the site comes back and returns normal 200 responses, crawling ramps back up. Pages that were dropped usually return to the index, and generally to their old positions, once Google can crawl them again, though it can take a while for a large site.

How much downtime is too much?

Outage Likely SEO impact
A few minutes None. Googlebot probably didn't even try to crawl during that window.
A few hours Usually none. Crawling may slow down briefly.
One to two days Crawling slows noticeably; some pages may start to drop.
Several days or more Pages drop from the index and lose traffic until they're recrawled.

The bigger risk with short outages is the people, not the crawler: visitors who arrive during an outage leave, and some don't come back.

The status code matters more than the outage

What your server returns while it's down makes a big difference:

  • 503 Service Unavailable tells Google the problem is temporary. Already indexed pages are kept while you fix things. This is the right code for maintenance and outages.
  • 404 Not Found or 410 Gone tell Google the page no longer exists. Indexed pages are removed. A maintenance page that returns 404 can do real damage.
  • 200 OK with an error message ("We'll be back soon") is a soft error. Google may index the maintenance message in place of your real content.
  • Timeouts and connection errors are treated like server errors, and crawling slows quickly.

Planned downtime done right

If you need to take a site offline for maintenance:

  1. Return 503 Service Unavailable on every page, ideally with a Retry-After header saying when you expect to be back.
  2. Keep robots.txt reachable. If robots.txt itself returns a server error, Google may stop crawling the whole site until it can read it again.
  3. Don't block crawling with a Disallow: / rule in robots.txt. That can get your pages removed from results.
  4. Keep it short. Google recommends against serving 503s for more than a day or two. For a longer closure, keep a normal, indexable home page up with a 200 status explaining the situation.
  5. Check afterwards that every page returns 200 again, then watch Google Search Console's Page indexing and Crawl stats reports for a few days.

Telling customers about planned maintenance ahead of time, on a status page, avoids the support tickets too.

Protecting SEO from unplanned outages

You can't schedule an outage, but you can make sure it stays short:

  • Monitor your site from outside. An external uptime monitor checks your site every minute and alerts you as soon as it fails, so you can fix it in minutes rather than finding out from a customer, or from Google days later. Search Console isn't a monitoring tool: see does Search Console alert you about downtime?
  • Watch your SSL certificate. An expired certificate makes browsers block your site, even though the server is up.
  • Use a CDN or caching so short origin problems don't reach visitors or crawlers.
  • Choose reliable hosting with redundancy and a clear uptime commitment.
  • Have a recovery plan, including who's on call and how to roll back a bad deployment.

If Search Console shows errors such as "Googlebot cannot access your site", see what that message means and how to fix it.

How Odown helps

Odown checks your websites and APIs every minute from 17 regions and alerts you by email, SMS, Slack, Discord and other channels the moment something fails. It also checks the SSL certificate of each monitored site daily and, from the Pro plan, gives you status pages with incident updates and scheduled maintenance notices. Plans start at $12 a month, with a free 14-day trial.

FAQ

Does a few minutes of downtime affect SEO?

No. Googlebot crawls most pages only every few days, so it probably won't even notice a short outage, and a single failed crawl doesn't change rankings.

How long can a website be down before it affects Google rankings?

Google starts dropping URLs that keep returning server errors after a day or two. Shorter outages mainly slow down crawling.

Will my rankings come back after an outage?

Usually, yes. Once the site returns normal responses, Google recrawls the pages and they generally return to the index in their previous positions. On a large site this can take days or weeks.

What status code should a maintenance page return?

503 Service Unavailable, ideally with a Retry-After header. Never 404, and avoid returning 200 with a "down for maintenance" message.