Before you start: decide what gets translated
Translate every page a customer might see. If that's too much at once, start with the pages that bring in work: home, services, pricing and contact. Add the rest soon after, so nobody clicks from a Spanish page into an English one.
Not sure you need Spanish at all? Start with do you need a Spanish version of your website? It shows how to check your own customers.
Step 1: Give each language its own address
Each Spanish page needs its own URL. Google recommends a different URL for each language version of a page, rather than switching the language with cookies or browser settings. If both languages share one address, Google can only show one of them.
You have four ways to do it. Google's guide to multilingual sites lists these pros and cons:
| Option | Example | Good | Watch out |
|---|---|---|---|
| Folder | yourcompany.com/es/ | Easy to set up, low maintenance (same host) | One server location, harder to split into separate sites later |
| Subdomain | es.yourcompany.com | Easy to set up, can be hosted anywhere | Visitors may not know if “es” means a language or a country |
| Country domain | yourcompany.mx | Clear country targeting | Costs more, more to run, targets one country only |
| URL parameter | yourcompany.com?lang=es | Google doesn't recommend it |
Source: Google Search Central, Managing multi-regional and multilingual sites.
For a US business serving English and Spanish speakers in the same places, a folder is the simple choice. That's what we use: mangohla.com in English and mangohla.com/es/ in Spanish.
Step 2: Translate the words, then adapt them
Word-for-word translation reads like a translation. Write the Spanish so it sounds natural to your customers, while keeping every fact identical: prices, hours, phone numbers, guarantees and service areas.
- Pick tú or usted and stick to it. Mixing them on one site feels careless. Our site uses tú throughout.
- Use the words your customers use. Trade terms, product names and local phrases vary. Ask your Spanish-speaking customers and staff.
- Have someone fluent read every page before it goes live, even if a person did the first draft. AI and translation tools are fine for a draft, not for the final word.
Step 3: Translate the small things people miss
Most half-translated sites get the paragraphs right and miss the pieces around them. Go through this list:
- Page titles and meta descriptions (what people read in Google results)
- Menu, buttons and footer
- Image alt text (the description screen readers read out)
- Form labels, placeholder text and error messages
- The thank-you page and the confirmation email
- Pre-filled messages, like the text a WhatsApp or SMS button opens with
- Your “page not found” page
- Downloads, like menus, price lists or PDFs
On our site, a Spanish visitor who skips a form field sees “Escribe tu nombre.” instead of an English error, and our WhatsApp button opens with “¡Hola Mangohla! Me interesa un sitio web.”
Step 4: Add hreflang tags
hreflang tags tell Google which page is the Spanish twin of which English page, so it can show the right one to each searcher. Put them in the <head> of both pages:
<link rel="alternate" hreflang="en" href="https://yourcompany.com/services/">
<link rel="alternate" hreflang="es" href="https://yourcompany.com/es/services/">
<link rel="alternate" hreflang="x-default" href="https://yourcompany.com/services/">
Three rules from Google's documentation:
- Each language version must list itself and all the other versions. The English page lists English and Spanish, and so does the Spanish page.
- The links must go both ways. If two pages don't both point to each other, Google ignores the tags.
- x-default is the fallback for visitors whose language doesn't match any version. For most US businesses that's the English page.
You can also put hreflang in your XML sitemap or in HTTP headers. Google treats all three methods the same, so pick the one your website platform makes easiest.
Source: Google Search Central, Tell Google about localized versions of your page.
Step 5: Add a language switch that keeps people on the same page
Put a language switch on every page, in the same place, and make it a real link to the same page in the other language. Someone reading your roofing page in English should land on the roofing page in Spanish, not on the Spanish home page. Google also suggests linking to the other language versions of a page, so visitors can choose.
Label each language in its own language: “English” and “Español,” not “Spanish.” Flags are a poor fit, because Spanish isn't one country.
Step 6: Don't redirect people by browser language
It's tempting to send everyone whose browser is set to Spanish straight to the Spanish page. Google advises against it: don't redirect people to another language version based on what you think their language may be. Those redirects can stop people, and search engines, from reaching every version of your site.
What we do instead:
- If your browser prefers Spanish and you haven't chosen a language yet, a small “¿Prefieres leer en español?” suggestion appears. One tap opens the Spanish page, and closing it keeps you in English.
- Once you choose a language, we remember it and open that version next time.
Step 7: Set the page language
Mark each page with its language: <html lang="es"> on Spanish pages, <html lang="en"> on English ones. Google says it doesn't use this attribute to decide a page's language. It reads the visible text. But screen readers use it to pick the right pronunciation, and browsers use it to decide when to offer translation, so it still matters for your visitors.
The same goes for Spanish words in your URLs: Google doesn't use the URL to work out a page's language, so Spanish addresses are for people, not rankings. We use them on our guides because they're easier to read and share.
Step 8: Tell Google about your Spanish pages
- Add every Spanish page to your XML sitemap, and resubmit the sitemap in Google Search Console.
- Use URL Inspection in Search Console on your main Spanish pages and request indexing.
- Check the Spanish pages in a phone browser, with the language switch, the forms and the thank-you page.
Step 9: Keep both languages in sync
A common problem with bilingual sites shows up months later: a price or phone number changes in English and stays old in Spanish. Make updating both languages one step, not two.
On our site, each page's English and Spanish text sit side by side in one file. A small script then builds the Spanish pages from it, so a change can't reach only one language. If your site runs on a website builder, check that its multilingual feature shows which pages have untranslated changes.
The checklist
- Every customer-facing page has a Spanish version at its own address.
- The Spanish reads naturally, uses tú or usted consistently, and was checked by someone fluent.
- Prices, hours, phone numbers and guarantees match in both languages.
- Titles, meta descriptions, alt text, buttons, forms, errors, emails and the thank-you page are translated.
- Each page has hreflang tags for English, Spanish and x-default, on both versions.
- A language switch on every page links to the same page in the other language.
- Nobody is redirected based on a guess about their language.
- Spanish pages use
lang="es". - Spanish pages are in the sitemap, and the sitemap is submitted in Search Console.
- Updating a page updates both languages.
Common questions
Does my website builder handle this?
Most website builders offer a multilingual feature or an add-on. Before you rely on it, check three things: each language gets its own address, it adds hreflang tags, and it lets you translate page titles, meta descriptions and form messages.
Will Spanish pages count as duplicate content?
No, as long as the main content is translated. Google only treats language versions as duplicates when the main content stays in the same language.
How long does it take?
It depends on the number of pages and how fast the Spanish gets written and checked. When we build a site, the Spanish version is part of the project: our founding websites go live within 21 days of getting your photos and answers, in both languages.