Adding a second language to an existing website, step by step
Add a second language without a rebuild: audit the site, choose URLs and tools, translate, set up hreflang, test on staging and keep both in sync.
By Sohail Hussain21 November 20266 min read
To add a second language to an existing website, audit what the site is built on and whether its templates can carry the new language, give the language its own URLs (usually a subfolder such as /ar/), choose the translation tooling for your platform, translate and review the content, build the language-specific pieces such as the switcher, fonts and right-to-left layout, add hreflang and translated metadata, test on a staging site, and set up a routine so both languages stay current. On a well-built site this takes weeks. On a site with hard-coded layouts, the audit sometimes shows that a redesign is the cheaper route.
Arabic is the hardest common case, because it adds right-to-left layout and a new script to the translation work, so it is the example throughout. The same steps apply to any language. This is the process we follow when adding Arabic as part of our Arabic and multilingual websites service, and it builds on the guide to building an Arabic website.
Is a second language worth adding?
Look for evidence before you spend on it:
- enquiries or calls arriving in that language;
- Search Console impressions from countries where that language dominates;
- the sales team losing deals, or tenders requiring documents, in that language;
- customers asking for it directly.
It is not worth it if no one will maintain the second language after launch. A half-translated site with an abandoned Arabic blog does more harm than an English-only site, because it shows Arabic readers exactly how much they matter. It is also not worth publishing machine translation alone to save money; machine vs human translation explains why.
What should you check before you start?
Step 1: audit the current site
The audit decides the cost. Check:
- Platform support. Does the CMS or site builder support multiple languages, natively or through a plugin?
- Hard-coded text. Button labels, form labels, footer text and error messages written into templates instead of the CMS. Every one has to be found and made translatable.
- CSS direction, for Arabic. Layouts built with
margin-left,float: rightand absolute left positions will not mirror. Layouts built with logical properties will. RTL web design explains the difference. - Forms and emails. Confirmation emails, autoresponders and CRM notifications all need the second language.
- Third-party widgets. Chat, booking, maps and reviews each have their own language settings, and some have none.
- Text in images and PDFs. Each needs a translated version or replacing with real text.
Then count the words. Paste the main pages into our word counter to get a figure for translation quotes.
Step 2: choose the URL structure
Give the new language its own URLs and leave the existing ones alone. A subfolder (example.com/ar/) suits nearly every business. Keeping English at the root means no existing URL changes and no rankings are put at risk. Subdomain vs subfolder vs ccTLD covers the alternatives.
How do you add the language on your platform?
Step 3: pick the translation tooling for your platform
Each platform has its own route, as of October 2026. Check the platform's current documentation, because features and plan limits change.
| Platform | How a second language is added |
|---|---|
| WordPress | A translation plugin: WPML, Polylang or TranslatePress |
| Shopify | Languages in the store settings, translated with Shopify's Translate & Adapt app or a third-party app |
| Webflow | Webflow Localization, a paid add-on |
| Wix | Wix Multilingual, built in |
| Squarespace | No full built-in multilingual feature; duplicated pages per language or a third-party translation service |
| Next.js or another custom build | Locale routing in the app, with content per language in the CMS |
For WordPress, WPML vs Polylang vs TranslatePress compares the options. For Next.js, building a multilingual Next.js site has the code. Whatever the platform, confirm before committing that the tool supports right-to-left layout if the language needs it, and that it covers forms and, for a store, checkout and order emails.
How should the content be translated?
Step 4: translate and review the content
Freeze the source content first. Translating pages that are still being rewritten in English doubles the cost.
Then:
- Write a short glossary: brand names, product names, terms that stay in English, and agreed translations for each service.
- Give the translator access to the staging site, so they see the context of each string.
- Have a second native speaker review the translation, ideally someone in your own team who knows the business.
- Review the result in the layout, not in a document. Line breaks, truncated buttons and awkward headings only show on the page.
Write titles and meta descriptions in the new language from the start, for the words people actually search, not as a translation of the English.
What has to be built besides the translated text?
Step 5: build the language-specific parts
- The language switcher, in the header of every page, linking to the same page in the other language. Language switcher design covers the patterns.
- Fonts for the new script. The brand's Latin font almost certainly has no Arabic; choose an Arabic companion and load it only on Arabic pages.
- Right-to-left layout, for Arabic:
dir="rtl"on the page and mirrored components, fixed one by one where the audit found physical CSS. - Forms, emails and messages: labels, placeholders, validation errors, thank-you pages and confirmation emails.
- Numbers and dates formatted for the new locale.
Step 6: set up hreflang, metadata and sitemaps
Add hreflang tags so each page lists itself and its translation with full URLs, plus an x-default. Our hreflang tag generator produces them. Add every new URL to the sitemap. Make each page's canonical point to itself, never from the translation to the original. Google's guide to managing multilingual sites is the reference for these rules, and hreflang explained has worked examples.
How do you launch without breaking anything?
Step 7: test everything on staging
Test on a staging site, not on the live one, and run the relevant parts of the launch checklist for the new language:
- every template in both languages, on desktop and on a phone;
- every form, submitted for real, with the confirmation email checked in both languages;
- the switcher on every template, including pages without a translation;
- the hreflang tags and canonicals in the page source;
- the existing pages, unchanged, at their existing URLs.
Step 8: launch and keep both languages in sync
After launch, add a Search Console URL-prefix property for the new language folder and watch the new pages get indexed over the following weeks. Use URL Inspection on a few of them to confirm that Google treats each as its own page rather than a duplicate of the original.
Then set up the routine that decides whether the second language survives. Every new page or change in English creates a translation task before it goes live, and someone owns the second language. Without that, the two versions drift apart within months.
Was this guide useful?