How to Conduct a Technical SEO Site Audit
A technical SEO site audit is a structured review of crawlability, indexability, rendering, performance, and site health to find issues that can stop search engines from properly accessing or understanding a website.
Start here
- Start with Search Console Coverage and a crawl — those two give you 80% of the picture.
- Scope your audit before you start: full site, sample, or specific area.
- Prioritize fixes by impact and effort, not by error count.
- Validate every crawler finding in Search Console to avoid chasing ghosts.
- Document affected URLs, recommended actions, and estimated fix time for each issue.
What I'd do first
- Open Google Search Console and check the Coverage report for critical errors like 404s, server errors, or pages blocked by robots.txt.
- Run a crawl with Screaming Frog or Sitebulb to catch broken links, redirect chains, and duplicate titles.
- Test a handful of important pages with URL Inspection in Search Console to confirm they're indexed and see the rendered version.
- Check Core Web Vitals in Search Console's Core Web Vitals report and PageSpeed Insights for mobile and desktop.
- Review your robots.txt and XML sitemap to ensure nothing important is accidentally blocked or missing.
Plain-English take
A technical SEO audit is basically a health check for your site's relationship with Google. You're looking for things that might stop Googlebot from crawling your pages, understanding what they're about, or deciding to show them in search results. It's not about content or links — it's about the plumbing. If the pipes are clogged, the water doesn't flow. The goal is to find those clogs and fix the ones that matter most first.
When it actually matters
- You're launching a new site or redesign — catch issues before they tank your rankings.
- Traffic dropped suddenly — a technical issue might be the culprit.
- You've never done one before — there's almost always low-hanging fruit.
- After a migration or CMS change — redirects, canonicals, and sitemaps often break.
- Quarterly maintenance — even stable sites accumulate issues over time.
What I got wrong
- I used to crawl the whole site without setting a scope first, which wasted time on irrelevant pages like staging or admin areas.
- I treated every crawler warning as equally urgent — now I prioritize by actual impact on indexing or traffic.
- I only checked the HTML source and missed JavaScript rendering issues, headers, or X-Robots-Tag directives.
- I'd find issues in the crawler but never validate them in Search Console, leading to false positives and wasted effort.
Next step
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Primary source for indexing, crawling, sitemaps, robots rules, and Search Console guidance.
- Google Search Console Help — Official documentation for Coverage/Pages, URL Inspection, sitemaps, and manual actions.
- Moz SEO Audit Checklist — Widely used practitioner checklist with pass/fail workflow and audit documentation conventions.
- Ahrefs Technical SEO Audit — Practical walkthrough of crawl-first auditing and GSC-based validation.
Notes from Callum Bennett.