How to Make a Website Multilingual in 2026

The first decision is which locales to publish, and the answer is rarely 'all of them.' Every locale you add is a commitment: you'll maintain its content, monitor its SEO, review its translations, and respond to its visitors. Adding 10 locales that you can't maintain is worse than adding 2 locales that you can.

Start with the locales that map to your actual audience. Look at your existing traffic in Google Analytics — what countries and languages already visit? Look at your customers — what languages do they speak? Look at your competitors — what locales do they serve that you don't? The intersection of 'where my audience is' and 'where I can deliver quality' is your locale shortlist.

For most service businesses, the answer is two locales: your primary business language plus one community language (e.g., English + Chinese for a US dentist serving a Chinese community). For cross-border businesses, two to four locales (e.g., English + Chinese + Spanish for a consultant serving US, China, and Latin America). For software and content sites, four to ten locales may make sense once unit economics justify the maintenance cost.

Three viable URL structures for multilingual sites: (1) locale-prefixed subdirectories (example.com/zh-CN/, example.com/es/), (2) locale-prefixed subdomains (zh-cn.example.com, es.example.com), or (3) separate domains per locale (example.cn, example.es, example.com). Each has trade-offs.

Subdirectories are the most common choice and usually the best. SEO equity compounds across locales (links to /zh-CN/ benefit the whole domain), maintenance is simple (one CMS, one codebase), and hreflang works cleanly. Google's documentation explicitly recommends subdirectories when feasible.

Subdomains split SEO equity across locales (links to zh-cn.example.com don't benefit example.com as much as /zh-CN/ would). They make sense when each locale is operated by a separate team with separate infrastructure, or when locale-specific legal requirements (data residency, content licensing) require physical separation. Most sites don't need this.

Separate domains make sense for truly separate businesses sharing a brand (e.g., a global fast food chain with country-specific menus and pricing). The complexity — separate SEO, separate DNS, separate hosting — is rarely worth it for small or mid-size multilingual sites.

Cogo Site uses subdirectories by default (/zh-CN/, /es/, etc.), which is the right answer for 95% of multilingual sites. If you need subdomains or separate domains for legal reasons, that's a custom configuration; otherwise stick with subdirectories.

Translation quality determines whether your multilingual site compounds or cannibalizes. Three approaches, in order of cost and quality:

Approach A — Pure human translation. Highest quality, slowest, most expensive. Best for legal, medical, or regulated content where errors are costly. Cost: $0.10-$0.30 per word for professional translation. Time: weeks to months for a full site.

Approach B — AI translation with native-speaker review. AI translates, a native speaker reviews homepage and conversion-critical pages. Quality is close to human translation at 10-20% of the cost. Best for most service businesses. Cogo Site uses this approach by default.

Approach C — Pure AI translation. Fastest, cheapest, lowest quality. Acceptable for internal tools or low-stakes content; risky for customer-facing sites. Google can detect low-effort machine translation and may downgrade both locales.

The hybrid approach (B) is the sweet spot for most sites. Cogo Site's AI translation produces locale-appropriate phrasing (not word-for-word), and a native speaker should always review homepage, pricing, and conversion-critical pages. The result is 90% of human quality at 10% of the cost.

Hreflang tells Google which locale version to show which searcher. Without it, Google may serve the wrong locale to the wrong searcher, causing bounces and lost rankings. Every multilingual page needs three pieces: a self-referential hreflang tag, alternate tags for every other locale, and an x-default tag pointing to the locale for unmatched searchers.

Beyond hreflang, each locale gets its own title, meta description, and URL slug — all in the locale's language. A common mistake is translating the body content but leaving English SEO metadata; Google reads this as 'low-effort translation' and ranks accordingly. Translate everything.

Sitemaps: each locale should be in your XML sitemap. Most modern CMSs (including Cogo Site) generate multilingual sitemaps automatically with correct hreflang annotations. If you're hand-managing sitemaps, add hreflang annotations to each URL entry.

Structured data: JSON-LD on each locale page should be in the locale's language where applicable (e.g., FAQ Question names translated, Article headline translated, Breadcrumb name translated). See our hreflang guide for the full hreflang spec.

Translation is half the work. The other half is locale-specific UX details that separate a real multilingual site from a translated one.

Date and time formats: US uses MM/DD/YYYY, most of the world uses DD/MM/YYYY, ISO standard is YYYY-MM-DD. Pick the format matching each locale's convention; don't use one format globally.

Phone numbers and addresses: format per locale's postal convention. US addresses are '123 Main St, San Francisco, CA 94101'; Chinese addresses are reverse-order (country, province, city, district, street, number). Cogo Site's locale-aware formatting handles this automatically.

Currency and units: prices in USD for en-US, CNY for zh-CN, MXN for es-MX. Don't auto-convert — show the locale's actual currency.

Social proof: show WeChat / Weibo / QQ testimonials on zh-CN, Facebook / Twitter / Yelp testimonials on en-US. Don't show English social proof on Chinese pages — it signals 'foreign operator.'

Form labels and validation: phone number validation rules differ (10 digits US, 11 digits China mainland), postal codes differ (5 digit US, 6 digit China), name fields differ (Western first/last vs Chinese family/given in that order). Validate per locale.

Font stacks: Chinese needs CJK-capable fonts (Noto Sans CJK, PingFang, Microsoft YaHei); English needs Latin fonts (Inter, system-ui). Mixed-script typography needs fallback stacks. Cogo Site handles this per locale; hand-built sites need careful CSS.

After launch, monitor three things: (1) Google Search Console's International Targeting report for hreflang errors, (2) Search Console's Performance report per locale (queries, CTR, position), (3) Analytics per locale (traffic, engagement, conversion).

Common post-launch issues: hreflang errors (fix immediately), one locale's pages not indexed (check URL inspection), wrong locale ranking in wrong region (verify hreflang is correct), low engagement on one locale (review translation quality and UX details).

Iterate based on data. If zh-CN has 10x the traffic of en-US, your audience is Chinese — prioritize that locale. If es-MX has high traffic but low conversion, the translation may be awkward or the pricing wrong — fix it. Multilingual sites are living systems; the launch is the start, not the end.

Re-audit hreflang quarterly. Sitemap changes, content migrations, and CMS updates can break hreflang silently. A quarterly Ahrefs or Sitebulb crawl catches issues before they cost rankings.

Mistake 1 — Publishing too many locales at once. Each locale is a maintenance commitment; 10 locales you can't maintain is worse than 2 you can. Start with your highest-value locales, prove the model, expand later.

Mistake 2 — Choosing subdomains or separate domains without a real reason. Subdirectories compound SEO equity; subdomains and separate domains don't. Use subdirectories unless legal or operational requirements force otherwise.

Mistake 3 — Translating body content but not SEO metadata. Title, description, URL, alt text, structured data — all need translation. Leaving English metadata signals 'low effort' and tanks rankings.

Mistake 4 — Machine translation without native review. AI translation is good but not perfect. Always have a native speaker review homepage and conversion-critical pages. The cost is small; the quality gain is large.

Mistake 5 — Same UX details across locales. Date formats, phone formats, currencies, social proof, form validation — all need locale-specific handling. A 'one size fits all' UX signals 'we don't actually know your locale.'

Mistake 6 — Forgetting Baidu and Bing. Google is the dominant search engine in the West, but Baidu dominates Mainland China and Bing still matters in some enterprise/education segments. Make sure your hreflang and sitemap work for all three.