Website multilingual localization guide: Implementation strategies for inbound customer acquisition

"We want to support foreign languages, but don't know where to start." "Isn't installing a translation tool enough?" These are common questions heard from small and medium-sized business owners interested in inbound demand across tourism, hospitality, dining, and retail.

In 2025, foreign visitors to Japan reached a record high of over 42.68 million, with inbound consumption reaching 9.5 trillion yen (JNTO / Japan Tourism Agency estimates). With visitor numbers projected to remain around 40 million in 2026, websites supporting English, Chinese, and Korean are transforming from a "nice-to-have added value" into vital customer acquisition infrastructure.

This article provides a practical overview of the multilingual landscape, covering implementation options, technical SEO requirements like hreflang tags, tool comparisons, and expected costs.

---

Why multilingual website support is necessary now

Inbound tourists conduct online research beforehand

JNTO surveys reveal that most foreign visitors to Japan research travel information on their smartphones prior to departure. Many users refer to official websites when searching for accommodations, dining, and tourist spots; consequently, websites that only display Japanese risk being filtered out of search results or abandoned by visitors.

Language prioritization should fundamentally align with the composition of incoming foreign visitors.

While English ranks fourth by individual country, it serves as the lingua franca for non-Kanji regions across North America, Europe, Southeast Asia, and the Middle East, making it the first language that should be implemented. A practical approach is to start with English and subsequently add Korean and Chinese based on your business targets.

Multilingual support directly impacts SEO

To reach users searching in their native languages, translated content must be indexed by search engines. Browser-level auto-translation (such as Google Translate widgets) does not allow search engines to index the translated content, offering zero SEO benefits. An architecture where translated text resides on dedicated URLs is fundamental to inbound SEO.

---

Three implementation options

Multilingual implementations generally fall into three categories. The optimal solution depends on your technology stack, budget, and the number of supported languages.

1. Translation widget model (Weglot, GTranslate, etc.)

These SaaS tools enable multilingual capabilities simply by adding a single line of JavaScript to your existing site. They integrate smoothly with numerous CMS platforms, including WordPress and Shopify.

Pros

• Can be launched in as little as a few hours
• Generates independent URLs for SEO compatibility (Weglot automatically creates language-specific URLs)
• Choice of engines such as DeepL, Microsoft, or Google Translate

Cons

• Incurs ongoing monthly subscription fees (Weglot starts from €15/month)
• Relies on machine translation accuracy, requiring human review for critical pages
• Site design and layouts can occasionally break due to translated text expansion

Best suited for: Teams with limited technical resources, those seeking rapid validation, or sites built on WordPress and Shopify

2. Built-in framework i18n capabilities

Modern frameworks like Next.js and Astro feature built-in i18n routing. This method statically generates language-specific URLs such as /en/about/ and /zh/about/, managing translated copy via JSON files.

// astro.config.mjs
export default defineConfig({
  i18n: {
    defaultLocale: 'ja',
    locales: ['ja', 'en', 'zh-cn', 'ko'],
    routing: {
      prefixDefaultLocale: false,
    },
  },
})

Pros

• No SaaS fees, keeping running costs minimal
• Provides complete control over web performance and SEO
• Developer-friendly content management maintained entirely in JSON and Markdown

Cons

• Higher initial development effort (encompassing architecture, copy management, and testing)
• Translation work must be handled separately

Best suited for: New site builds or full redesigns adopting modern frameworks such as Next.js or Astro

3. Language-specific subdomain or subdirectory architecture

This approach preserves the existing CMS and site architecture while adding pages in other languages under en.example.com (subdomain) or example.com/en/ (subdirectory). For WordPress, this can be achieved using Multisite or specialized plugins.

Pros

• Minimal impact on the existing website
• Allows independent content management for each language

Cons

• Requires manual translation and updates, making content prone to becoming outdated
• Search engines like Google may treat subdomains as separate sites, risking dilution of domain authority

Best suited for: Informational sites supporting only one or two languages with low update frequencies

---

Technical SEO requirements: Setting up hreflang tags

To capture SEO value on a multilingual site, configuring the hreflang attribute is essential. The hreflang tag informs Google that alternative language versions of a page exist, ensuring the appropriate regional version appears in search results.

Basic syntax (placed within the HTML head)

<link rel="alternate" hreflang="ja" href="https://example.com/about/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/about/" />
<link rel="alternate" hreflang="zh-Hans" href="https://example.com/zh/about/" />
<link rel="alternate" hreflang="ko" href="https://example.com/ko/about/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/about/" />

Three key considerations for hreflang configuration

1. Reciprocal links are mandatory: If a Japanese page points to an English page, the English page must also point back to the Japanese page. Unidirectional tags are invalid.
2. Set x-default: Specify a fallback page for users whose language does not match any targeted version.
3. Maintain consistency with canonical tags: Ensure each language version's canonical tag points to its own URL rather than pointing to another language's version.

Implementation via XML sitemaps (for large-scale sites)

When managing a high page count, including hreflang annotations within XML sitemaps is far easier to maintain than editing individual HTML head sections. After configuration, verify recognition via the "Sitemaps" report in Google Search Console.

---

URL architecture: Subdirectories vs. subdomains

Google recommends the subdirectory approach (example.com/en/), as it consolidates domain authority. When targeting specific countries explicitly, country code top-level domains (ccTLDs) are also effective.

---

Controlling translation quality

While machine translation accuracy continues to improve, human verification remains indispensable for nuanced business phrasing and cultural considerations. Contracting translation agencies for every page is cost-prohibitive, making a hybrid strategy that allocates quality standards by page importance the most practical choice.

DeepL pairs exceptionally well with Japanese for both European and Asian languages, making it well-suited as a machine translation foundation for high-priority pages. Google Translate excels in its broad language coverage.

---

Cost estimates and implementation roadmap

Estimated implementation costs

For SMBs taking their first step, the most cost-effective path is to launch English support using widget-based tools like Weglot, subsequently expanding language coverage after verifying performance.

Implementation roadmap (3 steps)

1. Month 1: Rapid English rollout — Integrate a translation widget tool to generate English URLs. Complete native proofreading of the homepage and contact page, and configure hreflang tags.
2. Months 3–6: SEO validation and language expansion — Expand to Korean and Chinese while monitoring indexation via Google Search Console. Localize automated form confirmation emails.
3. Month 6+: Content enrichment and CVR optimization — Publish inbound-focused multilingual content, A/B test localized landing pages, and evaluate migrating to framework i18n alongside website redesigns.

Integrating multilingual support during a corporate website renewal minimizes overhaul expenses (refer also to How to Navigate Corporate Website Renewals and Select Agencies Successfully).

---

Common pitfalls and countermeasures

---

Conclusion

• With over 42.68 million foreign visitors in 2025, website localization has become essential infrastructure for inbound customer acquisition
• Three implementation models exist: translation widgets, framework i18n, and language-specific directories. Starting with widgets is most cost-effective for SMBs
• Configuring hreflang tags and adopting subdirectory URL architecture are critical for securing SEO benefits
• Maintain translation quality through a hybrid approach tiered by page priority
• Follow a phased roadmap: English rollout → performance validation → regional language expansion

Please feel free to reach out for consultations regarding multilingual websites and web development targeting inbound travelers.

Contact us here