Web

Multilingual website on the Costa: how many are worth it

How many languages depends on who writes to you and who buys from you, not the map. Better a few complete, checked versions than many half-done.

by ·October 23, 2026·12 min read

Whether to have a multilingual website is not something you decide by looking at a map of where the tourists come from. You decide it by looking at the language people write to you in, and the one they buy or book in. And a half-finished second version, with the menu translated and the rest in Spanish, or with a translation nobody has checked, usually does less good than a single version done properly: better a few complete languages than many half-done.

Say Lola, an invented name like everything else in this example, runs a small restaurant on the seafront promenade in Torre del Mar. During the week she hears from British neighbours who live in the area all year round and ask in English whether she has a table on the terrace. A Dutch couple send her messages to find out whether there are gluten-free dishes. In summer, French families book from their hotel. Some time ago, someone set up an English version for her: the navigation menu says ‘Home’, ‘Menu’ and ‘Contact’, but the menu itself, the group bookings policy and the opening hours are still in Spanish. The booking button leads to a form in Spanish, and the confirmation arrives in Spanish. In autumn she changed her closing time and updated it only on the Spanish version, so the English one still shows the summer hours. To top it all, the website detects the phone’s language and sends anyone whose phone is set to English to the English version, including her nephew, who lives in Málaga and wanted to see the menu in Spanish.

Nobody did anything wrong on purpose. What was easy to translate got translated, and the rest was left for later. The result is that Lola answers the same questions over and over again, and the odd customer turns up after the kitchen has closed.

How many languages are worth it on a multilingual website for your business

The useful question is not ‘where do the people passing through the Axarquía come from?’ but ‘who writes to me, who pays me and who is going to keep this up?’. Four questions will give you a better answer than any general statistic.

Which language they write to you in. Open your email, your messages and the notes on your phone from the last few weeks. Look at the language the enquiries arrive in, not the country of the person sending them. A German or Dutch customer may well write to you in English, and a business’s second language does not always have to be English. What your inbox says carries more weight than what any of us assume.

Which language they book or buy in. Not everyone who asks ends up paying. If the enquiries in one language are mostly curiosity and the bookings arrive in another, give priority to the language of the people who book. For a clinic or a garage, think about who makes appointments and comes back; for holiday accommodation, think about who pays for the stay.

Who will maintain each version. Every language multiplies the work involved in every change. New opening hours, a seasonal menu or a price rise all have to be changed in every version at once. If there is nobody with the time to do it, or a clear habit of getting it done, the second version will go out of date before the first.

Who will reply. A page in German tells the visitor they can write to you in German. If you then reply in Spanish or in a few disjointed phrases, the website will have promised something the business does not deliver. Publish in the languages you can actually serve customers in, even if it takes some help and some time.

With that in mind, the practical rule is simple: start with the language your customers use most besides Spanish, do it in full and check that it works for a few months. Only once that version stays up to date without effort does it make sense to think about a third. For many small businesses on the coast, two languages handled well already cover nearly everyone who actually writes to them.

What Google’s guidelines ask for, in plain English

Google publishes two guides on websites in more than one language. We summarise them here without embellishment and without adding anything they do not say.

The first point is that Google does not work out a page’s language from the technical tags. According to its guide on localised versions of a page, it does not use hreflang annotations or the HTML lang attribute to detect which language a page is in; it uses algorithms. And in its guide on multi-regional and multilingual sites, it explains that it looks at the visible content of the page. In other words, if the text is in Spanish, the page is in Spanish, whatever the menu says.

That leads to the second point. Google recommends using a single language for the content and navigation of each page, and avoiding side-by-side translations, with Spanish in one column and English in another. Its guide to multilingual and multi-regional sites also warns that translating only the fixed text, such as the menu and footer, while most of the content stays in one language can create a bad experience if the same content appears several times in search results with that fixed text in different languages.

