Technical SEO Audit: The 80-Point Checklist Used by Top Agencies

A technical SEO audit without a systematic checklist is a gut-feel exercise. You’ll catch obvious problems, miss the ones that actually cost you rankings, and deliver recommendations you cannot prioritize or defend. After running technical SEO audit processes across thousands of client sites — from SMBs to enterprise — this is the 80-point technical SEO audit checklist we actually use.

Everything here is actionable. Every item maps to a specific tool, command, or check. Priority levels (Critical / High / Medium) tell you what to fix first. Work through this systematically and you’ll have a complete technical health picture of any site.

Crawlability and Indexation (20 Points)

Robots.txt (5 Points)

1. [Critical] Robots.txt accessible at domain.com/robots.txt
2. [Critical] No critical pages or directories incorrectly disallowed
3. [High] XML sitemap URL(s) declared in robots.txt
4. [High] No conflicting directives for the same paths
5. [Medium] Wildcard patterns used correctly (no regex errors)

XML Sitemap (5 Points)

6. [Critical] XML sitemap submitted to Google Search Console and Bing Webmaster Tools
7. [Critical] Sitemap contains only canonical, indexable URLs (no redirects, no noindex pages)
8. [High] Sitemap <lastmod> dates are accurate and dynamic (update on content change)
9. [High] Sitemap image and video extensions implemented where applicable
10. [Medium] Sitemap file size under 50MB, items under 50,000 (split if needed)

Crawl Budget and Indexation (5 Points)

11. [Critical] No critical pages returning noindex tag or header
12. [Critical] Correct pages in index (Google Search Console Coverage report — no unexpected excluded/indexed URLs)
13. [High] Infinite crawl traps eliminated (faceted navigation, session IDs, calendar archives)
14. [High] Pagination implemented correctly (no orphaned page-2+ URLs without internal links)
15. [Medium] Internal search result pages noindexed or excluded via robots.txt

Canonicalization (5 Points)

16. [Critical] Canonical tag present on all pages pointing to preferred URL version
17. [Critical] www vs. non-www resolved — one version returns 301 to the other
18. [Critical] HTTP to HTTPS redirect in place; no mixed content on canonical HTTPS pages
19. [High] Trailing slash consistency enforced across the site
20. [High] Parameter handling configured in GSC for URL parameters that do not change content

Technical Infrastructure (15 Points)

HTTPS and Security (4 Points)

21. [Critical] SSL certificate valid, not expired, covers all subdomains
22. [Critical] No mixed content errors (HTTP resources on HTTPS pages)
23. [High] HSTS header implemented
24. [Medium] Security headers present (X-Content-Type-Options, X-Frame-Options, CSP)

Server Configuration (4 Points)

25. [Critical] Server response time under 200ms for TTFB (first byte)
26. [High] GZip/Brotli compression enabled on HTML, CSS, JS, SVG
27. [High] Browser caching implemented for static assets (long cache TTLs)
28. [Medium] CDN in place for global audience delivery

Redirect Chains and Errors (4 Points)

29. [Critical] No redirect chains longer than one hop (A→B→C should be A→C)
30. [Critical] 404 error pages returning correct 404/410 HTTP status (not 200 “soft 404”)
31. [High] Custom 404 page with navigation to help users find content
32. [High] All 301 redirects reviewed — no outdated redirects pointing to pages that have moved again

URL Structure (3 Points)

33. [High] URLs are clean, readable, keyword-relevant — no session IDs or dynamic parameters in canonical URLs
34. [High] URL depth shallow enough that important pages are within 3 clicks from homepage
35. [Medium] Hyphens used as word separators (not underscores)

Core Web Vitals and Page Speed (15 Points)

Core Web Vitals are a confirmed Google ranking factor. Our technical SEO audit service consistently finds these as the highest-impact performance improvements for competitive SERPs.

LCP — Largest Contentful Paint (4 Points)

36. [Critical] LCP under 2.5 seconds on mobile (measured with field data in CrUX, not just lab data)
37. [Critical] LCP element is a preloaded image or fast-rendering text (not a background-image)
38. [High] Hero images served in modern formats (WebP/AVIF) with appropriate sizing
39. [High] LCP resource has fetchpriority="high" attribute

INP — Interaction to Next Paint (4 Points)

