Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Investigating
Categories Localization Technical
Created by Guest
Created on Nov 4, 2024

Support slash in UrlPath translations

We have a need to identify language in URLs.

This resembles adding /fr to the URL path of our french pages in the URL Segment of the French homepage and the UrlRoot (i.e Catalog_UrlRoot = fr/catalogue, Product_UrlRoot = fr/produit, Brand_UrlRoot = fr/marques)

Current setting does not support adding a slash (/) in the UrlPath translations, which is causing undesirable user experiences and language display issues.

Benefits to adding this feature:

SEO:

Search engines (like Google) can easily recognize language-specific content when it’s separated by a path (i.e., /fr for French). This helps with international SEO, making it easier to index and rank pages in the relevant language markets.

User Experience:

Users can easily identify the page's language by looking at the URL, which enhances usability and makes navigation more predictable, especially on multilingual sites.

If users share a link, the URL will immediately indicate the language, which is particularly helpful

Simplifies site structure:

A /fr structure keeps language variations in an organized hierarchy within the main domain, making it easier to manage language-specific content and maintain consistent tracking or analytics per language version.

  • Optimizely
    Sara Winter
    Reply
    |
    Nov 4, 2024

    Thank you for submitting this request! Our team is currently reviewing if and how we may implement this, particularly with consideration of our wide client base. We will update this ticket once we have completed this investigation.