How to make multilingual tags in sitemap link with hreflang like article translations?

support
1

Hi Hugo community,

I’m working on a multilingual Hugo site, and I noticed an issue with tags in the sitemap. Each article has tags in its own language, for example:

Article 1 (en):

title: "Performance Optimization"
tags: ["Performance", "Tech"]

Article 2 (es):

title: "Optimización del Rendimiento"
tags: ["Rendimiento", "Tecnología"]

The sitemap correctly lists the tag pages, but there is no <hreflang> linking between corresponding tags. That means “Performance” and “Rendimiento” (or “Tech” and “Tecnología”) are treated completely separately, even though they belong to translated articles.

My question:
Is there a way to configure Hugo so that the sitemap reflects the relationship between multilingual tags based on the articles they belong to? Ideally, I’d like the sitemap to indicate which tags correspond across languages, similar to how article translations use <hreflang>.

Environment:

  • Hugo version: v0.148.2

  • Theme: hugo-theme-yue

Thank you for any advice or examples!

2

You are more likely to receive a prompt and accurate response if you post a link to your project’s Git repository.

See Requesting Help.

Let us see your code

Include a link to the source code repository of your project, because we really need the context of seeing your templates and partials to be able to help you. It is trivial to do a quick git clone on your repo, then run hugo server in your project, to help you out. On the other hand, recreating your code from screenshots, or sort of guessing at it, is not.

If you can’t share your repository for whatever reason, consider creating a dummy repo that you can share, which reproduces the problem you’re experiencing.

3

This example might be helpful:

git clone https://github.com/jmooring/hugo-multilingual-example
cd hugo-multilingual-example
npm i
hugo
cat public/de/sitemap.xml

See the README for a description of the approach used to translate terms, both the title and publication path.

5

Hello jmooring,

Thanks a lot for your reply and help! I tried the hugo-multilingual-example you shared, and it works exactly as expected — multilingual tags with the same meaning are correctly linked in the sitemap.

However, in my case (https://github.com/zhaozhaohong/example-for-hugo-theme-yue), it doesn’t behave the same way. I’m not sure why — perhaps the theme doesn’t support it?

6

I understand, thank you. “hugo-multilingual-example” also created separate multilingual content files for the ‘tags’ taxonomy, while “hugo-theme-yue” did not.
Website A: In the content/tags/ directory, _index.[language code].md files were created for each language version of every tag (e.g., content/tags/green/_index.en.md and content/tags/grün/_index.de.md). This file naming convention explicitly tells Hugo that the tags ‘green’ and ‘grün’ are translations of each other. This is key for tags to get hreflang associations.
Website B: Did not create such _index.[language code].md files in the content/tags/ directory to explicitly associate tag translations. Therefore, although the articles themselves have translation associations, the tags, as an independent taxonomy, did not receive this explicit cross-language signal, so their sitemap does not include hreflang.
Simply put, the .[language code].md association for articles only applies to the articles themselves. Tags require their own _index.[language code].md files to establish cross-language associations. “hugo-multilingual-example” did this, “hugo-theme-yue” did not.

7

I don’t understand. Do you still have a question?

8

No problem, everything is fine. Thank you for your help. The issue was because I hadn’t created a ‘tags’ directory in my own instance to use as the “translationKey.”

1 Like
9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.