[Sitemap] Control which languages end up in the sitemap, instead of including all.

[sayedbs]

Bug report for Strapi 5 multiple locales where I have configured only one locale

• For a single language, everything works as expected.
• When using multiple languages, the URLs are not generated correctly. Example:
  • I created an article with the German localization article-one-de.
  • Then I added a new localization for Australia (de_AT).
  • In the sitemap, the German URL appears correctly: http://localhost:3000/de/articles/article-one-de
  • However, the Australian URL appears incorrectly with an unknown/placeholder value, like: http://localhost:3000/de_AT/articles/bmrook-3-k-4-hk-670-yquxy-36-s-0-p
• When I manually edit the Australian URL to the correct value (e.g., article-one-for-at), it also automatically changes the German URL to match (article-one-for-at), which is incorrect.
  The system seems not to allow saving different slugs/URLs per localization — any change affects all languages simultaneously.

Steps to reproduce the behavior

• Add a new entry for any content for multiple localize
• goto to the sitemap webtool addon
• click to re-generate
• Open the sitemap table on click, and Go to the sitemap or open localhost:/api/sitemap/index.xml
• Find the slug/id ( you see the random value instant of the actual slug 'k-4-hk-670-yquxy-36-s-0-p`

Expected Behavior:

• Each localization (language/region) should allow its independent URL/slug. example
  • de-DE: http://localhost:3000/de-DE/articles/my-first-article-1
  • de-DE: http://localhost:3000/de-CH/articles/my-first-articula-one
  • ....... and so on..
• Updating a localized URL should only affect that specific language, not the others.
• The sitemap should correctly reflect each localized URL separately.

Are there any solutions for that?

[boazpoolman]

Hi @sayedbs,

Thank you for reporting this issue.
I have confirmed the following as a bug:

When I manually edit the Australian URL to the correct value (e.g., article-one-for-at), it also automatically changes the German URL to match (article-one-for-at), which is incorrect.
The system seems not to allow saving different slugs/URLs per localization — any change affects all languages simultaneously.

Though I can't seem to reproduce the issue with the "random" value. Could you paste a dump wt_url_patterns table of your DB? I suspect that your pattern is not configured for the Australian language.

[sayedbs]

@boazpoolman you are right not configured yet, but as a user, I not need other local rights now, so I not need to configure it. But a sitemap is showing with the wrong URL.

[boazpoolman]

@sayedbs I'm trying to figure out the expected behavior here.

Are you saying that you have two locale's in your Strapi project (German and Australian), but you only want one of those languages in the sitemap?

Webtools works in such a way that when you create a new locale, it will generate URLs for entities of that locale. It's not something you can opt-out of. And the sitemap add-on will just include all URLs it can find. This is how it currently works but I'm open to exploring new workflows, so please help me understand your usecase.

[sayedbs]

Hello @boazpoolman ,
Thanks for the comments. You are on the right points, so please take your time.

I have another issue about sitemap, after installing Webtool and trying to create a duplicate Entry, and clicking to save changes then each click shows:

Strapi alert:

Browser console:

interesting, this is when I go back to the list, then the showing each click generates/duplicates one item here:

Should I create another issue for the duplication issue?

Thanks

[boazpoolman]

Yes, please create a new issue for the duplication issue. Thanks !

[sayedbs]

Here is the new one issue in Github: #268

[boazpoolman]

@sayedbs Great! I will take a look at that issue.

Regarding this issue (#267), could you answer my question?

Are you saying that you have two locale's in your Strapi project (German and Australian), but you only want one of those languages in the sitemap?

I'm trying to better understand what behavior you expect here.

[sayedbs]

@boazpoolman you are on right point. I have 2 or multiple but sitemap set only for one right now where i configured one.

[boazpoolman]

I'm going to rebrand this issue to a feature request, being: "Control which languages end up in the sitemap, instead of including all".

The bug you've reported in here regarding manually editing the URL alias I've created a new issue for, that's #270.