Technical SEO · 11 minute read
Technical SEO Audit Checklist
A useful audit joins crawler evidence to rendered pages, search data and business priority. The output is a sequence an engineer can verify, not a spreadsheet of warnings.
Updated 13 August 20261 July–22 August 2026 · anonymised Search Console evidence
- Total clicks
- 5,500
- Total impressions
- 47,816
- Average CTR
- 11.5%
- Average position
- 18.8
The short answer
Turn Warnings Into Release Priorities
A useful audit joins crawler evidence to rendered pages, search data and business priority. The output is a sequence an engineer can verify, not a spreadsheet of warnings.
1. Confirm what should be indexable
Start with the intended page inventory. Compare the XML sitemap, internal crawl, analytics landing pages and Search Console pages. A crawler only shows what it can reach from its starting rules; it does not tell you whether a missing page matters.
Check status codes, robots directives, canonicals and authentication boundaries. Private account, portal and enquiry-completion routes should not enter the public index.
- 200, redirect, 404 and 5xx coverage
- robots.txt and meta robots
- XML sitemap membership
- Self-canonical and duplicate handling
2. Inspect rendered templates
Modern sites can send different content before and after JavaScript runs. Inspect the rendered heading, links, canonical and structured data on each important template. Confirm there is one primary content landmark and a logical heading sequence.
Group findings by template. Fixing one component can repair hundreds of URLs, while editing examples one by one hides the actual cause.
- Rendered titles and main content
- Mobile navigation and internal links
- Pagination and filtered routes
- Structured data matching visible content
3. Trace internal authority
Every commercial page needs a clear route from the site architecture and relevant contextual links. Find orphan pages, excessively deep paths and clusters that compete for the same intent.
Anchor text should explain the destination naturally. Sitewide exact-match repetition is not a substitute for an understandable hierarchy.
- Click depth
- Orphan and dead-end pages
- Competing titles and queries
- Broken links and redirect chains
4. Measure experience and delivery
Use field Core Web Vitals to understand whether real visits are affected and lab traces to diagnose the mechanism. Check LCP resource discovery, interaction delays and layout geometry rather than installing generic fixes.
Finish with owners, acceptance checks and dates. A finding is not complete until production has been recrawled and the expected response, canonical or rendered element is present.
- LCP, INP and CLS by device
- Server and asset request paths
- Priority, effort and affected templates
- Production verification
Decision rule
Turn Warnings Into Release Priorities
Start with indexation and template faults that affect valuable pages, then verify each fix on production.
Discuss a technical SEO audit