Nuxt in practice: SEO-friendly static generation
Use Nuxt nitro preset:static to pre-render an entire Vue application as pure static HTML, ideal for edge distribution.
Quick answer
How is Nuxt different from plain Vue?
Nuxt gives you routing, rendering strategy, and SSR/SSG out of the box. Plain Vue needs you to assemble the build chain yourself.
Machine-readable page data: /data/vue-practical.json
In-depth analysis
Nuxt is Vue meta-framework, hybrid by default and first-class for static generation. nuxt generate or nitro preset:static produces pure static HTML, ideal for edge distribution. Three steps: (1) set nitro.preset=static in nuxt.config; (2) use useAsyncData to fetch server-side data into the pre-render; (3) nuxi generate to produce dist. Bottom line up front: for SEO-friendly static sites in the Vue ecosystem, Nuxt is the lowest-friction choice. Common pitfalls are leaving ssr:true without switching to the static preset (production ends up needing a server), and SSR/CSR environment variable mismatches causing hydration failures.
// nuxt.config.ts — full-site static generation
export default defineNuxtConfig({
ssr: true,
nitro: { preset: 'static' },
});
// Build: nuxi generateVue/Nuxt Overview · Key takeaways
- Tech choice and boundaries confirmed
- Core config in place
- Locally verified
- Postmortem notes recorded
FAQ & pitfalls
Can Nuxt do pure static?
Yes — nitro preset static or adapter-static pre-renders the whole site.
Explore the hub
See all 5 guides in Vue & NuxtSame category as this article, sorted across the codebase.
Vue/Nuxt architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of Vue/Nuxt's layering and data flow.
Vue/Nuxt best practices: engineering conventions for production
Field-tested Vue/Nuxt practices from production, avoiding the common anti-patterns.
Vue/Nuxt deployment guide: zero-ops edge publishing with Cloudflare Pages
Git-driven Vue/Nuxt deployment in practice: commit to build, atomic publish to every edge node.
Vue/Nuxt performance tuning: push first paint and edge response to the limit
Around Vue/Nuxt's real bottlenecks, an actionable LCP / INP / CLS checklist.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 02
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide → - 03
Why are _headers / _redirects not taking effect?
Both files must sit at the root of the output directory (dist/); anything under src/ is never uploaded. A purely static project should not add _worker.js either — that gives up the zero-cold-start advantage.
See the full guide →