The third point concerns addresses. Google recommends a separate URL for each language, rather than serving one or the other based on cookies or browser settings. It asks you to avoid redirecting people automatically to a version based on the language or region you think they have, and not to use IP address analysis to adapt the content. One option it suggests is showing visible language links on every page, so people can choose their language themselves.

The fourth point is hreflang tags, which tell Google which pages are translations of one another. The rules are few and strict. Each version has to list itself and all the others. If two pages do not point to each other, Google ignores those tags. Google also suggests considering a fallback page, marked with the x-default value, for people who speak a language you do not offer. It can be any page, and it is especially useful on a language or country selection page, or on a home page that redirects visitors automatically. The code indicates the language, and optionally the region, but you cannot indicate a country on its own.

Finally, some reassurance: versions in different languages are only treated as duplicates if the main content is left untranslated. A complete translation is not treated as duplicate content.

This website is itself published in Spanish, English and French, with one URL per language (/es/, /en/, /fr/), hreflang tags that list one another and an x-default; we checked its code on 14 October 2026.

What breaks on a multilingual website

The idea rarely fails; the details do. Here are some of the things that can go wrong, and nearly all of them can be checked in a few minutes if you know where to look.

Translated menu, Spanish text. This is Lola’s case. Visitors think they have found your website in their language, tap ‘Menu’ and find the menu itself in Spanish. For them it is worse than if the website had been only in Spanish from the start, because you have made them a promise and not kept it. And, according to Google’s guide, it is the visible content that counts.

Opening hours or prices updated in only one version. This is the costliest mistake and the quietest. Nobody tells you that the English version says you open on Mondays. You find out when someone turns up and finds the shutters down. Every change to opening hours, prices, seasons or terms has to go into every version on the same day.

Form or confirmation in only one language. The page is translated, but the contact form asks for ‘Nombre’ and ‘Teléfono’, the error messages appear in Spanish and the confirmation email arrives in Spanish. Right at the moment the customer is making up their mind, you switch language on them. Check the whole journey, from the button to the email they receive afterwards.

Automatic redirection by IP or browser language. It looks convenient and it is not. The British resident who wants to practise their Spanish, the Spanish tourist whose phone is set to English or the neighbour using a work computer all end up on a version they did not choose. Google asks you not to redirect like this or adapt content by IP. The right approach is to show the version the visitor has arrived at and offer them a clear language switcher.

A switcher that sends people to the home page. Someone reads your prices in English, switches to French and lands on the French home page, having to look again for what they were reading. The switcher has to take them to the same page in the other language. If that page does not exist in that language, the honest thing is to say so, not to hide it.

Unchecked translation. An automatic translator can be useful for a first draft, but on a menu, in booking terms or in a clinic’s instructions, a badly translated sentence causes confusion or worse. Someone who speaks the language well should read it before it goes live.

There is a way of doing this well that is worth copying: telling people what stays in one language. On the new Club Natación Axarquía website, the English version is not just a translated menu: groups, programmes, calendar, results and contact details are in English too. And the website flags what stays in Spanish: the names of the championships, as published by the federation, and the registration form. Better to flag it than to have people find out at the counter.

The same goes for your home page. If you have already worked on giving it a single button that is clear, that button has to lead, in every version, to the form in the same language, not to the Spanish one.

Before and after: what you can check this week

You do not need to rebuild anything to find out what state your website is in. This table works as a checklist. Each row takes a few minutes to check on your phone.

TodayChangeHow to checkWho
The menu is in English and the content in SpanishTranslate the full content of the pages used in that language, or take the version down until it is readyOpen three pages of the English version and read the first paragraph of eachYou, with whoever helps you translate
The opening hours or prices were updated in only one versionChange the details in every version on the same day and note it in a change logPut the opening hours page for each language side by side and compareWhoever updates the website
The form or the confirmation arrives in SpanishTranslate the labels, error messages and confirmation emailSend a test enquiry from the English version and read the email you receiveWhoever runs the website
The website switches language by itself depending on the phoneRemove the automatic redirection and add a visible switcher on every pageSet your phone to English, go to the Spanish address and see whether it switchesWhoever runs the website
The language switcher sends people to the home pageMake it lead to the same page in the other language, or flag it if that page does not existFrom the contact page, switch language and see where you landWhoever runs the website

