Jan Amann

Sorry, I can't follow. Can you elaborate on what the issue is and maybe include some screenshots?

@jlalmes Can you provide a screenshot from the Google Search Console issue that shows the issue? Maybe I was a bit too naive to think that this isn't an issue...

Hmm, I see—thanks! Is maybe `localePrefix: 'always'` a viable workaround for you for the time being? I'll look into getting this fixed for `localePrefix: 'as-necessary'` though, but I can't promise...

**Small update:** The factory functions for navigation APIs that are being worked on in #426 could help to mitigate this for `localePrefix: 'as-necessary'`. However, as soon as the user introduces...

That's a good point actually. Based on [your use case](https://github.com/amannn/next-intl/issues/647#issuecomment-1829489531), in https://github.com/amannn/next-intl/commit/18157bc255c0f278e85569c9e367f40d5806b0c1 I've added a note that `localeDetection: 'never'` is also useful if you have locales per domain. With that,...

Sounds good! I've started working on an implementation.

@zipme I've addressed your use case in https://github.com/amannn/next-intl/pull/678, this should help! In regard to this issue: As a second step, if the navigation APIs would accept `domains` (like the middleware),...

Replied here: https://github.com/amannn/next-intl/issues/653#issuecomment-1905948937

Yep, I ran into this too: https://github.com/amannn/next-intl/issues/718#issuecomment-1856252053, see also: https://github.com/vercel/next.js/issues/56531. It seems like [there's some progress being made in this area](https://github.com/vercel/next.js/issues/56531#issuecomment-1927533401), so hopefully this gets resolved soon. We can leave...

Hey @Robin-Ln, sorry I wasn't able to look into this PR deeper yet. Upgrading to Auth.js v5 is certainly something I'm looking for, but since the stable release hasn't been...