Choose languages based on the people you can actually serve. Translate the complete enquiry journey and explain currency, scope and communication expectations. A Turkish business serving English-speaking customers can show prices in Turkish lira and explain the quote process without fabricating dollar conversions. A translated homepage alone is insufficient when forms, errors and essential service terms remain inaccessible.
Choose languages you can support through the conversation
A language version is an invitation to communicate. Before adding it, consider whether the business can answer enquiries in that language or has a clear, honest alternative. Ten translated menu options do not automatically create ten supported markets. Start with the audiences you actually intend to serve and the service you can deliver to them.
Map the content needed for each audience. The core offer may remain the same, but examples, terminology and practical questions can differ. Localisation means making that information understandable, not changing the price invisibly based on a visitor's location. Be explicit about the currency and whether a displayed amount is a one-time build fee or a recurring cost.
For example, an overseas customer seeing a Turkish-lira quote should not have to guess whether the symbol means another currency. Keep TRY as the stated basis and format it readably for the chosen language. Do not invent live conversion values or imply that a foreign-currency estimate is a guaranteed settlement amount when no such arrangement exists.
Build complete journeys with stable equivalent pages
Translate the parts that support a decision: service descriptions, package limits, forms, errors and supporting information. A polished landing page followed by untranslated submission errors creates a broken journey. Include empty search states, not-found pages and confirmation text in the content inventory so they are not forgotten because they appear less often.
Use stable page identities to connect equivalent language versions. The language switcher should keep the visitor on the same topic where a counterpart exists. Avoid constructing those links by replacing pieces of a slug. A translated address can change independently of the content identity, especially when editors improve a title later.
Review each language in its actual layout. German labels may be longer; Arabic needs direction-aware composition; Japanese and Hindi need appropriate glyph support and line breaking. Keep email addresses and prices readable in right-to-left contexts. These checks should be part of the design process, not postponed until visitors report clipped text or confusing fields.
Keep international expectations concrete and maintainable
State which parts of the work depend on the customer's preparation, what will be delivered and which ongoing costs are separate. If communication crosses time zones, explain the process without promising immediate availability. The application can collect the preferred contact channel and project languages separately so the language of the form does not silently determine the site being commissioned.
Maintain package facts from one approved source across all languages. A change in page limits or revisions should not leave one translation offering something different. Keep the route mapping, structured data and readable alternatives tied to the same content set. Consistency is both a visitor benefit and a practical way to reduce editorial mistakes.
Finally, judge expansion through actual fit. Are relevant visitors able to understand the offer and submit useful enquiries? Can the business respond competently? Publishing another language is a meaningful commitment to maintain information and communication, not a shortcut to international sales. A clear, complete experience in a supported language is more useful than a large selection of unfinished translations.
Test a complete international enquiry. Open a service in the chosen language, compare the package scope and submit a clearly identified authorised test. Confirm that the form distinguishes the current interface language from the languages requested for the new project. The operator should be able to understand that distinction in the saved record.
Review currency wording and contact expectations with someone who reads the language naturally. An amount may be correctly formatted yet still leave uncertainty about taxes, recurring costs or what happens after the application. Keep unresolved commercial facts out of invented copy and complete owner confirmation before commercial publication.
When adding another language later, repeat the whole process rather than translating only the visible headline. Include routes, metadata, form failures and supporting information in the publishing checklist. Assign responsibility for future changes so one locale does not drift into an older package offer. International reach is better served by a dependable, understandable journey than by a language selector whose options lead to different promises or incomplete content.
Practical checklist
- Localize service explanations
- Maintain equivalent pages
- Plan responses in each language
A concrete example: A Turkish business serving English-speaking customers can show prices in Turkish lira and explain the quote process without fabricating dollar conversions.
A boundary to keep clear: A translated homepage alone is insufficient when forms, errors and essential service terms remain inaccessible.
Your next step
Tell Orvunweb about your project