40. [Critical] INP under 200ms (replaced FID as Core Web Vital in 2024)
41. [High] Long tasks in main thread identified and broken up
42. [High] Third-party scripts (chat, analytics, ads) not blocking interaction
43. [Medium] Input handlers using passive event listeners where appropriate

CLS — Cumulative Layout Shift (4 Points)

44. [Critical] CLS score under 0.1 on mobile
45. [Critical] All images and embeds have explicit width/height attributes set
46. [High] Ads, cookie banners, and dynamic insertions not causing layout shifts
47. [Medium] Web fonts loaded with font-display: swap and preconnect for font origins

General Performance (3 Points)

48. [High] JavaScript rendering not required for critical above-the-fold content
49. [High] Render-blocking CSS and JS eliminated or deferred
50. [Medium] Total page weight under 3MB for typical page (lower for mobile)

On-Page Technical Elements (10 Points)

Title Tags and Meta Descriptions (3 Points)

51. [Critical] Every page has a unique title tag (50-60 characters) — check for duplicates in GSC
52. [High] Meta descriptions unique per page (150-160 characters) — not duplicate or missing
53. [High] No title/description truncation issues — verify with SERP simulator

Heading Structure (3 Points)

54. [High] Single H1 per page matching the primary content topic
55. [High] H2-H6 hierarchy logical — no jumping from H2 to H4
56. [Medium] Headings contain semantic keyword variations (not identical to title tag)

Image Optimization (4 Points)

57. [High] All images have descriptive alt text (not keyword-stuffed, not empty on informational images)
58. [High] Images served via responsive srcset for different screen sizes
59. [High] Lazy loading implemented for below-the-fold images (loading=”lazy”)
60. [Medium] Image file names are descriptive (not IMG_4521.jpg)

Structured Data / Schema Markup (10 Points)

61. [Critical] Organization or LocalBusiness schema on homepage with sameAs properties
62. [Critical] BreadcrumbList schema on all inner pages
63. [High] Article/BlogPosting schema with author Person schema on all content pages
64. [High] FAQPage schema on key informational pages
65. [High] Product + Offer + AggregateRating schema on e-commerce product pages
66. [High] VideoObject schema on all pages with embedded video
67. [High] No schema validation errors in Google’s Rich Results Test
68. [Medium] LocalBusiness schema for each location on multi-location sites
69. [Medium] WebSite schema with potentialAction (Sitelinks Search Box)
70. [Medium] Schema properties match visible page content (no hidden or misleading schema claims)

Internal Linking Architecture (5 Points)

71. [Critical] No orphaned pages (pages with zero internal links pointing to them)
72. [High] Pillar pages receive disproportionately high internal link equity
73. [High] Anchor text descriptive and keyword-relevant (not “click here”)
74. [High] No broken internal links (crawl with Screaming Frog or Ahrefs)
75. [Medium] Internal link depth — important pages within 3 clicks of homepage

International and Multi-Language SEO (5 Points)

76. [Critical] Hreflang tags implemented correctly for multi-language/multi-region sites
77. [Critical] Hreflang self-referencing canonical consistent with canonical tags
78. [High] Return tags implemented — every hreflang points back to every other language version
79. [High] x-default tag present for the fallback page
80. [Medium] Language/region alternate pages are indexed and accessible (not blocked by robots.txt)

Mobile and Accessibility (5 Points)

81. [Critical] Mobile-friendly test passes (Google’s Mobile-Friendly Test)
82. [Critical] No intrusive interstitials on mobile (pop-ups blocking content on page load)
83. [High] Touch targets minimum 48x48px with adequate spacing
84. [High] Viewport meta tag correctly set
85. [Medium] Accessible color contrast ratios (WCAG 2.1 AA minimum)

JavaScript SEO: The Technical SEO Audit Checklist Extension

Modern sites built on JavaScript frameworks (React, Vue, Angular, Next.js) require additional technical SEO audit checklist items beyond the standard 80 points. JavaScript SEO is a discipline of its own — and failures here can silently bury otherwise well-optimized sites.

The core issue: Googlebot renders JavaScript, but not instantly. There’s a delay between when Googlebot first crawls a page and when it renders the JavaScript. During this window, any content rendered by JavaScript is invisible. For sites where key SEO content (H1 tags, body copy, internal links, structured data) is injected by JavaScript rather than served in the initial HTML response, this creates indexation delays and ranking instability.

