--- title: "Is a multilingual website worth it? When it pays off and when it wastes money" description: "Is translating your business website worth it? When extra languages really bring you customers, when it just costs money, and how to do it without mistakes." date: "2026-10-23" category: "Websites for business" keywords: "multilingual website, translate my website, multilingual site for business, is translating my website worth it, website for foreign customers" portada: "/portadas/portada-web-en-varios-idiomas-merece-la-pena.webp" --- A restaurant in a tourist area puts its menu at the door, in Spanish. A group of Germans walks past, looks at it, understands nothing and carries on down the street. The owner has been saying for years that he doesn't need the website in English because "plenty of Spanish speakers come here". And that's half true: plenty of people come, but the ones who spend the most are exactly the ones slipping away. The question isn't whether it looks good to have the website in four languages. The question is whether customers who speak another language are a real part of your revenue. If they are, the website in their language is an open door. If they aren't, it's an expensive ornament you also have to maintain. ## What "multilingual website" really means It is not a button with little flags that translates the text on the fly while the visitor waits. A genuinely multilingual website has its own address per language (`/en/`, `/de/`), its own title and description, a translated menu, translated forms and translated legal texts. Google treats each version as a separate page, and that is exactly what you want: showing up when someone searches for "spanish restaurant in Las Palmas" in English, something that will never happen if your only page is in Spanish. ## Five signs that it is worth it 1. **You get foreign customers and you don't know how many.** Count them for a week: tables, calls, bookings coming from another channel. It's almost always more than the owner thinks. 2. **You sell to people who research before deciding.** Accommodation, aesthetic clinics, renovations, buying a home, language schools. That customer compares three websites before writing, and almost always in their own language. 3. **Your area gets tourism or a stable foreign population.** The coast, the Balearics, the Canaries, big cities. You don't have to be a hotel: a hairdresser in an area with many British residents already notices it. 4. **You take bookings or orders online.** Every doubt in another language is an abandoned cart halfway through. A form in German converts far better than a form in Spanish for someone who doesn't speak Spanish. 5. **Your margin per customer is high.** A renovation, a week of holiday rental, an aesthetic treatment. One extra customer a month pays for the translation several times over. ## When it isn't, and what to do instead - **Emergency and local trades.** Locksmith, drain unblocking, tow truck, emergency vet. Someone with an emergency searches, calls and pays; the volume of searches in other languages is too low to be worth the work. - **Neighbourhood businesses with a steady clientele.** If 95% of your customers live less than two streets away, your language is already theirs. - **A tight budget.** Before translating, invest in your own photos, mobile speed, recent reviews and one page per service. Translating a website that takes five seconds to open fixes nothing: it just makes it take five seconds in two languages. ## How many languages: start with one, not seven English comes first almost always: it's the bridge language for any visitor who doesn't speak Spanish. After that, the second language should be chosen with data, not wishful thinking: German in the Balearics, the Canaries and the Mediterranean coast; French where there is a French or Belgian community; Dutch in specific spots. And here's the part almost nobody calculates: **every language is a maintenance commitment**. When you change prices, opening hours or services, you'll have to change them in every version. A website with four languages and two abandoned ones looks more neglected than a website in Spanish only, well looked after. ## Translating is not running the text through a machine translator Some translations lose customers, and you don't notice until someone laughs at them: - "Menú del día" turned into *day's menu* instead of *menu of the day* or *lunch special*. - "Consulta" translated as *consultation* when the English customer expects *appointment*. - "Reserva" as *reservation* in a restaurant (correct) and in a clinic (where it sounds odd). - Prices in Spanish format (1.250,00 €) mixed with English format (1,250.00), which in a quote look like a different figure. - "Five minutes from the centre" translated literally, without saying which centre. On top of that, the automatic translator installed as a widget pushes the text through JavaScript: the visitor sees the page in Spanish for a second, Google doesn't index it properly and the forms stay in Spanish. It's fine as a stopgap on a content site, not for selling. There are two honest routes: human translation reviewed by someone who knows the sector, or AI translation reviewed by a person fluent in the language. What never works is publishing the machine translation without reading it. ## The four mistakes that ruin a multilingual website 1. **Translating only the homepage.** The visitor lands, understands the headline, clicks "Services" and is back in Spanish. They leave. 2. **A flag switcher with no address of its own.** If the button only changes the text with JavaScript, Google indexes a single version and you'll never appear in searches in the other languages. 3. **Translating your customers' reviews.** A translated testimonial stops being a testimonial. They stay in their original language and, if needed, a line of context is added. 4. **Mixing languages on the same page.** Menu in English, footer in Spanish, form in Spanish, legal notice in Spanish. The visitor concludes the website is half-finished, because it is. ## The technical detail almost nobody sets up It's called `hreflang` and it's an invisible tag that tells Google: "this page is the English version of that one, and this is the German one". Without it, Google may decide to keep a single version and show the Spanish one to a German customer, who will move on to the next result. You don't need to know how to code to demand it. Just ask whoever builds the website: "does each language have its own address and its own hreflang tag?". If the answer is "the what?", change provider. ## How to know after three months whether it worked - Look in your statistics at how many visits come in through `/en/` and `/de/`, not the website total. - Add a question to the form: "which language would you like us to reply in?". - Count the quotes you close with foreign customers and compare them with the previous quarter. - If a version doesn't even reach twenty visits in three months, don't delete it: it's the perfect excuse to review whether the content answers what that audience is looking for. ## A realistic plan in three steps First, English. Translate only the five pages that matter: homepage, services, prices, contact and legal notice. Measure for three months. If people come in, add the second language on the same terms. Don't launch seven languages on day one. Two articles that help you decide: [how to fill tables at a restaurant with your website](/blog/en/web-para-restaurantes-como-llenar-mesas) and [what a holiday rental website needs](/blog/en/web-para-apartamentos-turisticos-y-alquiler-vacacional). And if budget is what's holding you back, here is [what a business website really costs](/blog/en/cuanto-cuesta-una-pagina-web-para-negocio). This very website publishes its blog in seven languages, article by article, with a review in each one: it can be done without multiplying the cost by seven. If you want to see what yours would look like in two or three languages, you can [request a free design proposal](https://www.pedroaren.com/solicita-web/en) and decide afterwards, with no commitment.