Technical SEO Audit Template: The 150-Point Checklist for 2026

A technical SEO audit is not a one-time project — it’s a systematic process that reveals the infrastructure gaps between your site’s current state and its organic search potential. Every ranking factor, content investment, and link building effort depends on the technical foundation underneath it. Weak crawlability, indexation issues, or Core Web Vitals failures can suppress rankings regardless of content quality or authority.

This 150-point checklist covers every technical dimension that matters for organic search performance in 2026. Work through it methodically, prioritize by impact, and document findings with specific evidence for each issue identified.

Section 1: Crawlability and Robots Directives (30 Points)

Robots.txt Configuration

Robots.txt controls which areas of your site Googlebot can access. Errors here are high-severity — blocking entire sections of your site from crawling prevents indexing regardless of other optimizations.

1. Robots.txt file exists and is accessible at yourdomain.com/robots.txt
2. No critical site sections accidentally blocked (check for overly broad Disallow: / rules)
3. Sitemap URL(s) declared in robots.txt
4. Staging/development environments have separate robots.txt with Disallow: /
5. Parameterized URLs that create crawl traps are blocked (e.g., ?sort=, ?filter= if they create duplicate content)
6. No legitimate content pages blocked (search for False Positives in Disallow rules)
7. Robots.txt uses correct syntax (case-sensitive User-agent, no wildcards for Googlebot)
8. File is under 500KB (Google’s robots.txt size limit)

Meta Robots and X-Robots-Tag

9. No important pages use noindex directive unintentionally
10. Noindex is implemented consistently — either meta robots tag or X-Robots-Tag header, not conflicting
11. Paginated pages beyond page 2 are handled (noindex or canonical to page 1 for thin pagination)
12. Search result pages and filtered facets with minimal unique content use noindex
13. Thank you pages, account pages, and checkout flows use noindex
14. Tag pages and date archive pages (for CMS sites) are noindex unless they have unique value

Crawl Budget Efficiency

15. Crawl stats in Google Search Console show stable or increasing pages crawled per day
16. No server errors (5xx) appearing in crawl stats
17. Internal links don’t point to redirected URLs (redirects waste crawl budget)
18. Faceted navigation / filtering does not generate excessive unique URLs being crawled
19. Session IDs and tracking parameters are excluded from crawling (via robots.txt or rel=canonical)
20. Log file analysis confirms Googlebot is crawling your highest-priority pages most frequently
21. No significant crawl budget being consumed by known low-value pages (admin URLs, API endpoints)

Server Response Codes

22. All important pages return 200 OK status codes
23. No important pages returning 404 (check Search Console Coverage > Not found)
24. No important pages returning 503 Service Unavailable (crawl rate impact)
25. Redirect chains are resolved (A → B → C should be consolidated to A → C)
26. No redirect loops exist
27. 404 page returns actual 404 status code (not soft 404 returning 200)
28. Deleted/removed content returns 410 Gone rather than 404 where appropriate
29. Internal redirects use 301 (permanent) not 302 (temporary) for permanent URL changes
30. HTTP to HTTPS redirect is implemented globally and correctly

Section 2: Indexation and URL Architecture (25 Points)

Canonical Tags

1. Every page has a self-referencing canonical tag
2. Canonical URLs use HTTPS protocol
3. Canonical URLs match the exact URL the page is served at (no trailing slash inconsistency)
4. Duplicate content pages (www/non-www, http/https, with/without trailing slash) all canonicalize to one version
5. Paginated pages do not all canonicalize to page 1 if they contain unique, valuable content
6. Syndicated content uses canonical pointing to the original source URL
7. No pages have multiple conflicting canonical tags
8. AMP pages (if used) correctly use canonical to the non-AMP version

URL Structure Quality

39. URLs are human-readable with meaningful keywords
40. No URLs use dynamic parameters where static paths are possible (e.g., /product/blue-widget/ not /product.php?id=1234)
41. URL hierarchy reflects site architecture (category/subcategory/product)
42. No excessive URL depth beyond 4–5 levels
43. URLs use hyphens, not underscores, as word separators
44. No uppercase characters in URLs (URLs are case-sensitive, creates duplicate content risk)
45. Trailing slash usage is consistent across all URLs
46. No keyword stuffing in URLs (readable, not /best-cheap-affordable-widget-buy-online/)

