If your website speaks only one language, you are quietly turning away buyers who are ready to pay. Research is clear: most people prefer to read and buy in their own language, even when they understand English. Multilingual website design is how a small or medium business opens a second, third, or fourth market without building a second, third, or fourth company. This guide walks through the decisions that matter most: translation versus localization, URL structure, hreflang, and a language switcher your visitors can actually find.
We will keep this practical. You do not need an enterprise budget to do this well. What you need is the right structure from day one, because fixing language architecture after launch is far more expensive than planning it before. Treat this as the blueprint you follow before the first page gets translated.
Why multilingual website design pays off for SMEs
The business case starts with a number. In the CSA Research study “Can’t Read, Won’t Buy”, which surveyed 8,709 consumers across 29 countries, 76% of online shoppers said they prefer to buy products with information in their native language, and 40% said they will never buy from websites in other languages (CSA Research). For a Vietnamese exporter or a service business courting foreign customers, that second figure is the one that stings: nearly half of a potential audience may leave before reading your offer.
Multilingual website design turns that leakage into revenue, and it compounds over time. Every localized page is a new entry point for search traffic in a new market, which means your content works for you in several languages at once instead of one. The upfront effort is real, but so is the long tail of qualified visitors it brings for years after you publish.
Translation is one step, localization is the goal
Translation swaps words from one language to another. Localization adapts the whole experience so it feels native: currency and date formats, examples and imagery, payment methods people trust locally, and a tone that matches how buyers in that market actually speak. A page can be grammatically perfect and still feel foreign if the prices are in the wrong currency and the call to action reads like a machine wrote it.
This is why machine translation alone rarely wins trust. Use it to move fast on high volume content, then have a human review anything that touches money, legal terms, or your core sales message. The goal is a visitor who forgets they are reading a translated page, because nothing on it reminds them that they are.
Pick the URL structure before you translate a word
Where your languages live in your URLs affects SEO, maintenance cost, and how clearly users understand where they are. Google supports three main approaches, and the right one depends on your resources and how many markets you target (Google Search Central).
| URL structure | Example | Best for | Watch out for |
|---|---|---|---|
| Country domain (ccTLD) | shop.de | Strong geographic targeting, clear trust signal | Costs more, one domain per country, more to maintain |
| Subdomain | de.shop.com | Easy to set up, can host in different regions | Users may not know if “de” means language or country |
| Subdirectory | shop.com/de/ | Low cost, low maintenance, inherits domain authority | Single server location, needs a clean internal structure |
For most SMEs we recommend the subdirectory approach. It keeps all your search authority on one domain, it is the cheapest to run, and it scales cleanly as you add languages. Reserve country domains for the day a single market is large enough to justify its own operation. Avoid putting the language in a URL parameter such as a query string, because Google does not recommend it and it is fragile for both users and crawlers.
Tell Google which language to show with hreflang
Once you have localized pages, you need search engines to show the right one to the right person. That is the job of hreflang annotations, which tell Google that a Vietnamese page and its English equivalent are the same content in two languages, not duplicates competing with each other. Google recommends hreflang as the primary way to link language versions (Google Search Central). Add an x default version too, so searchers who match none of your languages land on a sensible fallback.
Two mistakes cost SMEs the most here. First, automatically redirecting visitors based on their IP address or browser setting: Google advises against it because it can stop users and crawlers from seeing all versions of your site, and it frustrates the traveller or expat who wants a language other than their location implies. Second, serving several languages on one URL, or changing language with a cookie instead of a distinct address. Keep one language per page, each on its own URL, and let people choose.
Make the language switcher easy to find and trust
The switcher is a small element with an outsized effect on whether international visitors stay. A few rules, drawn from the US Web Design System and Google, make it work (US Web Design System):
- Label each language in its own language. Write “Tiếng Việt”, “English”, “Deutsch”, not the translated names, because people scan for the word they recognize.
- Do not use flags to represent languages. Flags map to countries, not languages, and one language often spans many countries.
- Place the switcher at the top right of the header, as a single independent control, so it stays where international users instinctively look for it.
- Let users choose rather than forcing a language on them, and skip automatic redirects based on location.
- Keep the switcher visible in sticky headers, and send users to the matching page in the new language, never to a near empty landing page.
Get these right and the switcher disappears into the background, which is exactly what you want. A confused visitor who cannot find their language is a visitor who leaves, and they rarely come back to try again.
Webie’s take: In our own projects we default to the subdirectory structure for exactly the reasons above: it is the most convenient and common setup, quick to stand up, and easy to manage as the number of languages grows. On one multilingual site we built for a Vietnamese SME selling abroad, the share of visitors arriving on the second language grew 30 to 45% after we structured the languages properly and let search engines index each one. My honest advice on translation: for a website that sells, invest in human translation. Automatic tools get you live fast, but a person keeps the meaning and the small nuances intact, and that is what makes a foreign visitor trust you. We reserve machine translation for bulk pages and bring a human to everything that carries the message.
Your multilingual website launch checklist
Use this as a working checklist before you push a multilingual site live. It covers the decisions that are painful to change later:
- URL structure chosen and kept consistent across every language
- hreflang annotations in place, including an x default fallback
- One language per page, each on its own URL, with no cookie based switching
- Language switcher with endonyms, no flags, placed at the top right
- No automatic redirect based on IP or browser language
- Currency, dates, phone formats, and payment methods localized per market
- Human review of every page that touches money, legal, or your main sales message
If this list already feels like a lot alongside running your business, that is normal. Building and maintaining multilingual sites is part of what we do at Webie, from architecture to SEO in each language. You can see the full scope on our services page.
Frequently asked questions
It is good enough to launch high volume content quickly and to help visitors who would otherwise have nothing in their language. It is not good enough on its own for pages that sell, explain pricing, or carry legal weight. The reliable pattern is machine translation first, then human review on the pages that matter most.
For most SMEs a subdirectory such as yoursite.com/en/ is the better start. It is cheaper, easier to maintain, and keeps all your search authority on one domain. Move to a dedicated country domain only when a single market grows large enough to justify running it separately.
Not if you set it up correctly. hreflang annotations tell Google that your language versions are alternates of the same page, not duplicates. The risk appears only when pages have no hreflang, mix languages on one URL, or redirect automatically. Done properly, each language earns its own search visibility.
Ready to open your next market? Talk to the Webie team about a multilingual website built for growth. Call +84 969 838 467 or email huyen.dang@webie.com.vn and we will map the right structure for your business.
