Updated: 4 August 2026 · SEO, International
Running a site in two languages sounds like it should double your reach. Done wrong, it can do the opposite — Google sees two versions competing for the same searches and neither ranks as well as a single, clear version would.
Why this goes wrong so often
The most common mistake is duplicating content almost word for word across languages without telling Google they're translations of each other, rather than two competing pages. Search engines then treat them as separate, similar pages targeting overlapping queries, and both suffer.
The second common mistake is the reverse problem: translating literally rather than adapting. A Spanish page translated word-for-word from English often uses phrasing nobody actually searches for in Spanish, because search behaviour doesn't map directly between languages.
The technical fix: hreflang, done correctly
hreflang tags tell Google "this page has an equivalent in another language, here's where to find it." Done right, each version can rank in its own language's results without competing against its sibling.
What needs to be true for it to work:
- Every page needs a self-referencing hreflang tag, plus one pointing to each translation
- The relationship has to be reciprocal — if the Spanish page points to the English one, the English one has to point back
- URLs need to be stable; changing one without updating the tag breaks the relationship silently
Get this wrong and the two versions genuinely do compete, which is the exact outcome the tags exist to prevent.
Adapt, don't just translate
Real search behaviour differs by language, not just vocabulary. A term that gets thousands of searches in English might have a completely different, more specific equivalent in Spanish — or vice versa. Keyword research needs doing separately for each language, not derived by translating the other one's results.
The same applies to tone and structure. Spanish-speaking readers researching a purchase decision often expect more direct, concrete information earlier in the page than an English equivalent might lead with. Adapting for that, not just swapping words, is what makes the translated version actually convert.
What to do if you're serving Spain from abroad
If your business is based outside Spain and you're building Spanish content to reach customers here, the trust signals that matter locally carry more weight than they would in your home market: a Spanish phone number, reviews in Spanish, a real address if you have one. That's the specific case covered in Spanish SEO.
Checking it's actually working
Google Search Console shows which language version ranks for which query — if you see the English version showing up for Spanish searches or vice versa, that's a sign the hreflang setup needs attention. It's worth checking every few months, not just at launch, since a site restructure can quietly break the relationship between versions.
A common scenario worth naming directly
A frequent case: a business translates its site into Spanish, publishes it, and six months later notices the Spanish version barely gets any traffic while the English one does fine. Before assuming the market simply isn't there, check three things in order: whether hreflang is actually implemented correctly, whether the Spanish content was adapted or just translated, and whether the keywords targeted are ones Spanish speakers actually search — not the direct translation of the English ones.
In most cases I've looked at, it's one of the first two, not a lack of demand. The market exists; the technical or content setup is quietly working against it.
When two separate domains makes more sense than one bilingual site
For most small businesses, subfolders on one domain are the right setup — simpler to maintain, and all the accumulated authority stays in one place. But there are cases where splitting into two country-specific domains makes more sense: when the two markets have genuinely different offers, pricing, or legal requirements, not just a translated version of the same page. Running two domains means starting SEO authority from zero on the second one, which is a real cost — it's worth that cost only when the businesses behind each language are different enough that forcing them onto one structure would compromise both.
Frequently asked questions
Do I need completely separate content for each language, or can I translate? Translation is the right starting point, but treat it as a first draft to adapt, not a final version. The structure and technical setup matter more than whether every sentence is a fresh composition.
What if I only have resources to properly maintain one language? Better to do one language well than two half-heartedly. A thin, neglected second-language version can drag down the site's overall quality signals more than having no second version at all.
Does subdomain vs subfolder matter for multilingual SEO?
Both can work with correct hreflang. Subfolders (like /es/) are simpler to set up correctly and are what this site itself uses.
How do I know if my two versions are competing instead of complementing? Search for the same query in both languages and see if the "wrong" language version outranks the right one — a clear sign hreflang isn't working as it should.
If you're planning a bilingual site or think your current setup might be working against itself, send me the URLs and I'll take a look. How I work is in SEO.
