Localized Pathnames Based on Default Locale with Mixed Routing Support

[barmiedev]

Is your feature request related to a problem? Please describe.

Yes. I want to expand my product to new territories, but I need SEO and analytics to remain consistent and coherent across all markets. Ideally, I’d like to maintain a single codebase with domain + prefix-based navigation to manage different countries efficiently—while still allowing users to switch between languages within each location.

Describe the solution you'd like

I’d love the ability to define localized pathnames that are mapped to a default locale. For example, if the default locale is English, and other available languages are Polish and Czech, the pathnames would look like this:

// Pathnames mapping
'/diets': {
  en: '/diets',
  pl: '/diety-pudelkowe',
  cz: '/diety-krabickove',
},
'/cart': {
  en: '/cart',
  pl: '/koszyk',
  cz: '/kosik',
},
'/checkout': {
  en: '/checkout',
  pl: '/zamowienie',
  cz: '/objednavka',
},

Additionally, I’d like to configure both domain-based and prefix-based navigation.

Example scenarios

When visiting my-site.com (English default):

• my-site.com/diets
• my-site.com/cart
• my-site.com/pl/cart
• my-site.com/cz/checkout

When visiting my-site.pl (Polish default):

• my-site.pl/diety-pudelkowe
• my-site.pl/koszyk
• my-site.pl/en/koszyk
• my-site.pl/cz/zamowienie

When visiting my-site.cz (Czech default):

• my-site.cz/diety-krabickove
• my-site.cz/kosik
• my-site.cz/en/kosik
• my-site.cz/pl/objednavka

Summary
I’m looking for a feature where pathnames are always associated with the default locale of a given deployment (e.g. .com, .pl, .cz), and language switching happens within that context - without changing the entire route structure to match the new language. This approach ensures SEO consistency, a clean user experience, and better tracking alignment across internationalized versions of the site.

Describe alternatives you've considered

I'm thinking about some function to wrap the pathnames, but no decision yet.

[amannn]

next-intl assumes that a locale is only available via a single URL, so either my-site.com/pl or my-site.pl.

You can however work around this limitation with custom prefixes to hide e.g. a regional variant. This can be used to enable the same locale on multiple domains (see the announcement blog post).

I'll move this to a discussion since it seems to be a usage question.

[barmiedev]

Those prefixes and domains are working perfectly!

My question though is more about navigation/pathnames - I have several deployments of my app (with different environment variables, APIs etc), and I'd love to bind default language on a specific domain (so for example if domain is my-site.pl then the default language is pl) with a set of pathnames. So if the default language is pl I will have Polish pathnames on all languages - preferably with the usage of the current intl navigation (without dividing pathnames to separate objects).

So:

• my-site.pl/diety
• my-site.pl/en/diety
• my-site.pl/cz/diety

And when going to my-site.com:

• my-site.com/diets
• my-site.com/pl/diets
• my-site.com/cz/diets