A translated site serves one structure in two languages. A bilingual architecture serves two structures — separate URLs, separate semantic hierarchy, separate structured data and separate keyword vocabulary per language, connected by hreflang. Translation preserves the words. Architecture preserves the intent, which is what search and AI retrieval read.
Last updated 25 July 2026
A translated site keeps one information architecture and swaps the words. A bilingual site gives each language its own URLs, headings, structured data and vocabulary. The difference shows up when the two audiences search differently — which, in most B2B markets, they do.
The concrete case in most LATAM B2B markets: one buyer is a local commercial client searching in Spanish, the other is a multinational or expatriate searching in English. Same service, two vocabularies, two intents.
Give each language a distinct, permanently addressable URL — most commonly a path prefix such as /es/. Avoid switching language by cookie, session or auto-redirect on the same URL, because a crawler or retrieval system then cannot index both versions independently.
Subdomains and country domains also work. What matters is that the URL is stable and language-specific, not which of the three patterns you pick.
Every page declares the full set: itself, each alternate language, and an x-default. The declarations must be reciprocal — if the English page points at the Spanish one, the Spanish page must point back. One-way declarations are the most common implementation error.
Yes, and it should be genuinely per-language rather than copied. The entity is the same organisation, but the descriptive fields, service names and any text properties belong in the language of that page. Reusing one language block across both versions makes one of them unclassifiable.
The organisation identifier stays constant across versions so the entity resolves as one business rather than two.
Auto-redirecting by IP, which prevents indexing of the alternate. Non-reciprocal hreflang. Translating keywords literally rather than using each market’s actual vocabulary. And machine translation, which produces text that reads as low quality to both people and retrieval systems.
Machine translation is the expensive one, because it fails quietly — the page exists, indexes, and quietly underperforms without ever looking broken.
When one audience genuinely dominates and the second would be a courtesy rather than a channel. A poorly maintained second language is worse than none — it splits authority, creates duplicate-content ambiguity and signals neglect to precisely the buyer it was meant to reach.
The honest test is whether someone will maintain the second language at the same standard as the first. If not, the better decision is one language done properly.
This page is itself the demonstration: it exists at its own URL in both languages, with reciprocal hreflang and independent structured data.
Ver esta guía en español →