Skip to main content
株式会社オブライト
Business DX2026-07-15

Multilingual Website Costs — Where Machine Translation Ends and Localization Begins

A neutral breakdown of multilingual website costs, from auto-translate widgets to full localization, covering cost drivers and the link to inbound demand.


What Is a Multilingual Website?

A multilingual website is a website that lets a company communicate in languages other than Japanese. The level of support needed varies greatly depending on the purpose — whether it's inbound tourism outreach for visitors to Japan, or communication with overseas business partners and international talent. This article provides a neutral, stage-by-stage breakdown of multilingual website costs and the factors that drive them.

Three Stages of Multilingual Support

- Auto-translate widget: Embedding a machine translation tool such as Google Translate to display the site mechanically in other languages
- Key-page translation: Having a human translator handle only the top page, company overview, and main product/service pages
- Full localization: Translating and restructuring the entire site to match the target language's culture and business customs, including dedicated pages and messaging tailored to the local market

Cost Ranges by Stage

StageTypical scopeApproximate cost range (per language)
Auto-translate widgetTool setup and embedding onlyRoughly ¥10,000s–¥100,000 (a monthly fee may apply separately)
Key-page translationRoughly 5–10 pages translated by a human, reusing the Japanese-language designRoughly ¥150,000–¥600,000
Full localizationEntire site translated, local content added, cultural adjustments includedRoughly ¥800,000–¥3,000,000

Note that costs stack up with each additional language. A single language such as English typically falls within the ranges above, but supporting multiple languages — say, English, Chinese (Simplified/Traditional), and Korean — generally means translation costs are added for each additional language.

The Difference Between Machine Translation and Localization

Auto-translate widgets are inexpensive to implement, but they carry the risk of unnatural translations for technical terms or idiomatic expressions, and in some cases the meaning may not come across correctly depending on context. This is a particular concern for product descriptions, contract-related information, or medical and legal content, where a mistranslation could lead to real problems.

Localization, on the other hand, is not just about swapping words — it involves adjusting the content itself to match the target country or region's culture, business customs, and stylistic preferences. For example, phrasing that reads as naturally polite in Japan may come across as roundabout overseas, sometimes requiring the tagline or the order of the message itself to be rewritten. Simple translation and localization require very different amounts of work and cost.

Main Drivers of Cost Variation

- Number of languages: Translation and proofreading costs accumulate with each additional language
- Translator expertise: Whether translators with expertise in a specific field (medical, legal, technical, etc.) are required
- Native-speaker review: Whether proofreading by a native speaker of the target language is included
- Scope of pages covered: Whether the entire site is translated or only key pages
- Update frequency: Whether the multilingual versions need to be kept in sync with ongoing updates to the Japanese version

About Technical Requirements

Building a multilingual site also requires setting up hreflang tags to tell search engines how language versions of each page relate to one another, and designing a URL structure for each language (subdirectories, subdomains, country-specific domains, etc.). These are technical details best confirmed with your vendor, but checking at the quoting stage whether multilingual SEO setup is included can help avoid unexpected additional costs later.

The Connection to Inbound Demand

For industries that interact directly with visitors to Japan — tourism, hospitality, food service, retail — a multilingual website can become a direct entry point for inquiries and reservations. In these cases, it's worth considering not just information delivery but also multilingual support for booking flows and payment methods, which tends to push costs higher than a standard multilingual site. If inbound tourism is the goal, it's worth considering multilingual support as part of a broader inbound strategy across operations, not just the website.

For a concrete example of inbound-focused efforts in the hospitality industry, see Inbound DX Case Study for Japanese Inns.

For guidance on the ordering process and how to compare quotes for web development in general, not just multilingual sites, see The Complete Guide to Ordering a System Without Failure.

How to Proceed and Avoid Common Pitfalls

- Clarify your purpose: The level of support you need differs depending on whether the goal is information delivery or generating inquiries/reservations
- Decide on priority languages: Prioritize the languages spoken by your main customer or visitor base
- Establish a translation workflow: Decide in advance how multilingual versions will be updated whenever the Japanese version changes
- Understand the limits of machine translation: Consider human translation for important pages rather than relying on auto-translation

Frequently Asked Questions

Is an auto-translate widget not enough on its own?

It depends on the purpose. For simple informational content, auto-translation can serve a purpose, but for content where a mistranslation could cause real problems — product descriptions, contract-related information — it's advisable to consider human translation or native-speaker review.

How many languages should we support?

There's no universal answer. It's advisable to check your customer base and visitor data, such as the language breakdown in your analytics, and prioritize the languages with actual demand.

How long does multilingual support take?

Key-page translation typically takes about one to two months, while full localization can take three months or longer. Timelines vary depending on the volume of content and the stakeholder review process, so it's wise to build in a comfortable schedule.

Summary

Multilingual website costs can range from just a few tens of thousands of yen for an auto-translate widget to several million yen for full localization — the range varies enormously depending on the level of support. What matters most is clarifying the purpose of multilingual support — information delivery versus generating inquiries or reservations — and determining the appropriate level of support from there. Before placing an order, it's advisable to get quotes from multiple vendors and compare them after confirming the scope of translation and whether SEO setup is included.

Feel free to contact us

Contact Us