Dear webmasters, if something goes drastically wrong with your hoster, and you can’t host your website anymore, please return a “503 Service unavailable” HTTP result code. Doing so helps search engines to understand what’s up – they’re generally more than happy to give your site some time to catch up again.

Returning an error page with “200 OK” will result in us indexing the change of content like that (and if all of your pages return the same error page, then we may assume that these URLs are duplicates). Redirecting to a temporary page will result in that redirect being used for indexing. It’s fine to show text to users on a 503 error page, or use fancy JavaScript, etc.

A simple way to handle that - if the webserver is down - is to change the site’s DNS to point to a temporary server that returns the 503 for you.

Once the issue is resolved, we’ll generally jump back in and crawl your site to get the indexed information updated. If you weren’t able to return a 503, it’ll probably take a bit of time for things to settle back down with regards to search, but it’ll come back, don’t worry. If you need to ramp crawling up slowly, you might also want to adjust the maximal crawl rate in Webmaster Tools (we pick up that setting about once a day).

At any rate, if your site was affected by issues like these, I hope you’re able to resolve them (and the other, perhaps more important issues that often go along with disruptions like these) as soon as possible. If there’s something Google can do with regards to web-search to help get your site get back on its feet, feel free to post here, in our forums, or join our office-hours hangouts.

OriginalĀ https://plus.google.com/+JohnMueller/posts/QsTebva3T7v (archive.org)

Comments / questions

There's currently no commenting functionality here. If you'd like to comment, please use Twitter and @me there. Thanks!

Tweet about this - and/or - search for latest comments / top comments

Related pages