I need around a week to transition a heavily data-driven website from one back end to another. During that time I do plan to attempt to keep some pages live, but they won't all work well or look brilliant. Some pages won't work at all.

What is the best way to ensure I don't scare Google? Should I hide everything from robots.txt, or mark everything that doesn't work as "503", or are there other things that I should be considering?


1 Answer 1


503 everything is the best strategy I can think of, together with a retry after HTTP header.

Source: http://googlewebmastercentral.blogspot.co.il/2011/01/how-to-deal-with-planned-site-downtime.html

  • Great answer, thank you: great to see that Google have already thought of this one. I hadn't considered the "retry-after". Jun 1, 2014 at 18:23
  • Thanks. I would also consider a custom 503 error page. You don't want to scare off your visitors with the ugly default message. Analytics code on this page is also recommended. Jun 1, 2014 at 19:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.