Website Health Audit Guide
Combine availability, routing, crawl, security, and performance signals into a repeatable review.
1Build a representative URL inventory
Start by recording the intended outcome and the evidence available today. Work from representative URLs before expanding the scope, and keep the same settings for the verification run.
Review status, redirects, final destinations, timing, and supporting signals together. Group repeated findings by template or root cause so the implementation fixes the system rather than one URL at a time.
2Establish an HTTP and redirect baseline
Start by recording the intended outcome and the evidence available today. Work from representative URLs before expanding the scope, and keep the same settings for the verification run.
Review status, redirects, final destinations, timing, and supporting signals together. Group repeated findings by template or root cause so the implementation fixes the system rather than one URL at a time.
3Check DNS, SSL, and trust signals
Start by recording the intended outcome and the evidence available today. Work from representative URLs before expanding the scope, and keep the same settings for the verification run.
Review status, redirects, final destinations, timing, and supporting signals together. Group repeated findings by template or root cause so the implementation fixes the system rather than one URL at a time.
4Review slow and unstable destinations
Start by recording the intended outcome and the evidence available today. Work from representative URLs before expanding the scope, and keep the same settings for the verification run.
Review status, redirects, final destinations, timing, and supporting signals together. Group repeated findings by template or root cause so the implementation fixes the system rather than one URL at a time.
5Create an accountable repair plan
Start by recording the intended outcome and the evidence available today. Work from representative URLs before expanding the scope, and keep the same settings for the verification run.
Review status, redirects, final destinations, timing, and supporting signals together. Group repeated findings by template or root cause so the implementation fixes the system rather than one URL at a time.
6Save a baseline and schedule follow-up
Start by recording the intended outcome and the evidence available today. Work from representative URLs before expanding the scope, and keep the same settings for the verification run.
Review status, redirects, final destinations, timing, and supporting signals together. Group repeated findings by template or root cause so the implementation fixes the system rather than one URL at a time.