The audit question: serve your page URLs with JavaScript disabled in your browser. What content is visible? If your H1 tag, main body content, and primary navigation links disappear, you have a JavaScript SEO problem. The fix is server-side rendering (SSR) or static generation for critical content — which is why modern frameworks like Next.js default to SSR for exactly this reason.

Internal links generated by JavaScript are crawled but less reliably than HTML links. Navigation menus built as React components, infinite scroll pagination that loads links dynamically, and modal dialogs that reveal content are all crawlability risks. Audit these specifically — use a JavaScript-enabled crawler (Screaming Frog with Chrome rendering, or Botify) alongside a non-JS crawl and compare the link graphs. The differences reveal your JavaScript SEO exposure.

Structured data injected by JavaScript is processed by Google but should be verified with the URL Inspection tool in Google Search Console, which shows the rendered DOM — what Google actually sees after rendering. Schema in the initial HTML response is always more reliable than schema injected after page load.

Log File Analysis: What Most Technical Audits Miss

Log file analysis is the most underutilized component of a technical SEO audit checklist. While most audits rely on crawlers and GSC data, server log files tell you the ground truth of how Googlebot is actually behaving on your site — what it is crawling, how frequently, and where it is getting stuck.

Access your server logs (Apache access logs, Nginx access logs, or CDN logs from Cloudflare, Fastly, etc.) and filter for Googlebot user agent. What you’re looking for: which URLs Googlebot visits most frequently, which pages it never visits, where it encounters errors, and whether crawl budget is being wasted on low-value URLs like faceted navigation, pagination, or parameter variations.

Common log file discoveries that change audit priorities: Googlebot spending 40% of crawl budget on filter URLs that were supposed to be noindexed but aren’t. Googlebot not visiting key product pages that were recently published because internal link architecture hasn’t surfaced them yet. Googlebot encountering consistent 503 errors during peak traffic hours, indicating server capacity issues invisible in standard performance testing.

According to Google’s crawl budget documentation, crawl budget management is a real consideration for large sites and directly affects how quickly new content gets indexed. Log file analysis is the only way to see your actual crawl budget allocation rather than estimating from GSC data.

How to Run This Technical SEO Audit Checklist

The tools for a complete technical SEO audit checklist execution:

• Screaming Frog SEO Spider: Crawl all URL-level checks (title tags, meta, H1, canonicals, redirects, response codes, internal links)
• Google Search Console: Coverage, Core Web Vitals (CrUX field data), Manual Actions, Enhancements (schema)
• PageSpeed Insights: CWV lab and field data per URL
• Ahrefs or Semrush Site Audit: Broken links, orphaned pages, redirect chains
• Google Rich Results Test: Schema validation per page
• Chrome DevTools Lighthouse: Accessibility, performance, best practices per page

According to Moz’s Technical SEO Guide, systematic technical auditing is the foundation that separates high-performing sites from those left behind in competitive SERPs. For large sites (10,000+ pages), a full crawl needs to be run with JavaScript rendering enabled in Screaming Frog to catch issues with React/Vue/Angular frameworks. Many technical SEO issues on modern JavaScript-heavy sites only appear in rendered crawls.

According to Google’s JavaScript SEO documentation, Googlebot renders JavaScript but on a delayed basis — meaning JS-rendered content may lag in indexation compared to server-rendered content. This is a systemic risk for any site built on client-side rendering.

Prioritizing Technical SEO Audit Findings

Not all findings are equal. After completing this technical SEO audit checklist, prioritize by:

1. Indexation blockers: Anything preventing pages from being crawled or indexed (robots.txt errors, noindex on key pages, canonicalization loops)
2. Core Web Vitals failures: CWV below threshold are ranking-factor issues with direct fix paths
3. Structured data errors: Rich result eligibility is binary — errors mean no eligibility
4. Redirect chains: Link equity loss, user experience degradation
5. Internal link gaps: Orphaned pages, poor link equity distribution
6. On-page technical elements: Duplicate titles, missing meta descriptions, image optimization

If you need a professional technical SEO audit with implementation support, our SEO audit service covers all 80 of these points plus entity optimization, content gap analysis, and a prioritized implementation roadmap. For site-specific assessment, the fastest path is our qualification form.

The difference between a site that dominates its competitive space and one that underperforms despite good content is almost always technical. Get the infrastructure right first — everything else compounds from there.