Multilingual website: when it actually pays off

A multilingual website looks like an easy win: get the text translated and more customers should follow. In reality, a second language only pays off when there is a real customer speaking it and a real sales process behind it. If a translation is added just in case, you gain maintenance work but not sales. In this article we look at when a language version pays off, what it requires beyond text, and how hreflang helps Google show the right version.

When a second language brings in money

The simplest test question is this: are you already getting enquiries or customers who speak that language? If Finnish customers are calling and asking for quotes, a Finnish-language site is the logical next step. If nobody has ever asked in English, an English-language site will not create demand by itself.

The second question concerns your sales process. A language version pays off when you can also reply, quote and invoice in that language. A site that promises a service in Finnish, but where the person answering only speaks Estonian, leaves a poor impression and the enquiry often stalls.

The third question is upkeep. Every extra language increases the maintenance load: every price change, new service and new blog post has to be done more than once. If you plan to update the site often, it is worth working out that duplicated effort honestly before deciding. An out-of-date translation is worse than no translation at all, because a wrong price or an old contact detail damages trust more than a single-language site does. The same logic applies to any language, whether Finnish, English or Russian.

A language version is more than text

A common misconception is that translation is enough. In practice, a language version is a whole service channel. If a customer reads the site in Finnish, they expect everything else that comes with the purchase to be in Finnish too.

• Prices and terms must be in the same language and up to date.
• The contact form, automated replies and emails must work in that language.
• The quote and the invoice must arrive in the language the customer reads.
• Someone has to be able to answer the phone or an email within a reasonable time.

Machine translation is a separate topic. A Google Translate widget on the site does not replace a language version, because it creates no indexable page and no visibility in the other language. Machine translation without human review produces errors in service terminology that reduce trust and cut the number of enquiries. A sensible workflow is this: machine translation can be a draft, but the final text is reviewed by someone who genuinely speaks the language and knows your field. The same applies to blog posts: a half-translated site, where some content is in Estonian and some is machine translated, looks sloppy. Customers quickly notice when a text has been written by someone who knows the subject.

Hreflang explained simply

Hreflang is a tag that tells Google which page is intended for which language and region. If you have the same service page in Estonian and Finnish, hreflang helps Google show the Finnish version to a Finnish searcher and the Estonian version to an Estonian one.

The tag can be placed in the head of the page, in the HTTP header or in the XML sitemap. The language codes are straightforward: et for Estonian, fi for Finnish and en for English. A region can be added where needed, for example fi-FI or en-GB. There is also x-default, which marks the page a visitor is sent to when their language does not match any version. The exact rules are set out in Google's own documentation. There is no need to worry about duplicate content: when the references are in place, the same content in different languages is fine as far as Google is concerned.

Common hreflang mistakes

• References are not reciprocal. If the Estonian page points to the Finnish one, the Finnish page must point back, otherwise the tag is ignored.
• Automatic redirection based on browser language or IP address. This can stop the search engine from seeing all the versions.
• Hreflang points to a page that does not exist or to an address that redirects elsewhere.

Hreflang is a one-off technical job. Once the references are set up correctly, they need no day-to-day maintenance.

Where to put your language versions

Every language version needs its own permanent URL. That means the Finnish page lives at a fixed address that can be shared, bookmarked and indexed by Google. There are three options.

• A subdirectory, for example yourcompany.ee/fi. The easiest to manage, and the whole domain's authority works in favour of every language.
• A subdomain, for example fi.yourcompany.ee. Technically more separate, but harder to manage, and Google may treat it as a separate site.
• A separate domain, for example an address ending in .fi. It looks local, but it needs its own upkeep and its authority starts from zero.

For a small or medium-sized business, a subdirectory is usually the sensible choice, because it keeps administration in one place and the existing site supports the new language version. A separate domain is worth considering when a local domain ending is an important trust signal in the target market and the plan is long term. The worst option is a language version with no address of its own, where the content simply switches at the same URL, because Google then cannot index the versions separately. Once the addresses are settled, adding hreflang is straightforward, because every version has a fixed reference.

The Finnish market and buyer expectations

Finland is the first logical additional language for many Estonian companies, because the market is close and the demand is often already there. That said, Finnish buyers have clear expectations. They are used to receiving quotes and invoices in Finnish and they expect a reply in Finnish. An English reply to a Finnish enquiry works less well than a Finnish one, even if your service is good.

Keywords need separate thought

Another misconception is that translation is enough for the search engine too. In reality, a Finnish customer searches using different words. A heading translated word for word may be linguistically correct, but not what people actually type into the search box. Before translating, it is worth checking which words are genuinely used in the target market. Pages should be built around those words. This is the same work we do for an Estonian-language site as part of our SEO service: keywords, headings and content go together.

When the sales process works in Finnish, the translation has been reviewed by a person and hreflang is in place, a Finnish-language site is an investment whose results can be measured: the number of Finnish-language enquiries, their share of the total, and how many of them reach the quote stage. If any of those pieces is missing, it is worth sorting that out before translating.

If you are weighing up a second language, the first sensible step is to review the numbers and the plan. Our prices are published openly, and through our contact page and free audit we can assess together whether a real customer is waiting in your second language, or only extra work.