Translate Your Next.js Site Into 20+ Languages
Skip the i18n engineering. Verbi translates your existing Next.js or custom site at the edge — no library to wire up, no [locale] routing to build, no message files to maintain. A quick DNS change and you're multilingual.
Powered by tools you already trust
Multilingual Next.js, Without the i18n Build
Next.js dropped its built-in i18n config, so going multilingual means a library, middleware, and [locale] routing — and you still source every translation. Verbi translates your shipped site at the edge instead, with zero code.
- No i18n library or refactor
- Translations included, not just plumbing
- Works on any framework
i18n Is an Engineering Project
Next.js gives you the routing primitives, but going multilingual still means real engineering — and you still have to produce every translation.
You add an i18n library, configure middleware for locale detection, restructure routes under a [locale] segment, and wrap your app in providers. It’s a refactor that touches your whole routing layer.
Every new string means updating message catalogs across every language, and the middleware has edge cases. The translation content itself is still on you — the library only handles the plumbing.
Every Language, Zero Engineering
Verbi sits in front of your Next.js or custom site as a reverse proxy. Your codebase stays exactly as it is — no library, no routing changes — and Verbi translates every page automatically, serving each language at a clean subdirectory URL with full SEO.
No i18n library or refactor
Verbi runs at the DNS level, so there’s nothing to add to your codebase — no middleware, no [locale] segments, no providers.
Translations included
DeepL translates your content automatically. You don't write or maintain message 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.
Works on any framework
Next.js, Astro, SvelteKit, Remix, or plain HTML — if it serves a page on a domain you control, Verbi can translate it.
Setup in minutes
A quick DNS change. Pick your languages. You're live — no deploy required.
Always in sync
Ship an update and translations update automatically on the next visit.
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.
Marketing & Landing Pages
Hero copy, sections, social proof, and CTAs — everything a visitor sees first.
Blog & MDX Content
Articles and posts rendered from MDX or a CMS — translated on the fly.
Documentation
Guides, references, and help content so international users can self-serve.
Pricing & Product Pages
Plan names, feature lists, and CTAs — the pages that convert.
App & Dynamic Routes
Server-rendered and dynamic pages translated just like static ones — or exclude any path you want left untouched.
Forms & Footer
Form labels, footer links, and help content so visitors can reach you in their language.
Built for How Next.js Works
Verbi translates the HTML your app already returns, so it fits any rendering strategy without touching your code.
No library or [locale] refactor
Skip next-intl, middleware, and route restructuring. Verbi works at the DNS level, so your routing and components stay exactly as they are.
SSR, SSG, and ISR all covered
Verbi translates the HTML your app returns, so server-rendered, statically generated, and incrementally revalidated pages are all handled the same way.
Exclude your app routes
Keep marketing pages translated and leave /app or /dashboard untouched with a path exclusion — so only public-facing pages get localized.
Go Live in Three Steps
No code, nothing to rebuild. Your Next.js site stays exactly as it is — Verbi adds the languages.
Point your domain to Verbi
Add a couple of DNS records. No code changes, no redeploy, no i18n library to install.
Choose your languages
Pick from 20+ languages in the Verbi dashboard. Verbi translates your whole site automatically with DeepL.
You're live
Your translated pages are served at yoursite.com/fr, /de, /es — each with full SEO. Ship updates and translations follow.
Next.js Translation FAQ
Start Reaching Customers
In Their Language
Add your first language in minutes. 14-day free trial,
no changes to your site.