## What - Add SSR or build-time prerendering for the frontend, starting with unit pages. ## Why - The app is client-side rendered only, with no @angular/ssr setup. Content appears only after the browser runs the JS bundle. - Google renders JS, but on a delay and not on every crawl. Bing, social scrapers, and LLM crawlers often skip JS, so they see an empty shell. - Unit pages hold the main SEO content and are fairly static, which makes them a good prerender target. ## Notes - Angular 18 supports SSR and static prerendering through @angular/ssr. - Prerendering the unit routes at build is the lower-risk option. Full SSR fits if pages need per-request data. - This is the largest SEO change. Scope it on its own.
What
Why
Notes