Any recommended way how to add canonical and alternate meta tags?

[tixyAppAdmin]

Seems to me that the only way to add canonical and alternate tags would be to create generateMetatags function for every page component in the app which would be a bit tedious work and create lot of boilerplate.

[amannn]

What kind of canonical and alternate meta tags are you looking for?

Note that next-intl already informs search engines about the different languages a given page supports:

In addition to handling i18n routing, the middleware sets the link header to inform search engines that your content is available in different languages.

(from the middleware docs)

[amannn]

Hmm, I haven't encountered that issue so far. What's important is that Google is able to access /de and not being redirected away if accept-language doesn't match this path. If you use a default configuration for the next-intl middleware, that should be the case.

Is the site you're talking about this one: https://www.massif.ch? One thing I've noticed is that there are separate entries for /en and /de in the sitemap. Maybe consolidating them to one entry could help? I also found that if I search for site:https://www.massif.ch/de/ on Google that a few pages already show up.

(Really cool website btw. 👏)

[ynamite]

That's the one :) thanks a lot, glad you like it.

Google recommends this structure for multilingual sitemaps (source), at least as far as I understood it.

Yeah, the page is being indexed, but I just find it weird that Search Console views /de/ as duplicate content and sets the canonical URL to / 🤷

While it probably doesn't make a big difference, it would be nice to be able to set localized canonical URL tags.

P.S. I love next-intl. Initial setup was super easy and once I got the hang of it, everything else was a breeze too! ❤️

[amannn]

A sitemap with alternate entries is absolutely fine, what I meant is that you have two entries that both point to your home page:

[ynamite]

I know, but as far as I understood the information from Google regarding sitemaps, this is the way it should be done.
One URL points to /en/, including all alternates (even one pointing to itself).
The other points to /de/, again including all alternates (even one pointing to itself).
I'm not entirely sure if this is correct though.

[amannn]

Oh, you're totally right—I overlooked this part:

Therefore if you have 3 versions of a page, your sitemap will have entries for the URLs of each version, and each entry will have 3 identical child entries.

Also the sample below confirms this.

Interesting, I should probably update the sitemap docs to reflect this. Many thanks for the heads-up!

[ynamite]

Glad to help!