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]

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!

[amannn]

@ynamite I just had a minute to fix the sitemap example in the docs: #1712. I'll check again in the future if this has any effect on which pages of the App Router example are indexed on Google.

Many thanks again for bringing this up, I totally missed this when setting up the example!

[ynamite]

@amannn sure thing, glad to be able to contribute a bit!
Will be interesting to see if indexing remains unchanged or not. So long!

[ynamite]

Glad to help!