Expanded Major Public Pages to 11 Languages
We provide the homepage, pricing, and major feature guides in 11 languages and organized language-specific brand names, feature terms, and metadata to deliver the same product contract.
For users in various countries to understand 5BY.AI, beyond simple automatic translation, features and limitations must be conveyed with the same meaning in each language. We expanded the language scope of major public pages to 11 and organized product proper nouns and search visibility information together.
The quality of multilingual pages is judged not by the number of translated sentences but by whether the same product is described in every language.
What Changed in This Update
- Supports English, 한국어, 日本語, 简体中文, 繁體中文, Deutsch, Français, Español, Italiano, Português (Brasil), and Русский.
- Provides language-specific text on the homepage, pricing, and major feature guides.
- Consistently maintains 5BY.AI and 5by Tools brand notation and Pack, Saved, Anchor, Handoff proper nouns.
- Reviewed language-specific title, description, canonical, Open Graph, and structured data default alignment.
- Manages locale keys together so that text describing the same user outcome is not omitted in specific languages.
- Organized the Chrome Web Store Listing to match the public language scope.
How to Verify
- Select a language on the homepage.
- Navigate to pricing, feature guides, and account pages to check that the selected language is maintained.
- Check that product proper nouns and pricing conditions are displayed with the same meaning across languages.
- If there are translation omissions or meaning differences, leave feedback with the page URL and language together.
Example in Actual Usage Flow
For example, to verify this change, the user selects a language on the homepage. They navigate to pricing, feature guides, and account pages to check that the selected language is maintained. Then they check that product proper nouns and pricing conditions are displayed with the same meaning across languages. Finally, if there are translation omissions or meaning differences, they leave feedback with the page URL and language together. In this flow, the following conditions should also be checked. Support for 11 languages does not mean complete translation of all developer notes and user-generated content. Therefore, this update is not just adding one more notice item but enabling the user to check the start, result, and limitations of the feature within the same flow.
Before and After the Change
Before the change, users had to guess this feature or notice from other screens or navigate across multiple pages. After this update, we provide the homepage, pricing, and major feature guides in 11 languages and organized language-specific brand names, feature terms, and metadata to deliver the same product contract. However, items where public notices and actual account/runtime status may differ need to be checked separately, and notice text alone should not be interpreted as expanding permissions or availability.
Scope and Things to Note
- Support for 11 languages does not mean complete translation of all developer notes and user-generated content.
- The AI service's own UI language and 5BY.AI's public page language are independent of each other.
- Product proper nouns are not arbitrarily translated to look like different features.
- When new pages and features are added, simultaneous language-specific reflection and review continue to be needed.
Why This Change Matters in the Overall 5BY.AI Structure
Multilingual expansion is both a surface effort for global visibility and a process of verifying the product contract. Accurate description in only one language is not enough. In every language, 5BY.AI must be equally understood as a memory infrastructure that handles the user's thinking trajectory and reentry coordinates.
Criteria for Verifying This Update
- The public screen title, summary, and actual provided feature should describe the same content.
- Adding a new feature should not arbitrarily change existing Saved, Anchor, Handoff, and account flows.
- Conditions that are in preparation or vary by account should be marked separately without exaggerating as fully available.