Next.js / Deploy
Step 19 of 23
Test and deploy the integration
Build the application, verify every public language, and publish reviewed content before sending multilingual pages to visitors.
Run the same production build locally or in continuous integration before deployment:
Terminal
pnpm build- ALTIFIED_SECRET_KEY is set in the hosting provider and is never public.
- ALTIFIED_PROJECT_ID and ALTIFIED_DEFAULT_LOCALE match the dashboard project.
- The root Next config is wrapped with withAltified.
- Literal copy translates in Server Components and falls back to source text safely.
- Client Components and dynamic values use an explicit server translation flow when needed.
- Default and target-language URLs render the same route in the selected language.
- The published switcher preserves nested paths and works on desktop and mobile.
- Translations have been reviewed and terminology has been added to the glossary.
- Localized metadata uses the production origin and correct canonical URL policy.
- pnpm build or npm run build completes successfully.
After deployment, visit representative routes in the default language and every target language. Test a top-level page, a nested dynamic route, a missing translation fallback, and a language change on the deepest route.
Safe rollout
Publish one target language first if the site is large. Review its registered strings, glossary behavior, routing, metadata, and cache behavior before enabling the remaining languages.