[Update] April 3, 2024
Hi Creators,
On March 11, we will update roblox.com to allow search engines to index localized experiences and catalog pages in all languages supported on our platform. This will greatly increase the visibility of your creations through off-platform search results to users with non-English browser language preferences.
How does this work?
We will add locales in front of URLs on www.roblox.com depending on your current language settings.
As an example, today we have the following URL:
- https://www.roblox.com/games/1818/Classic-Crossroads
In the future, you will be able to access the same content on alternate URLs such as:
- https://www.roblox.com/es/games/1818/Classic-Crossroads
- https://www.roblox.com/ja/games/1818/Classic-Crossroads
- https://www.roblox.com/es-mx/games/1818/Classic-Crossroads
(How) will I be affected as a Creator?
This change will largely be seamless for most creators. Over time, you can expect your creations to appear more prominently in search result rankings for non-English languages. To take advantage of this, make sure you enable automatic translation for your experiences (refer to this post for details). Turning on automatic translation will also allow users worldwide to better discover your experiences (through recommendations and search) on Roblox.
Any existing links or bookmarks to www.roblox.com web pages will continue to work seamlessly.
If you are a browser plugin creator or build custom tools that rely on identifying specific URLs on roblox.com, you may need to update your tools to accommodate the new URL patterns. See more details below.
Technical Details
We are providing these technical details for the small number of plugin creators or tool developers who may be impacted, to ensure you can adapt to the new URL patterns.
- We will continue to support accessing www.roblox.com without a locale in the URL.
- If necessary, we may sometimes redirect users making GET requests.
- This change will only impact www.roblox.com. It will not impact apis.roblox.com, or any other subdomains.
Browser Plugins
If you have a Chrome extension or Firefox browser plugin that relies on matching specific URLs for content scripts or other behavior, you may need to modify your rules to handle the new URLs.
Before
- “matches”: [ “https://www.roblox.com/my/avatar” ]
After
- “matches”: [ “https://www.roblox.com/my/avatar”, “https://www.roblox.com/*/my/avatar” ]
Identifying Locales in URLs
Locale path prefixes are short strings (between 2-6 characters) that represent a language or language + country combination. A few examples:
-
es-es = Spanish (Spain)
-
es-mx = Spanish (Mexico)
-
ja = Japanese (Japan)
We plan to support two patterns:
-
Standalone ISO 639-1 language codes (2 alphabetic characters)
- Examples: en, ja, de
-
Two letter ISO 639-1 + ISO 3166 country codes (2-3 characters alphanumeric) separated by a hyphen
- Examples: en-us, es-mx, ar-001, ja-jp, de-de
If you want to check whether a specific URL contains a locale programmatically, here are some options you can consider:
-
In Javascript-based tools, you can use the Intl.getCanonicalLocales API for modern browsers to determine if a string is a valid locale.
-
Many programming languages offer standard libraries for identifying locales
-
Another option would be to use a regular expression that detects both patterns listed above. Keep in mind that some paths might trigger false positives, e.g. roblox.com/js/… is a regular folder and not a locale.
We welcome any feedback and comments you may have. Please kindly drop us a note below.
Thank you.