Technical SEO
How to run a technical SEO audit that earns measurable clicks
Most site audits fail because they dump 400 low-impact warnings on pages with zero search demand. This guide walks through joining crawl diagnostics with Search Console traffic so you fix revenue-bearing pages first.
- Author
- Eleanor Vance, Principal Technical SEO
- Reviewed by
- Marcus Reid, Staff Search Engineer
- Last reviewed
1. Separate crawlability, indexability, and canonicalisation
Robots.txt controls crawler fetching, not indexing. A URL blocked in robots.txt can still appear in Google results if internal or external links point to it. Use explicit meta robots noindex or X-Robots-Tag headers when a page must stay out of search results.
Check that every indexable 200 OK URL declares a self-referencing rel="canonical" matching the exact protocol and trailing-slash convention listed in your XML sitemap.
2. Weight technical issues by measured Search Console impressions
Export or connect 90 days of Google Search Console page metrics before prioritising fixes. A broken canonical or accidental noindex on a page earning 2,000 monthly impressions outranks 50 missing alt attributes on archived press releases.
After deploying a fix, immediately re-fetch the target URL to confirm HTTP headers and rendered HTML before waiting 14–28 days to measure seasonality-adjusted click recovery.