SSR vs prerender vs client-render for pSEO templates

SSR vs prerender vs client-render for pSEO templates

Rendering choice is a crawl-budget and index-speed decision. Match the method to the page tier:

1. Money templates (high-volume, revenue-bearing) → server-side render. Owner-action: HTML must contain the full content on first byte. Gate: curl the URL, confirm body text present without JS.
2. Mid-tier templates at 10k+ scale → static generation + incremental rebuild. Gate: rebuild time per page under what your publish cadence allows.
3. Low-tier / rarely-changing → prerender cache (serve bots a snapshot). Gate: snapshot age under 7 days.
4. Never ship client-only render for pages you want indexed fast. Googlebot defers JS; Bing and most AI crawlers barely run it at all.
5. Guardrail: test with the URL Inspection live test, not just local. Rendered vs crawled HTML must match.

Rollback: keep the prior rendering path behind a flag for one release cycle.

Ship gate: don't publish until all boxes are checked.