Multilingual website: when and how to do it right

I'm Elmar Mamedova, a full stack developer in Málaga, and I will be blunt from the start: a multilingual website is only worth it when you have a real audience in another language or a concrete plan to reach one. Translating for the sake of it does not sell more; it creates double the work, double the maintenance and, done badly, it can even penalize you on Google. Before jumping into several languages, the question is not «can I?», but «who do I want to reach and in which language do they actually search for me?».

In this article I will explain when it makes sense to take the leap, which URL structure to choose, how to avoid the SEO mistakes I see over and over, and what really gets translated and what does not. All from the experience of building and maintaining bilingual websites, not from theory. If you want to see how I approach full projects, you will find it on my web development page.

The rule I apply is simple: every language is a product you have to keep alive. If you are not going to update, review and answer customers in that language, better not open it. I have seen websites with a ghost English version, outdated texts and a form nobody attends. That gives a worse impression than having no English version at all, because it promises something it then fails to deliver.

That said, there are cases where going multilingual is a clear growth lever. If you sell to tourists or foreign residents, if you export products, if you work with international clients or if your sector runs in English by default, every visit in the right language converts far better. In a city like Málaga, with so many foreign residents and so much tourism, a well-made English version can make the difference between being found or losing the person to a competitor.

• You sell to tourists, expats or foreign residents in your area.
• You export products or provide services outside your country.
• Your sector communicates in English by default (tech, boating, luxury).
• You have real traffic or enquiry data in another language that you lose today.
• You can commit to keeping every version as cared for as the main one.

This is where half the SEO game is decided, which is why it pays to choose wisely. You have three main paths to separate languages, and each has consequences. For most businesses serving one market in several languages, the cleanest and simplest option to maintain is the subdirectory, like yourdomain.com/en. It concentrates all the authority on a single domain and it is the one I use by default unless there is a strong reason not to.

1. 1Subdirectory (yourdomain.com/en): the recommended option; one website, concentrated authority and simple maintenance.
2. 2Subdomain (en.yourdomain.com): valid if you need to separate infrastructures, but Google treats it almost like a separate site.
3. 3Country domain (yourdomain.co.uk): only makes sense with different teams and strategies per market, and it multiplies the cost.

Whatever you choose, the important thing is that each language has its own indexable URL. Never hide languages behind a button that swaps the text with JavaScript without changing the address: for Google that is a single page and you lose all the potential to rank in the other language. Each version has to be a real page, with its URL, its title and its content truly translated.

Mistake number one is not using hreflang tags, or using them badly. These tags tell Google which version to show each user according to their language, and they prevent your own pages from competing with each other. Without them, it is common for Google to show the Spanish version to someone searching in English, or to read the two versions as duplicate content. Set up properly, each person lands in the right language.

The second classic mistake is unreviewed machine translation. A text translated by a machine and published as is stands out, gives a poor impression and Google detects it. The third is forgetting to translate what is not visible: meta titles, descriptions, image alt text and structured data. There is little point translating the body if the result in the search engine still appears in Spanish. If you want to get this part right, I recommend my article on migrating a website without losing SEO, because many mistakes are made at exactly that moment.

• Set up hreflang on every page, with the x-default tag for the default language.
• Do not publish machine translation without human review; it shows and undermines credibility.
• Translate meta titles, descriptions, image alt text and structured data too.
• Keep a map of equivalences: each URL in one language points to its twin in the other.
• Generate a sitemap that includes all language versions correctly linked.

Not everything has to be in every language, and accepting that saves you a huge amount of work. What I always translate is everything that touches the sale and trust: service pages, home page texts, forms, adapted legal notices and error or confirmation messages. These are the pages that decide whether someone hires you, so in their language they have to sound natural, not like a brochure translated in a rush.

What often is not worth translating one hundred percent is the full blog or very local content that only interests one audience. Here I prefer a realistic strategy: translate the articles people really search for in the other language and leave the rest in the original language. It is better to have twenty impeccable pages in two languages than a hundred half-done. Perceived quality matters more than quantity, especially when the goal is to sell.

Technically, I build multilingual websites with an architecture designed to scale from the start. Texts are not hard-coded by hand into each page, but centralized in translation files, so that adding or fixing a language does not force you to touch the code. Each language has its URL, its hreflang and its sitemap, and the language selector genuinely changes the address, not just the text on screen.

This has a huge maintenance advantage: when the business changes a price, a service or a phone number, it is updated in an orderly way and you do not risk the English version falling out of date. A poorly built multilingual website ages terribly; a well-structured one is maintained with almost the same effort as a normal website. The difference lies in the decisions made at the beginning, not in the number of languages.

A multilingual website is a great tool when it answers a real need and is executed with judgment. The key is not how many languages you have, but that each one is cared for, indexable and truly speaks your customer's language. If you are going to do it, do it right from day one: clean URL structure, correct hreflang, reviewed translation and maintenance designed to last.

And if you are unsure whether it is worth it, start with the data: look at where your visits come from and which language your customers really search in. Often the answer is right there, waiting. If you want us to look at it together so you can decide with judgment, write to me through the contact page and I will tell you honestly whether multilingual is your next step or not.