A business in Miami hears the same question in two languages every day. A bilingual website answers it both ways: the customer who searches "roof repair near me" and the one who searches "reparación de techos" each land on a page written for them. That takes three decisions: how the second language is produced, where it lives and how visitors and search engines move between the two.
What is a bilingual website?
A bilingual website is one site that publishes its content in two languages, with a separate page for each. The English page and the Spanish page have their own addresses, their own titles and their own text. A visitor reads one language at a time and can switch whenever they want.
That leaves out the page that shows both languages side by side. Google says it uses the visible content of a page to work out its language, and recommends a single language per page.
Which way of translating the site fits your business?
There are three ways to produce the second language, and they differ in what search engines can index and in how the text reads.
| Option | How it works | Where it falls short |
|---|---|---|
| Translation widget | A script swaps the text in the visitor's browser | No separate pages in the second language, and nobody reviews the wording |
| Machine translation with review | Software drafts each page and a bilingual person corrects it | The draft follows the English wording, so the review has to be thorough |
| Written for each language | Each version is written for its own readers and searches | More work per page, and both versions need upkeep |
In its guide to managing multilingual sites, Google recommends a different URL for each language version instead of cookies or browser settings that change the language on the same page. Without separate addresses, it may not find every version.
Writing for each language also matters because the Spanish search is rarely the literal translation of the English one. A page that targets "web design" may need "diseño web" or "páginas web" in Spanish.
Where should each language live?
For a business that serves one market in two languages, a folder per language on the same domain is the simplest choice. Google's guide compares the main URL structures:
| Structure | Example | What Google notes |
|---|---|---|
| Country-specific domain | example.de | Clear geotargeting, but more expensive and tied to a single country |
| Subdomain | de.example.com | Easy to set up, but users may not recognize the targeting from the address |
| Subdirectory | example.com/de/ | Easy to set up and low maintenance |
| URL parameter | example.com?loc=de | Not recommended |
English and Spanish in Miami are two languages inside one market, so both versions belong on the same domain: English at the root and Spanish under /es/, or the other way around.
Translate the addresses too. A page at /es/servicios/diseno-web/ tells a Spanish speaker what it holds before they click. A page at /es/services/web-design/ does not.
How do you tell Google which page is which?
With hreflang, an annotation that links each page to its version in the other language. Google's documentation on localized versions of a page sets out the rules:
- Each language version lists itself and every other version.
- The links go both ways. If two pages do not point to each other, Google ignores the annotations.
- An
x-defaultvalue names the fallback page for visitors whose language matches neither version.
Translated pages do not count as duplicates: Google only treats localized versions as duplicates when the main content stays untranslated.
How should visitors switch languages?
With a visible link on every page that leads to the same page in the other language, not to the homepage. Someone reading about a service in English who taps "Español" expects that service in Spanish.
Leave the choice to the visitor. Google advises against redirecting users automatically from one language version to another, because the redirect can keep people and search engines from seeing every version of the site.
What does a bilingual site need beyond the pages?
The parts around the pages are easy to leave in one language. Check these before launch:
- Titles and descriptions. Each version needs its own, written for the search in that language.
- Forms and confirmation messages. A Spanish page that ends in an English form breaks the conversation.
- Image alt text. Screen readers read it in the language of the page.
- Analytics. Inquiries split by language, to see which version brings in customers.
This site works that way. English lives at the root and Spanish under /es/, with translated addresses, and each page that exists in both languages points to its counterpart with hreflang and an x-default.
If the bilingual version arrives with a redesign, protect the addresses that already rank. The SEO website redesign checklist covers the redirects. For how two languages play out on the map, see the guide to local SEO for Miami businesses.
At TersLab, with a team in Miami and in Buenos Aires, we plan, design and build web design in English and Spanish.
Frequently asked questions
Does a bilingual website help SEO?
Yes. Each language version can show up for the searches made in that language. A site published in English alone has no page written for a search typed in Spanish.
Is a translation plugin enough for a bilingual website?
No, if the plugin only swaps the text in the browser. The second language needs pages with their own addresses, and Google recommends a different URL for each language version.
Will Google treat the Spanish pages as duplicate content?
No. Google's documentation says localized versions of a page are only considered duplicates when the main content remains untranslated.
Do you need a separate domain for the Spanish version?
No. A folder such as /es/ on the same domain is easy to set up and to maintain. A country-specific domain fits a business that targets another country.
