SSR vs Client sided rendered
I am building a web app and have a server written in another language and want to write the frontend in vue/nuxt.
I'm having problems understanding SSR and where it should apply and where not.
In my case, an external api, where every page is protected, no public page.
If I understand correctly SSR servers the html and so the page gets rendered as a static site which in turn turns up the SEO, absolutely great for public sided pages, but what about protected pages?
Is it in my best interest to just turn of ssr for simplicity, e.g. all middleware etc.
I have one middleware which is just basic auth0 plugin and I'm using their provided login page.
Also there is no option in the setup to choose icelandic 🇮🇸
2 Replies
Hi @LordGhandi. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
You're correct in your understanding: Server-Side Rendering (SSR) in Nuxt means the server generates the HTML for each page request, which is great for SEO and initial load performance—especially for public-facing pages. For protected, authenticated-only pages (like dashboards or internal tools), SSR is often less critical, since SEO is not a concern and all content is behind authentication.
When to use SSR:
- Public pages that benefit from SEO, fast initial load, and accessibility.
- Content that should be indexable by search engines or shared on social media with rich previews.
When to use Client-Side Rendering (CSR) / SPA mode:
- All pages are protected and require authentication.
- SEO is not a concern.
- You want to simplify your setup (no need for SSR middleware, session handling on the server, etc.).
In your case, since every page is protected and you use Auth0 for authentication, it is reasonable and common to disable SSR for simplicity. This way, your Nuxt app will behave like a classic Vue SPA, and you can host it on any static hosting provider. You can do this by setting
The knowledge sources do not mention anything about language selection or Icelandic support in the Nuxt setup. If you need internationalization (i18n), you can use the Nuxt I18n module, but there's no information in the provided sources about Icelandic specifically. Summary:
- For protected, non-public apps, disabling SSR is a good choice for simplicity. - SSR is mainly beneficial for public, SEO-sensitive pages. - No info in the sources about Icelandic language selection in the setup. If you need more details on how to set up SPA mode or i18n, let me know! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
ssr: false in your nuxt.config.ts:
Client-Side Rendering
This approach removes the need for server-side middleware and makes deployment and development simpler, especially when your backend is a separate service in another language. Just ensure your authentication flow works fully client-side (which Auth0 supports).
On Icelandic language support:The knowledge sources do not mention anything about language selection or Icelandic support in the Nuxt setup. If you need internationalization (i18n), you can use the Nuxt I18n module, but there's no information in the provided sources about Icelandic specifically. Summary:
- For protected, non-public apps, disabling SSR is a good choice for simplicity. - SSR is mainly beneficial for public, SEO-sensitive pages. - No info in the sources about Icelandic language selection in the setup. If you need more details on how to set up SPA mode or i18n, let me know! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
<@358749735323959308> Kapa.ai is still learning and improving, please let me know how I did by reacting below.