INTRO
“We already know React” is not a reason to ship a client-only SPA as your company website. For content, SEO, and first paint, Next.js (or similar) usually wins. Here is the decision frame I use with buyers.
Hidden costs of a marketing SPA
Empty HTML shells hurt LCP and social previews unless you add SSR/prerender later — often more work than starting with App Router.
Routing, metadata, and OG tags become bolt-ons instead of first-class.
When Next.js is the default
Public pages, blogs, hire/services intent, and case studies want unique titles, canonicals, and fast HTML. App Router metadata APIs fit that job.
Keep interactivity as islands: forms, calculators, light motion — not the whole tree as `"use client"`.
When a SPA is still fine
Authenticated product shells behind login, internal tools, or apps where SEO is irrelevant.
Even then, a Next.js app with authenticated routes can host both marketing and product without two repos — if you design boundaries carefully.
KEY TAKEAWAYS
“Marketing sites rarely need SPA-first.”
- 02
Metadata and LCP are product requirements.
- 03
Use SPA patterns where SEO does not matter.
CONCLUSION
Closing thought
Rebuilding a React SPA marketing site on Next.js? Send the current URL via Contact for a scoped migration plan.
CONTINUE
Related pages
UP NEXT
Vercel vs VPS for a Next.js SaaS — How I Choose
A practical hosting decision guide for Next.js SaaS: when Vercel is enough, when you need a VPS/API host, and how to avoid premature devops.
Read next article