body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Help Center

Conversation

Glenn Gabe

@glenngabe

Have a planned site outage for a week or longer & using a 503 status code? Via

@johnmu

: A day or so is fine, but a few days or longer could cause issues. Google will start dropping urls from the index (and maybe a lot of those urls): youtube.com/watch?v=GR-A6k

GIF

5:47 PM · Dec 15, 2021

Replying to

More: When the urls come back, G will try & crawl/index them again. They might come back to their original ranking, but it's not guaranteed. Avoid using 503s for an extended period of time. You can even set up a static version of the site in the short-term youtube.com/watch?v=GR-A6k

GIF