The Technical SEO Audit Checklist That Still Matters

Audit in the order that breaks things

Technical SEO problems compound. Work top down: can crawlers reach the page, can they index it, can they render it, is it fast, and is it the canonical version.

1. Crawlability

Check robots.txt for accidental blocks — staging rules that shipped to production are the classic failure. Confirm your sitemap contains only canonical, indexable, 200-status URLs, and reference it from robots.txt. Then crawl the site and look for redirect chains, internal 404s and parameter explosions from filters and sorting.

Add one modern check: are AI crawlers allowed? GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot and Google-Extended each control a distinct surface. Many sites block them by accident through a bot-management preset.

2. Indexation

Compare the pages you want indexed against Search Console's coverage report. Look for thin archives, tag pages and paginated duplicates consuming crawl budget. Noindex or consolidate rather than leaving them to compete.

3. Rendering

Disable JavaScript and view your most important page. If the copy, headings and links are gone, both answer engines and AI retrieval pipelines are seeing an empty shell. Server-render or pre-render the primary content.

4. Speed and Core Web Vitals

Target LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 on mobile field data, not lab scores. The usual wins: compress and correctly size images, preload the hero asset, defer third-party tags, and reserve space for anything that loads late.

5. Canonicalisation and duplication

One hostname, one protocol, one trailing-slash convention, all others 301'd. Self-referencing canonicals on unique pages, and consistent internal links to the canonical form.

6. Structured data and internationalisation

Validate Organization, WebSite and page-type schema. If you serve several languages or regions, map variants with reciprocal hreflang plus x-default — half-implemented hreflang is worse than none.

Prioritising what you find

Sort every issue by traffic at risk multiplied by effort. Blocked or non-indexable revenue pages are always first. Site-wide speed work is usually second. Schema, hreflang and housekeeping follow. A prioritised list of twelve fixes beats an exhaustive report of two hundred.