Skip to main contentSkip to contact details

Article

Multilingual Websites for Small Businesses Going Abroad: A Practical Guide

How small service businesses can build a multilingual website: choosing languages, URL structure, hreflang, localisation and translation quality.

Illustration of a globe with connections to different countries
AMOSPublished:

A multilingual website gives each language its own clear address, tells search engines which version is for which audience, and adapts content to local customers instead of only translating words. For most small service businesses, the simplest setup is one domain with a folder for each language, for example /de for German. Add hreflang tags, translate with care, and check how people in each market actually search. Start with one new language you can serve well, then expand.

Who is this guide for?

This guide is for owners of small service businesses who want customers from other countries. Examples include a dental clinic that treats visitors from Germany, a law firm with clients abroad, a bakery near a tourist area, or a plumber in a border region.

You do not need an IT team to follow it. You do need to make a few decisions yourself. This guide explains those decisions.

Which languages should my website offer?

Choose languages based on the customers you can actually serve, not the languages that look impressive.

Ask yourself these questions:

  • Where do my enquiries already come from? Your contact form and phone calls show which countries already find you.
  • Can I answer in that language? A German page is not much use if no one can reply to a German e-mail or phone call.
  • Can I deliver the service there? A plumber cannot fix a pipe in another country. A law firm or a dental clinic that serves visitors may be able to.
  • Will I keep the pages up to date? An outdated translation with old prices or opening hours can cause confusion.

A dental clinic in Antalya, for example, might add English and German first because many of its patients come from those markets. It might add other languages only once the first ones work well.

Which URL structure should I use?

A URL structure is how your web addresses are organised for each language. There are three common options.

OptionExampleAdvantagesDrawbacks
Country domain (ccTLD)example.de, example.frStrong local signal, familiar to local usersSeparate domains to buy, manage and build up
Subdomainde.example.comEasy to separate technicallyOften treated more like a separate site, more setup
Subfolderexample.com/deOne domain, simple to manage, everything in one placeWeaker country signal than a country domain

For most small businesses, subfolders are the practical choice. You keep one domain, one set of settings and one place to manage.

This is also how AMOS works. Your website, articles, forms, legal pages and the chatbot can be published in many languages under one domain: your default language at the root, for example German under /de and Japanese under /ja.

What is hreflang and why does it matter?

Hreflang is a small piece of code that tells search engines which language and region each page is for. It also tells them which pages are translations of each other.

Without hreflang, a search engine may show your Turkish page to a reader in Germany. With it, the search engine has a clear hint about which version to show.

A few basic rules:

  1. Each language version should point to all the others, including itself.
  2. The links should work in both directions. If the English page points to the German one, the German page should point back.
  3. Add a default version with "x-default" for visitors whose language you do not offer.
  4. Use correct codes, such as "de" for German or "de-AT" for German in Austria.

Hreflang is a hint, not a command. It helps search engines understand your site, but it does not guarantee where a page appears.

What is the difference between translation and localisation?

Translation changes words from one language to another. Localisation adapts the whole page for a local audience.

Localisation includes:

  • Currency and prices shown in the form local customers expect.
  • Date, time and phone formats. Germany and Türkiye write dates differently from the US.
  • Legal pages. Privacy and cookie notices may need to reflect local rules. Ask a legal advisor about each market.
  • Examples and photos that make sense to local readers.
  • Contact options that local customers use and trust.

A bakery that takes orders from tourists might explain pick-up times and payment methods clearly in each language. A law firm might explain which kinds of cases it handles for foreign clients and which it does not.

Do people search the same way in every country?

No. The same service can be described with different words in different countries. A direct translation of your keyword may not be what local people type.

Some practical points:

  • Check the local term. People in one German-speaking country may use a different word for a service than people in another.
  • Check which search engine people use. Google is common in many markets, but some countries rely heavily on others, such as Naver in South Korea or Baidu in China.
  • Think about AI assistants. More people ask assistants questions in full sentences. Clear answers to common questions help in every language.
  • Ask a native speaker which words they would search for your service.

For example, a dental clinic should not just translate "dental implant price". It should check what patients in each country actually ask and answer those questions on the page.

How do I make sure the translation is good enough?

Machine translation has become useful, but it still makes mistakes. Small errors in a medical, legal or price-related page can mislead a customer.

A simple quality process:

  1. Translate the most important pages first: home, services, contact and legal pages.
  2. Have a native speaker review them, ideally someone who knows your field.
  3. Check numbers, names and terms such as prices, opening hours and service names.
  4. Review before publishing, not after a customer complains.
  5. Update all languages when you change something in the main version.

In AMOS, every translation waits for your approval before it goes live. You decide what is published in each language.

A short checklist before you launch

  • One clear language per page, with no mixed text.
  • A language switcher that is easy to find on desktop and phone.
  • Subfolders such as /de or /en for each language.
  • Hreflang tags on every language version.
  • Localised prices, formats, contact details and legal pages.
  • A native-speaker review of key pages.
  • A plan for answering enquiries in each language.

Where AMOS fits, and what you decide

AMOS is for service businesses with roughly 5 to 50 people that get new customers through their website and have no SEO, content or IT team. It can publish your site, articles, forms, legal pages and chatbot in several languages under one domain. You approve every translation before it goes live. The AMOS panel itself is available in English and Turkish.

What AMOS does not do matters too. AMOS does not promise rankings, traffic or revenue. It reports measured change in impressions, clicks and enquiries next to the work that was done.

You still decide which markets to enter, which languages to offer and whether a translation is good enough to publish.

How to start a pilot

A pilot starts with a short call about your website, your team and the markets you sell in. The length, terms and price of the pilot are agreed on that call, because they depend on your site and your markets.

If you are planning to reach customers in Germany, the wider EU or elsewhere, use the contact form or the chatbot to request a pilot. We reply within one working day.