Index Coverage Review

47. Google Search Console Coverage report reviewed — understand reason for each exclusion
48. Indexed pages count is stable or growing (sudden drops indicate indexing issues)
49. No valuable pages appearing in “Crawled – currently not indexed” (thin content or quality signal issue)
50. No valuable pages in “Discovered – currently not indexed” (crawl budget or priority issue)
51. XML sitemap submitted and processed without errors in Search Console
52. Sitemap includes all important URLs and excludes noindex pages
53. Sitemap lastmod dates are accurate (reflect actual last modification)
54. Image sitemap implemented if site has important image content
55. Video sitemap implemented if site has important video content

Section 3: On-Page Technical Elements (25 Points)

Title Tags and Meta Descriptions

1. Every page has a unique title tag
2. Title tags are 50–60 characters (not truncated in search results)
3. No duplicate title tags across the site
4. Every page has a meta description
5. Meta descriptions are 150–160 characters
6. No duplicate meta descriptions across the site
7. Title and description reflect actual page content (not generic templates)

Heading Structure

63. Every page has exactly one H1 tag
64. H1 contains the primary keyword for the page
65. Heading hierarchy is logical (H2 follows H1, H3 follows H2 — no jumps)
66. Headings are descriptive and match the content sections they introduce
67. No visual headings implemented with CSS styling on <p> or <div> tags instead of actual heading tags

Internal Linking

68. Important pages receive sufficient internal links from other site pages
69. Internal link anchor text is descriptive and varied (not all “click here”)
70. No broken internal links (crawl with Screaming Frog to identify)
71. Internal links use absolute URLs (not protocol-relative)
72. No orphan pages (pages with zero internal links from the rest of the site)
73. Navigation and footer links use canonical URL forms (with/without trailing slash, consistent)
74. No excessive internal links per page (Google recommends keeping within reason; 100+ on one page dilutes link equity)
75. Breadcrumb navigation implemented and functional
76. Related content links implemented on article and product pages

Image Optimization

77. All images have descriptive alt text (not empty, not keyword-stuffed)
78. Images are compressed and served in next-gen formats (WebP, AVIF)
79. Images have explicit width and height attributes (prevents CLS)
80. Hero images are preloaded with <link rel="preload">
81. Lazy loading implemented for below-the-fold images (not for above-the-fold images)

Section 4: Core Web Vitals (20 Points)

Largest Contentful Paint (LCP)

1. LCP score is “Good” (<2.5s) in Google Search Console field data
2. LCP element is identified (use Chrome DevTools Performance panel)
3. LCP element (usually hero image or headline) is present in initial HTML — not lazy-loaded
4. LCP image is preloaded with <link rel="preload" as="image">
5. LCP image is served from CDN close to users
6. LCP image uses correct MIME type and compression level
7. No render-blocking resources delaying LCP (inline critical CSS, defer non-critical JS)

Interaction to Next Paint (INP)

89. INP score is “Good” (<200ms) in Search Console field data
90. No long tasks (>50ms) blocking the main thread on key interaction pages
91. JavaScript is code-split and deferred where possible
92. Third-party scripts (analytics, chat, ads) are loaded asynchronously
93. Interaction handlers are lightweight and don’t trigger expensive DOM operations

Cumulative Layout Shift (CLS)

94. CLS score is “Good” (<0.1) in Search Console field data
95. All images have explicit dimensions (width/height attributes or CSS aspect-ratio)
96. Ad units have reserved space that doesn’t shift content when loaded
97. Fonts load without layout shift (use font-display: swap; preload critical fonts)
98. No content injected above existing content after page load
99. Embeds (videos, iframes) have reserved dimensions
100. Animations use transform/opacity (not width/height/margin changes that trigger layout)

Section 5: Mobile Optimization (15 Points)

