Deploy a Nuxt app as a static website

Nuxt supports server-rendered applications and static generation. Use static generation when routes can be rendered at build time and the deployed site only needs a web server for HTML, CSS, JavaScript, and assets.

Generate the static site

Install dependencies and generate the production output:

npm ci
npx nuxt generate

Nuxt pre-renders routes and creates deployable static files in .output/public/. Upload the contents of that directory to HostRight's public directory.

If you use a purely client-rendered app, review the generated fallback pages and test unmatched routes. For pages that need complete HTML on first load, prefer pre-rendering the routes and data they need.

Make routes buildable

Every route that should appear in the static output must be discoverable or included in the prerender configuration. Data required during generation must be available to the build process. Do not put private API keys into public runtime configuration.

If a page needs request-time authentication, server-only data, server routes, or per-request personalization, deploy Nuxt through a Node.js application instead of static hosting.

Upload to HostRight

Add the domain to HostRight and upload the contents of .output/public/ into the domain's public directory.

Use Git or SFTP to repeat the deployment. Do not upload the source repository or node_modules when only the generated static output is required.

Test generated pages

Open the home page, every important route, assets, forms, metadata, canonical URLs, and 404 behavior. Test direct navigation and browser refresh from a nested path. Check that generated links use the correct domain and base URL.

Connect DNS and SSL

Point the domain to HostRight, wait for DNS to resolve, and provision SSL under Account Manager → SSL Certificates.

Nuxt static hosting is a good fit for marketing sites, documentation, blogs, portfolios, and content-heavy frontends. Use Node.js hosting for a live Nuxt server.