5xx errors indicate a server-side failure and can cause Google to slow crawling. Persistent failures may eventually affect previously indexed URLs. Investigate which addresses fail, for how long and whether the response originates in the application, hosting platform or CDN; do not estimate ranking losses from a single error.
Read the status alongside the user impact
Google's HTTP-status guidance explains that 5xx responses can temporarily slow crawling and that persistent server errors can affect indexed URLs. Do not infer their duration or scope from one screenshot. The immediate objective is reliable delivery of the correct content.
Determine whether the problem affects the homepage, a product group or a particular filter action. Are enquiries or payment steps involved? Include the task the customer cannot complete alongside the technical code. That makes the business priority of the correction easier to assess.
Create one evidence set for the incident
Record the exact URL, explicit time zone, HTTP status, response headers and attempted action. Correlate application errors, resource use and CDN events for the same period. A screen displaying 502 does not identify where the original failure occurred.
A cached homepage loading does not establish that the whole site is healthy. Test uncached product pages, logged-out access and form submission separately. Have the authorised technical team compare CDN and origin responses, recording conditions that reproduce the problem.
| Evidence | Purpose | Question |
|---|---|---|
| Full URL and page type | Identify the affected group | Is one template involved? |
| Time and duration | Connect incident records | Does it coincide with a release or load? |
| Response source | Locate the layer | Does the application or an intermediary produce it? |
| User action | Understand business impact | Is reading or completing an enquiry blocked? |
| Repeat check | Assess persistence | Is the problem continuing? |
Resolve the cause rather than hiding the symptom
Application logs for a 500, or the proxy-to-application connection for a 502 or 504, can be starting points; the status alone is not a root-cause diagnosis. Serving maintenance text with 200 does not establish recovery. Preserve appropriate status semantics and a useful alternative route.
Verify timeout, database or external-service corrections with a reproducible scenario. Do not apply arbitrary 403 responses to throttle crawlers; Google treats 429 as an overload signal. Report temporary recovery and permanent correction separately and assign recurrence alerts to a named owner.
Check normal and previously failing conditions
Repeat the same URL and action after the correction. Include unaffected examples to assess whether another area regressed. Successful content delivery and later changes in search reporting may become visible at different times.
Track error frequency, access to the affected pages and outcomes of critical actions together. Distinguish a past interruption from an ongoing failure. Assign an incident owner and a notification route so a future availability problem does not remain unnoticed.