---
title: "Comment by Jonas on \"From CSR to SEO-Friendly SSG + CSR in an Existing Vite App (Using Vike)\" | Hashnode"
description: "Solid path if you want crawlable HTML without bolting on a full SSR runtime. Keeping CSR for the app shell and SSG for the public pages is a sane split. Win con"
url: "https://hashnode.com/posts/from-csr-to-seo-friendly-ssg-csr-in-an-existing-vite-app-using-vike/69c55f9c10e664c5daf9927b/comment/6aa41d267411afb20c713b12"
---

[Discussion](https://hashnode.com/posts/from-csr-to-seo-friendly-ssg-csr-in-an-existing-vite-app-using-vike/69c55f9c10e664c5daf9927b)

Comment [From CSR to SEO-Friendly SSG + CSR in an Existing Vite App (Using Vike)](https://hashnode.com/posts/from-csr-to-seo-friendly-ssg-csr-in-an-existing-vite-app-using-vike/69c55f9c10e664c5daf9927b)

[Jonas](https://hashnode.com/@jonasb)

[Sep 11](https://hashnode.com/posts/from-csr-to-seo-friendly-ssg-csr-in-an-existing-vite-app-using-vike/69c55f9c10e664c5daf9927b/comment/6aa41d267411afb20c713b12)

Solid path if you want crawlable HTML without bolting on a full SSR runtime. Keeping CSR for the app shell and SSG for the public pages is a sane split.

Win condition for me is still the same: body and meta in the first response. AI crawlers that skip JS don't care that Vike is clever if the HTML is thin.

After you ship, I'd curl a few routes and confirm the body actually filled, not only titles.
