GuideInternational SEO

Translating Keywords Is Not International SEO

Translating a keyword list from English into another language ignores that search intent, SERP composition, and technical architecture all shift by market. This guide covers what to check before expanding.

It's a common pattern: a company exports its English keyword list, runs it through a translator — human or automated — and uses that as the basis for content in another language. The problem isn't translation itself. It's assuming translation solves the strategy. It doesn't.

Search intent doesn't travel with the translation

The same concept can be searched with different terms, at different stages of the buying process, or with different result expectations depending on the country. Two markets that share a language — Mexico and Spain, or Spain and the US Hispanic market — don't necessarily share the same vocabulary, the same decision stage, or the same competitors for the same term.

The SERP changes from market to market too

• The competitors dominating a result in one country are rarely the same in another, even when the language matches.
• SERP features (featured snippets, knowledge panels, local results) can appear for a query in one market and be absent for the same query in another.
• Competition level for the same term can be significantly lower in one market than another, changing which content should be prioritized first.

Architecture: ccTLD, subdomain or subfolder

Before writing a single localized word, there's a structural decision that shapes everything else: how you're going to organize your site's versions by country or language.

There's no universal answer. The decision depends on available resources, the current domain, and whether brand strategy per country requires full separation.

Hreflang: reciprocity and x-default

Hreflang tells search engines which page version to show based on a user's language and region. Correct implementation has two requirements that commonly fail in practice: it must be reciprocal (if page A points to B, B must point back to A), and it should include an x-default for users who don't match any specific variant.

Each page should identify itself with a hreflang element, in addition to identifying the other language/region versions.Google Search Central — Localized versions

• Missing reciprocity: the English page points to the Spanish version, but the Spanish version doesn't point back.
• Using language codes without region when country variants actually exist (es vs. es-MX vs. es-US).
• No x-default, leaving Google without a clear fallback version for traffic that doesn't match any declared hreflang.
• Hreflang pointing to URLs that canonicalize to a different page, which cancels the signal.

Checklist before launching an international version

1. 1Validate that real search volume exists in the target market — don't assume it based on population size alone.
2. 2Research keywords independently in the target market, without starting from the translated list as a final basis.
3. 3Review the actual SERP in that market for priority queries: who's competing, what content format is winning.
4. 4Choose architecture (ccTLD, subdomain, or subfolder) based on resources and brand objectives, not by default.
5. 5Implement reciprocal hreflang across all relevant versions, including x-default.
6. 6Adapt content beyond language: currency, units, cultural references, and local examples.
7. 7Set up market-segmented measurement before launch so results can be evaluated separately.

What to do with this

Translation is a mechanical step within an international expansion, not the whole strategy. Intent research, architecture, and hreflang are what determine whether that translation actually reaches the right person in the right result.