502s are common with reverse proxies, load balancers and CDNs (like Nginx or Cloudflare) when the backend application is down, overloaded or returning garbage. They're often transient but can also signal a real backend outage.
For SEO the risk mirrors 500: if Googlebot repeatedly gets 502s, it can't fetch pages, and sustained errors can reduce crawling and temporarily affect indexing. A brief blip is usually harmless.
Diagnose the backend and the proxy configuration — application crashes, timeouts between proxy and origin, or restarts. Recurrent 502s and 503s together point to capacity or stability problems worth escalating.
This is a technical SEO topic I handle for clients:
Technical SEO →
