Do you need a multilingual website?
You need a multilingual website when a meaningful share of your customers prefer to search, read or buy in another language, and you can serve them in that language after they contact you. For a US business that might be Spanish; for a UK exporter it might be French or German; for a brand selling into the Gulf it is usually Arabic.
Translate for real demand, not for appearance. Check Search Console and analytics for visitors from other countries and languages, ask your sales team which languages customers use, and look at search volume in the target language. Start with the pages that earn revenue, such as the home page, key services or products, checkout and contact, then expand once the first language proves its value.
- Good reasons: customers who search in that language, a new market, or a legal or contractual need
- Weak reasons: wanting to look international, or a plugin that makes translation seem free
- Before you start: someone who can answer emails, calls and support in that language
- First pages: home, key services or products, pricing, checkout, contact and policies
- Budget for: translation, native review, design changes and ongoing updates in every language
Which URL structure is best for a multilingual website?
For most businesses, subfolders such as example.com/es/ or example.com/ar/ are the best URL structure for a multilingual website, because every language shares the main domain's authority and is simple to manage. Subdomains such as es.example.com and separate country domains such as example.co.uk also work, but they take more effort to build up and maintain.
Whatever you choose, give every language version its own URL. Avoid switching languages only with cookies, scripts or browser settings on a single URL, because search engines will usually see and index just one version. Google also advises against redirecting visitors automatically based on their location or browser language; offer a clear language switcher instead and let people choose.
- Subfolders: /en/, /es/ and /ar/ on one domain, the simplest option for most sites
- Subdomains: es.example.com, useful when versions run on different systems
- Country domains: example.co.uk or example.ae, a strong local signal but more to manage
- Avoid: URL parameters such as ?lang=es and cookie-only language switching
- Language switcher: labeled with each language's own name, such as Español or Deutsch, rather than flags
How do you design an Arabic or other right-to-left website?
Design a right-to-left website by mirroring the whole layout, not just the text: navigation, columns, directional icons, progress steps, carousels and form fields all flip to read from right to left. Set the page's language and direction attributes correctly for Arabic, Urdu, Persian or Hebrew, so browsers, screen readers and translation tools handle the text properly.
Typography matters as much as layout. Choose a font designed for Arabic script, such as Noto Naskh Arabic, IBM Plex Sans Arabic or Cairo, allow extra line height, and never add letter spacing, which breaks the joined letters. Make sure phone numbers, prices and Latin brand names display correctly inside Arabic sentences. Devmenta's Arabic website design service covers all of this.
- CSS logical properties, such as margin-inline-start, so one stylesheet serves both directions
- Directional icons and arrows mirrored, while logos, media controls and clocks stay as they are
- Forms and validation messages tested in both directions
- Numbers formatted consistently, with Western or Eastern Arabic numerals chosen for the audience
- Layouts checked with real Arabic copy on real phones, not placeholder text
What is the best translation workflow for a website?
The best translation workflow combines a glossary and style guide, translation by a professional or a machine translation engine, review by a native speaker who knows your industry, and a final check of each page in context on a staging site. Translating text in a spreadsheet without seeing the page is how buttons overflow, headings break and meaning gets lost.
Google's spam policies can treat large amounts of automatically translated content published without human review as low-value, and customers notice awkward phrasing immediately, so machine output should always be edited by a native speaker. Plan for updates too: when an English page changes, the translated versions need the same change, ideally flagged by your plugin or translation tool, so languages never drift apart.
- A glossary of product names, service terms and words never to translate
- A style guide for tone, formality and regional variants, such as Latin American or European Spanish
- Native review for every customer-facing page
- Translated metadata, image alt text, URL slugs, forms, emails and error messages
- Professional translation for legal pages, contracts and medical or financial content
How do you do SEO for each language?
Do SEO for each language as if it were a separate market: research keywords in that language, write titles and meta descriptions natively, and earn links and mentions from sites in that language and region. Translating your English keywords word for word often misses how people actually search, because phrasing, slang and even product names can differ.
Arabic is a good example: people may search in Modern Standard Arabic, a local dialect, Arabic written in Latin letters, or English, so check search data for each form. Localize URL slugs where it helps, include every language in your sitemap, and monitor each language folder separately in Search Console. Answer-first content in each language also helps AI tools quote you correctly.
- Keyword research for each language and country, not one translated list
- Native titles, meta descriptions and H1s written for local searchers
- Local proof: reviews, case studies and contact details relevant to that market
- Separate Search Console reports for each language folder
- Internal links that keep visitors within their chosen language
Which platforms handle multilingual websites best?
WordPress, Shopify, Webflow and custom frameworks can all run good multilingual sites; the difference is how translation and hreflang are managed. On WordPress, plugins such as WPML, Polylang and TranslatePress handle language versions. Shopify uses its Translate and Adapt app with Shopify Markets, and services such as Weglot work across several platforms.
Custom builds on frameworks such as Next.js give the most control over routing, hreflang and right-to-left layouts, which suits complex web apps and bilingual portals. Whichever platform you pick, confirm before building that it supports separate URLs per language, translated metadata and slugs, automatic hreflang, right-to-left themes if you need them, and a workflow your team can run without a developer.
- WordPress: WPML, Polylang or TranslatePress, plus a theme with RTL support
- Shopify: Translate and Adapt, Shopify Markets and an RTL-ready theme for Arabic
- Webflow: built-in localization, available as a paid add-on
- Custom: Next.js or similar with internationalized routing, for apps and portals
- Any platform: the language switcher, forms and checkout tested in every language
What mistakes should you avoid with a multilingual website?
The most common multilingual mistakes are automatic redirects based on location, half-translated pages, missing or one-way hreflang tags, raw machine translation, and forgetting the parts of the site people see after the click, such as forms, confirmation emails, checkout and error messages. Each one either confuses search engines or makes customers doubt you can really serve them.
Devmenta has built bilingual and right-to-left sites for real clients, including Lamset Noor Studio, a bilingual Arabic and English photography studio in Saudi Arabia, and Chef & Sweets, a restaurant with Russian menus and WhatsApp ordering. Our web development team plans URL structure, hreflang, translation workflow and per-language SEO from the start.
- Automatic redirects by IP or browser language that trap visitors in the wrong version
- Country flags used for languages, which confuses speakers from other countries
- Pages that mix languages, or translated body copy under English titles and menus
- One-way or broken hreflang links, and canonical tags pointing across languages
- Untranslated checkout pages, confirmation emails, PDFs and error messages
- Contact details, prices or offers that differ between language versions