Platform

Translate Your Nuxt Site Into 20+ Languages

Skip the i18n engineering. Verbi translates your existing Nuxt site at the edge — no module to configure, no locale routing to wire up, no message files to maintain. A quick DNS change and you're multilingual.

Powered by tools you already trust

Any websiteWorks with your existing site, any platform
Translated by DeepLNatural, ranking-safe translations
Served by CloudflareCached at 300+ edge locations
Why Verbi for Nuxt

Multilingual Nuxt, Without the i18n Setup

Going multilingual in Nuxt usually means adding @nuxtjs/i18n, configuring locale routing, and maintaining a message file for every string — and you still source every translation. Verbi translates your shipped Nuxt site at the edge instead, with zero code.

  • No i18n module or refactor
  • Translations included, not just plumbing
  • Works with SSR, SSG, and hybrid rendering
DIY i18n setup
Verbi
Install & configure a module
A quick DNS change
Wire up locale routing
Subdirectory URLs handled
Maintain message files
Automatic with DeepL
You source the translations
Translations included
The problem

i18n Is an Engineering Project

Nuxt has a capable i18n module, but wiring it up is still real engineering — and you still have to produce every translation.

Setup and config

You add @nuxtjs/i18n, define your locales and routing strategy, set up lazy-loaded message files, and adjust links to use the localized-route helpers. It touches your config, routing, and components.

Ongoing maintenance

Every new string means updating the message files for each locale. The module handles routing and formatting — the translation content itself is still on you.

The Verbi approach

Every Language, Zero Engineering

Verbi sits in front of your Nuxt site as a reverse proxy. Your codebase stays exactly as it is — no module, no routing changes — and Verbi translates every page automatically, serving each language at a clean subdirectory URL with full SEO.

No i18n module or refactor

Verbi runs at the DNS level, so there's nothing to add to your Nuxt app — no @nuxtjs/i18n, no locale routing, no message files.

Translations included

DeepL translates your content automatically. You don't write or maintain locale files for every language.

Full SEO, handled

Subdirectory URLs, hreflang tags, translated sitemaps, and per-language meta tags — all automatic, so each version is eligible to rank.

Any rendering mode

Universal (SSR), static (nuxt generate), and hybrid routes are all translated the same way.

Setup in minutes

A quick DNS change. Pick your languages. You're live — no redeploy required.

Always in sync

Ship an update and translations update automatically on the next visit.

Why it matters

Speak Your Customers' Language

Going multilingual isn't just about language, it's about trust, conversion, and reaching markets your competitors skip.

76%

Prefer Their Language

of online users prefer to engage with products presented in their own language.

40%

Won't Convert At All

of consumers will never buy from a website that isn't in their native language.

70%

Higher Conversion

Localized sites can achieve up to 70% higher conversion rates than English-only alternatives.

Every Route and Every Page Covered

Verbi translates the rendered HTML, so static, server-rendered, and dynamically generated pages are all handled automatically.

/fr/

Marketing & Landing Pages

Hero copy, sections, social proof, and CTAs — everything a visitor sees first.

/fr/blog

Content & Nuxt Content

Articles and docs rendered from Nuxt Content or a CMS — translated on the fly.

/fr/docs

Documentation

Guides, references, and help content so international users can self-serve.

/fr/pricing

Pricing & Product Pages

Plan names, feature lists, and CTAs — the pages that convert.

/fr/dashboard

App & Dynamic Routes

Server-rendered and dynamic pages translated just like static ones — or exclude any path you want left untouched.

/fr/contact

Forms & Footer

Form labels, footer links, and help content so visitors can reach you in their language.

Under the hood

Built for How Nuxt Works

Verbi translates the HTML your Nuxt app already returns, so it fits any rendering mode without touching your code.

No @nuxtjs/i18n or refactor

Skip the module, locale routing config, and message files. Verbi works at the DNS level, so your pages and components stay exactly as they are.

SSR, SSG, and hybrid covered

Verbi translates the rendered HTML, so universal (SSR), static (nuxt generate), and hybrid route-rules pages are all handled the same way.

Exclude app routes

Keep marketing pages translated and leave /app or /dashboard untouched with a path exclusion.

Go Live in Three Steps

No code, nothing to rebuild. Your Nuxt site stays exactly as it is — Verbi adds the languages.

1

Point your domain to Verbi

Add a couple of DNS records. No code changes, no redeploy, no i18n module to install.

2

Choose your languages

Pick from 20+ languages in the Verbi dashboard. Verbi translates your whole site automatically with DeepL.

3

You're live

Your translated pages are served at yoursite.com/fr, /de, /es — each with full SEO. Ship updates and translations follow.

Nuxt Translation FAQ

No. Verbi works at the DNS level instead of inside your app, so there's no i18n module, locale routing, or message files to set up. You point your domain at Verbi with a couple of DNS records, pick your languages, and it serves translated versions of your existing site automatically.
Yes. Verbi translates the rendered HTML your app returns, so universal (SSR), statically generated (nuxt generate), and hybrid/route-rules rendering are all handled the same way.
Yes. Verbi translates the rendered page, so Nuxt Content, dynamic routes, and CMS-driven pages are all covered. It's framework-agnostic too — Vue, plain Vite, or any site that serves HTML on a domain you control works the same way.
No. Each language gets its own subdirectory URL (/fr/, /de/), translated meta tags, hreflang annotations, and a dedicated sitemap — the structure Google recommends. Each version is indexed separately and eligible to rank in its market.
Yes. You can exclude any path — like /app or /dashboard — so only the pages you want translated are served in other languages. Brand names and specific terms can be protected with the glossary too.

Start Reaching Customers
In Their Language

Add your first language in minutes. 14-day free trial, no changes to your site.

14-day free trial Live in minutes Cancel anytime