[GH-ISSUE #2195] i18n sitemap optimisation #634

Open
opened 2026-02-26 18:47:51 +03:00 by kerem · 3 comments
Owner

Originally created by @eithan1231 on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2195

Describe the improvement you are suggesting in detail

This is a super low value issue, that shouldn't take any priority. I just happened to notice it.

The main website has good i18n support, but the sitemap does not properly implement i18n page alternatives. See See here for googles recommendation for alternative paths.

Sitemap in question: https://documenso.com/sitemap.xml

Additional Information & Alternatives (optional)

No response

Do you want to work on this improvement?

No

Please check the boxes that apply to this improvement suggestion.

  • I have searched the existing issues and improvement suggestions to avoid duplication.
  • I have provided a clear description of the improvement being suggested.
  • I have explained the rationale behind this improvement.
  • I have included any relevant technical details or design suggestions.
  • I understand that this is a suggestion and that there is no guarantee of implementation.
Originally created by @eithan1231 on GitHub (Nov 14, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2195 ### Describe the improvement you are suggesting in detail This is a super low value issue, that shouldn't take any priority. I just happened to notice it. The main website has good i18n support, but the sitemap does not properly implement i18n page alternatives. See [See here](https://developers.google.com/search/blog/2012/05/multilingual-and-multinational-site) for googles recommendation for alternative paths. Sitemap in question: https://documenso.com/sitemap.xml ### Additional Information & Alternatives (optional) _No response_ ### Do you want to work on this improvement? No ### Please check the boxes that apply to this improvement suggestion. - [x] I have searched the existing issues and improvement suggestions to avoid duplication. - [x] I have provided a clear description of the improvement being suggested. - [x] I have explained the rationale behind this improvement. - [x] I have included any relevant technical details or design suggestions. - [x] I understand that this is a suggestion and that there is no guarantee of implementation.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 14, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

<!-- gh-comment-id:3532244387 --> @github-actions[bot] commented on GitHub (Nov 14, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)
Author
Owner

@Mythie commented on GitHub (Nov 14, 2025):

Man I'm not even sure if framer can do that

<!-- gh-comment-id:3532249997 --> @Mythie commented on GitHub (Nov 14, 2025): Man I'm not even sure if framer can do that
Author
Owner

@eithan1231 commented on GitHub (Nov 14, 2025):

suing them is your only option

<!-- gh-comment-id:3532325574 --> @eithan1231 commented on GitHub (Nov 14, 2025): suing them is your only option
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#634
No description provided.