Multilingual SEO for Your Own Site: Hreflang, Regional Keywords, Localized Content, and Rankings
1. The three most common mistakes in multilingual SEO
Mistake one: machine-translating your English content and dropping it under /de/ makes it a German site. Google crawls both versions, sees the high similarity, flags duplicate content, and keeps only one version in the index, usually the higher-authority English original. Mistake two: adding hreflang on only one side. Page A links to B, but B doesn’t link back to A, so Google ignores it. Mistake three: translating English keywords and using them as German keywords.
The counterintuitive part: the bottleneck in multilingual SEO isn’t translation quality, it’s keyword research. No matter how good the machine translation is, if you’re targeting how English buyers search, German buyers will never use that term. German buyers search “Anfrage,” not “Request.” Spanish buyers search “presupuesto,” not “quotation.” For hreflang syntax details, see Hreflang for Multilingual Sites: How to Write the Tags, Regional Pages, and Common Mistakes.
| Common mistakes | What actually happens | The right way |
|---|---|---|
| Machine-translated English version under /de/ | Flagged as duplicate content, only one version ranks | Native-language keywords plus localized content |
| hreflang added on only one side | Google ignores it and doesn’t serve by language | Self-reference plus cross-links on every version |
| English keywords translated directly | Low search volume, no rankings | Redo research with native-language keyword tools |
| All languages share one sitemap | Hard to pinpoint errors | Split into sub-sitemaps by language |
| Ignoring x-default | Users in unknown regions see the wrong version | Add x-default pointing to the default version |
2. How to write hreflang tags without errors
The standard way to write hreflang is to add link tags in the head of every language version’s page, pointing to all the other language versions, including itself. For example, the English page should point to the en, de, and es versions, and the German page should also point to the en, de, and es versions. This is cross-linking; one-sided tags aren’t recognized. You also need an x-default pointing to your default language version, to handle requests from unknown regions.
The three most common mistakes: First, the URL that hreflang points to returns a 404 or redirects to another page, and Google ignores the tag entirely. Second, the language code in the hreflang tag uses zh-CN instead of zh-Hans, or uses en-GB while the page content is in American English. Third, using hreflang to point to versions for different countries that share the same language, such as en-US and en-GB, when the content is nearly identical, which gets flagged as soft duplication. For where to draw the line on country-specific landing pages, see Build landing pages by country.
| hreflang syntax | Correct example | Common mistake |
|---|---|---|
| Self-referencing | hreflang=”en” points to the English version itself | Forgetting the self-reference |
| Cross-linking | The German page points to en/de/es as well | Only en points to de, de doesn’t point back |
| x-default | Add hreflang=”x-default” pointing to the default version | No x-default |
| Language codes | Use ISO 639-1 two-letter codes | Mixing en-US and en_GB formats |
| URL status | All target URLs return 200 | Pointing to a 404 or a 301 redirect |
3. Regional keyword research: don’t translate, search again
The point of regional keyword research is to “start over,” not to “translate.” The method: use keyword tools in the local language (switch Google Keyword Planner to the target region, switch Ahrefs/Semrush to the target country), enter your core product terms, and see what words local buyers actually search with. Each language version needs at least 30 to 50 core keywords, split into four groups: brand terms, product terms, general industry terms, and comparison/decision terms.
Example: a packaging machinery company targets “packaging machine manufacturer” in its English version, but in German-speaking markets local buyers more often search “Verpackungsmaschine Hersteller” and “Verpackungsanlage.” If you simply translate the English into German as “Verpackung Maschine Hersteller,” search volume is only a third of the real local terms. When building the German version, switch Ahrefs to the Germany region, enter “Verpackungsmaschine,” and pull 30 related terms, among which “Abfüllmaschine” and “Schlauchbeutelmaschine” are high-frequency local long-tail terms with no equivalent in the original English version. For the multilingual GEO angle, see Multilingual GEO: German, Spanish and Arabic markets beyond English.
| Keyword type | Count per language | Methodology | Example (German-speaking market) |
|---|---|---|---|
| Brand keywords | 5 to 10 | Company name plus spelling variants | Company name, + GmbH |
| Product terms | 10 to 15 | Local-language tool with region filter | Packaging machine |
| General industry terms | 10 to 15 | Hot terms on local forums and B2B platforms | Filling machine, manufacturer |
| Comparison/decision terms | 5 to 10 | Competitor brands plus test/comparison | Manufacturer comparison |
4. Localized content: not translation, but a rebuild
Localization is not the same as translation. Translation swaps the language; localization reworks prices, units, taxes, contact details, and shipping options to match local habits. Quotes for German-speaking markets must include VAT (MwSt), US pages show pre-tax prices plus an estimated sales tax, and Japanese pages use yen prices with tax included. Units in product specs need to change from metric to imperial (US) or stay metric with conversions noted (Commonwealth countries).
Content length also needs a second look. German runs 20% to 30% longer than English on average, so the same sentence takes up more characters and mobile layouts shift. French and Spanish run 15% to 25% longer than English. If you reuse the English CSS and layout as-is, the German product spec table will break on mobile. If the text in your charts is baked into the image, follow the Charts and tables on multilingual sites approach and embed it as SVG instead of an image, so the language can switch automatically.
| Localization item | English original | German version | US version |
|---|---|---|---|
| Price display | USD, pre-tax | EUR, incl. MwSt | USD, pre-tax plus estimated sales tax |
| Units | Metric mm/kg | Metric mm/kg | Imperial inch/lb |
| Contact | Email plus US phone number | Email plus local German phone number | Local toll-free number |
| Content length | Baseline | 20% to 30% longer | 10% to 15% longer |
| Shipping | US warehouse | EU warehouse or direct shipping | Local US warehouse |
5. Rank tracking: report by language version
Multilingual SEO tracking can’t rely on overall rankings alone. You have to break the data out by language version. In Search Console, split by country/region and language to see impressions, clicks, CTR, and average position for each language version. Run a per-language report every week instead of lumping all language versions together.
To judge whether a language version is working, look at three metrics: how many target keywords rank in the top 20, what share of total organic traffic that language version brings in, and its inquiry conversion rate. If the German version has fewer than 5 target keywords in the top 20 eight weeks after launch, something is wrong with your keyword research or content localization, and you need to go back and check. For keyword cannibalization, see keyword cannibalization.
| Metrics to track | Healthy Threshold | Alert threshold | Data source |
|---|---|---|---|
| Target keywords in top 20 | 10 or more after 8 weeks | <5个需复查 | Filter by language in Search Console |
| Traffic share for that language | At or above the market benchmark | More than 50% below benchmark | Language dimension in GA4 |
| CTR | Within 2pp of the English version | More than 5pp below the English version | Search Console |
| Inquiry conversion rate | Within 1pp of the English version | More than 3pp below the English version | Source language in CRM |
FAQ
How do hreflang, subdirectories, and subdomains work together?
Can I just translate English keywords for multilingual SEO?
Do you actually need x-default, and where does it go?
German and French content runs longer than English. How do you handle the layout?
How long after launching multilingual versions will I see ranking results?
How do country landing pages differ from multilingual versions?
Final thoughts
The biggest difference between multilingual SEO and single-language SEO is that you can’t apply one English methodology to every language. hreflang is just the entry point; what actually determines rankings is native-language keywords and localized content. Translation solves “can they understand it”; localization solves “will they buy it.”
Three steps to launch: First, use a subdirectory structure with interlinked hreflang tags, and set up x-default. Second, redo keyword research for each language version using native-language tools to find 30 to 50 keywords, rather than translating English terms. Third, monitor each language version separately; if fewer than 5 target keywords reach the top 20 within 8 weeks, go back and check your keywords and content.
One line worth remembering: multilingual SEO isn’t translating English into German, it’s redoing the whole thing around how German buyers actually search.