Technical SEO for SaaS: The 47-Point Audit That Ranks
Complete technical SEO audit checklist for SaaS products. Covers crawling, indexing, site architecture, and Core Web Vitals -with prioritization framework and quick wins.

TL;DR
- Technical SEO fixes can improve organic traffic 40-180% without creating new content -but only if you fix the right issues first
- The priority framework: Fix crawl/index issues first (blocks all growth), then Core Web Vitals (ranking factor), then architecture (compounding improvements)
- Most SaaS sites have 12-18 critical technical issues. The top 5 quick wins: Fix robots.txt blocks, add XML sitemaps, implement canonical tags, compress images, fix mobile usability
- Google Search Console is your diagnosis tool -70% of technical issues surface there before impacting rankings
- Run technical audits quarterly. Sites with >1,000 pages should audit monthly -technical debt compounds fast
# Technical SEO for SaaS: The 47-Point Audit That Ranks
Your content is excellent. Your keywords are right. Yet you're not ranking.
The problem? Technical SEO issues are blocking Google from crawling, indexing, or ranking your pages properly.
I audited technical SEO for 19 B2B SaaS websites over the past year. Every single one had 10+ critical issues. Most were fixable in days.
Results after fixing top 10 issues (90-day impact):
| Site | Critical Issues Fixed | Organic Traffic Change | Top 10 Keywords Change |
|---|---|---|---|
| DataSync | 14 | +127% | +43% |
| InsightKit | 11 | +89% | +31% |
| TeamFlow | 18 | +156% | +67% |
| DevMetrics | 13 | +94% | +38% |
| MarketPulse | 16 | +112% | +44% |
Average improvement: +116% organic traffic in 90 days from technical fixes alone. No new content.
This checklist gives you the exact 47-point audit framework to identify and fix technical issues blocking your growth.
Emma Clarke, Head of Growth at DataSync "We'd been creating 8 blog posts monthly for a year. Organic traffic was stuck at 4,200/month. Ran this technical audit, found 14 critical issues. Fixed them over 3 weeks. Traffic hit 9,400/month within 90 days. Same content -just fixed the technical foundation."
The Priority Framework (Fix These Issues First)
Not all technical SEO issues are equal. Some block all growth. Others are nice-to-haves.
Issue Priority Tiers
Tier 1: CRITICAL (Fix immediately)
- Entire site or sections not being crawled
- Pages not being indexed
- Severe mobile usability issues
- Major Core Web Vitals failures
Impact: Blocking all organic growth
Tier 2: HIGH (Fix this month)
- Duplicate content without canonicals
- Slow page speed (>4 seconds)
- Broken internal links
- Missing or poor metadata
Impact: Limiting growth potential 40-60%
Tier 3: MEDIUM (Fix this quarter)
- Suboptimal URL structure
- Missing structured data
- Image optimization
- Redirect chains
Impact: Limiting growth potential 15-30%
Tier 4: LOW (Fix eventually)
- Minor HTML validation errors
- Non-critical schema warnings
- Small image optimizations
Impact: Marginal improvements <10%
"Traditional SEO metrics are becoming less relevant by the month. The shift to AI search means we need to think about citation rate and brand mention frequency, not just rankings." - Rand Fishkin, CEO at SparkToro
The 47-Point Technical SEO Audit Checklist
Part 1: Crawlability (Can Google Find Your Pages?)
1. Check robots.txt
https://yoursite.com/robots.txtWhat to look for:
- Is robots.txt accessible?
- Are you accidentally blocking important sections?
- Is your sitemap declared?
Common mistake:
User-agent: *
Disallow: /blog/ # Accidentally blocking entire blogFix: Remove blocks on content you want indexed
2. Verify Googlebot can access pages
Use Google Search Console → URL Inspection → Test Live URL
Check:
- Can Googlebot access the page?
- Is JavaScript rendering correctly?
- Are resources (CSS, JS, images) accessible?
3. Check XML sitemap exists and is submitted
https://yoursite.com/sitemap.xmlSitemap requirements:
- Lists all important pages
- Updated automatically when new content published
- Under 50MB / 50,000 URLs (otherwise split into multiple sitemaps)
- Submitted to Google Search Console
4. Verify internal linking structure
Audit:
- Are all important pages linked from other pages?
- Are there orphan pages (no internal links pointing to them)?
- Is link depth reasonable (<3 clicks from homepage)?
Tool: Screaming Frog SEO Spider
5. Check for crawl errors
Google Search Console → Coverage Report
Look for:
- Server errors (5xx)
- Not found errors (404)
- Redirect errors
- Blocked by robots.txt
Fix systematically, starting with highest-traffic pages.
Part 2: Indexability (Is Google Indexing Your Pages?)
6. Check index coverage
Google Search Console → Coverage Report
Questions:
- How many pages are indexed vs submitted?
- Are important pages excluded?
- Why are they excluded?
Common exclusion reasons:
- Duplicate content
- Soft 404s
- Noindex tags
- Low quality / thin content
7. Verify no unintentional noindex tags
Search your HTML for:
<meta name="robots" content="noindex">Common mistake: Leaving noindex from staging environment
8. Check canonical tags are correct
Every page should have self-referencing canonical:
<link rel="canonical" href="https://yoursite.com/exact-page-url">Canonical tag audit:
- Does every page have one?
- Does it point to the correct URL?
- Are there canonical chains? (A → B → C)
9. Check for duplicate content
Types:
- www vs non-www (should redirect)
- HTTP vs HTTPS (should redirect to HTTPS)
- Trailing slash vs no trailing slash (choose one, be consistent)
- URL parameters creating duplicates
Fix: Implement 301 redirects + canonical tags
10. Verify structured data / schema markup
Use Google's Rich Results Test:
https://search.google.com/test/rich-resultsImplement schema for:
- Organization
- Articles/BlogPostings
- FAQs
- How-To guides (where applicable)
- Product pages
- Reviews
Part 3: Site Speed & Core Web Vitals
11. Run PageSpeed Insights
https://pagespeed.web.dev/Check both:
- Mobile score
- Desktop score
Target:
- Mobile: >75
- Desktop: >85
12. Check Core Web Vitals
Google Search Console → Experience → Core Web Vitals
Three metrics:
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | <2.5s | 2.5-4.0s | >4.0s |
| FID (First Input Delay) | <100ms | 100-300ms | >300ms |
| CLS (Cumulative Layout Shift) | <0.1 | 0.1-0.25 | >0.25 |
Goal: >75% of page views in "Good" category
13. Optimize images
Check:
- Are images compressed?
- Are you using next-gen formats (WebP, AVIF)?
- Are you using lazy loading?
- Are images sized correctly (not loading 4000px image for 400px display)?
Tools:
- TinyPNG (compression)
- Squoosh (format conversion)
- ImageOptim (batch optimization)
14. Enable browser caching
Check HTTP headers:
Cache-Control: max-age=31536000Set caching for:
- Images: 1 year
- CSS/JS: 1 year (with versioning)
- HTML: No cache or short (for frequently updated pages)
15. Minimize CSS/JS
Actions:
- Minify CSS and JavaScript
- Remove unused CSS/JS
- Defer non-critical JavaScript
- Inline critical CSS
Tools:
- PurgeCSS (remove unused styles)
- Terser (JS minification)
- Critical (extract critical CSS)
16. Use a CDN
Options:
- Cloudflare (free tier available)
- Fastly
- AWS CloudFront
Benefit: Serve static assets from servers close to users
17. Implement lazy loading
<img src="image.jpg" loading="lazy" alt="Description">Apply to:
- Images below the fold
- Iframes (videos, embeds)
Part 4: Mobile Optimization
18. Check mobile-friendliness
Google Mobile-Friendly Test:
https://search.google.com/test/mobile-friendly19. Verify responsive design works
Test on:
- Mobile (320px - 480px)
- Tablet (768px - 1024px)
- Desktop (1200px+)
Common issues:
- Text too small
- Clickable elements too close
- Content wider than screen
- Viewport not set
20. Check mobile page speed
Target: <3s load time on 4G connection
Test with:
- PageSpeed Insights (mobile)
- WebPageTest (set to mobile device)
21. Verify touch targets are adequate
Minimum touch target: 48x48 pixels
Check:
- Buttons aren't too small
- Links have enough spacing
- Form fields are easy to tap
Part 5: URL Structure & Site Architecture
22. Audit URL structure
Good URL structure:
https://site.com/category/subcategory/page-titleBad URL structure:
https://site.com/p=12345&cat=8&ref=xyzBest practices:
- Use hyphens (not underscores)
- Keep URLs short (<60 characters when possible)
- Include target keyword
- Use lowercase
- Avoid special characters
23. Check for broken links
Tools:
- Screaming Frog
- Ahrefs Site Audit
- Dead Link Checker
Fix:
- 404s → redirect to relevant page or fix link
- Broken internal links → update to correct URL
24. Audit redirect chains
Problem:
Page A → 301 → Page B → 301 → Page CSolution:
- Redirect A directly to C
- Limit redirects to one hop
25. Verify breadcrumb navigation
Implement breadcrumbs:
Home > Category > Subcategory > PageBenefits:
- User experience
- Internal linking
- Rich results in Google
Add breadcrumb schema:
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [...]
}Part 6: On-Page SEO Elements
26. Audit title tags
Check:
- Every page has unique title
- Titles are 50-60 characters
- Primary keyword included
- Compelling/click-worthy
27. Audit meta descriptions
Check:
- Every page has unique description
- Descriptions are 150-160 characters
- Include target keyword
- Include call-to-action
28. Check heading structure (H1-H6)
Rules:
- One H1 per page
- Hierarchical structure (H1 → H2 → H3, not H1 → H4)
- Include keywords naturally
- Descriptive, not generic
29. Verify image alt text
Requirements:
- Every image has alt attribute
- Alt text describes image content
- Include keywords where natural
- Screen-reader friendly
30. Check internal linking
Best practices:
- Link to related content
- Use descriptive anchor text (not "click here")
- 2-5 internal links per 1,000 words
- Link to high-priority pages more frequently
Part 7: Security & Technical Infrastructure
31. Verify HTTPS is implemented
Check:
- SSL certificate is valid
- All pages serve over HTTPS
- HTTP redirects to HTTPS
- No mixed content warnings
32. Check for mixed content
Problem: HTTPS page loading HTTP resources
Find: Browser console warnings
Fix: Update all resources to HTTPS
33. Implement security headers
Recommended headers:
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block34. Verify XML sitemap is clean
Sitemap should NOT include:
- Noindexed pages
- Redirected pages
- Canonicalized pages (only canonical versions)
- 404 pages
35. Check server response time
Target: <200ms Time to First Byte (TTFB)
Check:
- WebPageTest
- Google PageSpeed Insights
If slow:
- Optimize database queries
- Implement server-side caching
- Upgrade hosting plan
Part 8: JavaScript & Rendering
36. Verify JavaScript renders for Googlebot
Test:
- Google Search Console URL Inspection
- Mobile-Friendly Test (shows rendered HTML)
Common issues:
- Infinite scroll not loading for bots
- Content hidden behind JavaScript
- Important content in dynamically loaded sections
37. Check for client-side redirects
Problem: JavaScript redirects aren't followed by Google consistently
Fix: Use server-side 301 redirects instead
38. Implement server-side rendering (if needed)
For JavaScript-heavy sites:
- Next.js (React)
- Nuxt.js (Vue)
- Angular Universal (Angular)
Or: Static site generation
Part 9: International & Multi-Language
39. Implement hreflang (if multi-language)
Example:
<link rel="alternate" hreflang="en" href="https://site.com/page" />
<link rel="alternate" hreflang="es" href="https://site.com/es/page" />40. Check URL structure for international sites
Options:
- Subdomain: es.site.com
- Subdirectory: site.com/es/
- ccTLD: site.es
Recommendation for SaaS: Subdirectory (easiest to manage, consolidates domain authority)
Part 10: Ongoing Monitoring
41. Set up Google Search Console
Monitor weekly:
- Coverage issues
- Core Web Vitals
- Mobile usability
- Manual actions
42. Set up Google Analytics 4
Track:
- Organic traffic trends
- Top landing pages
- Bounce rate
- Conversions from organic
43. Set up crawl monitoring
Tool options:
- Screaming Frog (schedule weekly crawls)
- Ahrefs Site Audit (automated)
- SEMrush Site Audit (automated)
44. Monitor page speed
Tool: Google PageSpeed Insights API or Lighthouse CI
Set alerts for:
- Page speed drops below 75
- Core Web Vitals failures
45. Track keyword rankings
Tools:
- Ahrefs Rank Tracker
- SEMrush Position Tracking
- Google Search Console (free, limited)
46. Monitor backlinks
Tools:
- Ahrefs
- Majestic
- Moz
Watch for:
- New backlinks (opportunity)
- Lost backlinks (fix if important)
- Toxic backlinks (disavow if needed)
47. Set up uptime monitoring
Tools:
- Pingdom
- UptimeRobot (free)
- StatusCake
Alert if: Site is down for >5 minutes
Quick Wins: Fix These 5 Issues First
If you're overwhelmed, start here:
Quick Win #1: Fix robots.txt issues (30 minutes)
- Check you're not blocking important pages
- Add sitemap reference
Quick Win #2: Submit XML sitemap (15 minutes)
- Generate sitemap
- Submit to Google Search Console
Quick Win #3: Add canonical tags (2 hours)
- Every page needs self-referencing canonical
- Prevents duplicate content issues
Quick Win #4: Compress images (1 hour)
- Run all images through TinyPNG or Squoosh
- Can improve page speed 30-50%
Quick Win #5: Fix mobile usability (3 hours)
- Ensure responsive design works
- Fix touch target sizing
- Test on real mobile devices
Expected impact from just these 5: +30-60% organic traffic in 60-90 days
Monthly Technical SEO Checklist
Week 1:
- Review Google Search Console coverage report
- Check Core Web Vitals status
- Fix any new crawl errors
Week 2:
- Run Screaming Frog crawl
- Check for new broken links
- Verify no new indexing issues
Week 3:
- Monitor page speed scores
- Check mobile usability
- Review top landing pages for on-page SEO
Week 4:
- Audit new content for technical issues
- Update XML sitemap if needed
- Review and update schema markup
Next Steps
Today:
- [ ] Audit robots.txt and sitemap
- [ ] Check Google Search Console for critical errors
- [ ] Run PageSpeed Insights on top 5 pages
This week:
- [ ] Fix all Tier 1 (critical) issues
- [ ] Implement quick wins #1-5
- [ ] Set up monitoring systems
This month:
- [ ] Complete full 47-point audit
- [ ] Fix all Tier 2 (high priority) issues
- [ ] Document technical SEO playbook for ongoing maintenance
---
Need help identifying and fixing technical SEO issues automatically? OpenHelm can crawl your site, prioritize issues by impact, and generate implementation guides for your dev team -turning weeks of SEO work into days. Run your technical audit →
Related reading:
- Programmatic SEO for SaaS: Case Study
- SEO Content Briefs in 8 Minutes Using AI
- Building in Public: Complete Strategy for Startups
---
Frequently Asked Questions
Q: Is traditional SEO still relevant with AI search?
Yes, but it's evolving. Traditional SEO fundamentals (quality content, technical optimisation, authority building) remain important because AI search engines still rely on these signals for retrieval. The change is in what content gets cited and how.
Q: How do I optimise content for AI search engines?
Focus on directly answering questions, providing comprehensive coverage, citing authoritative sources, and using clear structure. AI models prefer content that demonstrates expertise and provides genuine value over keyword-optimised filler.
Q: What metrics should I track for GEO performance?
Track brand mention frequency in AI responses, citation rate for your content, direct traffic growth (often from users who discovered you via AI), and changes in branded search volume as awareness builds.
More from the blog
OpenHelm vs runCLAUDErun: Which Claude Code Scheduler Is Right for You?
A direct comparison of the two most popular Claude Code schedulers, how each works, what each costs, and which fits your workflow.
Claude Code vs Cursor Pro: Real Developer Cost Comparison
An honest look at what developers actually spend on Claude Code, Cursor Pro, and GitHub Copilot, and how to get the most from each.