TL;DR
Multilingual SEO is different from international SEO. International targets countries; multilingual targets languages. A site in Spanish might serve users in Spain, Mexico, Argentina, and US Hispanic populations. The strategic question isn’t “how do I implement hreflang” but “which languages should I invest in, and how do I create content that serves linguistically diverse audiences without duplicating effort?” The technical implementation follows strategic decisions about market priority, content localization depth, and whether translation or transcreation serves your audience better.
The Conversation
Yuki, Head of International at a B2B software company, currently English-only, expanding to European and Latin American markets, considering German, Spanish, French, Portuguese: We’re an English-only B2B software company expanding internationally. Our target markets are Germany, France, Spain, Mexico, Brazil, and Argentina. I know I need to translate our website, but I don’t know where to start or how to do it properly for SEO.
SDC SEO Brain: Let me reframe the question. You’ve listed six countries, but you actually have four language decisions: German, French, Spanish, and Portuguese. Some of these map one-to-one (German for Germany), but Spanish serves Spain, Mexico, and Argentina. Portuguese serves Brazil and Portugal. Your first strategic decision is whether you’re targeting languages or countries.
Yuki: What’s the practical difference?
SDC SEO Brain: If you create Spanish content, you have one asset serving multiple markets. If you create Spain-Spanish and Mexico-Spanish and Argentina-Spanish, you have three assets. The first approach is simpler and concentrates SEO authority. The second approach addresses regional differences but triples your content investment and creates potential duplicate content issues.
Yuki: Our product doesn’t have regional differences. The software is the same everywhere.
SDC SEO Brain: Then language-level targeting probably makes more sense. One Spanish site section serves all Spanish-speaking markets. One Portuguese section serves Brazil and Portugal. You use hreflang to tell Google which language version to show which users, without creating separate country versions. This concentrates your link building and content investment.
Yuki: What about search behavior differences? Don’t people in Spain search differently than people in Mexico?
SDC SEO Brain: Vocabulary differences exist. Spain-Spanish uses “ordenador” for computer; Mexico uses “computadora.” But for B2B software terms, differences are often smaller. Your buyers are searching for your product category, feature terms, and problem-solution queries. Those tend to be more universal within a language. The question is whether vocabulary differences affect your primary keywords enough to justify separate content.
Yuki: How do I research that?
SDC SEO Brain: Use keyword tools with regional filtering. Check if your target keywords have significantly different search volumes by country. If “software de gestión de proyectos” has strong volume in both Spain and Mexico, one piece of content serves both. If terminology diverges significantly, you might need regional variations. Start with assumption of unified language content and diverge only where data shows meaningful differences.
Yuki: Let me ask about the actual content creation. Should I translate our English content or create new content for each language?
SDC SEO Brain: Neither extreme is right. Pure translation misses cultural context and local search patterns. Completely new content is expensive and loses leverage from your existing work. The middle ground is localization: start with English content structure and key points, adapt for local market context, and optimize for local keyword variations. Some content translates well; other content needs significant adaptation.
Yuki: What kind of content needs more adaptation?
SDC SEO Brain: Case studies need local examples. Pricing pages need local currency and potentially different tier structures. Blog posts about trends need regional relevance. Compliance and legal pages need local regulations. Product descriptions and feature pages often translate more directly because the product is the same. The closer content is to cultural context, the more adaptation it needs.
Yuki: What about AI translation? Can we use that to scale quickly?
SDC SEO Brain: AI translation has improved dramatically but still produces content that reads as translated rather than native. For B2B where trust matters, obviously translated content can hurt credibility. The practical approach: AI for first draft efficiency, human review by native speakers for quality and cultural fit, and human creation for high-stakes pages like homepage and key landing pages. Don’t publish AI translation without human review.
Yuki: That’s still expensive. We have hundreds of pages.
SDC SEO Brain: You don’t need to translate everything. Prioritize ruthlessly. Identify your top 20 pages by traffic and conversion value. Translate those first with high-quality human localization. Tier two: another 50 pages with AI-assisted translation and human review. Tier three: remaining pages only if and when each language proves its ROI. Many companies translate everything and discover most pages generate zero traffic.
Yuki: How do I know if a language is worth the investment before I make it?
SDC SEO Brain: Three signals. First, existing traffic: check GSC for impressions from target countries. Are German users already finding you despite English content? That’s demand signal. Second, competitor presence: are competitors investing in German content? If they are and ranking, there’s a market. If no one is, either you’re early or there’s no market. Third, sales data: are you closing deals in Germany through other channels? SEO expands existing demand; it rarely creates demand from nothing.
Yuki: We do have sales in Germany, mostly through outbound. Not much in Latin America yet.
SDC SEO Brain: Then German makes strategic sense as first investment. You’re supporting an existing market where you already win deals. Spanish and Portuguese for Latin America might be more speculative. Start German, prove the model, then expand. This also lets you refine your localization process before scaling.
Yuki: Let’s talk technical implementation. How should the URLs be structured?
SDC SEO Brain: Three main options. Subdirectories: example.com/de/ for German, example.com/es/ for Spanish. Subdomains: de.example.com. Separate country-code domains: example.de, example.es. For most businesses, subdirectories are best: all languages benefit from your main domain’s authority, implementation is simpler, and management is centralized.
Yuki: What about country-code domains? Doesn’t example.de rank better in Germany?
SDC SEO Brain: Country-code domains do send strong geographic signals for that specific country. But they start with zero authority, require separate SEO investment, and don’t benefit from your main domain’s strength. For a company expanding internationally without established local presence, subdirectories on your main domain usually outperform starting fresh country domains. The authority inheritance matters more than the geographic signal.
Yuki: When do country-code domains make sense?
SDC SEO Brain: When you have strong local presence: local team, local office, local brand recognition. When regulatory or trust reasons favor local domains. When you’re entering a market where your main domain has negative associations or is blocked. For B2B software expanding from the US, these rarely apply. Your example.com authority is an asset. Use it.
Yuki: What about hreflang implementation?
SDC SEO Brain: Hreflang tells Google which language version to show which users. Every page in every language needs hreflang tags pointing to all language versions of that page, including itself. Common mistakes: missing the self-reference, incomplete tag sets across all versions, and using wrong language codes. If page A in English points to page B in German, page B must point back to page A. Asymmetric implementation causes Google to ignore the tags.
Yuki: Do I need to specify country too? Like es-ES versus es-MX?
SDC SEO Brain: Only if you’re creating country-specific versions. If you have one Spanish version serving all Spanish speakers, use “es” without country code. If you have separate Spain-Spanish and Mexico-Spanish versions, use “es-ES” and “es-MX” to differentiate. For your unified language approach, language-only codes (es, de, fr, pt) are appropriate.
Yuki: What about the English version? We serve multiple English-speaking countries.
SDC SEO Brain: For English, you can use “en” for generic English, or specify “en-US” if your content is US-focused. If you don’t have UK or Australia-specific versions, generic “en” with an “x-default” tag works. The x-default tells Google: “if no specific language match exists, show this version.” Your English version should be x-default.
Yuki: What’s the biggest mistake companies make with multilingual SEO?
SDC SEO Brain: Creating content without local keyword research. They translate their English content, including the keywords they target, without checking if those translated keywords have search volume or if different terms are used locally. You might rank number one for a translated term nobody searches. Always research keywords in the target language using native speaker input and local keyword tools. The SEO opportunity isn’t just translation of your English strategy. It’s discovery of the local search landscape.
Yuki: So we need separate keyword research for each language?
SDC SEO Brain: Yes. Your English keyword strategy reflects how English speakers search. German speakers may use different terms, frame problems differently, or prioritize different features. Keyword research in German, with a German native speaker or agency, reveals these differences. The content structure might parallel your English site, but the specific targeting should be locally optimized.
FAQ
Q: What’s the difference between multilingual and international SEO?
A: Multilingual targets languages; international targets countries. A Spanish site might serve Spain, Mexico, Argentina, and US Hispanic populations. International SEO might create separate versions for each country with the same language. The choice depends on whether your content needs country-specific adaptation or if one language version serves all speakers of that language.
Q: Should I use subdirectories, subdomains, or country domains for multilingual content?
A: For most businesses, subdirectories (example.com/de/, example.com/es/) are best. All languages benefit from your main domain’s authority, implementation is simpler, and management is centralized. Country-code domains (example.de) make sense only when you have strong local presence, local brand recognition, or regulatory requirements.
Q: Do I need separate content for Spain-Spanish and Mexico-Spanish?
A: Only if vocabulary differences significantly affect your target keywords. For B2B software, terminology is often similar across Spanish-speaking markets. Research keyword search volumes by country. If your terms have strong volume in both Spain and Mexico, one Spanish version serves both. Diverge only where data shows meaningful differences.
Q: Can I use AI translation for multilingual SEO?
A: AI translation works for first drafts but shouldn’t be published without human review. AI-translated content often reads as translated rather than native, hurting trust in B2B contexts. Use AI for efficiency, human native speakers for quality review, and human creation for high-stakes pages. Prioritize fewer pages done well over many pages done poorly.
Q: How do I prioritize which languages to invest in first?
A: Three signals. Existing traffic: check GSC for impressions from target countries even on English content. Competitor presence: are competitors investing in that language? Sales data: are you closing deals in that market through other channels? Start with languages supporting existing market traction, prove ROI, then expand.
Summary
Multilingual SEO targets languages; international SEO targets countries. A Spanish content investment might serve Spain, Mexico, Argentina, and US Hispanic populations. Decide whether you’re creating language-level content (one Spanish version) or country-level content (Spain-Spanish, Mexico-Spanish). Language-level is simpler and concentrates authority.
One language version serving multiple countries concentrates SEO investment. Instead of creating and optimizing three Spanish sites for three countries, one Spanish subdirectory builds authority from all Spanish links and serves all Spanish searchers. Country-specific versions make sense only when significant regional differences affect your key terms.
Vocabulary differences matter most when they affect primary keywords. Research target keywords in each language market using local tools and native speakers. If “project management software” translates to terms with strong volume across Spanish-speaking countries, one version serves all. Diverge only where keyword data shows meaningful differences.
Localization sits between translation and creation. Pure translation misses cultural context; new content wastes leverage. Start with English structure and points, adapt for local context, optimize for local keyword variations. Closer to cultural context (case studies, compliance) needs more adaptation. Product features translate more directly.
AI translation requires human review. AI produces content that reads as translated rather than native. For B2B where trust matters, obviously translated content hurts credibility. Use AI for efficiency, native speakers for review, humans for high-stakes pages. Don’t publish unreviewed AI translation.
Subdirectories usually outperform country domains for expanding companies. example.com/de/ inherits authority from your main domain. example.de starts at zero. Country domains make sense with strong local presence; otherwise, authority inheritance matters more than geographic signals.
Hreflang requires symmetric implementation. Every page must point to all language versions including itself. If English points to German, German must point back to English. Asymmetric tags get ignored. Use language codes (es, de) for unified language versions; language-country codes (es-ES, es-MX) only for country-specific versions.
Local keyword research reveals the opportunity. Translating your English keywords without checking local search volume risks ranking for terms nobody uses. Keyword research in the target language, with native input, discovers how local searchers frame problems and seek solutions.
Sources
- Google Search Central: Managing multi-regional and multilingual sites
- Google on hreflang implementation
- <a href="https://en.wikipedia.org/wiki/ListofISO639-1codes”>ISO 639-1 language codes
- Google Search Console: International targeting report