Technical SEO Audit Guide
A start-to-finish workflow for discovering, prioritizing, and validating technical search issues.
1Define scope and business goals
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.
2Collect URLs from crawls and sitemaps
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.
3Inspect status, redirects, and indexability
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 metadata and internal links
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.
5Prioritize by template and impact
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.
6Verify fixes and monitor critical URLs
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.