Skip to content
Orino Docs

CSR-only Nuxt page

What this means

Section titled “What this means”

This page calls definePageMeta({ ssr: false }), which turns off server-side rendering for the route. Nuxt renders it entirely in the browser instead.

Nuxt is a universal (SSR) framework by default: the server renders the full HTML on the first request, so crawlers and AI systems get real content. With ssr: false, the server sends an almost-empty shell and the page only fills in once JavaScript runs. Googlebot can execute JavaScript, but it does so on a delayed second pass and not reliably — and most AI crawlers (GPTBot, ClaudeBot, PerplexityBot) do not run JavaScript at all. To them the page looks blank.

How to fix it

Section titled “How to fix it”

In almost all cases the fix is to remove the ssr: false flag so the page renders on the server like the rest of your site.

pages/dashboard.vue
<script setup>
// Remove this — it disables SSR for the whole route:
// definePageMeta({ ssr: false })
</script>


<template>
  <main>
    <h1>Dashboard</h1>
    <!-- content -->
  </main>
</template>

If a specific piece of the page genuinely cannot run on the server (for example, it touches window or a browser-only library), keep the page server-rendered and isolate just that part in a <ClientOnly> wrapper instead of disabling SSR for the entire route.

<template>
  <main>
    <h1>Dashboard</h1>
    <p>This heading and copy are server-rendered and indexable.</p>


    <ClientOnly>
      <BrowserOnlyWidget />
      <template #fallback>
        <p>Loading…</p>
      </template>
    </ClientOnly>
  </main>
</template>

Controlling rendering per route

Section titled “Controlling rendering per route”

If you need different rendering modes across your site, use routeRules in nuxt.config.ts rather than scattering ssr: false across pages. This keeps public, indexable routes server-rendered while allowing client-only or prerendered behaviour where it makes sense.

nuxt.config.ts
export default defineNuxtConfig({
  routeRules: {
    '/': { prerender: true },        // static, fully rendered
    '/blog/**': { swr: 3600 },       // server-rendered, cached
    '/app/**': { ssr: false },       // private dashboard — fine to be client-only
  },
})

Only disable SSR for routes that are not meant to be indexed (authenticated dashboards, internal tools). Public marketing and content pages should always be server-rendered.

Verify the fix

Section titled “Verify the fix”

Fetch the page and confirm the real content is in the initial HTML, not just a loading shell:

Terminal window
curl -s https://yourdomain.com/your-page

You should see your actual headings and copy in the response body. Then re-run the audit:

Terminal window
npx orino-cli audit

The nuxt-csr-page check should now pass.

Section titled “Related fixes”