Most B2B SaaS companies treat SEO as a marketing problem. After auditing 40+ SaaS sites, we'd argue at least 70% of organic growth potential is locked behind engineering decisions, not content strategy.
This checklist is the version we work through with engineering teams on every SEO engagement. It's opinionated, ordered by impact, and explicitly skips the bits that don't move the needle.
1. Rendering strategy
The fastest win on most SaaS sites: rendering the marketing pages on the server, not in the browser.
If your marketing site is a Single Page Application (Create React App, Vue CLI without SSR, a Webflow export with heavy JS), the indexing of your content is at the mercy of Google's headless renderer. That renderer is slower, more resource-constrained, and skips some patterns.
Move to server-side rendering (SSR) or static site generation (SSG) via Next.js, Nuxt, Astro, Remix or SvelteKit. Most SaaS marketing content is updated weekly at most, so SSG with on-demand revalidation is the sweet spot.
How to verify what Google actually sees:
- View your page source (Ctrl+U). If the main content isn't in the HTML, neither is Google going to see it reliably.
- Use Google Search Console's URL Inspection → Test Live URL to see the rendered HTML and any blocked resources.
2. Core Web Vitals (still ranking factors in 2026)
Three metrics matter. Targets are Google's "good" thresholds:
- LCP (Largest Contentful Paint) < 2.5s
- INP (Interaction to Next Paint) < 200ms
- CLS (Cumulative Layout Shift) < 0.1
For most SaaS sites, the killer is hero image LCP. Three rules that fix 80% of cases:
- Use a modern framework's
<Image>component (Next.js Image, Nuxt Image) with correctwidth/heightandpriorityon the hero. - Serve AVIF or WebP. JPEG hero images on a B2B SaaS in 2026 is malpractice.
- Use
fetchPriority="high"on the LCP image element.
For INP, the offender is usually third-party JavaScript — chat widgets, analytics, A/B testing scripts. Audit with Chrome DevTools' Performance tab and lazy-load anything that doesn't need to load on first paint.
CLS is almost always caused by late-loading webfonts or dynamic ad slots. Reserve space with aspect-ratio CSS and use font-display: swap with proper fallback metric overrides.
3. Indexable URL structure
Three rules:
- One canonical URL per piece of content. Trailing slashes, www vs non-www, http vs https — pick one and 301 redirect the rest.
- No
?utm_or session ID in canonical tags. Strip them. - No
?page=2for the same content as?page=1. Userel="canonical"correctly OR consolidate to a single paginated route with view-more.
For SaaS specifically: ensure your dashboard URLs (/app/*, /dashboard/*) are blocked in robots.txt AND marked noindex in meta. Marketing pages should be the only thing in the index.
4. Structured data that matters
Schema.org markup that meaningfully impacts SERP appearance for SaaS:
- Organization — site-wide, on root layout
- BreadcrumbList — every non-home page
- FAQPage — pricing pages, product pages, help center articles
- Article — every blog post
- Product + Offer — pricing pages (if you publish prices)
- SoftwareApplication — your main product page
- WebSite with
potentialAction(SearchAction) — root, if you have site search
Skip:
- LocalBusiness (you're SaaS, not a coffee shop)
- Review (only if you've genuinely earned real reviews — fake review schema is penalised)
- Event (rarely relevant for SaaS)
Validate with Google's Rich Results Test, not just the Schema Markup Validator — the latter is more lenient.
5. Internationalisation done right
The most common mistake we see in international SaaS SEO is broken hreflang. Rules:
- Every translated page must
hreflanglink to every other translation, including itself. - Every set of
hreflangtags must include anx-defaultfallback. - The
hreflangvalue must match the<html lang>of the target page. - Use
language-regioncodes (en-US,de-DE) when you have true regional variants, plain language codes (en,de) when you don't.
A surprisingly common bug: your CMS exports a hreflang for a translation that doesn't exist on the live site. Google reports this as No return tags in Search Console. Audit with Screaming Frog or Ahrefs site audit.
6. Crawl budget management
For SaaS sites with thousands of pages (changelog, help center, blog), crawl budget is real. Three levers:
robots.txt— block/app/*,/api/*,/?preview=*. Don't block CSS or JS — Google needs them to render.sitemap.xml— only include canonical, indexable pages. Don't list every old changelog entry.- Internal linking — your most important pages should be linked from the homepage in ≤2 clicks.
For very large sites, split into multiple sitemaps by section (sitemap-blog.xml, sitemap-docs.xml) and submit them all to Search Console.
7. JavaScript SEO
If you're shipping a modern framework correctly, this is mostly solved. But two patterns still break:
- Client-side routing without proper history API — every route change must update
<title>, meta tags, canonical, OG tags. Frameworks usually handle this; vanilla SPAs often don't. - Lazy-loaded content that needs scrolling — Google's renderer doesn't scroll. Anything below the fold loaded via Intersection Observer might not be indexed. Use
loading="lazy"for images, not for primary content.
8. Performance budget enforcement
Code-quality tools fail when budget creeps in over time. Set up:
- Lighthouse CI on every PR — fail builds if LCP > 2.5s or JS bundle > 300KB
- Bundle analyzer in CI — flag regressions in JS payload
- Real User Monitoring (RUM) with Vercel Analytics, Cloudflare Web Analytics or Datadog RUM — synthetic Lighthouse doesn't reflect real users on slow 4G
9. Logs you should look at monthly
- Google Search Console → Pages → Why pages aren't indexed — find indexing issues before they tank organic traffic
- Search Console → Core Web Vitals report — real Chrome user data, not Lighthouse synthetic
- Server logs filtered to Googlebot user-agent — see what Google actually crawls, how often, and what errors it hits
- Search Console → Performance → Queries by page — find pages ranking just outside the top 10 for valuable queries (the "page 2 gold" report)
The 80/20 if you can only do one thing
If you only have time for one initiative this quarter: fix your LCP and indexable HTML rendering. Together they unlock 60–80% of the organic potential of most SaaS sites we audit.
Everything else is incremental. These two changes move the floor of every page.
If you'd like a free technical SEO audit on your SaaS — we'll send you a prioritised findings report within 7 days — tell us your domain.