1. Site passes Google’s Mobile-Friendly Test
2. Viewport meta tag is correctly configured: <meta name="viewport" content="width=device-width, initial-scale=1">
3. Text is readable without zooming on mobile (minimum 16px base font size)
4. Touch targets are adequately sized (minimum 48×48px for buttons and links)
5. No horizontal scrolling on mobile viewport widths
6. Mobile navigation is functional and accessible
7. Pop-ups and interstitials don’t cover content on mobile (violates Google’s intrusive interstitials policy)
8. Mobile page speed is acceptable (test with PageSpeed Insights on mobile setting)
9. Click-to-call functionality works for phone numbers on mobile
10. Forms are usable on mobile (input fields trigger correct keyboard type)
11. Same content served on mobile and desktop (mobile-first indexing)
12. Structured data consistent between mobile and desktop versions
13. No mobile-specific redirects that create separate m.example.com URLs without proper canonical handling
14. AMP implementation (if used) is error-free and consistent with canonical
15. Images load correctly on high-DPI (Retina) screens

Section 6: Structured Data and Schema Markup (20 Points)

1. All appropriate schema types implemented for content types present on site
2. No schema markup errors in Google’s Rich Results Test
3. Schema markup matches visible page content (no misleading markup)
4. JSON-LD format used (preferred over Microdata and RDFa)
5. BreadcrumbList schema implemented on all pages
6. Organization schema on homepage with logo, contact, and social profile URLs
7. Article schema on all blog/content pages with author, datePublished, dateModified
8. FAQPage schema implemented on FAQ sections
9. Product schema includes price, availability, and condition
10. LocalBusiness schema includes NAP (Name, Address, Phone) matching Google Business Profile
11. Review/AggregateRating schema matches ratings visible on page
12. No schema for content not visible on page (violation of Google’s guidelines)
13. SiteLinksSearchBox schema implemented on homepage if site search is prominent
14. Video schema implemented for embedded video content
15. Event schema for event pages with correct date/location
16. JobPosting schema for job listings
17. Speakable schema for news content targeting Google Assistant
18. Author entity markup linking to author profiles
19. Publisher entity correctly referencing Organization schema
20. Schema validated in Search Console Rich Results report

Section 7: Security and Technical Hygiene (15 Points)

1. Site serves entirely over HTTPS (no mixed content warnings)
2. SSL certificate is valid and not expiring within 30 days
3. HTTPS redirect in place (HTTP automatically redirects to HTTPS)
4. No mixed content errors (HTTP resources loaded on HTTPS pages)
5. Security headers implemented: HSTS, X-Content-Type-Options, X-Frame-Options
6. Site is not blocklisted by Google Safe Browsing (check Search Console Security Issues)
7. No manual actions in Google Search Console
8. No spam or malware detected in Search Console
9. CMS and plugins are up to date (outdated software creates security vulnerabilities that can lead to spam injection)
10. Admin areas are protected from public access and Googlebot crawling
11. No sensitive data exposed in URLs or source code (API keys, internal parameters)
12. Server response times are <200ms (Time to First Byte)
13. CDN implemented for static asset delivery
14. GZIP or Brotli compression enabled on server
15. Browser caching configured with appropriate cache-control headers

Prioritizing Audit Findings

Not all technical SEO issues have equal impact. Use this prioritization framework to direct remediation effort where it matters most:

Critical (fix within 48 hours): Any issue blocking Googlebot from crawling or indexing important pages; security issues flagged in Search Console; pages returning 5xx errors; HTTPS failures.

High (fix within 2 weeks): Core Web Vitals failures in field data; significant duplicate content issues; missing canonical tags on key pages; structured data errors on high-traffic templates.

Medium (fix within 30 days): Missing or suboptimal meta tags; internal linking gaps; image optimization issues; sitemap inaccuracies; minor crawl budget inefficiencies.

Low (backlog): Minor URL structure improvements; additional schema markup types; font loading optimization; aesthetic technical improvements without ranking impact.

Document each finding with: issue description, affected pages (count and examples), estimated impact, recommended fix, implementation effort, and assigned owner. Revisit the checklist quarterly and after any major site change.