Technical SEO for SaaS Platforms: Handling Dynamic Routes & JS

The SPA SEO Nightmare

Googlebot has improved at rendering JavaScript, but it's not perfect. If your marketing site is built on the same React app as your dashboard, you risk key content not being indexed.

1. Server-Side Rendering (SSR) vs. Client-Side Rendering (CSR)

• CSR: The browser builds the page. Googlebot might see a blank page.
• SSR (Next.js): The server sends full HTML. Google loves this.
• Recommendation: Use Next.js or Astro for your marketing pages. Keep the app on CSR if needed (behind the login).

2. Managing "App" Subdomains

• app.yourdomain.com: Should be noindex. You don't want Google crawling your user's private dashboards.
• www.yourdomain.com: This is for SEO.

3. Canonicalization of Features

SaaS platforms often have duplicate pages for similar features.

• Page A: "Time Tracking for Agencies"
• Page B: "Time Tracking for Consultants"
• Solution: Ensure unique content on both. If they are 90% identical, canonicalize to a main "Time Tracking" page or rewrite them to be distinct.

4. International SEO (Hreflang)

SaaS is global.

• Strategy: If you target French users, use fr.yourdomain.com or yourdomain.com/fr.
• Hreflang: Implement tags to tell Google "This is the French version of this page."

Check out our Technical SEO Audit Prompts for a checklist.

Conclusion

Don't let your tech stack kill your rankings. Engineering and Marketing must collaborate on the architecture.