GuidesWeb technical choices

SSR, SSG, SPA: the differences, and the SEO impact

By the Banzai Labs teamUpdated on 3 min read

SSGAt build timeSSROn each visitSPAJSIn the browser
SSG: the page is built at build time. SSR: on each visit. SPA: in the browser.

Three ways to build a page

Mode When the page is built Ideal for
SSG (static) Once, at build time Showcase site, blog, documentation
SSR (server) On each visit Personalised or fast-changing content
SPA (single page) In the browser Logged-in tool, dashboard

Impact on speed and SEO

  • SSGFastest, simplest to rank. You rebuild to publish.
  • SSRAlways up to date, well indexed. A server must answer fast.
  • SPAVery smooth once loaded. An empty page for a crawler that does not run JavaScript.

The right habit

Pages that must be found (home, offers, guides, product pages) as static or SSR. Screens behind a login as SPA.

This site, for example, is generated statically with Astro. See also Website, web app, PWA, native app and Core Web Vitals.

Frequently asked questions

Is a SPA bad for SEO?
Google can run JavaScript, with a delay and no guarantee. Many AI crawlers do not. For content you want found, server or static rendering is better.
Can modes be mixed?
Yes. Current frameworks (Astro, Next.js, Nuxt) allow static pages, others rendered on demand, and interactive islands.
Which is cheapest to host?
Static: plain files, served by a CDN or a small server.

Read next

All guides