Technical SEO Checklist: 40 Items to Audit Before You Publish
The complete technical SEO checklist — 40 items covering crawlability, indexation, Core Web Vitals, schema, and site architecture.
Ashikur RahmanHead of Strategy5 min readTechnical SEO is table stakes. None of your content strategy, link building, or on-page optimization matters if search engines can't crawl, render, and index your pages. This checklist covers the 40 technical items that separate sites that rank from sites that don't.
Why Technical SEO Is Table Stakes
You can't outwrite a site that search engines can't read. Technical SEO ensures your content has the best possible chance of being discovered, indexed, and ranked. It's not glamorous — but it's foundational.
Crawlability and Indexation (Items 1–10)
1. robots.txt configuration
Your robots.txt file tells crawlers which pages to access and which to skip. Check that it's not accidentally blocking important pages, CSS, or JavaScript files.
2. XML sitemap accuracy and submission
Submit an XML sitemap to Google Search Console and Bing Webmaster Tools. The sitemap should include all indexable pages and exclude noindexed, canonicalized, or redirected pages.
3. Canonical tag implementation
Every page should have a self-referencing canonical tag unless it's intentionally a variant. Canonical tags prevent duplicate content issues.
4. Redirect chains and loops
Audit for redirect chains (A → B → C) and loops (A → B → A). Chains longer than one hop waste crawl budget and slow down page loading.
5. Orphan pages
Orphan pages have no internal links pointing to them. Search engines may never discover them. Ensure every important page is reachable through internal links.
6. Crawl budget optimization
For large sites (10,000+ pages), block low-value pages from crawling while keeping them indexable if they have SEO value.
7. Log file analysis
Server log files show exactly how Googlebot crawls your site. Analyze them to identify crawl budget waste and pages Googlebot can't access.
8. Index coverage in Search Console
Review the Index Coverage report. Pages marked "Discovered – currently not indexed" or "Crawled – currently not indexed" need attention.
9. Noindex tag audit
Verify that pages marked noindex are intentional. Accidentally noindexed pages disappear from search results entirely.
10. Pagination and infinite scroll handling
For paginated content, use rel="next" and rel="prev" or load-all approaches. Infinite scroll should have paginated URLs that crawlers can access.
Core Web Vitals and Performance (Items 11–20)
11. Largest Contentful Paint (LCP)
Target under 2.5 seconds. Common fixes: optimize hero images, preconnect to critical domains, and reduce server response time.
12. Interaction to Next Paint (INP)
Target under 200 milliseconds. Common fixes: reduce JavaScript execution time, break up long tasks, and optimize event handlers.
13. Cumulative Layout Shift (CLS)
Target under 0.1. Common fixes: set dimensions on images and ads, use font-display: swap, and avoid dynamically injected content.
14. Image optimization
Compress images to WebP or AVIF format, use responsive srcset attributes, and lazy-load images below the fold.
15. Lazy loading implementation
Lazy-load images and iframes that are below the fold. Don't lazy-load above-the-fold content — it hurts LCP.
16. Font loading strategy
Use font-display: swap to prevent invisible text during font loading. Preload critical fonts.
17. JavaScript rendering
Ensure critical content is visible in the initial HTML, not rendered by JavaScript. Server-side rendering or static generation is preferred.
18. Third-party script management
Audit all third-party scripts. Defer non-critical scripts and load them after the main content.
19. CDN configuration
Use a Content Delivery Network to serve assets from geographically closer servers.
20. Server response time
Target server response time under 200ms. Common fixes: upgrade hosting, implement server-side caching, and optimize database queries.
Site Architecture and Internal Linking (Items 21–30)
21. URL structure and hierarchy
URLs should reflect your site hierarchy: domain.com/category/page-name.
22. Breadcrumb implementation
Breadcrumbs help users and search engines understand page hierarchy. Implement with BreadcrumbList schema markup.
23. Internal linking strategy
Link from high-authority pages to the pages you want to rank. Use descriptive anchor text.
24. Navigation structure
Your main navigation should be flat — most pages reachable within 3 clicks.
25. HTML sitemap
Include an HTML sitemap for users and crawlers.
26. Faceted navigation handling
For e-commerce sites, ensure faceted URLs are either noindexed, canonicalized, or blocked from crawling.
27. HTTPS and security
Every page should load over HTTPS. Mixed content triggers browser warnings.
28. Mobile-first design
Your mobile site should have the same content and structure as your desktop site.
29. Hreflang for international sites
Implement hreflang tags correctly to show the right version to the right audience.
30. Structured data implementation
Add schema markup for articles, FAQs, how-tos, products, and local businesses.
On-Page Technical Elements (Items 31–40)
31. Title tag optimization
Every page needs a unique title tag under 60 characters, front-loaded with the primary keyword.
32. Meta description implementation
Every page needs a unique meta description under 160 characters.
33. Header tag hierarchy (H1–H6)
Use one H1 per page, followed by H2s for major sections, H3s for subsections. Never skip heading levels.
34. Image alt text
Every image needs descriptive alt text.
35. Open Graph and Twitter Card tags
Implement for social sharing.
36. Schema markup validation
Test all structured data with Google's Rich Results Test.
37. AMP considerations
Evaluate whether AMP provides value for your audience before investing.
38. Print stylesheet and accessibility
Add print stylesheets and ensure WCAG accessibility compliance.
39. 404 page optimization
Custom 404 pages should help users find what they're looking for.
40. Content freshness signals
Regularly update important content with current information.
How to Prioritize Your Technical Fixes
| Priority | Items | Why |
|---|---|---|
| Fix immediately | 1, 2, 3, 8, 9, 11, 13, 27 | Direct impact on indexation and rankings |
| Fix this week | 4, 5, 17, 18, 20, 21, 31, 32 | High impact, moderate effort |
| Fix this month | 6, 7, 14, 15, 16, 22, 23, 30, 33, 36 | Important but less urgent |
| Plan for next quarter | 10, 12, 19, 24, 25, 26, 28, 29, 34, 35, 37, 38, 39, 40 | Maintenance and optimization |
FAQ
What is the most important technical SEO factor? Crawlability and indexation. If search engines can't crawl and index your pages, nothing else matters.
How often should I run a technical SEO audit? Full audits quarterly. Automated monitoring weekly. After any site migration or redesign, run an immediate audit.
Do Core Web Vitals affect rankings? Yes — Google uses Core Web Vitals as a ranking signal. Poor CWV also correlates with higher bounce rates.
Can technical SEO fix a content problem? No. Technical SEO ensures search engines can find and render your content. Weak content won't rank regardless of technical optimization.
Need a Technical SEO Audit? Let's Talk
Forty items is a lot. Most sites have 5–10 critical issues hiding in this list. Growthwarden runs a technical SEO audit with prioritized fixes.
Ashikur Rahman
Head of Strategy
Ashikur leads strategy at Growthwarden. He crafts data-driven growth frameworks that align marketing execution with business objectives, ensuring every campaign delivers measurable ROI.
Get the next article.
Field notes every few weeks. No sales sequences.