Foldwren

Do you need a multilingual website?

How to tell whether a second language is worth adding to your website, why proper translation matters, and which pages to start with.

Most Australian small businesses do not need a multilingual website. Some very much do. The difference comes down to who your customers are, and whether you can look after them in that language once they get in touch.

It is a bigger commitment than it first appears, so it pays to think it through before anyone translates a word.

Who benefits from a second language?

A translated site makes sense when a meaningful share of your customers would rather read about your services in a language other than English. That commonly includes:

  • Businesses serving a particular community, such as a GP clinic, accountant, migration agent or real estate agency in an area where many residents speak Vietnamese, Mandarin, Arabic, Greek or Punjabi
  • Tourism businesses, such as a regional winery, tour operator or guesthouse that hosts overseas visitors
  • Exporters and wholesalers with buyers in other countries
  • Education providers and anyone serving international students
  • Health and community services, where being clearly understood really matters

Look for evidence before you decide. Do customers bring a family member to translate? Is your bilingual staff member the reason some people choose you? Do enquiries arrive in another language already?

Then ask the harder question: can you follow through? A site in Mandarin makes a promise. If nobody who answers the phone speaks Mandarin, that promise is broken at the first call. It is fine to offer partial service as long as you are plain about it. "Linh speaks Vietnamese and is in the clinic Monday to Thursday" is honest and helpful.

Why a translate button is not enough

Free automatic translation widgets are tempting. Add one and your site appears in dozens of languages. We would steer you away from relying on them, for two reasons.

First, machine translation stumbles on trade terms, local expressions and tone. The result can be anywhere from slightly odd to plain wrong, and on medical, legal or financial content, wrong is a serious problem.

Second, a widget generally changes the text in the visitor's browser without creating real pages in that language. Search engines have nothing to index, so the widget does little to help you get found by people searching in that language.

Proper translation means a professional translator, preferably one who knows your industry and writes for Australian speakers of the language. For important material, look for a translator certified by NAATI, the national accreditation body. Then have a second fluent speaker read it through, ideally someone from the community you are trying to reach.

There is a sensible middle path for low-risk content. A machine-translated draft that a fluent person checks and corrects can work for a cafe menu or a list of opening hours. It is not suitable for consent forms, contracts or health advice.

The technical side, briefly

Your web person will handle the detail, but these are the things to ask for.

  • A real page for each language, each with its own address, so it can be found in search, shared and bookmarked.
  • Language tags in the page code that tell search engines which version is which.
  • A visible language switcher at the top of every page, with each language written in its own script or spelling. "Italiano", not "Italian". Skip the flags, since flags represent countries and plenty of languages cross borders.
  • A flexible design. Translated text can run much longer or shorter than English. Arabic and other right-to-left languages need the layout mirrored, and fonts must support the characters used.

Upkeep is the real cost

Translation is not a one-off job. Every time the English page changes, the translated page needs to change with it. New prices, new hours, a new service, a changed policy.

An out-of-date translated page is worse than none, because it gives wrong information to the very people you set out to help.

Before you start, settle who will translate updates and how quickly, and how you will keep track of which pages exist in which language. Remember the less visible text as well: forms, error messages, auto replies, booking confirmations and downloadable documents all need attention. So do the enquiries that arrive in that language. Someone has to reply.

Start with the pages that matter most

You do not need to translate the whole site. Start small and see what happens.

  1. A landing page in the second language covering who you are, what you offer, and who on your team speaks the language
  2. Your one or two main service pages
  3. Contact and booking details, including the form
  4. Practical information people need before they visit, such as fees and what to bring

Leave the blog and news in English for now. After a few months, look at visits to the translated pages and enquiries that came from them, and ask customers whether they found the pages useful. Expand if it is earning its keep.

Five questions to answer before committing

  • Who exactly are we trying to reach, and how do we know they want this?
  • Who will respond to enquiries in that language?
  • Who will translate, and who will check the translation?
  • Who will update the translated pages when the English ones change?
  • Which five pages would make the biggest difference?

If you can answer all five with a name or a specific plan, go ahead. If two or more draw a blank, sort those out first.

Your order