Skip to content
Discussion options

You must be logged in to vote

From the next-intl docs about localePrefix: 'never':

If you’d like to provide a locale to next-intl, e.g. based on user settings, you can consider setting up next-intl without i18n routing. This way, you don’t need to use the routing integration in the first place.

However, you can also configure the middleware to never show a locale prefix in the URL…

In this case, requests for all locales will be rewritten to have the locale only prefixed internally…

Alternate links are disabled in this mode since URLs might not be unique per locale. Due to this, consider including these yourself, or set up a sitemap that links localized pages via alternates.

What that means for your SEO questions:

  1. S…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@andrewLapshov
Comment options

Answer selected by andrewLapshov
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants