Do I need separate URLs for each language?

Yes, for SEO. Give each language its own URL (e.g. /en/, /ja/). A single URL that swaps text with JavaScript is hard for search engines to index per language. Separate static URLs let Google index and rank each language independently.

Morgan Vault › Guides › Multilingual without a translator

Guide · Multilingual SEO

How to Make a Website Multilingual Without a Translator

Q: What is hreflang and do I need it?

hreflang is a set of link tags that tell Google which language and region each page targets. With multiple language versions you need it so Google serves the right version to each user and does not treat the versions as duplicate content.

Q: How do I handle right-to-left languages like Arabic or Hebrew?

Set the dir="rtl" attribute on the html element for those languages and make sure your layout does not hard-code left/right assumptions. Most modern CSS using logical properties or flexbox adapts with minimal extra work.

No translators, no plugins. Use AI to localize your website into many languages and get every language version correctly indexed by Google. This is the exact method morganvault.com uses to run 23 languages — one translation dictionary, one static HTML page per language, and hreflang.

By Morgan Wang · Updated 2026-07-30

Short answer

How do you make a website multilingual without a translator and still get it indexed?

Move all text into one translation dictionary (short ids as keys, one set per language). Translate that dictionary with AI (Claude) and proofread the key pages. Generate one real static HTML page per language so crawlers see fully localized content rather than JavaScript-filled blanks. Add hreflang and a self-referencing canonical on every page so Google serves the right language. Finally, add a language switcher. This is exactly how this site runs 23 languages.

Six steps

1. Choose languages and URL structurePick your target languages and give each its own URL path, e.g. /en/, /ja/, /es/. Subdirectories are the simplest structure for Google to crawl and index per language.
2. Put all text in one translation dictionaryMove every piece of UI text into one place keyed by a short id (a JSON or JS object), one set per language. This becomes the single source of truth for every translation.
3. Translate with AI, not an agencyAsk Claude to translate the dictionary into each target language. Re-check tone on your highest-traffic pages (home, pricing, FAQ); have a native speaker proof them before launch if budget allows. Far cheaper and faster than hiring translators for every language up front.
4. Generate one static HTML page per languageFor SEO, render a real static HTML page for each language so crawlers see fully localized content, not a blank page waiting on JavaScript. A small script can stamp the dictionary into a template, one page per language.
5. Add hreflang and canonicalOn every page add hreflang link tags pointing to each language version plus a self-referencing canonical. This tells Google which language to serve to which user and avoids duplicate-content confusion.
6. Add a language switcherGive visitors a simple menu to switch languages and remember their choice. Optionally detect the browser language on first visit and redirect to the matching version.

Why trust this method? This site is the proof

The site you are reading runs 23 languages, all generated from a single translation dictionary, one static HTML page per language, with full hreflang — no translators hired, no multilingual plugin. The engine itself is not much code; the real cost is translation review and keeping content in sync, not engineering. This is exactly what Chapter 4 of the Morgan Vault e-book walks you through.

Frequently asked questions

Is AI translation good enough for a real website?

For most marketing and product copy, modern AI translation is a strong baseline — good enough to launch. The honest approach is to label it AI-assisted, proof your highest-traffic pages, and have a native speaker check when budget allows. Far cheaper and faster than hiring translators for every language up front.

Do I need separate URLs per language?

Yes, for SEO. Give each language its own URL (e.g. /en/, /ja/). Swapping text with JavaScript on one URL is hard for search engines to index per language. Separate static URLs let Google index and rank each language independently.

What is hreflang and do I need it?

hreflang is a set of link tags telling Google which language and region each page targets. With multiple language versions you need it so Google serves the right version to each user and does not treat the versions as duplicates.

How do I handle right-to-left languages like Arabic or Hebrew?

Set dir="rtl" on the html element for those languages and make sure your layout does not hard-code left/right assumptions. Most modern CSS using logical properties or flexbox adapts with little extra work.

How many languages is too many?

There is no hard limit — morganvault.com runs 23 languages from a single dictionary. The cost is mostly translation review and keeping content in sync, not engineering. Start with the languages your audience actually uses and expand as the dictionary makes it cheap.

Want the whole end-to-end path?

The full 200-page hands-on e-book: from your first line of HTML to deployment, SEO/AEO, multilingual i18n, subscriber collection, and traffic strategy. Includes copy-pasteable scripts and AI prompt templates. 23 languages.

See the e-book bundle — $39.90 →

How to Make a Website Multilingual Without a Translator

Six steps

Why trust this method? This site is the proof

Frequently asked questions

Want the do-it-with-me full version?

Want the whole end-to-end path?

Read next