Why Google Insists on 503 Errors During PHP Patch Downtime—And What It Means for Your Site

Ever taken a server offline for a quick PHP patch and wondered, “How on earth will Google react to this little hiccup?” Well, it turns out there’s a pro-level move that many miss: serving a 503 status code to signal that your site’s downtime is just a brief intermission—not a full curtain close. Google Search Central just dropped a timely reminder about this, especially pertinent as PHP rushed out emergency fixes for some nasty security flaws that could let hackers run amok without signing in. The catch? Google doesn’t want to see a 503 linger beyond a day or two, or it might start treating your URLs like last season’s hits—dropping them from the index. So, what’s the smartest way to keep your SEO mojo intact when the PHP gods call for downtime? Spoiler: it’s all about the status code dance and keeping your crawl game sharp even when things temporarily break. Curious how this all shakes out and what the experts recommend? Dive into the full scoop. LEARN MORE

Google Search Central is reminding anyone who takes servers offline for PHP patches to return a 503 status code, which tells Google the outage is temporary.

The LinkedIn post went up Wednesday, the day PHP released emergency fixes for two critical flaws that can let attackers run code without logging in.

The post doesn’t say how long a 503 can stay up. Google’s crawl rate documentation recommends against serving one for more than one to two days, because URLs that return it for multiple days may be dropped from the index.

What Google And Mueller Said

Google Search Central wrote:

“Serving a 503 (Service Unavailable) HTTP status code ensures already indexed URLs are preserved in Search while you work. Once you start serving 200 responses again, things naturally return to normal.”

The post also warned against generic 404s or 200 error pages during the downtime. It linked to Google’s page on how HTTP status codes affect its crawlers.

In a 2013 post, Google’s John Mueller wrote that returning an error page with a 200 OK status code causes Google to index that error content.

Mueller posted his own reminder on Bluesky earlier Wednesday and said where the 503 can come from:

“If you’re taking PHP sites down to schedule time to deal with “unplanned updates”, use HTTP 503 instead of letting responses time out / 404 / 500. You can do this outside of PHP / point DNS elsewhere / CDN.”

The 2011 Google post he linked shows how to send a 503 with PHP code, which won’t help when PHP is what’s coming down.

In a reply, a Bluesky user ranked the responses roughly, from best to worst, as 503, 500, 403, 404 and 200. Mueller called it “a good model.”

How 503s Affect Crawling

Google’s crawl rate documentation lists 500, 503, and 429 responses as the way to urgently reduce crawler traffic for a short period. When Google’s crawlers hit a large number of URLs returning those status codes, they reduce the crawl rate across the entire hostname, including URLs that still return content. Once the number of errors drops, Google automatically increases the crawl rate again.

When returning a 503 or 429, you can add a Retry-After HTTP header that tells Google’s crawlers when to try again, either as a number of seconds or as a date and time in UTC.

Google’s crawl rate page also warns that slower crawling means Googlebot discovers fewer new pages and refreshes existing ones less often. Google Ads campaigns may be canceled or paused.

When I covered comments from Google’s Gary Illyes in 2024, he said a 503 lasting 10-15 minutes every now and then “is not ‘extended’ by any means, so you should be fine.”

How Long Google Recommends Serving A 503

Google’s crawl rate page warns:

“We don’t recommend that you do this for a long period of time (meaning, longer than 1-2 days) as it may have a negative effect on how your site appears in Google products. For example, in the case of Search, if Googlebot observes these status codes on the same URL for multiple days, the URL may be dropped from Google’s index.”

Google’s status codes page, the one the LinkedIn post linked to, says already indexed URLs that return server errors are “preserved in the index, but eventually dropped.”

Google’s guide to pausing a website calls disabling a whole site an extreme measure that should only last a very short time, a few days at most.

The guide also says not to return a 503 for the robots.txt file, because that blocks all crawling. It adds that Google’s systems can’t refresh titles, descriptions, metadata, or structured data on a page that returns a 503.

Why This Matters

The 503 has to come from something that keeps running while PHP is offline, such as a CDN rule or a temporary server you’ve pointed DNS at. Your robots.txt file should keep responding normally so Google can still crawl the site. The 503 is a short-term measure, since Google’s documentation recommends against serving one for longer than one to two days.

Looking Ahead

Sites on PHP 8.1 or older no longer get regular official updates. PHP has published limited source fixes for versions 7.4 through 8.1 for teams that build PHP themselves, and hosts or support vendors may supply their own, as Vahan Petrosyan reported for SEJ. For a closure that runs past a day or two, Google’s pause guide points to an indexable home page served with a 200 as a placeholder. Once the site returns 200s again, Google’s status codes page says crawling picks back up gradually.

Featured Image: Tetiana Yurchenko/Shutterstock