Taking your site offline to patch PHP? Google wants the downtime handled the right way. On October 21, Google Search Central posted a reminder on LinkedIn telling site owners who take servers offline for emergency PHP patches to return a 503 status code. A 503 tells search engines the outage is temporary, so pages already in Search stay put while you work.
The reminder went up the same day PHP released emergency fixes for two critical flaws. Both vulnerabilities allow an unauthenticated attacker to execute arbitrary code on the server, and the PHP team recommends updating as the only safe solution, with no workaround able to fully address the problem. Fixed versions shipped on four branches: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Security advisories told organisations to consider isolating or taking unpatched systems offline, which is why so many site owners were suddenly facing planned downtime at once.
Google's post landed a few hours after the fixes shipped, at about 17:40 UTC on October 21. It was short and direct: a friendly reminder for everyone running emergency PHP patches or taking servers offline, not to forget the 503. The post linked to Google's documentation page on how HTTP status codes affect Google's crawlers, which carries a last-updated date of February 4, 2026, so the guidance itself is long-standing. What was new was the timing.
Serving a 503, which means Service Unavailable, ensures already indexed URLs are preserved in Search while you work, according to the post. Once you start serving 200 responses again, things naturally return to normal. The post also warned against two common shortcuts during maintenance: generic 404 pages, and error pages served with a 200 status code. A 404 tells Google the page is gone, and a 200 on an error page tells Google the error page is the content. Both can cost a site its indexed pages.
John Mueller of Google added a reminder of his own on Bluesky earlier the same day, recommending that people who take PHP sites offline for unplanned updates use a 503. His post linked to a 2011 Google post about planned downtime, which gives instructions for sending a 503 using PHP code. That old advice is still the foundation of the current guidance, even though the practical details have changed since then.
There is a practical problem with the advice, and Mueller flagged it himself. If PHP is the component being taken offline, a 503 written in PHP code will not execute, because PHP itself is down. The 503 has to come from something that stays up while PHP is down, such as a CDN routing rule or a temporary server that DNS points to. That is the detail most likely to catch a site owner in the middle of an emergency patch.
The other detail is robots.txt. According to Google's guide to pausing a site, if a 503 is served in response to robots.txt requests, all crawling is blocked. A site that takes its entire server offline will return errors for its robots.txt file as well, so the file needs to keep answering normally while the rest of the site is down. Getting the 503 right on pages but wrong on robots.txt can stop Googlebot from crawling anything at all.
A 503 is a short-term tool, not a parking space. Google's crawl-rate documentation advises against serving 503 status codes for longer than 1 to 2 days, and warns that if Googlebot sees a 503 on a URL for multiple days, the URL may be dropped from the index. The protection the 503 offers only lasts while the outage stays brief. For a longer closure, Google suggests an indexable home page returning a 200 instead.
Sites running PHP 8.1 or older face a related problem: those versions no longer receive regular official updates, so the emergency fixes do not cover them in the usual way. The PHP team has published limited source fixes for versions 7.4 through 8.1, but site owners on old versions should check with their host or developer about what is available. Patch promptly, keep the outage short, and let the 503 do its job for a day or two at most.
Emergency downtime is when technical SEO earns its keep or loses it. A site that serves 404s or 200 error pages during a patch can watch indexed pages disappear from Search, and with them the rankings that took months of link building to earn. A correctly served 503 costs nothing and preserves the work, but only if it is set up before the server goes dark, from infrastructure that stays up.
The lesson for SEOs is to have the plan written down before the emergency arrives. Know who controls the CDN rules, know how DNS can point to a temporary server, and know that robots.txt must keep answering. Link builders should care for the same reason: every link pointing at a page that drops from the index loses its value until the page returns. A one-day patch handled with a 503 is a non-event. The same patch handled with a 404 can undo months of work.
Sources: Search Engine Journal, October 24, 2026.
Related reading on this site: Google Explains How Redirects Affect Ranking Signals, Google: Technical SEO Remains Key for AI SEO, November Search Console Click Spikes Are Bot Traffic, Google Rank Data Issues, Lighthouse Update and AI Opt-Out, SEO Split Testing in 2027: How to Prove a Change Actually Worked, and Google Loses Again to SerpApi in Scraping Case.
Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.
Start free trial