A 4xx by mistake: Google protects VLC's home page, not yours
Published
VLC's website sent Google an error code instead of its home page. Google kept the page in its index for a while, because it is one of the most important pages on the web. Your pages will most likely not get that treatment.
What happened
SEOs noticed that VLC's site had lost its favicon in Google results, and that its home page now ranked below its download page. Gary Illyes, from Google, explained on LinkedIn that the site had served the HTTP status 418 ("I'm a teapot"), which Google treats like most 4xx errors: as "not found".
Because VLC's home page is one of the most important pages on the internet, Search temporarily protected it from being dropped from the index. But with nothing left to read, Google had "nothing left to show: no snippet, no favicon, no nothing", only the link and the last good title. The site answers normally again, and Google expects things to sort themselves out.
The problem
The protection is reserved for a handful of pages Google deems essential, and it lasts "a short while". Google does not say how long, nor how a page qualifies. For everyone else, a 4xx is read as "this page is gone", and the page heads out of the index.
Such errors are often sent by mistake: a firewall or bot-protection rule that blocks Googlebot, a maintenance mode that answers 403 or 404, a deployment that breaks a route, a CDN rule. Visitors often still see the page, so nobody notices. Google documents the difference: 5xx errors and 429 are read as temporary and slow crawling down, while 4xx errors mean the content is gone.
The impact
The snippet and the favicon go first, and with them part of your click-through rate: a bare blue link next to full results gets fewer clicks. Then the page drops out of the index, and coming back takes a new crawl, which can take days or weeks for less-visited pages.
On a home page or a key product page, that is the brand query and the most commercial traffic that go missing, and AI assistants that rely on search indexes lose track of the page too.
Who should check: sites behind a firewall or bot protection, sites that use a maintenance page, and any site that has had a sudden drop with no change in content.