Key takeaways
- Audit in layers: crawl → index → understand → perform → enhance.
- Fix template-level issues first; one fix can resolve thousands of URLs.
- Compare what you want indexed (your sitemap) with what is indexed (Search Console).
- Turn findings into a prioritised backlog with owners — a report nobody acts on is wasted.
Technical SEO ensures that search engines and AI crawlers can access, render, understand and trust your website. Even outstanding content underperforms if technical issues get in the way. This checklist is the condensed version of the audit we deliver as our Technical SEO Audit service.
Before you start: tools and data
- Google Search Console and Bing Webmaster Tools access (verified properties).
- A crawler configured to render JavaScript if your site depends on it.
- PageSpeed Insights / Lighthouse and Chrome DevTools.
- Schema validator and Google’s Rich Results Test.
- Server or CDN access logs, if available, for crawl behaviour.
- Analytics to connect technical issues with traffic and revenue.
Part 1: Crawlability (points 1–9)
- robots.txt exists, returns 200 and does not block important sections, CSS or JavaScript.
- XML sitemaps are referenced in robots.txt and submitted in Search Console and Bing Webmaster Tools.
- Sitemaps contain only indexable, canonical URLs returning 200.
- No important pages return 4xx or 5xx errors.
- Redirect chains and loops are eliminated; internal links point directly to final URLs.
- No orphan pages — every important URL is linked internally.
- Crawl depth: key pages are reachable within three or four clicks from the homepage.
- Faceted navigation, internal search and URL parameters do not create endless crawlable URL variations.
- Server response times are stable; no crawl rate problems reported in Search Console crawl stats.
Part 2: Indexing (points 10–17)
- Compare sitemap URLs with the Page indexing report; investigate “Crawled – currently not indexed” and “Discovered – currently not indexed”.
- Every page has a self-referencing or correct canonical tag.
- noindex is used intentionally (thank-you pages, internal search, cart) and not on important pages.
- HTTP/HTTPS and www/non-www versions redirect to one preferred version.
- Trailing slash and letter case are consistent.
- Duplicate and near-duplicate content (tags, archives, printer versions) is consolidated or noindexed.
- Thin pages are improved, merged or removed.
- Pagination is crawlable with normal links; important items are not only reachable through infinite scroll.
Part 3: Architecture and internal links (points 18–22)
- Logical hierarchy reflected in navigation, breadcrumbs and URLs.
- Hub and category pages link to their most important children.
- Descriptive anchor text; no generic “click here” for important links.
- Broken internal links fixed.
- Topic clusters wired correctly (see our content cluster guide).
Part 4: Rendering and on-page signals (points 23–28)
- Main content, headings and links are present in the rendered HTML (check with URL Inspection’s rendered view).
- One descriptive H1 per page and a logical heading hierarchy.
- Unique title tags and meta descriptions on indexable pages.
- Images have alt text, sensible file names and dimensions.
- Language declared in the HTML (
langattribute). - No important content hidden behind interactions that crawlers cannot trigger.
Part 5: Performance and mobile (points 29–33)
- Core Web Vitals field data passes for main templates (LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1). See our Core Web Vitals playbook.
- Images are responsive, compressed and in modern formats.
- Render-blocking CSS/JS minimised; third-party scripts audited.
- Mobile layout: readable text, adequate tap targets, no horizontal scrolling.
- Content parity between mobile and desktop (Google indexes mobile-first).
Part 6: Structured data (points 34–36)
- Organization and WebSite markup on the homepage; BreadcrumbList site-wide.
- Article, Product, LocalBusiness, Event or other types where content genuinely fits.
- No errors in validators; markup matches visible content.
Part 7: Security, international and AI (points 37–40)
- HTTPS everywhere with valid certificates; no mixed content; no security issues in Search Console.
- hreflang implemented correctly for multilingual or multi-regional sites (reciprocal, valid codes, canonical-consistent).
- AI crawler access reviewed in robots.txt according to your business decision; optional
llms.txtpublished. Learn more in our GEO guide. - Fast discovery: IndexNow or equivalent for participating search engines; sitemaps update automatically.
Prioritising your findings
| Priority | Criteria | Examples |
|---|---|---|
| Critical | Blocks crawling or indexing of important pages | robots.txt disallowing a section, noindex on templates, server errors |
| High | Affects many URLs or key revenue pages | Canonical errors on product pages, poor LCP on article template |
| Medium | Limits performance or understanding | Redirect chains, missing schema, weak internal linking |
| Low | Polish and best practice | Image file names, minor meta duplicates |
Turning the audit into action
- Group issues by template or system, not by individual URL.
- Estimate impact and effort for each group.
- Create tickets with clear acceptance criteria and owners.
- Fix, deploy and validate in Search Console.
- Re-crawl after 4–6 weeks and compare with the baseline.
Conclusion
A technical audit is a health check for your organic channel. Work through the 40 points, prioritise ruthlessly and track the impact. If you plan a redesign or domain move, read our website migration guide before you start. Prefer an expert review? Our Technical SEO Audit is delivered in 10 business days with a walkthrough call.