Google On Taking Sites Down When Fixing The Emergency PHP Exploit - PHP2Shell

The World Wide Web is rushing now to fix and place its servers for the critical PHP exploit known as PHP2Shell. Most are capable to place these without downtime but many sites are going offline until the place is implemented, fair to be excellent safe. Google's John Mueller offered direction on how to grip Google Search if you decide to obtain downward your location during patching it for the PHP safety vulnerability.

If you are unaware of this PHP issue, in short, PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 now have a fix for two crucial vulnerabilities that can authorize unauthenticated distant code execution. So everyone is rushing to place things up asap before the evil group or bots commencement attacking. There is lots of safety of this summed up on Techmeme.

In fact, many sites are being taken offline, to be excellent cautious, until the PHP patches are in place. "Several government, academy and hospital websites in Europe were taken offline on Wednesday as organizations rushed to defend themselves from two crucial safety flaws in PHP, a programming tongue that powers a ample portion of the ​internet," Reuters reported.

If you are taking that approach, Google's John Mueller provided direction on how to obtain downward your site, so that it won't outcome in lengthy term ranking or indexing issues for your location in Google Search. John wrote on Bluesky, "If you're taking PHP sites downward to agenda period to agreement alongside "unplanned updates", use HTTP 503 alternatively of letting responses period out / 404 / 500. You can do this exterior of PHP / item DNS elsewhere / CDN."

Google has spoken concerning this before in akin cases but Google additionally has older records on this - current are links to those documents:

• How to agreement alongside planned location downtime
• Temporarily intermission or disable a website

Google has stated akin direction in 2021 alongside the Log4j safety vulnerability.

Here is several of our former safety of how Google Search handles sites being downward and what to do:

• Google SEO Tips On Taking A Site Offline To Fix Log4j Security Vulnerability
• Site Down Time Can Remove You From Google Index
• Google On How To Technically Pause Your Online Business
• Site Down Too Long? Your Google Rankings Will Suffer
• Site Down? How To Use A 503 Code To Save Your Google Rankings
• Google: Site Going Offline For Longer Than A Day; Upload A Static Version
• Google: Use 503 Status Code Only For Hours, Not Weeks
• Jewish High Holy Days Approaching: Google Shares Tips On How To Temporarily Close Your Site
• Google Official Tips On Closing A Site For Days (For Maybe Shabbat)

Here is John's post:

If you're taking PHP sites downward to agenda period to agreement alongside "unplanned updates", use HTTP 503 alternatively of letting responses period out / 404 / 500. You can do this exterior of PHP / item DNS elsewhere / CDN. developers.google.com/search/blog/... developers.google.com/search/docs/...

[image or embed]

— John Mueller (@johnmu.com) October 21, 2026 at 11:26 AM

Forum conversation at Bluesky.