SaaS Application Architecture: Separating Public SEO Funnels From Logged-In App Shells
Bundling your marketing homepage inside the same monolithic dashboard SPA forces every Googlebot and prospect to download megabytes of workspace code. Decoupling the public edge shell multiplies speed and signups.
Dmitry K., Technical SEO Lead · SEO Space
Indexation benchmark targets
- Public shell
- Static/SSR on primary root domain
- App workspace
- /app/* or app.domain authenticated SPA
- Signup handoff
- Shared session cookie + instant redirect
- Docs & tools
- Publicly indexable calculator funnels
Why Monolithic Dashboard SPAs Hurt Both Product Velocity and Acquisition
Early startups frequently ship their landing page, pricing table, and interactive workspace inside a single Create-React-App or Vite SPA bundle. Prospects hitting the homepage download chart libraries and state stores before reading a single headline, while marketing edits require full application QA.
Routing the root domain through fast edge-cached SSG/SSR while isolating authenticated workspaces on app.domain or /app/ lets marketing ship daily without risking workspace stability.
When early engineering teams build an MVP in Vite + React or an authenticated Next.js client workspace, putting `/` through `/settings` behind the same SPA router starves the business of compounding organic acquisition later. Fixing routing separation two years in requires tricky reverse-proxy surgery.
Architecture anti-pattern
Do not serve the marketing homepage and pricing page inside the same 800 KB dashboard webpack/vite bundle. Every anonymous visitor pays the CPU and download penalty of workspace charting and auth libraries they have not logged into yet.
- Serve marketing pages, pricing matrices, integrations, and public docs on the primary root domain with X-Robots-Tag clean defaults.
- Apply X-Robots-Tag: noindex, nofollow cleanly on authenticated /app/* workspace shells.
- Redirect authenticated sessions smoothly from / to the workspace via fast edge cookies—while leaving bots on public HTML.
Edge Routing Rule Preserving Search Crawl & Logged-In UX
Check session presence only when strictly appropriate while keeping public bots on full marketing HTML.
// Cloudflare Worker edge split example
export default {
async fetch(req: Request): Promise<Response> {
const url = new URL(req.url);
if (url.pathname.startsWith('/app/')) {
return fetch(APP_ORIGIN + url.pathname + url.search, req);
}
return fetch(PUBLIC_SSG_ORIGIN + url.pathname, req);
},
}; Clean Boundary Between Growth Surface and Product App
Define crisp ownership across repositories and routing prefixes.
| Surface Layer | Hosting & Stack | Indexation Policy |
|---|---|---|
| Marketing, Pricing & Blog | Astro SSG on Cloudflare / CDN | Indexable, fast HTML, Schema @graph |
| Public API Docs & Calculators | SSG + lightweight interactive islands | Indexable high-intent acquisition hooks |
| Authenticated SaaS Dashboard | React/TypeScript SPA + PostgreSQL API | Auth-gated + X-Robots-Tag: noindex |
Connecting Public Documentation, Calculators & App Deep Links
High-performing SaaS products turn documentation pages, integration directories, and interactive ROI/schema tools into organic entry doors sitting directly on the primary root domain (`/tools/`, `/integrations/`, `/docs/`). Authenticated sessions stay isolated cleanly under `/app/` or `app.domain` tagged `noindex`.
Database Telemetry, Webhooks & Conversion Attribution
Keep anonymous landing attribution intact when a visitor crosses from static marketing into sign-up and mobile onboarding.
- Pass initial landing route and UTM/referrer context cleanly into first-party signup cookies or workspace onboarding payloads.
- Serve `apple-app-site-association` and `assetlinks.json` from `/.well-known/` if shipping companion iOS/Android apps.
- Rate-limit unauthenticated public API endpoints cleanly while excluding verified search bots from HTML page throttling.
Need this indexation setup audited on your domain?
Send your website URL. We check raw HTML parity, log crawl hits, canonical discipline, and sitemap architecture manually within 24 hours.