Add multi-language support (including right-to-left)
Serve your site in more than one language, with correct right-to-left layout.
When to use this
When your audience spans languages, or you're expanding to new markets.
Before you start
- Decide your main language and the ones you're adding. Add languages your customers actually read — not everything you can think of.
- Have your key content finished-ish first: translating a page you're about to rewrite wastes work.
- If you're adding Hebrew or Arabic, expect layout changes (text and layout flip direction) — that's normal and the prompt handles it.
The prompt
Add multi-language support to my site. Outcome: visitors can switch between [languages, e.g., English, Spanish, Hebrew], and everything reads correctly in each. Requirements: - A clear language switcher in the header that remembers the visitor's choice. - Translate all interface text and page content; keep [English] as the source language. - For right-to-left languages ([Hebrew / Arabic]), mirror the entire layout — text alignment, menus, icons and spacing — not just the words. - Format dates, numbers and [currency] correctly for each language. - Make it easy for me to add or edit translations later without touching code. Must-haves: if a translation is missing, fall back to the source language, and make sure the switcher works on mobile. When done, show me how to add a new language.
Already building? Paste this into your project. Starting fresh? Open a free account with a compatible builder below.
Build it on
What this creates
- A language switcher in the header
- Every page available in each language you chose
- Correct right-to-left layout for Hebrew or Arabic if you added them
- Dates, numbers and currency formatted the way each language expects
Check it worked
Paste the prompt, wait for the build to finish, then confirm these — in plain language, no technical checks needed:
- Switching language changes the whole page, not just parts of it
- You stay on the same page when you switch, instead of being sent to the home page
- In a right-to-left language the layout mirrors properly — menus, alignment and icons included
- Forms, buttons and error messages are translated too (not only the main text)
- Nothing appears in a mix of two languages on the same screen
Something missing? That's normal — ask for it in one short follow-up message rather than re-running the whole prompt.
Next steps
Fix the translation gaps
After switching languages and browsing every page
Find any text still showing in the original language when another language is selected — including buttons, form labels, error messages, empty-state text, email templates and the page titles browsers show in tabs. Translate everything that is missing.
You'll know it worked when: You can browse the whole site in each language without meeting a stray sentence in the wrong one.
Tell Google about the languages
Once the translations are decent
Add the technical signals that tell search engines this site exists in multiple languages, so each version can appear for people searching in that language. Include each language version in the sitemap.
You'll know it worked when: Each language version has its own address and is listed in the sitemap.
Add a language people actually asked for
When you see demand
Add [LANGUAGE] to the site: translate all pages and interface text, add it to the language switcher, and keep the same structure and links as the existing versions.
You'll know it worked when: The new language appears in the switcher and every page is available in it.
Watch out for
- Machine translation is a first draft. For anything that sells or explains a policy, have a human who speaks the language read it. Awkward translation reads as unprofessional in exactly the market you were trying to win.
- Right-to-left is more than mirrored text. Check that punctuation, phone numbers and mixed English words sit correctly — this is the most common place where it looks broken.
- Keep your build prompts in English even when your site is in other languages — results are measurably better.
Platform notes
All three can do this. Right-to-left (Hebrew, Arabic) needs full layout mirroring — call it out explicitly, as many builders default to left-to-right. Keep one language as the source and translate from it.
Spend fewer credits
Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.
- Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
- Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
- Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
- One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
- Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
- Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.
The prompts on this page are written to do most of this work for you — that's the point of them.
Read the full guideRelated playbooks
Last reviewed: 2026-07-27