A multilingual website in Finland starts with a decision, not a plugin
A multilingual website in Finland works when each language has its own address, its own content and its own owner. Everything else is detail. The decision that matters is which languages you commit to keeping current, and it is a decision about staff time rather than about software.
Two languages maintained properly beat four languages where two of them are eighteen months out of date. The stale ones are not neutral. A Swedish page quoting a service you stopped offering costs you a customer and a small piece of your reputation.
So before anyone talks about plugins, answer one question. When the price list changes on a Tuesday, who updates each language, and by when.
Which languages you actually need
Start from who buys from you, not from who lives here. A B2B supplier selling to industrial buyers across the country may genuinely need only Finnish and English. A restaurant in the Helsinki city centre needs English long before it needs Swedish. A public sector supplier may need Swedish before it needs anything else.
The general case in Finland is worth knowing. Statistics Finland reported 610,148 people in the population with a foreign language as their native language at the end of 2024, which is 10.8 per cent, and the figure has been climbing every year. Many of them work, buy and search in English.
Then there is the question nobody asks. If you add a language, who answers the phone in it. A Swedish page that produces a Swedish enquiry answered in Finnish is worse than no Swedish page.
Swedish is not optional everywhere
Swedish is a national language, and in parts of the country it is the working language of daily business. Ostrobothnia, the coast around Vaasa and Jakobstad, large parts of the Turku archipelago and a belt of municipalities along the southern coast all have populations where Swedish is the first choice.
If you sell into those areas, a Swedish version is a commercial argument rather than a courtesy. Local buyers notice who bothered, and the competitors who did not.
If you sell nationally from Tampere to other companies, Swedish may add very little, and the effort is better spent making the Finnish and English versions genuinely good. Decide on the map, not on principle.
One address per language
Every language needs a URL you can send to someone. That means example.fi/en/services/ and example.fi/sv/tjanster/ as real pages, not one page that switches text depending on a cookie or a browser setting.
Three things depend on this. Search engines can only index a page that has an address. A customer can only share a link that stays in the language they were reading. And you can only measure which language earns anything if the analytics has separate paths to count.
Subfolders under one domain are the sensible default for a Finnish company, because the whole site inherits one reputation and one certificate. Separate domains per language make sense only when the businesses behind them are genuinely separate.
Never redirect people automatically by their browser language. A Finn in a hotel in Berlin with an English laptop should still reach the page they clicked.
The language switcher people actually use
Put it where people look, which is the top right on a desktop screen and inside the menu on a phone. Label each language in its own language, so Suomi, English and Svenska rather than a translated list.
Flags cause more trouble than they solve. English is not a British flag to a reader in Helsinki, and Swedish shown with a Swedish flag annoys the Finnish speakers of Swedish it is aimed at. Words are shorter and clearer.
The switcher should land on the same page in the other language. Dropping everyone onto the front page is the single most common mistake, and it costs you the reader who was two clicks from a booking.
Machine translation and why it backfires
Machine translation is a fine first draft and a poor published page. The grammar is usually right, which is exactly why the failures are hard to spot from the outside.
It breaks on the words that carry money. Service names, industry terms and legal phrases come out as literal translations that no Finnish buyer searches for, so the page is invisible in exactly the search that should have found it. It also flattens tone, and a translated page often reads like a brochure from a much larger, much blander company.
The compromise that works is a machine draft edited by someone who speaks the language and knows your trade. That is cheaper than translating from scratch and it removes the two failures that matter, the wrong terminology and the wooden tone. What it does not remove is the need to check the forms, the buttons and the error messages, which translation tools routinely miss.
hreflang without breaking it
Hreflang tells a search engine that three pages are the same page in different languages. Done right it stops the wrong version showing to the wrong reader. Done wrong it does nothing, silently.
The rules that catch people out are few. Every page in the set must list every other page in the set, including itself. The codes are language first, so fi, en and sv, with a region added only when you genuinely serve different regions in the same language. The URLs in the tags must be absolute and must be the exact addresses that load, with no redirects in between.
Add one x-default pointing at the version you want shown to everyone else. Then check it, because a single wrong tag on a template breaks the whole set across the site.
What has to be translated and what does not
Translate everything a buying customer reads on the way to contacting you. Services, prices, the process, the contact page, the booking flow, the delivery and returns terms.
You can usually leave the blog in one language, at least at first. Articles are the most expensive content to keep in step and the least likely to be the reason someone buys. Pick the language your readers search in and write there properly.
Some things have to exist in the local language whatever you decide. Anything a Finnish customer needs in order to understand what they are agreeing to belongs in Finnish, and if you sell to consumers that includes the terms, the cancellation rules and the privacy notice.
Forms, buttons and the small print
The interface is where half translated sites reveal themselves. A form with English labels and a Finnish submit button, a date picker starting on Sunday, a validation message in the wrong language, a confirmation email that arrives in the language the developer speaks.
Walk the whole path in each language before launch. Fill the form in badly on purpose, so you see every error message. Complete it properly, so you see the thank you page and the email that follows.
Watch the address field in particular. A form that demands a postcode in a foreign format, or refuses names with a and o carrying umlauts, turns away exactly the customers you built the page for.
Keeping three versions in step
Decide the source language and write there first, always. Without that rule you end up with three pages that each drifted in a different direction and no way to tell which is correct.
Then make the gap visible. A page that has changed in Finnish and not yet in Swedish should be flagged somewhere a human sees, rather than discovered by a customer. A simple light CMS can show which translations are behind, which is the difference between a system that stays current and one that decays quietly.
Give each language an owner by name. Shared responsibility for translation means no responsibility, and the version that nobody owns is always the one that goes stale.
Search behaves differently in each language
Do the keyword work separately per language. A direct translation of your best Finnish search term is frequently not what English speakers type, and the reverse is even more true, because Finnish compounds words in ways that change the search entirely.
Expect different volumes and different competition. The English version of a page may rank quickly against thin competition, while the Finnish version fights every local company in the sector. That is a reason to publish both, not a reason to skip one.
Our note on getting found on Google in Finland in English goes through what changes when the site is not in Finnish, including the Finnish terms you still have to cover.
Currency, dates and the details that read as foreign
Write dates the way each reader writes them, keep the euro the euro, and format phone numbers so they can be tapped from a phone anywhere.
Small signals of belonging matter more than they should. An English page that says a price is fifty euros plus VAT, written the way a Finnish invoice writes it, reads as local. The same page with a comma in the wrong place reads as a translation, and translations get trusted less.
Check the language attribute on each page too. It is one line in the code, it tells screen readers which voice to use, and it is wrong on a surprising number of multilingual sites.
What it costs to add a language
Four things drive the cost. The number of pages, the amount of interface text beyond the pages, whether the translation is drafted by machine and edited or written from scratch, and how much of it needs a specialist who understands your trade.
The build itself is usually the smaller half. Adding a second language to a site designed for it is routine. Adding one to a site built for a single language can mean rebuilding the navigation, the templates and the URL structure, which is why the question belongs in the first conversation rather than the second year.
The recurring cost is the honest one. Every language multiplies every future edit, so a site with three languages is three times the upkeep on content, forever. Our multilingual page describes how we set that up so the recurring part stays manageable.
A sensible order to do this in
Launch the main language complete, then add the second language as a smaller set of pages that covers the whole buying path. Ten good pages in Swedish beat a full site translated badly.
Watch what the second language does for three months before adding a third. Search Console will tell you whether anyone arrives, and your inbox will tell you whether they were worth having.
Then widen the language that is working and let the other one wait. Most Finnish companies that end up with a genuinely useful three language site got there in that order rather than all at once.