Companies usually discover multilingual SEO the hard way: they translate the site, wait three months, and nothing happens. The pages exist, they are indexed, and they rank nowhere.
Almost always the cause is one of three things — the wrong URL structure, missing or broken hreflang, or keyword research that was done in one language and translated instead of redone per market.
Pick a URL structure and commit
Three options work: country domains (example.de), subdomains (de.example.com) or subdirectories (example.com/de/). For most businesses, subdirectories win — they inherit the authority of the main domain, they are cheaper to run, and one strong domain beats five weak ones.
Country domains make sense when you have a genuinely separate legal entity, local warehousing or a brand that differs by market. If you are one company selling into several countries, subdirectories are almost always the right call.
hreflang: the part everyone gets wrong
Every language version of a page must point to every other version, including itself, and the references must be reciprocal. If your German page lists the English one but the English page does not list the German one, search engines ignore the cluster entirely.
Add an x-default for the version you want shown when no language matches. Then verify it — annotations are invisible to users, so mistakes survive for years unless someone checks the rendered HTML and the sitemap.
Localisation is not translation
Translated copy carries the source market's assumptions: its examples, its objections, its search terms. A German buyer searching for 'Individualsoftware' is not typing a translation of what an English buyer types, and the questions they ask before buying differ too.
Redo keyword research natively in each market, then write the page around those terms. It costs more than translation and it is the difference between pages that exist and pages that rank.
Handle the same language in different countries carefully
German for Germany, Austria and Switzerland, or Arabic for the UAE and Saudi Arabia, are separate markets with different competitors, currencies and expectations — but very similar text. Split them only when you can genuinely differentiate the content.
Otherwise you create near-duplicate pages competing with each other. One strong page per language, with local details handled through hreflang region targeting where needed, usually outperforms four thin ones.
Technical details that decide indexing
Self-referencing canonicals on every language version, so no version quietly points at another. Localised metadata — a translated page with an English title tag is a wasted result in the search listing. And a sitemap that lists every language version, ideally with hreflang annotations included.
Right-to-left languages need real attention: the dir attribute, mirrored layouts, and a check that carousels, dropdowns and forms actually work when the page flips. A broken Arabic layout costs conversions long before it costs rankings.
Decide what not to translate
Not every page deserves five versions. Deep technical catalogues, documentation and long-tail reference content can stay in one language while your commercial pages — home, services, industry landing pages, contact — go multilingual.
Mark those links clearly so the language switch is never a surprise, and keep the translated set genuinely maintained. Ten excellent localised pages beat two hundred machine-translated ones, which increasingly get treated as low-value content.
Key takeaways
- Subdirectories (example.com/de/) suit most businesses better than country domains.
- hreflang must be reciprocal and include a self-reference and x-default.
- Redo keyword research in each market instead of translating keywords.
- Localise metadata, not just body copy.
- Translate fewer pages, properly, rather than everything automatically.
Services:SEO & Content →
