SiteFixPlan field guide
How to prioritize website audit findings
Rank work by user harm, business importance, confidence, effort, and dependency.
Create a prioritized auditScores are inputs, not the queue
A low automated score does not automatically identify the first business priority. Combine severity with the page’s role, affected audience, frequency, confidence in the evidence, and the cost or dependency of the fix.
Use a consistent decision model
Start with blockers and legal or security risks, then issues affecting high-value journeys, then improvements that increase clarity or resilience. Group related findings so one implementation can resolve several symptoms.
- Impact: what happens to users or the business?
- Reach: how many important journeys are affected?
- Confidence: is the evidence confirmed?
- Effort: what resources and dependencies are required?
- Verification: how will the team know it worked?
Keep the backlog alive
Assign owners and target windows. Retest closed items, record the evidence, and revisit priorities when traffic, products, regulations, or technology changes.
Common questions
Should easy fixes always go first?
Quick wins are useful, but do not let them displace high-impact blockers merely because the harder work takes longer.
How many priorities should a plan have?
Keep the active list small enough to execute; preserve the rest in a ranked backlog.