Multilingual websites in Spain: how to reach customers in different languages

In short
A multilingual website works when each language has its own URL, copy that's adapted to the market rather than just translated, a visible language switcher and hreflang tags telling Google which version to show to whom. Start with the languages your real customers speak and the ones you can actually serve them in – not every language you could possibly offer.
On the Costa del Sol it's normal for a single business to serve customers in Spanish, English and at least one other language. An estate agency, a clinic or an excursions company may have customers searching Google in four or five different languages. A well-built multilingual website lets each of them find the version in their language, and lets Google show it in the right results. A badly built one can confuse visitors and Google at the same time.
For an expat-run business it often works the other way round from what you might expect: you already serve English speakers well, and what's missing is a proper Spanish version to reach local clients, who search in Spanish.
Which languages to choose
Don't start with a list of every possible language; start with the data you already have:
- The enquiries you receive. Which languages do people use when they contact you by WhatsApp or email?
- Your reviews. The language of the reviews on your Google profile gives you clues about your customers.
- Your analytics. Google Analytics shows visitors' browser language and country; Search Console shows the countries people find you from.
- Your capacity to serve. If you can't reply in a language, a website in that language will generate enquiries you can't turn into customers.
If you work in Catalonia, Galicia, the Valencian Community, the Balearic Islands or the Basque Country, also consider Catalan or Valencian, Galician or Basque: for many local customers it's their natural language.
Two languages done well are better than five done by halves. You can add more once you have data on demand.
Translation isn't enough: you need to adapt
A literal translation usually sounds odd and, on top of that, doesn't match what people actually type into a search engine. When adapting each version, check:
- How each market searches. The words a German or Russian customer uses to search for your service may not be a direct translation of the Spanish ones. The Atlantic Waves case study shows an example: each version was written around how that audience searches.
- What they need to know. A foreign property buyer may need information about the NIE (foreigner identification number) or taxes that a local buyer already knows about.
- Formats. Prices with or without VAT (IVA), date formats, the international dialling code on your phone number.
- Legal pages. The legal notice, privacy policy and cookie policy also need to be understandable in each language.
- Native review. Before publishing, have a speaker of that language read the whole page.
A separate URL for each language
Google recommends that each language version has its own address. Avoid showing different languages on the same URL by switching them with cookies or the browser language: Google might only ever see one version.
| Option | Example | When it makes sense |
|---|---|---|
| Subfolders | yoursite.es/es/, yoursite.es/en/ |
The easiest option to maintain for most businesses |
| Subdomains | en.yoursite.es |
If each version is managed with a different system or team |
| Country domains | yoursite.de, yoursite.co.uk |
If you're targeting specific countries and can maintain several sites |
For a local business with international customers, subfolders are usually enough: one domain, one website to maintain and clearly separated versions.
One important detail: don't automatically redirect visitors based on their country or browser language without letting them choose. An English customer living in Málaga may prefer to read in Spanish, and Google's crawlers might never get to see all the versions.
Navigation and the language switcher
- Visible and always in the same place, usually in the header and also in the mobile menu.
- With each language's name written in that language: Español, English, Deutsch, Українська.
- Without relying on flags. Flags represent countries, not languages: Spanish isn't only spoken in Spain, and English isn't only spoken in the UK.
- Taking people to the equivalent page. If someone is reading your services page in English and switches to German, they should land on the German services page, not the home page.
- With menus, buttons and forms translated, not just the main text.
Hreflang, explained without the jargon
Hreflang is a tag, invisible to visitors, that tells Google: "this page has these other versions in these languages". That way Google can show each person the version meant for them in the results.
The basic rules:
- Each version lists all the versions, including itself.
- The links are reciprocal. If the Spanish page points to the English one, the English one must point back to the Spanish one. If the return link is missing, Google may ignore the annotation.
- Correct codes. The language comes first and, optionally, the region after it:
es,es-ES,en,en-GB. A common mistake is usinguafor Ukrainian: the language code isuk;UAis the country code for Ukraine. Another is writingen-UKinstead ofen-GB. x-defaultindicates which version to show when none matches the person's language – for example, a language selection page or the main version.- Only between real, equivalent pages. Don't link to pages that redirect, return an error or haven't been translated yet.
This is how it looks in the code of a page available in Spanish, English and Ukrainian:
<link rel="alternate" hreflang="es-ES" href="https://yoursite.es/es/servicios/">
<link rel="alternate" hreflang="en" href="https://yoursite.es/en/services/">
<link rel="alternate" hreflang="uk" href="https://yoursite.es/uk/poslugy/">
<link rel="alternate" hreflang="x-default" href="https://yoursite.es/es/servicios/">
The same four lines must appear on all three pages. They can also be declared in the sitemap instead of in each page's code.
Maintaining a website in several languages
Launching is the easy part; the hard part is keeping the versions in sync.
- Decide who updates each language, and how you'll find out when a price or opening time changes.
- Change prices and contact details in every version at the same time.
- Have the form record the language the enquiry was sent in, so you can reply in the same one.
- Measure by language: visits, enquiries and source for each version. That way you'll know which languages deserve more investment.
Checklist
- I've chosen languages based on my customers and my capacity to serve them.
- Each language has its own URL.
- The copy is adapted and reviewed by a native speaker.
- The language switcher is visible on desktop and mobile, and leads to the equivalent page.
- There are no automatic redirects by language or country without the option to choose.
- The hreflang tags are reciprocal, use the correct codes and include
x-default. - Menus, buttons, forms and legal pages are available in each language.
- I know how many enquiries come from each version.
If you'd like to see how your website is doing, the free quick review includes a check of your languages and hreflang.
