ujans
Blog
Digital marketing

Multilingual SEO guide: hreflang, URL structure and localisation

Set up wrongly, a multilingual site confuses search engines about language versions and makes them compete. The right structure helps you reach the relevant audience in every language.

ujans team··5 min read

For businesses serving abroad, relying on tourists or having customers in more than one language, a multilingual website offers a big opportunity. But translating content and duplicating pages is not enough; you need to tell search engines accurately which page is for which language and region, and provide truly valuable content in each language.

Why multilingual SEO is different

Each language is a separate search market. Users search for the same thing in different words in different languages; word-for-word translation often misses the search intent. Also, if search engines do not associate the language versions of the same content correctly, they may show the wrong language to the user or treat the versions as duplicate content.

1. Choose the URL structure

There are three main structures for a multilingual site:

  • Subdirectory (ujans.com/en, ujans.com/de): Language paths under one domain. Easy to manage, and domain authority builds in one place. The recommended approach for most businesses.
  • Subdomain (en.ujans.com): May need separate management; sharing authority is more complex.
  • Country domain (ujans.de): Gives a strong local signal but needs a separate domain, separate management and separate authority building for each language.

Apply your chosen structure consistently; changing later carries redirect and ranking risk. For the domain and DNS side, the domain and DNS guide helps.

2. hreflang tags

hreflang tells the search engine which language and region a page is for and what its other language versions are. Principles of correct use:

  1. Must be reciprocal: If page A points to B, B must point to A. Missing reciprocity makes tags ignored.
  2. Self-reference: Each page must include its own language version.
  3. Correct language codes: Such as tr, en, de; with region (such as en-GB) if needed.
  4. x-default: A default page can be specified for users with no chosen or matching language.
  5. Consistent with canonical: Each language version must point to its own canonical address; canonicalising all versions to one page voids hreflang.
  6. Equivalent pages only: Do not add hreflang for a page with no equivalent in a language.

hreflang can be defined in the HTML head, HTTP header or XML sitemap. Defining it in the sitemap eases management for many pages.

3. Localisation, not just translation

  • Do keyword research separately in each language. "Adisyon programı" in Turkish and "restaurant POS software" in English capture the same intent but use different words.
  • Cultural fit: Currency, date format, units, address and phone formats, examples and tone must be adapted to language and country.
  • Local references: Customer reviews, sector examples and regulatory references should suit the target market.
  • Translation quality: Machine translation can give a fast first draft, but a native-speaking editor must review it before publication. Poor translation damages both trust and ranking. For AI-assisted content processes see AI-generated content and SEO.
  • No language mixing: Do not mix languages on one page; menu, button and form texts must be translated too.

4. On-page optimisation in every language

Each language version should have its own title, meta description, H1, image alt text and URL (with localised words if possible). Rather than merely translating the title and description, write them to raise clicks in that language's results. The basic principles of the SEO guide for small businesses apply.

5. Language switching and user experience

  • Provide a visible, accessible language switcher on every page; it should take the user to the equivalent version of the same page, not the home page.
  • Use automatic redirection (by browser language) carefully; search engine crawlers and the user's choice must not be blocked. A suggestion banner is safer than a forced redirect.
  • The language preference can be remembered, but each language version must stay reachable by direct link.

6. Technical points

  1. XML sitemap: Include all language versions and link them with hreflang.
  2. Crawlability: Language versions must not be blocked by robots rules and must be reachable through internal links.
  3. Canonical tags: Each version points to its own canonical address.
  4. Speed and mobile fit: The same performance in each language; see speeding up your website.
  5. Internal linking: Link between pages in the same language; do not create language confusion.
  6. Structured data: Mark up in each language with the right language and information; see the structured data guide.

7. Local visibility

Physical businesses need local profiles and directory listings in each market; the Google Business Profile and local SEO articles describe the steps. For the effect of multilingual pages aimed at foreign guests on direct bookings at hotels, see increasing direct bookings.

8. Measurement and monitoring

Track performance by language and country in Search Console; examine language versions as separate segments in analytics. How much traffic and conversion each language brings guides your content investment; the Google Analytics 4 guide helps with measurement setup.

Common mistakes

  • Publishing with machine translation only,
  • Adding hreflang that is not reciprocal,
  • Pointing all languages to the same canonical address,
  • Accidentally blocking language versions with robots or noindex,
  • Sending the user to the home page when they switch language,
  • Translating only the home page and skipping other pages,
  • Not doing keyword research in each language,
  • Ignoring local regulation and cultural differences.

Technology choice

Setting up the multilingual structure correctly from the start is much easier than adding it later. Weigh this need when choosing technology; see WordPress or custom development? and website cost. On a multilingual site, each extra language and its content also raises maintenance and translation cost; plan the budget accordingly.

A starter plan

  1. Decide target languages and markets.
  2. Choose the URL structure.
  3. Do keyword research in each language.
  4. Localise content and have a native-language editor review it.
  5. Set up hreflang, canonical and sitemap correctly.
  6. Set up the language switcher and language-level measurement.
  7. Monitor and improve performance regularly.

ujans builds multilingual websites in Turkish, English and German and sets up hreflang, URL structure, content localisation and technical SEO correctly from the start.

Looking for help with this?

Tell us what you need and our team will get back to you within one business day.

Get a quote