Bilingual website: when it pays off and how to do it right
A real bilingual site needs a separate address for each language. If both languages share one URL and swap with a button, Google indexes only one and the other does not exist for search. It is worth it when a real share of your customers searches in the other language, not when you simply want to look international.
The mistake that cancels all the work
The most common setup is an EN/ES toggle that swaps the text on the same page. It looks fine and does nothing for ranking: there is one address, Google indexes whichever language it finds first, and the other competes for no search at all.
All that translation work stays invisible to the one thing you did it for.
How it is done properly
Each language at its own address, with the address translated too: /en/services/ and /es/servicios/. The two link to each other with hreflang, which tells Google they are the same page in two versions and not duplicate content.
On a legal services site built this way, each language got its own address, and the site ended up with twenty-seven indexable pages instead of the handful one language would have given it.
What almost nobody translates and should
The contact channel. The most important and the least considered. If your customers in one language prefer WhatsApp and in the other email, the button itself has to change with the language, not just its label.
The URLs. A Spanish URL ranks for Spanish words. Translating the text and leaving the address in English wastes half the work.
Titles and descriptions. They are what shows in Google. If they exist in one language only, the translated page appears with the wrong title. And keep in mind that your Google Business Profile does not get a second version: you pick one primary language, and it should be the one most of your customers use.
When it is not worth it
If the second language is a hunch rather than a fact. Look at where your inquiries come from today before duplicating the whole site, because you duplicate the maintenance too: every change becomes two.
And if you’re going to translate with an automatic plugin, don’t. A machine translation nobody edited tells your customer you didn’t care enough to read it.
Frequent questions
Subdomain, subdirectory or separate domain?
Subdirectory, almost always: both languages inside the same domain, because it concentrates all the authority on one site instead of splitting it across two. What you should not do is stop halfway at /es/services/: if the prefix is the language, what follows is translated too. A separate domain is only justified when you genuinely operate in two countries, with a different address and phone number in each.
What if I only translate some pages?
You can, and sometimes should: translate the ones that answer searches in that language and leave the rest. What you must not do is link to a version that does not exist, because it sends the visitor to an error.
Should the site detect the visitor’s language automatically?
Detect yes, redirect automatically no. A forced redirect based on browser language confuses Google — which crawls mostly from the United States and in English — and ends up indexing a single version. What works is opening in the language of the address the person actually asked for, with the switch visible at the top. If you want to suggest the other language, use a dismissible notice, not a page change they did not ask for.