Short answer: put each language in its own subfolder on your main domain (/de/, /fr/), link every version to the others with hreflang tags that point both ways, translate the pages that earn money properly rather than machine-translating the whole site, and never auto-redirect visitors by IP. That multilingual SEO setup lets a small business rank in several European markets while keeping all its authority on one domain.
Europe has 24 official EU languages and plenty of markets where English pages rank poorly. A German buyer searching in German rarely clicks an English result when a German one sits beside it. The upside is that many local markets have fewer well-built competitors than the English-language results. The downside is that multilingual SEO breaks in quiet ways, and a broken setup can make your own pages compete against each other.
On this page
Choose markets before languages
Language and country are different decisions. German covers Germany, Austria and much of Switzerland. French covers France, Belgium, Luxembourg and western Switzerland. If your prices, delivery terms or regulations differ by country, you may need country versions (de-DE and de-AT), not just a German version.
For most small businesses, start narrower than you think:
- Follow existing demand. Look at where current enquiries and sales already come from in Google Analytics or your CRM.
- Check Search Console for impressions from countries you do not serve yet. Those are markets already finding you.
- Pick languages you can support after the sale. Ranking in Dutch is pointless if nobody can answer a Dutch email.
Pick a URL structure for multilingual SEO
Google's guidance on multi-regional sites lists the options. Whatever you pick, translate the slug too. /de/leistungen/webdesign/ reads better to a German searcher than /de/services/web-design/, and keywords in the URL are a small but real relevance signal. For a small business the trade-offs look like this:
-
Subfolders (
example.com/de/): one domain, one hosting account, and every backlink strengthens every language. This is our default recommendation. -
Country domains (
example.de): the strongest local signal and trusted by local buyers, but each domain starts with zero authority and costs more to run. Worth it when a country is a major market on its own. -
Subdomains (
de.example.com): easy to set up, but users may not recognise them as targeted, and in practice they often build authority more slowly than subfolders. -
URL parameters (
?lang=de): avoid. Google advises against them for language versions.
Hreflang without the headaches
Hreflang tells search engines which page is the equivalent in another language or region, so the right version shows to the right searcher. A correct set for a service page looks like this:
<link rel="alternate" hreflang="en-GB" href="https://example.com/services/web-design/" /><link rel="alternate" hreflang="de" href="https://example.com/de/leistungen/webdesign/" /><link rel="alternate" hreflang="fr" href="https://example.com/fr/services/creation-site-web/" /><link rel="alternate" hreflang="x-default" href="https://example.com/services/web-design/" />
On WordPress, WPML, Polylang and TranslatePress all generate these automatically once pages are linked as translations. The job left for you is making sure every translated page is linked to its source, because an unlinked translation gets no hreflang at all.
One detail surprises people: Google does not use hreflang or the lang attribute to work out what language a page is in. It reads the content. A page with a German hreflang tag and English body text is still an English page. Google's localised versions documentation sets the rules; these are the ones that trip people up:
- Return links are mandatory. If the English page points to the German page, the German page must point back. One-way annotations may be ignored.
- Each page lists itself as well as the other versions.
-
Use full URLs including
https://. -
Codes are language first, optional region second:
en-GB,de-AT,fr-BE. A region on its own is invalid, anden-UKis wrong because the ISO code for the United Kingdom is GB. - Add x-default for the version shown when no language matches, usually your English or language-selector page.
What Bing needs
Bing matters more in Europe than many assume, particularly on work laptops where Edge is the default, and its index also feeds several AI assistants. Bing has said it relies mainly on the HTML lang attribute and the content-language meta tag rather than hreflang. So on each language version set both, for example <html lang="de-DE">, keep hreflang for Google, and submit your sitemap in Bing Webmaster Tools. Enabling IndexNow, which Rank Math and most SEO plugins support, gets new translations picked up by Bing within hours instead of weeks.
Translation that ranks
Machine translation now produces a readable first draft. It is not good enough to rank on its own, for two reasons. First, people search with local phrases a literal translation misses. "Web design" in German searches is often just "Webdesign", but a small business owner may type "Homepage erstellen lassen". Second, thin machine-translated pages across a whole site look low-value to search engines.
We covered the same principles for right-to-left languages in our guide to English and Arabic bilingual SEO on WordPress; the hreflang logic is identical. A workable multilingual SEO process on a small budget:
- Research keywords in each language with a tool set to that country. Do not translate your English keyword list.
- Prioritise the homepage, main service or product pages, pricing and contact. Leave the blog archive in English until those earn traffic.
- Draft with machine translation, then have a native speaker edit for tone, local terms and search phrases.
- Localise, not just translate: currency, VAT wording, phone format, delivery terms, date formats and examples your reader recognises.
- Translate the metadata: title tag, meta description, image alt text and slug. These are the most commonly forgotten parts.
Local signals per country
Multilingual SEO also needs evidence that you serve each country, beyond the language. Our Google Business Profile checklist applies across Europe wherever you have a real presence. The signals that count:
- A local address or service area in each market, and a Google Business Profile where you trade locally.
- Prices in the local currency with the right VAT treatment.
- Links and mentions from sites in that country: local directories, trade bodies, suppliers and clients.
- Reviews in the local language.
- Legal pages in the local language: privacy policy, cookie consent and terms. In several EU countries a business-facing imprint page is expected or required.
Mistakes that cost rankings
Most multilingual SEO problems we see come from a short list of setup errors. Test each language version separately for speed as well, since translation plugins can add heavy scripts; our guide on fixing slow WordPress sites covers the usual causes.
- Auto-redirecting by IP or browser language. Googlebot crawls mostly from the US, so it may never see your other versions, and Google says to avoid this. Show a suggestion banner instead and let people choose.
- Canonical tags pointing to the English page from every translation. This tells Google to ignore the translations. Each version should canonicalise to itself.
- Half-translated pages where the menu is German but the content is English.
- Translations missing from the XML sitemap.
- Different page speed per language because a translation plugin loads extra scripts.
Questions we get asked
Can I rank in Germany with English pages?
For some B2B and technical searches, yes, because buyers search in English. For local services and consumer products, German pages will almost always outrank English ones.
Do I need a separate domain for each country?
No. Subfolders on one domain work well for most small businesses and are cheaper to run. Move to country domains only when a market is big enough to justify building its authority from scratch.
Is AI translation penalised?
Search engines judge quality, not the tool. Unedited machine translation tends to be thin and awkward, which is what hurts. Edited translation with local keyword research is fine.
How long before translated pages rank?
New language versions on an established domain often start picking up impressions within a few weeks. Competitive terms take months, as with any new page.
Should the blog be translated too?
Translate posts that match searches in that market. Translating every post adds maintenance with little return.
Planning a multilingual site?
We build and fix multilingual WordPress sites for small businesses selling across the UK and Europe, covering multilingual SEO, URL structure, hreflang, translated metadata and speed. See our SEO services for small businesses and international web development, check pricing, or tell us which markets you want to reach.
