Multilingual: do it now or wait for the right moment
The question is not 'should we do it' but 'when should we do it and have we done all three layers yet'.
You should consider going multilingual from the start if you really have clients or partners in another language within the next 12 months. If unsure, the right approach is to set up a structure ready for it but only activate additional languages when there is real demand, avoiding activation and then neglecting it. Doing multilingual poorly, especially by adding an automatic translation button without localized content, can harm SEO more than not doing it at all.
- There are foreign clients or plans for near-term export.
- Travel or international B2B in the next 12 months.
- no customer segment in other languages yet
- There is no one to maintain the translation after it is activated.
- only attaching an automatic translation button without localized content
Multilingual is one of the most commonly misunderstood technical decisions when creating a brand website. Many business owners think that adding a translate button is enough. In reality, true multilingualism is a system with three layers that must be done simultaneously: URL structure, hreflang tags (language indicators for search engines), and localized content. Missing one layer compromises all three.
The first question: do you have real customers yet?
This is the question that determines everything. It is not about "the future may have foreign clients," but rather "are there specific clients in a different language market in the next 12 months?" If the answer is yes, whether the entity is exporting, doing tourism, engaging in international B2B, or already has foreign partners, it should be multilingual from the start, as building the infrastructure later will be more costly than doing it right from the beginning.
If the answer is "maybe" or "for backup," a more suitable approach is to build a structure that is ready but not activated. This means the technique is set, the content is not yet available, and it will be filled in when real demand arises. This method saves maintenance costs without having to redo everything later.
The three layers must operate simultaneously
This is the part that many entities overlook. Multilingualism is not just a translation of the homepage.
- Path structure: Often uses subdirectories, e.g., /en/, /ja/, instead of separate domains, as it is easier to manage and better for SEO in the early stages.
- Hreflang tag: A technical tag located in the head of each page, informing search engines which language and region this page serves. Incorrect or missing tags can lead Google to misunderstand the relationship between versions, causing indexing errors (showing the wrong page or no page at all).
- Localized content: It’s not just about translating words, but adjusting the way of speaking, for example, calls to action that align with how users in that market actually search and make decisions.
Create in advance, activate later is suitable when: the main market is still domestic, the second language is just a tentative plan, and there are no resources to maintain bilingual content.
Common mistakes that make multilingual efforts counterproductive
- Attach automatic translation and consider it done: Machine-translated content without editing risks being assessed by search engines as low-value content. Readers will also recognize this immediately and lose trust.
- Lack or incorrect hreflang tags: Search engines do not know which version serves which market, leading to incorrect pages being displayed to the wrong audience.
- Activate multiple languages but only update one: After a few months, other language versions become outdated. Inconsistent content disrupts brand coherence and creates additional technical debt.
Multilingual is a process, not a project. The earlier you build the infrastructure, the stronger the foundation, but all new content must be continuously maintained in both languages, not just done once.
Strapi: Multilingual SEO Best Practices
The viewpoint of Sinh Vũ
At Sinh Vũ, multilingual support is an optional item in website services, not a default. The reason is that doing it correctly requires additional time for technical setup and a commitment to maintain content later. Sinh Vũ only recommends enabling a second language when you already have real customers in that market.
For clients who are uncertain, Sinh Vũ often sets up the structure of URLs and hreflang tags from the first build, even when content is not yet available. When the need arises, you can simply fill in the content in the pre-allocated spaces instead of starting from scratch. This is a way to save budget without sacrificing scalability.
What Sinh Vũ emphasizes with each client: the decision to enable multilingual support must be accompanied by a decision on who will maintain those versions. If the answer is still unclear, then it is not yet time to enable.
Decision checklist
Topic: When to create a multilingual website from the start. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Strapi: Multilingual SEO Best Practices. Google Search Central: Managing Multi-Regional and Multilingual Sites. Digital Applied: International SEO Hreflang Guide.
Frequently asked questions
Can Google Translate be integrated into the website?
Technically, it is possible, but low-quality machine translation content that has not been edited risks being rated as low-value content by search engines. If the goal is just for customers to read temporarily, it is acceptable, but if you want to SEO in that language market, it cannot replace truly localized content.
If we want to implement multiple languages later, will we need to redo the website?
It is not necessary if the structure is set up from the beginning. Sinh Vũ typically establishes subdirectories like /en/ or /ja/ and the hreflang framework (language indication tags for search engines) right in the first build, even if not activated yet. When there is a real need, you only need to fill in the content into the existing structure instead of having to redo everything.
How many people are needed to maintain a bilingual website?
There is no fixed number as it depends on the frequency of content updates. What Sinh Vũ finds practical is that each time content is updated in one language, the other versions also need to be updated accordingly; otherwise, the versions will diverge and lose consistency. You need to consider whether someone will be responsible for this before deciding to add more languages.