How to SSR dynamic routes in Vue 3 without generating static HTML for every URL?

[AnkitaKhokhar-1]

I'm working on a Vue 3 app using Vue Router, Express, and @vue/server-renderer. Fixed public pages are already prerendered, but dynamic pages still rely on API calls inside mounted(), so their content isn't available when JavaScript is disabled.

I have two cases:

Blogs: /blog/:blogTitle/:blogId

Company profiles: Around 70–80k URLs currently, potentially millions.

My Express server already fetches blog data for SEO metadata, but the Vue component fetches the content separately.

What's the best way to render these dynamic pages as HTML on the server while keeping Vue interactivity? Can I reuse my existing SSR setup without generating static HTML for every URL? I want my content to be visible when js is disabled.

[nicholas-greenwood]

yes, you can reuse your express + vue ssr setup. render the requested url when the request arrives, rather than generating a file for every possible url

your express handler already fetches the blog data for metadata, so i'd pass that same result into the vue page. mounted() doesn't run during ssr, which leaves that client-fetched content out of the server html

for each dynamic-page request:

1. create a fresh app, router and state to avoid leaking data between requests. use createMemoryHistory() on the server, install the router, then await router.push(req.originalUrl) and await router.isReady()
2. reuse the blog fetch, or fetch the profile in the handler. put the result into that request's state for the component to render, then await renderToString(app) and insert the html into your page shell
3. embed the initial data using an html-safe state serialiser, including only fields intended for the browser
4. on the client, create a new app with createSSRApp(), install the router and restore that state before rendering. await router.isReady(), then app.mount('#app'). skip the initial fetch when that route's data exists; keep fetching for later client-side navigation

the content is there without js; interactivity needs js. you can keep prerendering the fixed pages, though ssr server load and caching still need planning

[AnkitaKhokhar-1]

Thanks, It helps. I was reaching there with my R&D, but was not sure if it will work or not.
Will Update here later on with the solution, which works for me.