If every row checks out, your multilingual website is in good shape on these points. If two or more fail, it may be worth keeping a single version done properly while the other one is fixed.

Who this is not for

Not every business needs a second version, and saying so is part of the job too.

If nearly all your customers are local and write to you in Spanish, a well-made website in one language will serve you better. A garage in Vélez-Málaga that works mainly for people from the town gains nothing from a French version nobody is going to read.

If nobody in the business can serve customers in that language, think twice. A page in English invites people to write in English. If the replies take days or arrive in Spanish, the customer will feel less well looked after than if they had found the website in Spanish only.

If you are not going to maintain the second version, better not to start it. Wrong opening hours in English do more harm than having no English at all. And if nearly all your bookings come through platforms that already show your listing in the customer’s language, a version of your own can wait until you have time to look after it.

And if what you are after is showing up in more places by adding languages without translating them properly, Google’s own guidelines explain why that does not work: the language is determined by the visible content, and a version whose main content is left untranslated is treated as a duplicate.

What we would do

In a case like Lola’s, we would start by asking which language people write and book in, not by looking at the map. Most likely she would end up with two complete languages: Spanish and the one her customers use most. The pages that matter would be in that language in full, with a switcher that leads to the same page, a form and a confirmation in the language of whoever is writing, and a clear notice of the little that stays in Spanish.

The package that fits is Presence, which includes up to three languages (ES / EN / FR). In the brief we ask you for the languages you need at launch, and you can start with one and add later without rebuilding the website. The timeline is 21 to 30 days, counted from brief sign-off, assuming timely feedback on drafts.

For reference, Presence costs €1,490, Bookings €1,690, Shop €1,990 plus €89 a month and Operator €3,950 plus €99 a month; Care maintenance is a flat €69 a month, all excluding VAT.

With Care you get managed hosting, SSL, backups, security and dependency patches, and up to 1 hour a month of minor content or configuration changes, with email support from the same team that built the website.

If you would like to see what each package includes and request a quote, here are the Web & eCommerce packages.

Sources

  1. ‘Tell Google about localized versions of your page’. Google Search Central. https://developers.google.com/search/docs/specialty/international/localized-versions. Accessed 14 October 2026.
  2. ‘Managing multi-regional and multilingual sites’. Google Search Central. https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites. Accessed 14 October 2026.

Prepared by the Yerbabuena Digital editorial team with the help of AI tools for research, drafting and review; a member of the studio checks the facts, sources and conclusions before publication. Have we measured or cited something wrongly? Write to us at hola@yerbabuena.digital and we will correct it, with the date.

Frequently asked questions

Can I rely on the browser's automatic translation instead of translating my website?

It helps the visitor, but it is not a version of your own. You have no control over how it translates your menu, your terms or your opening hours, and you have no address of your own for each language that you can link to or send to a customer. Google recommends separate URLs for each language rather than relying on cookies or browser settings. If a language matters to you, it deserves a version checked by someone who speaks it well.

Is it better to have one domain per language or folders such as /en/ and /fr/ on the same domain?

The Google sources we cite ask for a separate URL for each language, but they do not choose between domains and folders. For a small business, our practical view is to use folders on a single domain: one renewal, one certificate and fewer things to keep an eye on. It is what we use on this website. Several domains usually make sense when each market runs almost as a separate business.

Do I need to translate the whole website or are the main pages enough?

The pages your customers use in that language are enough, but they need translating in full. Google says translating only the menu and footer, with the main content in one language, can create a bad experience if the same content appears repeatedly in search results with menus and footers in different languages. A version is treated as a duplicate if its main content is left untranslated. Better five complete pages in English than twenty with the text in Spanish.

#multilingual website#languages#international SEO#hreflang#small businesses
Back to Notes