Next.js localization

Next.js localization with Altified

Install the Altified Next.js SDK to translate frontend copy, dynamic content, metadata, and public language routes from your existing App Router application.

Next.js setup
pnpm add @altified/next
altified init
Localized App Router

The initializer creates the integration files, then your application continues using its existing pages and components.

/ The short answer

The Next.js SDK adds the wiring that connects your application to Altified: a server client, locale routing, automatic static copy translation, explicit dynamic content helpers, and localized metadata support.

/ 01

Install the package

Add @altified/next and run the initializer from your Next.js project root.

/ 02

Connect the project

Add the project ID, server secret, and default locale in your server environment.

/ 03

Translate content

Automatic frontend copy and explicit dynamic values resolve for the selected locale.

/ 04

Publish language routes

Use the proxy and metadata helpers to serve localized paths and search-ready page details.

/ Why it matters

A localization workflow that belongs inside your product.

Automatic static copy

Translate safe Server Component copy and common text props without wrapping every string manually.

Locale routing

Serve paths such as /fr/products/25 through your existing App Router pages.

Localized metadata

Translate titles, descriptions, Open Graph fields, canonical URLs, and alternate-language links.

Dynamic content helpers

Resolve stable keys for database records, CMS fields, runtime values, and API-backed content.

/ Frequently asked questions

Questions teams ask before localizing.

Does Altified work with the Next.js App Router?

Yes. The Next.js SDK is designed for App Router applications and supports server-rendered copy, locale-aware routes, dynamic content, and translated metadata.

Do I need to wrap every string manually?

No. Safe static copy can be discovered automatically, while database values, API responses, and other runtime content use explicit stable translation keys.

Can localized pages keep their own SEO metadata?

Yes. Each locale can serve translated titles, descriptions, Open Graph fields, canonical URLs, and alternate-language links from your application.