Google has reminded site owners that if they take a site offline to patch PHP, the 503 response should come from outside PHP, and robots.txt must stay reachable.
Key facts
- Effective: Applies now, during the current PHP patch window (reported by Search Engine Journal on Oct 21)
- Who is affected: Sites running on PHP that need downtime to patch, such as self-hosted WordPress / WooCommerce stores
- Do you need to act: If you plan downtime, set up the 503 response first. Sellers on hosted platforms like Shopify can leave it for now
What happened
According to Search Engine Journal, Google reminded sites that when they go offline to patch PHP, the 503 must be served from outside PHP (for example by the web server or CDN) and robots.txt should remain accessible. The report adds that days of server errors may cause URLs to be dropped. The reminder comes as a serious PHP core vulnerability was disclosed and patched; AIHOT relays that the NSA advised sites that cannot patch right away to go offline.
What this means for independent store owners
This mainly hits self-hosted stores, especially WordPress and WooCommerce. If you are about to take the site down for a PHP upgrade, do not let it throw a 500 or a blank page. When PHP is down, a 503 page generated by PHP goes down with it, so serve the 503 from Nginx, Apache or your CDN and let robots.txt through. Keep the window to hours, not days; per the report, it is multi-day server errors that put URLs at risk. Sellers on Shopify and other hosted platforms do not need to do anything, since the platform patches for them. One caveat: we only saw the report's summary, and we could not find an official number for how long is too long, so check Google's own documentation and watch crawl errors in Search Console before and after the downtime.