You've written blog posts. You've built landing pages. You've even done some keyword research. But your SaaS site still isn't ranking — and you can't figure out why.
Nine times out of ten, the answer is technical SEO.
Technical SEO is the foundation everything else sits on. Great content on a poorly structured site is like a billboard in the desert — nobody will ever see it. Google can't rank pages it can't find, can't understand, or takes too long to load.
This checklist covers every technical SEO item that matters for SaaS startups in 2026 — organized by priority, with specific fixes for each item. No theory, no fluff. Just the checklist we run for every client at AutoSEOBot.
Use this as a working checklist. Go through each section, check what applies to your site, and fix issues in priority order. We've tagged each section by urgency:
- 🔴 Critical — Fix immediately. Blocks indexation or causes major ranking loss.
- 🟡 Important — Fix this week. Significant ranking impact.
- 🔵 Recommended — Fix when possible. Improves rankings and UX.
- 🟣 Advanced — Competitive edge. Do after basics are solid.
1. Crawlability & Indexation
If Google can't crawl your pages, nothing else matters. This is the absolute foundation of technical SEO.
Critical
Robots.txt Configuration
robots.txt exists and is accessible
Visit yoursite.com/robots.txt — it should load without errors. A missing robots.txt means Google crawls everything (usually fine), but a misconfigured one can block your entire site.
Not accidentally blocking important pages
Check for overly broad Disallow rules. We've seen SaaS sites block /app/ which also blocked /app-features/ — wiping their most important landing pages from Google.
Blocking pages that shouldn't be indexed
Login pages, admin panels, staging environments, search result pages, user-generated filter combinations. These waste crawl budget and create thin content issues.
Sitemap reference in robots.txt
Add Sitemap: https://yoursite.com/sitemap.xml at the bottom. This helps Google discover your sitemap automatically.
Critical
XML Sitemap
Sitemap exists and is valid XML
Submit at /sitemap.xml. Validate with a tool like XML Sitemaps Validator. Broken XML = Google ignores it silently.
Only includes indexable, canonical, 200-status pages
No 404s, no redirects, no noindex pages. Every URL in your sitemap should return 200 and be the canonical version.
lastmod dates are accurate
Don't set all pages to today's date. Google will ignore lastmod entirely if it looks unreliable. Use actual last-modified dates.
Submitted to Google Search Console
Go to Search Console → Sitemaps → submit your URL. Monitor for errors weekly.
Important
Indexation Health
Check index coverage in Search Console
Pages → Indexing → see how many pages are indexed vs excluded. A healthy site has 90%+ of submitted pages indexed.
No accidental noindex tags
Search your codebase for noindex. Check both meta tags and HTTP headers (X-Robots-Tag). Staging configurations sometimes leak to production.
Canonical tags point to the right pages
Every page should have a <link rel="canonical"> pointing to itself (or the preferred version). Wrong canonicals = Google ignores the page you want ranked.
No orphan pages
Every important page should be reachable through internal links. Pages with no internal links pointing to them are effectively invisible to Google's crawler.
SaaS-Specific Trap
Many SaaS sites accidentally expose thousands of app pages (dashboards, settings, user profiles) to Google. These create massive crawl waste and thin content problems. Use robots.txt + noindex to keep your app behind a wall — only your marketing pages should be crawlable.
2. Site Architecture & URL Structure
Good site architecture helps Google understand what your site is about and which pages matter most. For SaaS sites, this is especially important because you typically have marketing pages, blog content, docs, and app pages — all needing clear separation.
Important
URL Structure
Clean, descriptive URLs
Good: /blog/technical-seo-checklist. Bad: /blog/post?id=847&cat=3. URLs should be readable and include target keywords.
Consistent URL patterns
Pick a convention and stick to it. /blog/post-name for all blog posts. /features/feature-name for feature pages. Inconsistency confuses both users and crawlers.
No duplicate content from URL variations
Trailing slashes, www vs non-www, HTTP vs HTTPS, query parameters — all should redirect to one canonical version. Check: does yoursite.com/page, yoursite.com/page/, and www.yoursite.com/page all resolve to the same URL?
Shallow depth — 3 clicks or fewer from homepage
Any important page should be reachable within 3 clicks from the homepage. Deep pages get less crawl priority and less link equity.
Recommended
Internal Linking
Strategic internal links from high-authority pages
Your homepage has the most link equity. Make sure it links to your most important pages — pricing, top features, pillar blog content.
Blog posts link to related content
Every blog post should link to 3-5 related posts or pages. This creates topic clusters that signal authority to Google. (We covered this in our keyword research guide.)
Anchor text is descriptive
Instead of "click here," use descriptive anchor text like "our SaaS SEO audit checklist." This tells Google what the linked page is about.
Breadcrumb navigation on all pages
Breadcrumbs help users navigate and give Google additional structure signals. They also appear as rich results in search.
🏗️ Ideal SaaS Site Architecture
Here's the structure we recommend for most SaaS marketing sites:
Level 1: Homepage → links to all major sections
Level 2: /features/, /pricing/, /blog/, /about/, /docs/
Level 3: Individual feature pages, blog posts, doc pages
Separation: App pages under /app/ or app.yoursite.com — blocked from crawlers
3. Core Web Vitals & Page Speed
Core Web Vitals are a confirmed ranking factor. In 2026, they matter more than ever — especially for SaaS sites competing in crowded markets where small ranking differences mean big traffic differences.
Critical
The Three Core Web Vitals
LCP (Largest Contentful Paint) under 2.5 seconds
LCP measures how fast the main content loads. Common fixes: compress images, use modern formats (WebP/AVIF), preload hero images, reduce server response time, eliminate render-blocking resources.
INP (Interaction to Next Paint) under 200ms
INP replaced FID in 2024. It measures responsiveness to all user interactions — not just the first one. Fix: break up long JavaScript tasks, defer non-critical scripts, use web workers for heavy computation.
CLS (Cumulative Layout Shift) under 0.1
CLS measures visual stability — things jumping around as the page loads. Fix: set explicit width/height on images and embeds, avoid inserting content above existing content, use CSS containment.
| Metric |
Good |
Needs Improvement |
Poor |
| LCP |
≤ 2.5s |
2.5s – 4.0s |
> 4.0s |
| INP |
≤ 200ms |
200ms – 500ms |
> 500ms |
| CLS |
≤ 0.1 |
0.1 – 0.25 |
> 0.25 |
Important
Page Speed Fundamentals
Images optimized and properly sized
Use WebP or AVIF. Serve images at the size they'll display — not 4000px wide for a 400px thumbnail. Use srcset for responsive images. Lazy-load below-fold images.
CSS and JavaScript minified
Minify all production CSS/JS. Remove unused CSS (most SaaS sites ship 60-80% unused CSS from component libraries). Tools: PurgeCSS, Lightning CSS.
Third-party scripts audited
Analytics, chat widgets, heatmaps, A/B testing tools — each adds weight. Audit: is each script still used? Can it load async? Can it defer until after interaction? One chatbot widget can add 500ms to load time.
CDN configured
Serve assets from a CDN to reduce latency globally. Cloudflare, Vercel Edge, AWS CloudFront — all work. If your audience is global, this is non-negotiable.
Font loading optimized
Use font-display: swap to prevent invisible text. Preconnect to font providers. Consider self-hosting fonts to eliminate external requests. Subset fonts to include only the characters you use.
Quick Win
Run PageSpeed Insights on your homepage, pricing page, and top 3 blog posts. Fix the issues it flags in order of impact. Most SaaS sites can get to "Good" scores by optimizing images and deferring non-critical JavaScript — two changes that take an afternoon.
4. On-Page Technical Elements
These are the HTML-level signals that tell Google what each page is about and how to display it in search results.
Critical
Meta Tags
Unique title tags on every page (50-60 characters)
Every page needs a unique, keyword-rich title. Include your primary keyword near the beginning. Format: "Primary Keyword — Brand" or "Primary Keyword: Compelling Modifier".
Unique meta descriptions (120-155 characters)
Not a direct ranking factor, but they massively impact click-through rate. Write compelling descriptions that include a call-to-action and your target keyword.
One H1 tag per page
Each page should have exactly one H1 containing the primary keyword. Use H2s for major sections and H3s for subsections. Don't skip heading levels.
Canonical tags on every page
Every page needs <link rel="canonical" href="..."> pointing to its preferred URL. This prevents duplicate content from URL parameters, tracking codes, or syndication.
Important
Image Optimization
Alt text on all images
Descriptive alt text helps Google understand images and is essential for accessibility. Don't keyword stuff — describe what the image shows.
Descriptive file names
Use saas-seo-audit-dashboard.webp instead of IMG_4832.png. File names are a minor but free signal.
Width and height attributes set
Always include width and height on <img> tags. This prevents CLS (layout shifts) as images load.
Recommended
Open Graph & Social Tags
OG title, description, and image on all pages
Controls how your pages look when shared on social media and in messaging apps. A compelling OG image can 2x click-through from social shares.
Twitter card meta tags
Use summary_large_image for blog posts and landing pages. Test with Twitter's Card Validator.
5. Schema Markup & Structured Data
Schema markup helps Google understand your content's meaning and can unlock rich results — star ratings, FAQ dropdowns, how-to steps, and more appearing directly in search results.
Important
Essential Schema for SaaS Sites
Organization schema on homepage
Name, URL, logo, social profiles, contact info. This establishes your brand entity in Google's knowledge graph.
Article schema on blog posts
headline, author, datePublished, dateModified, publisher. Enables enhanced search results with publish dates and author information.
FAQ schema on relevant pages
Pricing pages and feature pages with FAQ sections are perfect candidates. FAQ schema can double your SERP real estate with expandable questions.
Breadcrumb schema
Helps Google understand your site hierarchy and shows breadcrumb trails in search results. Implement alongside visual breadcrumbs.
Advanced
Advanced Schema for SaaS
SoftwareApplication schema
For your product pages. Include applicationCategory, operatingSystem, offers (pricing). Can trigger rich results for software searches.
Review/AggregateRating schema
If you have genuine reviews or G2/Capterra ratings, mark them up. Star ratings in search results significantly increase CTR.
HowTo schema on tutorial content
Step-by-step guides can trigger rich results with expandable steps. Great for "how to" blog content.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your Article Title",
"author": {
"@type": "Organization",
"name": "YourCompany",
"url": "https://yoursite.com"
},
"datePublished": "2026-03-18",
"dateModified": "2026-03-18",
"publisher": {
"@type": "Organization",
"name": "YourCompany",
"logo": {
"@type": "ImageObject",
"url": "https://yoursite.com/logo.png"
}
}
}
</script>
6. HTTPS & Security Headers
HTTPS has been a ranking signal since 2014. In 2026, it's table stakes. But many SaaS sites still miss important security configurations that affect both SEO and user trust.
Critical
HTTPS Configuration
HTTPS on all pages — no mixed content
Every page, image, script, and stylesheet must load over HTTPS. Mixed content warnings destroy trust and can cause browsers to block resources.
HTTP → HTTPS redirect (301)
All HTTP URLs should 301 redirect to their HTTPS equivalents. This preserves link equity and prevents duplicate content.
SSL certificate is valid and not expiring soon
Check your cert expiry date. Set up monitoring to alert you 30 days before expiration. An expired cert = browsers block your site entirely.
Recommended
Security Headers
X-Content-Type-Options: nosniff
Prevents MIME-type sniffing attacks. Simple one-line header addition.
X-Frame-Options: DENY or SAMEORIGIN
Prevents your site from being embedded in iframes on other sites (clickjacking protection).
Referrer-Policy: strict-origin-when-cross-origin
Controls what referrer information is sent when users click links. Balances analytics data with privacy.
Permissions-Policy header
Restricts browser features (camera, microphone, geolocation) your site doesn't need. Shows Google and users you take security seriously.
Content-Security-Policy (CSP)
The most impactful security header, but also the most complex to implement. Start with report-only mode to avoid breaking your site, then tighten gradually.
7. Mobile Optimization
Google uses mobile-first indexing — your mobile site IS the site Google evaluates. If your mobile experience is broken, your desktop rankings suffer too.
Critical
Mobile Fundamentals
Responsive design (no separate mobile site)
Use CSS media queries, not m.yoursite.com. Separate mobile sites create duplicate content problems and are a maintenance nightmare.
Viewport meta tag configured
Include <meta name="viewport" content="width=device-width, initial-scale=1.0"> in every page's <head>.
Text readable without zooming
Minimum 16px base font size. Line height of at least 1.5. If users need to pinch-zoom to read, you'll fail Google's mobile usability test.
Tap targets sized properly
Buttons and links need at least 48x48px touch targets with adequate spacing. Tiny, tightly packed links = mobile usability errors in Search Console.
No horizontal scrolling
Tables, code blocks, and images can break mobile layouts. Use overflow-x: auto on containers and max-width: 100% on images.
Important
Mobile Content Parity
Same content on mobile and desktop
Don't hide content behind "read more" toggles on mobile or remove sections entirely. Google indexes the mobile version — if content isn't there, it doesn't exist.
Images and videos accessible on mobile
Make sure all media loads on mobile. Check that video embeds resize properly and images aren't cut off.
No intrusive interstitials
Full-screen popups that cover content on mobile will trigger ranking penalties. Newsletter popups, cookie banners that cover the full screen, and app install interstitials are all problems.
8. International & Multi-Language SEO
Most early-stage SaaS startups can skip this section. But if you serve multiple countries or languages, getting this right is critical — and getting it wrong causes major indexation problems.
Advanced
Hreflang & Localization
Hreflang tags implemented correctly
If you have /en/, /de/, /fr/ versions, each page needs hreflang tags pointing to all language versions (including itself). Missing self-referencing hreflang is the most common mistake.
x-default hreflang for fallback
Include hreflang="x-default" pointing to your main/English version. This tells Google what to show users in non-targeted regions.
Content is actually translated, not just auto-translated
Machine-translated content without human review creates a poor user experience and can be flagged as thin content. Invest in real localization or don't do it at all.
Localized URLs (subdirectories preferred)
Use yoursite.com/de/ rather than de.yoursite.com or a separate domain. Subdirectories consolidate link equity under one domain.
Early-stage advice
If you're pre-Series A and primarily serve English-speaking markets, skip international SEO entirely. Focus your limited resources on dominating one language first. You can always add localization later.
9. SaaS-Specific Technical Issues
SaaS sites have unique technical SEO challenges that regular business sites don't face. These are the ones we see most often in our audits.
Critical
JavaScript Rendering
Marketing pages work without JavaScript
Many SaaS sites use React/Next.js/Vue for everything — including marketing pages. If your content requires client-side rendering, Google may not see it. Test: disable JavaScript in Chrome DevTools and check if your key content is still visible.
SSR or SSG for SEO-critical pages
Use Server-Side Rendering (SSR) or Static Site Generation (SSG) for all marketing, blog, and landing pages. Client-side rendering is fine for your app — not for pages that need to rank.
Check Google's cache for JS-rendered content
Search cache:yoursite.com/page in Google or use URL Inspection in Search Console. If content is missing from Google's cached version, it's not being indexed.
Important
SaaS-Specific Gotchas
Subdomain strategy is intentional
app.yoursite.com, docs.yoursite.com, blog.yoursite.com — each subdomain is treated as a separate entity by Google. Unless you have a good reason, keep everything under one domain. Subdomains dilute your authority.
Login/signup pages handled properly
Your /login and /signup pages don't need to rank (usually). Noindex them if they create duplicate content issues. But keep your main /signup page indexable if you want organic traffic for "[product] sign up" queries.
Feature pages aren't thin content
Many SaaS sites create one page per feature with just a headline and a screenshot. These are thin content. Feature pages should include: use cases, benefits, how-it-works, social proof, and a clear CTA — minimum 500 words of unique content.
Pricing page is crawlable
Some SaaS sites load pricing dynamically via API calls after page load. If Google can't see your pricing, you won't rank for "[product] pricing" queries — one of the highest-intent keywords for any SaaS company.
Documentation and help center contribute to SEO
Your docs pages can rank for long-tail technical queries and drive qualified traffic. Make sure they're on your main domain (not a separate subdomain) and properly indexed.
The #1 SaaS Technical SEO Mistake
Building your entire marketing site with your app framework (React SPA, etc.) without SSR. We've audited SaaS companies with 50+ landing pages that Google couldn't render a single one of. If your marketing pages are client-side rendered, this is your highest-priority fix. Consider using a static site generator (Astro, Hugo, Eleventy) for marketing pages — separate from your app.
You don't need to check everything manually. These tools automate most of the checklist above:
Free Tools
- Google Search Console — The source of truth. Index coverage, Core Web Vitals (field data), mobile usability, manual actions. Check weekly.
- Google PageSpeed Insights — Detailed Core Web Vitals breakdown with lab and field data. Run on every important page type.
- Google's Rich Results Test — Validates your structured data and shows which rich results you're eligible for.
- Screaming Frog (free up to 500 URLs) — The gold standard for crawling your site. Finds broken links, redirect chains, missing meta tags, duplicate content, and more.
- web.dev Measure — Lighthouse-powered performance and SEO audit in the browser.
Paid Tools (For Growing Teams)
- Screaming Frog (paid) — Unlimited crawling, JavaScript rendering, custom extraction, and scheduled crawls. Worth the £199/year once you have 500+ pages.
- Ahrefs Site Audit — Crawls your site and categorizes issues by severity. Great for ongoing monitoring with alerts.
- Semrush Site Audit — Similar to Ahrefs with a focus on actionable recommendations. Includes a health score to track progress.
- ContentKing — Real-time SEO monitoring. Detects changes to your site 24/7 and alerts you to issues before they impact rankings.
Our stack
At AutoSEOBot, we use Google Search Console (free) + Screaming Frog (paid) + custom Python scripts for automated auditing. This combination catches 99% of technical issues for our clients. Don't overspend on tools early — Google Search Console alone gets you 70% of the way.
11. Priority Framework: What to Fix First
You've got the checklist. Now the question is: where do you start? Not everything needs fixing at once. Here's our priority framework based on revenue impact:
| Priority |
Category |
Fix When |
Impact |
| P0 |
Crawlability blockers (noindex, robots.txt, broken sitemap) |
Immediately |
Pages literally invisible to Google |
| P0 |
HTTPS issues (mixed content, missing redirect) |
Immediately |
Trust + ranking signal lost |
| P1 |
Core Web Vitals (LCP, INP, CLS) |
This week |
Direct ranking factor + UX |
| P1 |
Mobile optimization |
This week |
Mobile-first indexing |
| P1 |
JS rendering issues (SPA marketing pages) |
This week |
Content invisible to Google |
| P2 |
Meta tags (titles, descriptions, canonicals) |
This month |
CTR + relevance signals |
| P2 |
Schema markup |
This month |
Rich results + SERP visibility |
| P2 |
Internal linking + site architecture |
This month |
Crawl efficiency + link equity |
| P3 |
Security headers |
When ready |
Trust signals (minor ranking impact) |
| P3 |
International SEO (hreflang) |
When expanding |
Multi-market presence |
🎯 The 80/20 for SaaS Technical SEO
If you only have one afternoon, do these five things:
1. Check robots.txt — make sure you're not blocking important pages.
2. Submit your sitemap to Google Search Console.
3. Run PageSpeed Insights on your homepage — fix any "Poor" metrics.
4. Add canonical tags to every page.
5. Test your site with JavaScript disabled — if content disappears, that's your #1 priority.
These five checks catch the most common technical SEO issues we find in SaaS audits. Everything else is optimization on top of a solid foundation. (Want the full audit? Check out our complete SaaS SEO audit checklist.)
"Technical SEO isn't glamorous. Nobody writes case studies about fixing canonical tags. But every ranking you've ever earned sits on a technical foundation — and when that foundation cracks, everything above it falls."
Not sure where your technical SEO stands?
We'll crawl your SaaS site, run every check on this list, and hand you a prioritized fix list — free. No sales pitch, no strings.
Get Your Free Technical SEO Audit →