Deciding which response failures need repair first
Prioritize response failures by verified user impact and intended page behavior. An audit count alone does not distinguish a broken contact page from a deliberately retired URL.
Group the evidence by purpose
For each finding, record whether the route should exist, where visitors encounter it and whether a relevant replacement is available. Separate current public service pages, critical navigation destinations, assets and retired paths. Keep intermittent failures distinct from consistently missing resources. Avoid adding estimated lost revenue when no measurement supports it.
Repair and verify in an explicit order
Address failures that prevent intended public use, then correct their discovery references and repeat the original requests. Document intentional missing pages so the same scanner warning is not repeatedly treated as a new defect. Keep a small before-and-after record for each change. Once the response behavior is correct, evaluate provider indexing and business outcomes as separate follow-up questions.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Does every non-200 response need a fix?
No. Redirects and missing-resource responses can be intentional. The question is whether the observed response matches the purpose of the requested URL.