Convert pathname

[MathiasSvDK]

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

Not really a problem

Describe the solution you'd like

It would be great for SEO to be able to convert the current path from the default langauge to xx langauge the user has.
It would be very much needed for <link rel="canonical"

Describe alternatives you've considered

None

[MathiasSvDK]

What i request is like in localized pathname:
https://next-intl-docs.vercel.app/docs/routing/navigation
Be able to retrieve the current localized path from the URL into the html to be able to create the <link rel="canonical"

[amannn]

Can you elaborate on what kind of canonical link you have to render on your page and why it is necessary?

Note that the next-intl middleware sets the link header for you that provides hints to search engines about different language versions of your page.

[MathiasSvDK]

We have an issue with google thinking that our .com domain is a copy of .dk (That they don't "work" together).
The pages are identical but translated and we need to let google know that they are the same.

Maybe i am doing it wrong? Do you have any knowledge about this?

[amannn]

Do you have alternateLinks enabled in the next-intl middleware?

Please refer to the docs, there's also a link to Google documentation that explains how the link header works.

[MathiasSvDK]

I don't have it disabled.
I found in the docs, as you linked that it says "Defaults to true" - so i assume it's enabled by default?

[amannn]

Yes.

[MathiasSvDK]

Any suggestion to how i then can fix this issue?

[amannn]

Sorry, I'm not sure what the issue is. As mentioned, the middleware returns alternate links, therefore there's no need for canonical links (which shouldn't be used for language versions anyway).

I'll convert this to a discussion since it's a usage question, I hope you understand.