Multilingual Websites for Europe: hreflang, Translation and Local SEO

Europe is one market for trade, but not for search. A customer in Lyon searches in French, one in Vienna searches in German with Austrian vocabulary, and one in Brussels might search in French, Dutch or English depending on the day. If your website speaks only one language, you are invisible to many of the people you want to reach.

A multilingual website done well can open new markets without opening new offices. Done badly, it creates duplicate content, confuses search engines and sends visitors to the wrong language. This guide covers the decisions that matter for multilingual website SEO in Europe: URL structure, hreflang, translation quality and local SEO in each country.

Language or country: decide what you are targeting

Before touching any code, be clear about whether you are targeting languages, countries, or both.

• Language targeting works when the content is the same for everyone who speaks that language. A software company might have one French version for France, Belgium, Switzerland and Luxembourg.
• Country targeting is needed when something differs by country: prices and currency, delivery options, legal information, stock or contact details. An online shop selling to Germany and Austria may need separate versions even though both are in German.

Many European businesses end up with a mix, for example en, fr-FR, fr-BE, de-DE and de-AT. Start with the markets that matter commercially, not with every language you could possibly add. Each version needs ongoing maintenance.

Choosing a URL structure

Google's guidance on managing multi-regional and multilingual sites describes the main options:

• Country-code domains (example.de, example.fr): a strong country signal, but each domain must be bought, managed and built up separately.
• Subdomains (de.example.com): easy to set up, but it is less obvious to users whether "de" means language or country.
• Subdirectories (example.com/de/): easy to manage on one site, and all versions benefit from the main domain's strength.
• URL parameters (example.com?lang=de): not recommended.

For most small and medium businesses, subdirectories are the practical choice. They are simple to host, share one domain's authority, and are easy for users to understand. Country-code domains make sense when you have a strong local brand and the budget to run them separately.

Whatever you choose, keep each page's content in one language. Mixing languages on the same URL, or translating only the navigation, confuses both visitors and search engines.

Setting up hreflang correctly

The hreflang annotation tells Google which language and regional versions of a page exist, so it can show the right one to each searcher. It does not make a page rank higher on its own, but it helps prevent the wrong version from appearing, such as your German-for-Germany page showing up in Austria when you have an Austrian version.

Key rules from Google's hreflang documentation:

1. Use one method: HTML link tags in the page head, HTTP headers, or an XML sitemap. Using more than one adds no benefit and doubles the chance of mistakes.
2. List every version on every version, including the page itself. The set of annotations should be identical across all versions.
3. Return links are required. If page A points to page B, page B must point back to page A, or Google may ignore the annotations.
4. Use valid codes: a language code (ISO 639-1), optionally with a region code (ISO 3166-1 Alpha 2), such as de-AT. A region code cannot be used alone. Use en-GB, not en-UK.
5. Use full URLs, including https://.
6. Add x-default for a fallback page, such as a language selector or your main international version.

Errors in hreflang are very common, especially missing return links and wrong codes. If your site is built on a modern framework or a well-designed CMS, generate the tags automatically from your content structure rather than maintaining them by hand.

Do not auto-redirect visitors by language or location

It is tempting to detect a visitor's browser language or IP address and redirect them automatically. Google advises against it: automatic redirects can stop users and search engines from reaching all versions of your site, and Googlebot usually crawls without a specific language preference.

A better approach:

• Show a clear language and country selector on every page, usually in the header.
• Optionally show a small, dismissible suggestion ("This page is also available in German") instead of forcing a redirect.
• Remember the visitor's choice for future visits.
• Use native language names in the selector ("Deutsch", "Français"), not flags, since flags represent countries rather than languages.

Translation quality: machine, human or both?

Machine translation has improved a lot, and AI can now produce a usable first draft in seconds. But publishing raw machine translation across hundreds of pages carries real risks: awkward phrasing that erodes trust, mistranslated legal or product details, and content that reads as low quality to both people and search engines.

A practical workflow for SMEs:

1. Use AI or machine translation for the first draft.
2. Have a fluent speaker, ideally a native speaker familiar with your industry, review and edit key pages: home, product or service pages, pricing, checkout and legal pages.
3. Build a glossary of brand terms and product names so they stay consistent.
4. Localize, not just translate: currencies, date formats, units, phone formats, examples and imagery.
5. Do keyword research in each language. The term people search for is often not a direct translation of your English keyword.

That last point matters more than most businesses expect. A literal translation of your main keyword may have little search demand, while locals use a completely different phrase.

Local SEO in each European market

Ranking in a new country takes more than translated pages.

• Local trust signals: local phone numbers, addresses where you genuinely have them, local payment methods, prices in the local currency and delivery information for that country.
• Google Business Profile for any real physical locations, with each location's details consistent with its page on your site.
• Local links and mentions: industry associations, local partners, press coverage and directories in each country.
• Country-specific legal pages: imprint requirements, privacy notices and terms that reflect local rules. If you collect personal data, our GDPR website checklist covers the essentials, and consent for analytics in each market is explained in our guide to cookie banners under GDPR.
• Performance: a fast site in every market. Our guide to Core Web Vitals for European e-commerce explains what to measure.

Technical checklist for a multilingual website

1. One language per URL, with a clear subdirectory or domain structure.
2. Correct lang attribute in the HTML for accessibility and browsers, even though Google detects language from visible content.
3. Hreflang annotations generated automatically, with return links and x-default.
4. Canonical tags that point to each page itself, not to the English version.
5. Translated titles, meta descriptions, URLs (where practical), image alt text and structured data.
6. An XML sitemap that includes all language versions.
7. A visible language selector on every page, with no forced redirects.
8. Separate analytics views or filters per market so you can see what works.

How HEXACODES can help

HEXACODES builds multilingual websites and online stores with clean URL structures, automatic hreflang, translated metadata and fast performance, and we offer SEO services to research keywords and optimize each market. We also use AI-assisted translation workflows with human review to keep costs down without sacrificing quality. Learn more about our AI services.

A full business website starting at $30/month can be a solid base for your first markets, and we can add languages as you grow. To plan your multilingual site, contact us.

Frequently asked questions

Do I need hreflang if my site has only two languages?

Hreflang is most useful when you have similar content in several languages or regional variants of the same language, such as German for Germany and Austria. With two clearly different languages, Google can usually tell them apart, but hreflang still helps it show the right version and is easy to add. It is good practice for any multilingual site.

Is machine translation bad for SEO?

Machine translation is not automatically a problem, but publishing unreviewed translations at scale can produce low-quality pages that do not serve users well. The safest approach is to use machine or AI translation as a draft and have fluent speakers review important pages. Localizing keywords for each market matters as much as translation quality.

Should I use subdirectories or country domains for a European website?

For most small and medium businesses, subdirectories such as example.com/fr/ are easier to manage and benefit from one domain's authority. Country-code domains send a stronger local signal but require separate management and link building for each one. Choose based on your budget, brand strategy and how different each market really is.