Next.js App Router Internationalization (i18n)
You can pick from two options when setting up an app with next-intl and Next.js’ App Router, depending on if you’d like to use unique pathnames for every language that your app supports.
With i18n routing→Without i18n routing→
Uses a top-level [locale] segment for prefixed pathnames like /en/about
or domain-based routing like en.example.com/about
Useful if you’d like to provide a locale to next-intl, e.g. based on user
settings, or if your app only supports a single language
To get a sense of what kind of setup you’d like to use, you can also explore the example apps.