What Is Technical SEO?
Technical SEO is the discipline of optimising your website's infrastructure so that search engines can efficiently crawl, index, and render every page. It is the foundation that all other SEO work depends on.
Think of it this way: if your website were a building, technical SEO is the structural engineering — the foundation, plumbing, and electrical work. You can have the most beautiful interior design (content) and the best location (backlinks), but if the foundation is cracked, the building cannot stand.
Google deploys automated crawlers that visit your website, follow links, read content, and store pages in their index. Technical SEO ensures this process happens without friction. When it fails — because of slow load times, broken links, blocked pages, or duplicate content — Google either cannot find your content or ranks it lower than it deserves.
For a comprehensive overview of our approach to technical SEO engineering, see our dedicated service page.
Why Technical SEO Matters More Than You Think
Most businesses focus exclusively on content and backlinks, ignoring the technical layer. This is a strategic mistake because:
- Google cannot rank what it cannot crawl. If Googlebot is blocked from accessing pages, those pages are invisible.
- Slow sites lose rankings and users. A 1-second delay in page load reduces conversions by 7%.
- Duplicate content splits authority. Without proper canonicals, Google divides ranking power across multiple URLs.
- Mobile failures are fatal. Google uses mobile-first indexing — your mobile site IS your site.
Technical issues are also the most common cause of sudden, dramatic ranking drops. A single misconfigured noindex tag deployed by a developer can de-index an entire section of your website overnight.
The 30-Point Technical SEO Checklist
Section 1: Crawlability (Points 1–8)
Crawlability determines whether Google can discover and access your pages.
1. Robots.txt Configuration
Your robots.txt file tells Google which parts of your site to crawl and which to ignore. Verify:
- It exists at
yourdomain.com/robots.txt - It does not accidentally block important pages or directories
- It points to your XML sitemap
2. XML Sitemap Your sitemap is a roadmap for Google. Check:
- Sitemap exists and is submitted in Google Search Console
- All important pages are included
- No 404 or redirected URLs are present
- Sitemap is under 50MB and 50,000 URLs
3. Internal Link Structure Every important page must be reachable within 3 clicks from the homepage. Orphaned pages (pages with no internal links pointing to them) are effectively invisible to Google.
4. Crawl Errors Check Google Search Console for crawl errors:
- Server errors (5xx)
- Not found errors (404)
- Blocked by robots.txt
- Redirect errors
5. Crawl Budget Optimisation For larger sites (1,000+ pages), ensure Google is not wasting crawl budget on:
- Parameter URLs (filters, sorting)
- Session URLs
- Internal search results pages
- Paginated archives with no unique content
6. HTTP Status Codes Every URL should return the correct status:
| Code | Meaning | Action |
|---|---|---|
| 200 | OK | Correct for live pages |
| 301 | Permanent redirect | Use for moved pages |
| 302 | Temporary redirect | Avoid — use 301 unless truly temporary |
| 404 | Not found | Fix broken URLs or redirect |
| 410 | Gone | Use for permanently removed content |
| 500 | Server error | Fix immediately |
7. Redirect Chains Ensure no redirect chain exceeds 2 hops. A → B → C → D wastes crawl budget and dilutes link equity. Every redirect should go directly to the final destination.
8. URL Structure Clean URLs improve crawlability and user experience:
- Use hyphens, not underscores:
/technical-seo-checklistnot/technical_seo_checklist - Keep URLs short and descriptive
- Avoid parameters where possible
- Use lowercase only
Section 2: Indexing (Points 9–16)
Indexing determines whether Google stores your pages in its database.
9. Index Coverage In Google Search Console, check the Index Coverage report:
- How many pages are indexed vs submitted
- Pages with errors or warnings
- Pages excluded and why
10. Canonical Tags Every page should have a self-referencing canonical tag or point to the preferred version:
<link rel="canonical" href="https://yourdomain.com/your-page" />
This prevents duplicate content issues from URL parameters, www vs non-www, and HTTP vs HTTPS variations.
11. Noindex Usage
Audit all pages with noindex meta tags. Ensure:
- Only pages that should NOT appear in search are noindexed
- No revenue-generating pages are accidentally noindexed
- Test pages and staging content are noindexed
12. Duplicate Content Search for duplicate title tags and content across your site. Common causes:
- CMS generating multiple URLs for the same content
- WWW and non-WWW versions both accessible
- HTTP and HTTPS versions both accessible
- Pagination creating thin duplicate pages
13. Hreflang Tags (Multi-Language Sites) If your site serves content in multiple languages, implement hreflang tags correctly to tell Google which language and regional version to show each user.
14. Meta Robots Directives Beyond noindex, check for other robots directives that may be limiting Google:
nofollowon internal links (prevents link equity flow)noarchive(prevents cached versions)nosnippet(prevents search result snippets)
15. JavaScript Rendering If your site relies heavily on JavaScript (React, Next.js, Vue), verify Google can render the content:
- Use the URL Inspection tool in Search Console to see rendered HTML
- Ensure critical content is in the initial HTML, not loaded via client-side JS
- Test with JavaScript disabled to see what Google might miss
16. Thin Content Pages Identify pages with minimal content that add no value:
- Pages under 200 words with no unique purpose
- Auto-generated pages with minimal content
- Placeholder or "coming soon" pages
Either build out thin pages, consolidate them, or noindex them until they have real content.
Section 3: Site Speed & Core Web Vitals (Points 17–22)
Google has confirmed Core Web Vitals as a ranking factor. These metrics measure real-user experience.
17. Largest Contentful Paint (LCP) Measures loading performance — how fast the main content appears.
- Good: Under 2.5 seconds
- Needs Improvement: 2.5 – 4.0 seconds
- Poor: Over 4.0 seconds
Common fixes: optimise images, implement lazy loading, reduce server response time, preload critical assets.
18. Interaction to Next Paint (INP) Measures responsiveness — how quickly the page responds to user interaction.
- Good: Under 200ms
- Needs Improvement: 200 – 500ms
- Poor: Over 500ms
Common fixes: break up long JavaScript tasks, defer non-critical scripts, reduce main thread work.
19. Cumulative Layout Shift (CLS) Measures visual stability — whether elements shift around while loading.
- Good: Under 0.1
- Needs Improvement: 0.1 – 0.25
- Poor: Over 0.25
Common fixes: set explicit dimensions on images and videos, avoid inserting content above visible area, use CSS contain where appropriate.
20. Page Size Keep total page weight under 3MB. Audit:
- Image file sizes (use WebP/AVIF format)
- Unused CSS and JavaScript
- Third-party scripts and their payload
21. Server Response Time (TTFB) Time to First Byte should be under 600ms. If TTFB is slow:
- Consider a CDN (Content Delivery Network)
- Optimise database queries
- Upgrade hosting if on shared servers
- Implement server-side caching
22. Image Optimisation Images are typically the largest contributor to page weight:
- Use next-gen formats (WebP, AVIF)
- Implement responsive images with
srcset - Lazy load below-the-fold images
- Compress all images (target 80% quality for JPEG)
- Add descriptive alt text to every image
Use our page speed checker tool to test your site's performance.
Section 4: Mobile, Security & Structure (Points 23–30)
23. Mobile-Friendliness Google uses mobile-first indexing. Your mobile site IS your primary site. Test:
- No horizontal scrolling
- Text readable without zooming
- Tap targets large enough (minimum 48x48px)
- No content hidden behind "click to expand" that Google cannot see
24. HTTPS HTTPS is a confirmed ranking signal. Ensure:
- Valid SSL certificate (not expired)
- All pages serve over HTTPS
- HTTP URLs redirect to HTTPS (301)
- No mixed content (HTTP resources loaded on HTTPS pages)
25. Structured Data Implementation Add relevant structured data (schema markup) to help Google understand your content:
| Schema Type | Best For |
|---|---|
| FAQPage | FAQ sections on any page |
| LocalBusiness | Local businesses with physical locations |
| Article | Blog posts and news articles |
| Product | E-commerce product pages |
| BreadcrumbList | Site-wide navigation breadcrumbs |
| Service | Service description pages |
Validate with Google's Rich Results Test.
26. Breadcrumb Navigation Implement breadcrumbs on all pages for:
- Better user navigation
- Enhanced search result appearance
- Clearer site structure for Google
27. 404 Page Create a custom 404 page that:
- Clearly tells the user the page doesn't exist
- Provides navigation to key sections
- Includes a search bar
- Links to the homepage
28. Pagination For paginated content (blog archives, product listings):
- Use rel="next" and rel="prev" where helpful
- Ensure each page has unique content value
- Consider "load more" or infinite scroll with proper implementation
29. Log File Analysis For advanced technical SEO, analyse server log files to see:
- Which pages Googlebot actually crawls (vs what you think it crawls)
- Crawl frequency by section
- Server errors returned to Googlebot
- Pages receiving zero crawl attention
30. International Targeting If targeting multiple regions:
- Use hreflang correctly
- Consider ccTLD, subdomain, or subdirectory approach
- Set geographic targeting in Google Search Console
- Ensure content is genuinely localised, not just translated
The Quarterly Audit Schedule
| Quarter | Focus |
|---|---|
| Q1 | Full 30-point audit. Set baseline metrics. |
| Q2 | Speed focus. Re-test CWV. Address any new crawl errors. |
| Q3 | Content audit. Find thin pages, fix duplicates, update canonicals. |
| Q4 | Pre-planning audit. Clean up before year-end. Set next-year priorities. |
Frequently Asked Questions
How often should I run a technical SEO audit? Full audit quarterly, with monthly spot-checks on crawl errors, Core Web Vitals, and index coverage. Use Google Search Console as your primary monitoring tool.
Do I need to fix every issue on this checklist?
Prioritise by impact. Crawlability blockers and indexing issues are critical — fix immediately. Speed improvements and schema markup are high-value but less urgent. Start with items that directly prevent Google from finding or ranking your content.
Can technical SEO alone improve my rankings?
Technical SEO removes barriers. It ensures Google can find and rank your content at its true potential. However, content quality and backlinks determine how high that potential is. All three pillars work together. See our overview of the complete SEO approach.
What tools do I need for a technical SEO audit? Essential (free): Google Search Console, PageSpeed Insights, Mobile-Friendly Test. Advanced (paid): Screaming Frog, Ahrefs Site Audit, SEMrush. Our free SEO audit tool can identify the most common technical issues.
Is technical SEO different for Next.js or React sites?
Yes. JavaScript-rendered sites require extra attention to ensure Google can render content. Server-side rendering (SSR) or static site generation (SSG) are preferred. Client-side-only rendering risks content being invisible to Google. Our SEO pricing includes technical audits specifically designed for modern JavaScript frameworks.
What is the most common technical SEO mistake?
Accidentally blocking pages with noindex or robots.txt. We've seen single misconfigured tags de-index entire website sections overnight. Always verify robots directives after any deployment.
Conclusion
Technical SEO is not optional — it is the infrastructure that makes all other SEO efforts possible. A site with exceptional content and strong backlinks will still underperform if Google cannot efficiently crawl, index, and render its pages.
This 30-point checklist covers the critical technical foundations. Run it quarterly, prioritise by impact, and treat technical SEO as ongoing maintenance — not a one-time project. The sites that consistently outrank competitors are the ones that treat their technical SEO with the same rigour they apply to product development.
