Angular Builds That Search Engines Can Read

A frequent fault in Angular SSR apps: the server builds the page, then the browser asks the API for the same data again while hydrating. Crawlers end up paying for both trips. TransferState writes the server's response into the HTML so the client reuses it, which also stops content from blinking out and back during hydration.

- ngOnInit() { this.http.get(url).subscribe(...) }
+ // resolver writes to TransferState on the server
+ const cached = transferState.get(KEY, null)
+ if (cached) return of(cached)

Standalone components did away with NgModules, and `@defer` now covers most custom lazy loading with a simple trigger. Content below the fold loads when it scrolls into view, so the first bundle shrinks without complicated route splitting. The placeholder is rendered on the server, which keeps that content in the HTML crawlers read.

Large teams like Angular because many routine decisions are already made: strict TypeScript, dependency injection and a router with typed guards and resolvers. When several teams share one codebase, that consistency matters more than benchmark scores. SEO logic lives in resolvers with unit tests instead of being spread across components.

export const routes: Routes = [{
  path: 'p/:slug',
  resolve: { product: productResolver },
  canActivate: [publishedGuard],
}]