Building a bilingual website that ranks in both languages

A bilingual website that ranks in both languages is built like two sites sharing one foundation: each language has its own URLs, content written for its own audience, and tags that tell Google which version to show to whom. Translation is only part of the job. What matters is that each version stands on its own, for visitors and for search engines.

Plenty of small businesses need a second language. A dental clinic in Lisbon treats Portuguese patients and English speaking expats. A cooking school in Bangkok attracts tourists. An engineering firm sells to clients across Europe. A property agency works with overseas buyers. The question is rarely whether to add a language. It is how to do it without weakening the original site or publishing a version nobody finds.

What is a bilingual website, and who needs one?

A bilingual website presents the same business in two languages, with an easy way to switch between them. It makes sense when you have two real audiences who search for you in different languages.

Before you start, answer three questions. Who is the second audience? What do they need to know? Who will reply when they get in touch? A polished second version that generates enquiries nobody can answer is worse than no second version. And if the second audience only needs the basics, a handful of focused pages may be enough.

How does Google understand a bilingual website?

Google needs to see each version on its own URL, with a clear signal linking the versions together. Without that, it may show the wrong language to a searcher, or not index one version at all.

A separate URL for each language

There are three common structures: a folder (example.com/pt/), a subdomain (pt.example.com) or a separate domain per country. For most small businesses a folder is the simplest choice, because everything stays in one site, one content system and one set of reports.

What to avoid: switching the language on the same URL based on a button, a cookie or the browser’s settings. Google will usually see only one of the versions, and the other might as well not exist.

Hreflang tags

Hreflang tags are short lines of code that tell Google: this page also exists in Portuguese, and here is the address of each version. Every version must reference itself and the other one. If only one side does, Google may ignore the tags. You can also add an x-default value to say which version to show people whose language matches neither.

A canonical tag per version

Each page’s canonical tag should point to itself, in its own language. A common mistake is pointing the second language version to the original. Google then treats it as a copy and does not show it.

No forced redirects by location

Automatically redirecting visitors by country or browser language sounds helpful, but it can stop both Google and people from reaching the version they need. Show a default version with a clear language switcher instead. You can gently suggest the other version, without forcing anyone there.

How do you research keywords for a bilingual website?

Do separate research for each language, because people do not search in translation. Someone in Lisbon searching in Portuguese for a dentist types something different from an expat who wants an English speaking dentist nearby, and the second search reflects a different need.

For each language, check:

• The phrases people actually type, not just the dictionary translation
• Terms locals search in English anyway, such as product and technology names
• Which competitors appear in each language, since they are often not the same
• Questions the second audience has that locals do not, such as language of service, getting there or paying from abroad

Our keyword research guide explains the method step by step.

Why is translation not enough?

Translation answers “what does the original say”. Localisation answers “what does this audience need to hear”. An overseas buyer looking at a flat needs to understand how buying works in that country, not the same copy written for a young local couple.

Machine translation or an AI draft is a fine starting point, but a native speaker should edit every page. Copy that reads as translated pushes visitors away, and unedited automatic content risks being seen as low quality.

One more point that is easy to miss: Google works out a page’s language from its visible content. An English page with menus, buttons and image alt text in another language sends a mixed signal. Translate everything: titles, meta descriptions, navigation, forms, error messages and the thank you page.

What changes when one language reads right to left?

If one of your languages is Arabic, Hebrew, Persian or Urdu, that version needs a genuinely mirrored layout, not just right aligned text. Menus, arrows, icons and form fields all flip direction. Phone numbers, email addresses and English words inside a sentence need to display in the right order, and punctuation should not jump to the wrong end of the line. Plan for both directions from the start: retrofitting right to left onto a finished site is where small, annoying bugs appear.

Whatever the languages, the code should declare each page’s language and direction. Browsers and screen readers rely on it to display and read the page correctly.

How do you build a bilingual website step by step?

1. Define each audience. Who they are, what they search for and who answers them.
2. Choose which pages exist in each language. You do not have to translate everything. A few strong pages beat many weak ones.
3. Pick a URL structure. Usually a folder per language, with short, readable addresses in each.
4. Research keywords separately for each language, and write the content around them.
5. Set up hreflang, canonical tags and a sitemap for both versions, then confirm in Google Search Console that both are crawled and indexed.
6. Build a language switcher that links to the equivalent page, not the home page. If a page has no translation, the switcher should not lead to a broken link.
7. Send enquiries to your CRM tagged with their language, so every lead is answered in the language they used.

A small tip for the switcher: write each language’s name in that language, such as “Português” and “English”, rather than using flags. A flag stands for a country, and many languages are spoken in many countries.

What happens when an enquiry arrives in the second language?

This is where bilingual websites succeed or fail. If the English form lands in a shared inbox and nobody replies in English until tomorrow, the investment is wasted. When each enquiry reaches the CRM with its language and the page it came from, routing it to the right person is easy. A WhatsApp bot can reply instantly in the customer’s language and book a call with someone who speaks it.

Businesses selling abroad also face time zones. A customer in another region may get in touch while your team is asleep. We look at that side in our article on taking your small business international.

A bilingual website checklist

• Each language has its own URLs
• Hreflang tags point both ways, and canonicals point to the page itself
• No forced redirects based on location
• Keywords are researched separately for each language
• Every element is translated, including menus, forms and alt text
• Right to left layouts, if any, are tested on mobile
• The language switcher leads to the matching page
• Every enquiry reaches the CRM tagged with its language

Two audiences, one system

A good bilingual website is not the original with a translation pasted on. It is two versions, each written for its audience, clearly marked for Google and connected to the same enquiry system. The basics of SEO for small business apply twice, once per language. At Kaede Digital we work in more than one language every day, our own site is built this way, and our team spans Tel Aviv, Lisbon, Bangkok and Tokyo. If you are planning a site in two languages, take a look at our small business website design service.

FAQ

Is translated content treated as duplicate content?

No. Google does not treat the same content in two different languages as duplicate content, as long as each version has its own URL and is marked up correctly. Duplicate content problems come from near identical pages in the same language.

Do I need to translate my whole website?

Not necessarily. Start with the pages the second audience really needs: the home page, your main service pages, about and contact. Expand later based on the enquiries and searches you see.

Can I use machine translation for my website?

As a first draft, yes. Before publishing, a native speaker should edit the text, adapt the messages to the audience and check the keywords. Copy that sounds translated damages trust, and visitors notice quickly.

How do I know Google understands both versions?

In Google Search Console you can check that pages in both languages are indexed and see which searches each version appears for. Also test by hand: search for your business name and main service in both languages and confirm the right version shows up.