SEO & GEO
International SEO for Europe 2026: hreflang, Domains & AI Search
International SEO for Europe in 2026: ccTLD vs subfolder, hreflang done right, AI translation without spam risk, and a market matrix for 9 European markets.

Key takeaways
In short:
- International SEO means optimising a website for several languages or countries so that Google, Bing and AI search tools show every user the right version.
- Domain strategy: country-code domains (ccTLDs) send the clearest country signal according to Google; subfolders are the easiest to maintain. Google does not recommend URL parameters.
- hreflang links language versions via HTML, HTTP headers or the sitemap. Every version must list itself and all others, or Google ignores the annotations (Google).
- No automatic redirects by IP or browser language: Googlebot usually crawls from the US and sends no
Accept-Languageheader. - Europe is not one market: Google holds more than 80% search share in all nine markets covered here (StatCounter, October 2026), yet languages, directories and AI features still differ.
Expanding across Europe raises the same questions for almost every business: one domain or several? How do you implement hreflang correctly? Is AI translation good enough? And how do you get mentioned by AI search in several languages? This guide answers them from Google's official documentation and current market data, from a European perspective: many languages, several multilingual countries and a regulatory environment that makes Google roll out features here differently. All information as of 6 November 2026.
What is international SEO, and how is multilingual different from multi-regional?
Google's documentation on managing multi-regional and multilingual sites distinguishes two cases:
- A multilingual website offers content in more than one language. Example: a Swiss company with German and French versions.
- A multi-regional website explicitly targets users in different countries. Example: an online shop with separate prices and shipping terms for Germany and Austria.
Many sites are both. An Austrian manufacturer with pages for Austria, Germany, Switzerland and France has two languages (German, French) and four regions. The distinction decides which signals you need: for pure language versions a language code such as de is enough; for country versions you need combinations such as de-AT or fr-CH.
Which domain strategy fits: ccTLD, subfolder, subdomain or separate domain?
Google lists four URL structures with their pros and cons (Google Search Central). The "Best for" column is our assessment.
| Structure | Example | Pros according to Google | Cons according to Google | Best for |
|---|---|---|---|---|
| Country-code domain (ccTLD) | example.fr, example.it |
clear geotargeting, server location irrelevant, sites easy to separate | expensive, sometimes limited availability, more infrastructure, sometimes strict registration rules, one country per domain | established brands with local teams and budgets per country |
| Subdomain on a gTLD | fr.example.com |
easy to set up, different server locations possible, easy to separate | users can't tell whether "fr" means language or country | separate systems per market, e.g. a local shop |
| Subfolder on a gTLD | example.com/fr/ |
easy to set up, low maintenance (one host) | geotargeting unclear from the URL, single server location, harder to separate | most SMEs with two to six languages |
| URL parameter | example.com?loc=fr |
– | not recommended by Google, segmentation difficult | don't use |
One option the table doesn't show is a separate domain per language, for example a .de domain for German and a .com domain for English. Technically it's a hybrid: the .de domain signals Germany, while .com is generic. It works when the language versions serve different audiences (DACH versus a pan-European, English-speaking audience) and are built separately.
What to know about domain endings
.euis not a country signal. Google treats.euand.asiaas generic domains, as well as some country endings such as.io,.ai,.co,.meand.tv(Google). A pan-European.eudomain still needs explicit hreflang signals.- Server location is a weak signal. Google says it isn't definitive because many sites are served through CDNs.
- Other signals include local addresses and phone numbers, local language and currency, links from local sites and your Business Profile.
- Ignored: geo meta tags such as
geo.positionordistribution.
A four-question decision framework
- Does content really differ by country (prices, legal terms, product range, contacts)? No → one version per language is enough; skip country versions.
- Is there a team and budget per country for links and maintenance? Yes → ccTLDs are realistic. No → subfolders concentrate authority on one domain.
- Do markets run on separate systems (different shop, different CMS)? Yes → subdomain or separate domain.
- Is the ccTLD available and can you legally register it? Some countries attach conditions. Check before deciding.
Changing the structure of an existing site should be planned like a relaunch: with a redirect map, monitoring and a clean migration. The steps are in our website redesign SEO checklist.
How do you implement hreflang correctly?
hreflang is an annotation that tells Google that several URLs are language or regional variants of the same content, so it can show each user the right one. According to Google there are three equivalent methods:
| Method | Where | Best for | Note |
|---|---|---|---|
HTML link elements |
in the <head> of every page |
small and mid-sized sites | must sit inside a valid <head> |
HTTP Link: header |
server response | PDFs and other non-HTML files | identical header for every version |
| XML sitemap | xhtml:link entries per URL |
large sites, many languages | requires the xmlns:xhtml namespace |
Google states explicitly that using all three at once brings no benefit in Search. Pick one and maintain it properly.
Rules that always apply
- Self-reference and completeness: every language version lists itself and all other versions.
- Return links: if two pages don't point to each other, Google ignores the annotations.
- Fully qualified URLs:
https://example.com/fr/, not/fr/or//example.com/fr/. - Cross-domain is fine: alternates don't have to be on the same domain.
- Codes: language first in ISO 639-1, optionally followed by the region in ISO 3166-1 Alpha 2. Case doesn't matter.
- x-default: a reserved value for users whose settings match none of your versions. Google recommends it especially for language selector pages.
Here is a complete set for a page in generic German, Swiss German, Swiss French and English. The same block appears on all four pages:
<!-- identical on all four language versions -->
<link rel="alternate" hreflang="de" href="https://example.com/de/leistungen/" />
<link rel="alternate" hreflang="de-CH" href="https://example.com/ch-de/leistungen/" />
<link rel="alternate" hreflang="fr-CH" href="https://example.com/ch-fr/prestations/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/services/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/services/" />
The generic de version catches German speakers in Germany, Austria and elsewhere. Google explicitly recommends such a catch-all when you have several regional variants of the same language.
Common hreflang mistakes
| Mistake | Example | Result | Fix |
|---|---|---|---|
| missing return link | DE points to EN, EN doesn't point to DE | annotations ignored | output an identical block on all versions |
| country code only | hreflang="at" |
invalid; Google doesn't derive a language from a country | de-AT |
| wrong region code | en-UK, de-EU |
Google ignores that part; UK and EU are not valid codes |
en-GB; there is no code for "EU" |
| language/country mix-up | be for Belgium |
be is Belarusian |
nl-BE, fr-BE, de-BE |
| unsupported code | es-419 (Latin America) |
not supported by Google | list individual countries |
| relative URLs | href="/fr/" |
invalid | fully qualified URL with https:// |
| hreflang to a non-canonical URL | pointing to a parameter URL whose canonical is elsewhere | conflicting signals | only reference canonical, indexable URLs |
The last row is our practical recommendation, derived from Google's guidance on canonicals (see below). For testing, Google mentions third-party tools such as Aleyda Solis's hreflang tags generator and Merkle's hreflang testing tool.
How does Google detect a page's language?
Many assume <html lang="fr"> tells Google the language. It doesn't. Google says it uses the visible content, not code-level information such as the lang attribute or the URL (Google). hreflang isn't used for language detection either; it only maps variants (Google).
So:
- One language per page, including navigation, footer and cookie banner. Half-translated pages (French navigation, English body) make detection harder.
- No side-by-side translations on the same page.
- Keep the
langattribute anyway: screen readers, hyphenation and accessibility depend on it, which also matters under the European Accessibility Act.
Why shouldn't you redirect automatically by IP or browser language?
Google advises against it clearly (Google):
- No automatic redirects from one language version to another based on the user's assumed language. They can prevent users and search engines from seeing all versions.
- No IP analysis to adapt content. Google calls it unreliable, and most Google crawls originate in the US. Google doesn't vary the crawler location to discover variants.
- Googlebot sends no
Accept-Languageheader. If you serve content purely by browser language, Google may only ever see one version.
Use a visible language and country switcher on every page instead. A subtle banner ("This page is also available in Italian") is fine, as long as it doesn't redirect automatically.
How do canonical and hreflang work together?
A canonical (rel="canonical") tells Google which of several identical or very similar URLs to index. hreflang links variants that should all be indexed. They don't conflict if you follow three rules:
- Each language version is its own canonical. The English page canonicalises to itself, not to the German one.
- Translated pages aren't duplicates. According to Google, localised versions only count as duplicates if the main content stays untranslated.
- Same language, several URLs: if, say,
example.de/andexample.com/de/show nearly identical German content, Google says to pick a preferred version and use canonical and hreflang so the right URL is served.
For de-DE, de-AT and de-CH, or fr-FR, fr-BE and fr-CH, with almost the same text, be honest: do prices, legal notes, contacts or vocabulary really differ? If not, a single generic language version is often better than three near-identical pages.
Translation, localisation or transcreation, and what can AI do?
| Approach | What happens | Best for | Risk |
|---|---|---|---|
| Translation | text is transferred into the target language | legal texts, documentation, product data | reads foreign, misses local search terms |
| Localisation | translation plus adapted currency, units, legal references, examples and contacts | service and product pages | medium effort, requires market knowledge |
| Transcreation | the message is rewritten for the market, with its own keyword research | home page, campaigns, guides that should rank | highest effort, best results |
Keyword research per language is essential. A directly translated keyword often has little search volume in the target market because people there use different terms. That applies even between France, Belgium and Switzerland, or between Germany and Austria.
AI translation and spam risk: Google allows AI content as long as it helps users. But its spam policies explicitly include automatically translated or rewritten content without added value under "scaled content abuse". Generating 500 pages in ten languages at the push of a button lands squarely in that territory. A safe workflow:
- AI draft based on a glossary of fixed terms and brand names.
- Localisation by someone who knows the market: examples, prices, regulations, contacts.
- Native-speaker review, especially for service pages.
- Only publish pages for which there is demand in the target market.
More on an AI-assisted editorial workflow in our guide to AI content marketing.
How do European markets differ?
The matrix summarises the main differences. Google share comes from StatCounter for October 2026 (all platforms). StatCounter measures page views on sites using its tracking code, not search queries, so treat the figures as indicative. According to Google Help (AI Mode, AI Overviews), AI Overviews and AI Mode are available in all EU member states, plus Switzerland and Norway.
| Market | Google share (Oct 2026) | Bing share | hreflang languages | AI Overviews / AI Mode | ChatGPT Ads |
|---|---|---|---|---|---|
| Germany | 88.47% | 6.41% | de (or de-DE) |
yes | yes, since 24 Aug 2026 |
| Austria | 80.64% | 11.14% | de-AT |
yes | yes |
| Switzerland | 81.25% | 11.55% | de-CH, fr-CH, it-CH |
yes | yes (listed for Ads Manager) |
| France | 89.24% | 5.18% | fr / fr-FR |
yes, since 22 Jul 2026 | yes |
| Netherlands | 89.6% | 4.64% | nl / nl-NL |
yes | yes |
| Belgium | 88.5% | 8.14% | nl-BE, fr-BE, de-BE |
yes | part of the European rollout; check the country list |
| Italy | 88.06% | 5.83% | it / it-IT |
yes | yes |
| Spain | 93.29% | 3.92% | es / es-ES |
yes | yes |
| Poland | 89.42% | 7.66% | pl |
yes | part of the European rollout; check the country list |
| Sweden | 85.82% | 8.68% | sv |
yes | yes |
| Denmark | 84.9% | 9.68% | da |
yes | yes |
| Norway | 90.6% | 5.47% | nb or no |
yes | yes |
| Finland | 87.26% | 5.23% | fi, possibly sv-FI |
yes | part of the European rollout; check the country list |
ChatGPT Ads sources: on 18 August 2026 OpenAI announced 31 European markets, naming among others Germany, France, Spain, Italy, the Netherlands, Sweden, Norway, Denmark and Austria. Switzerland appears in the Ads Manager availability list. We have not verified Belgium, Poland or Finland in OpenAI's announcement; check the country list before launching a campaign. In the EEA and Switzerland, ads are not personalised at first. Details in our guide to ChatGPT Ads in Europe.
What the matrix means in practice:
- Google remains the number-one channel, at 88.77% across Europe in October 2026 according to StatCounter.
- Bing exceeds 11% in Austria and Switzerland, well above Germany. Bing Webmaster Tools belong in the basic setup there, not least because Bing underpins Microsoft Copilot.
- Multilingual countries (Switzerland, Belgium, Finland) need language-region combinations. Switzerland also differs in vocabulary, spelling (no "ß" in Swiss German) and currency (CHF).
- Local directories are country-specific: for example Herold in Austria, and local.ch and search.ch in Switzerland. More in our guide to local AI search.
- Ads inside Google's AI answers are not available in the EU as of November 2026. On 28 October 2026 Google expanded ads in AI Mode to ten more countries; no EU country was among them.
Regulation keeps shifting the ground: on 23 July 2026 the European Commission fined Google a total of €890 million under the Digital Markets Act, partly for self-preferencing in Search. New Google features therefore often reach Europe later or in modified form. France, for instance, only got AI Overviews and AI Mode on 22 July 2026. What this could mean for 2027 is covered in SEO & AI search trends 2027.
How does GEO work across languages?
GEO (generative engine optimisation) is the practice of optimising content so that AI search tools such as ChatGPT, Perplexity or Google's AI Mode mention and cite a business. Internationally it adds three tasks:
- Prompt sets per language: don't just test in English. For each market, write 20 to 30 typical questions in the local language, the way real customers ask them, and record whether and how your business is mentioned. Translating your English prompts isn't enough, because customers in other countries compare different providers, terms and problems.
- Sources in the local language: in Germany, 80% of core sources in AI Mode are in German, according to SISTRIX. English content doesn't replace a local version if you want to be cited in France or Italy.
- Consistent entity: company name, address, services, founders and key facts must be identical in every language: on the website, in structured data (
OrganizationwithsameAs), in business profiles and in directories. Contradictions between language versions make it harder for AI systems to attribute the information to one company.
For Google, the single-language rule still applies: there are no special requirements for AI Overviews and AI Mode; indexed, snippet-eligible pages are the prerequisite. More in our guide to Google AI Mode & AI Overviews.
What does a real setup look like? Contentoren as an example
We use our own site as a neutral example because we can disclose the technical details. It shows one valid solution among several, not the only right one.
- Two domains, two languages:
contentoren.dein German for the DACH region,contentoren.comin English for a European audience. Both are produced as separate builds from the same codebase. - Language-specific URL paths: for example
/ratgeber/…and/leistungen/…in German,/insights/…and/services/…in English. - hreflang in HTML: every page lists itself and its counterpart in the other language with a fully qualified URL, i.e.
hreflang="de"andhreflang="en", plus anx-defaultthat points to the German version. - Absolute canonical per host: every page canonicalises to its own full URL on its own domain. The English page never points to the German one.
- Shared ID for article pairs: German and English guides share an ID, which generates the hreflang annotations and the language switcher automatically.
Why no country versions such as de-AT? Because our offering and content don't differ between Germany, Austria and Switzerland. A single generic de version is more honest than three near-identical pages.
Checklist: international SEO in 12 steps
- Prioritise target markets by demand and business potential, not by number of languages.
- Decide: language versions, country versions or both.
- Choose and document the domain strategy (ccTLD, subfolder, subdomain, separate domain).
- Do keyword research per language and country.
- Localise or transcreate; have native speakers review AI drafts.
- One language per page, including navigation, footer and cookie banner.
- Implement hreflang with one method: self-reference, return links, full URLs, valid codes, x-default.
- Set self-referencing canonicals for each language version.
- No automatic redirects by IP or browser language; add a visible language switcher.
- Add local signals: address, phone number, currency, Business Profile, local directories.
- Set up Search Console and Bing Webmaster Tools per property; filter performance by country.
- Build prompt sets per language for AI search and review them monthly.
Which mistakes do we see most often?
- Machine-translated pages at scale without review and without demand in the target market. This is the biggest risk, because it falls under Google's definition of spam.
- hreflang on the home page only. hreflang works per URL; every translated subpage needs its own set.
- Canonical pointing to the main language. The translated page then drops out of the index.
en-UKandde-EU. Neither is a valid code; both are ignored.- IP-based redirects. Googlebot then often sees only the US or English version.
- Mixed languages on one page, such as English product data inside German navigation.
- Focusing on Google alone. In Austria and Switzerland, Bing holds more than 11% according to StatCounter, and AI assistants draw on their own sources.
- Country versions without differences.
fr-FR,fr-BEandfr-CHwith identical text add maintenance without benefit.
Conclusion
International SEO in Europe comes down to clean foundations first: a deliberate domain strategy, correct hreflang with return links, self-referencing canonicals per language and no automatic redirects. The difference is then made by content: businesses that research keywords per market, localise rather than just translate, and keep their entity consistent across languages are more likely to be found in Google and in AI answers. Google dominates all nine markets covered here, but languages, directories and AI features vary from country to country.
If you want to set up your website for more European markets, Contentoren's SEO service (from €3,000 setup, incl. VAT) helps with structure, hreflang and content. For visibility in AI answers across several languages, see our GEO service (from €4,500 setup, incl. VAT). We can discuss which structure fits your markets in a no-obligation call: get in touch.
Sources
Accessed 6 November 2026
- Google Search Central: "Managing multi-regional and multilingual sites"
- Google Search Central: "Tell Google about localized versions of your page" (hreflang)
- Google Search Central: Spam policies ("Scaled content abuse")
- Google Search Central: "AI features and your website"
- Google Search Help: AI Mode availability
- Google Search Help: AI Overviews availability
- Google France: AI Overviews and AI Mode launch in France (22 Jul 2026)
- Google: "Ads in AI Mode expand to 10 new countries" (28 Oct 2026)
- European Commission: Google fined €890 million under the DMA (23 Jul 2026)
- StatCounter Global Stats: Search Engine Market Share, October 2026 (Europe and country pages)
- OpenAI: "ChatGPT Ads expands across Europe" (18 Aug 2026, updated 31 Aug 2026)
- OpenAI Help Center: Ads Manager availability
- OpenAI Help Center: Ads in ChatGPT
- SEO Südwest: ChatGPT Ads launch in the EU on 24 August (German)
- SISTRIX: "AI Citation Drift" (28 Apr 2026, updated 13 Oct 2026)
- ISO 639-1 language codes (Wikipedia list) and ISO 3166-1 Alpha 2
Frequently asked questions
Which is better for international SEO: ccTLD, subfolder or subdomain?
There is no single best option. Google says country-code domains such as example.de give the clearest geotargeting but are expensive and need more infrastructure, while subfolders such as example.com/de/ are easy to set up and low-maintenance but harder to separate. Google does not recommend URL parameters such as ?loc=de. Budget, number of markets and whether each country really gets distinct content should decide.
What does hreflang x-default mean?
x-default is a reserved hreflang value for users whose language or region settings don't match any of your versions. Google designed it mainly for language selector pages, but it can be used on any page. The target page doesn't need a language code of its own.
Why is Google ignoring my hreflang tags?
The most common reason is missing return links: if page A points to page B but B doesn't point back to A, Google ignores the annotations. Other frequent errors are invalid codes such as en-UK instead of en-GB, country codes without a language, and relative instead of fully qualified URLs.
Does Google use the HTML lang attribute to detect a page's language?
No. According to its documentation, Google determines a page's language from the visible content using its own algorithms, not from the lang attribute, hreflang or the URL. The lang attribute is still worth setting for screen readers and accessibility.
Can I use AI to translate my website?
Yes, but not unreviewed and at scale. Google's spam policies list automatically translated content without added value as an example of scaled content abuse. A safe workflow combines an AI draft, adaptation to the local market and review by a native speaker.


