Does your small business need a multilingual website? A guide

Adding a second language to your website sounds like an obvious win: more people can read it, so more people can buy from you. Sometimes that is how it works out. Just as often it doubles your maintenance for a handful of visitors who would have managed in English anyway. This guide explains when a multilingual website genuinely pays off for a small business, what it really costs, how the technical side fits together, and how to do it without damaging your Google rankings.

When a second language pays off, and when it does not

The question is not “could someone who speaks another language visit my site?” It is “do I have customers who search, read and buy in that language?”

Three cases where it clearly pays

• Customers who search in that language. If people type queries in French, Polish or Welsh to find what you sell, an English-only site is invisible to them.
• A market you actually ship to or serve. An online shop that posts to France, or a service business with a partner abroad, has a real audience on the other side of the language.
• A bilingual local community. A salon, clinic or tradesperson in an area with a large community living in another language can win customers simply by being the one business that speaks to them. That applies in Wales as much as in parts of London.

Our running example is MxR Racing, a motocross apparel store based in France that we host and manage. It sells to French riders at home and to English-speaking riders elsewhere. Both groups search in their own language and both need to understand sizing and returns before they order. A bilingual store was the right call, and the decision was easy because the second audience already existed.

Four cases where it does not

Be honest about these, because they are more common.

• “It would look more professional.” A half-translated site looks less professional than a good English one.
• A few overseas enquiries a year. If people already find you and write in English, they can use your site. Reply well and move on.
• You are not set up to serve them. A French page leading to a form answered only in English, or a shop that cannot ship to France, generates frustration rather than sales.
• You cannot keep it updated. Every new page, product and offer will need translating. If that will slip, the second language will decay in front of your customers.

If you are unsure, look at the evidence you already have. Google Search Console shows which countries and queries bring you visitors; your inbox shows which languages people write in. If neither shows a second language, you do not need one yet.

The real cost of a multilingual website

The technical part is the smaller cost. The ongoing part is where businesses get caught out.

Translation by a human, not just a plugin

Machine translation is fine for filling gaps. It is not fine for the pages that do the selling. Product descriptions, your about page, your returns policy and your calls to action need to read as if a native speaker wrote them, because customers notice when they do not, and trust you less for it. For MxR Racing the French copy comes from the business itself, which is the ideal position: the people who know the products write about them in their own language, and the English version is checked rather than guessed.

Budget for a translator or a fluent colleague for your core pages, and treat machine translation as a draft.

Every new page needs translating

The day the site launches, both languages are complete. Three months later you add a service, change your prices and write two blog posts, and the French site is behind. Either you translate everything as you go, or you accept that the second language will always be a slightly stale copy. There is no third option.

Maintenance roughly doubles

Updating product details, fixing a typo, changing opening hours: all of it happens twice, and forms, confirmation emails and error messages need both versions too. It adds up, which is why we would rather build a tight bilingual site of eight pages than a sprawling one of thirty where half the French pages are never looked at again.

Structure options, explained simply

Once you have decided to go ahead, the structure matters more than the design.

Separate URLs for each language

Every page in each language needs its own address. The usual choices are:

For nearly everyone we work with, a folder is the right answer: one domain, one hosting account, one SSL certificate and one set of search-engine authority. What you should never do is put both languages on the same page, or switch languages with a cookie that keeps the same address. Google needs a distinct URL for each version or it will only ever index one.

A language switcher

A visible link in the header, usually “EN | FR”, that takes the visitor to the same page in the other language, not back to the home page. Use the language’s own name (“Français”, not “French”). Do not redirect visitors automatically based on location; a British rider in France still wants the English version, and automatic redirects confuse Google’s crawler too.

Hreflang tags

Small tags in the page code that tell Google “this page is English, and the French version lives at this address”. They are what make Google show the French page to a French searcher. Every page needs them, in both directions. A plugin or a well-built template handles this; ask your developer to confirm it is in place, because it is the piece most often missed on cheap multilingual builds.

What to translate first

You do not have to do everything at once. Translate in the order a customer actually needs things.

1. The pages that sell. Home page, main service or product pages, pricing. These are what a new visitor reads before deciding whether to trust you.
2. The pages that remove doubt. About, contact, delivery and returns, FAQs. For a shop like MxR Racing, the sizing guide and returns policy matter as much as the product pages, because a rider will not order boots in a size they cannot check.
3. The transactional bits. Forms, button labels, checkout text, confirmation emails. Easy to forget, and jarring when they switch language mid-order.
4. Legal pages. Privacy policy and terms. Get these checked, because they carry obligations.
5. Blog posts, last, and only those that matter in that market.

How it affects SEO

Done well, a second language reaches a whole new set of search results without competing harder for the ones you already have. Done badly, it can hurt the rankings you had.

• Each language ranks separately. Your French pages compete in French results against French sites. They need their own keyword research, because the phrase people actually type is often not the dictionary translation.
• Translated titles and meta descriptions. Every page needs its own, in the right language. English titles on French pages waste the whole effort.
• No duplicate content problems, if hreflang is right. Google does not penalise you for the same content in two languages. It will, however, pick one version to show if you have not told it which is which.
• Local signals. If you serve a specific country, a Google Business Profile there, local listings and reviews in that language all help. Our SEO service covers UK and overseas audiences.
• Speed still matters. Multilingual plugins can add weight to every page. Keep an eye on Core Web Vitals after you add a language, especially if your overseas visitors are on mobile.

WordPress plugins versus a hand-built bilingual site

There are two sensible ways to build this, and the right one depends on how often the site changes.

WordPress with a multilingual plugin

Plugins such as WPML, Polylang and TranslatePress add language management to WordPress. You write a page in English, create its French twin, and the plugin handles the URLs, the switcher and the hreflang tags. For WooCommerce stores they also handle products, categories and, with care, the checkout.

The upside is that you can publish new content without a developer. The downside is complexity: an extra plugin touching every page, licence fees for the better ones, occasional conflicts, and more care needed with every WordPress update. It is the right choice for a site that changes often, such as a shop with a growing range.

A hand-built bilingual site

For a smaller site that changes rarely (a trades business, a clinic, a consultancy) we would rather build the two languages directly: a shared template, a folder for each language, the switcher and hreflang written into the code. There is no plugin to update and the pages are fast because nothing is translating on every request. The trade-off is that adding a page means asking us, which is fine a few times a year and a nuisance weekly. Our post on WordPress versus a custom website covers the general trade-off; the multilingual question follows the same logic.

A short checklist

Before you commit, make sure you can tick these.

• You have evidence of customers who search or write in the second language.
• You can serve them in that language, and ship or travel to where they are.
• A fluent human will translate or check the pages that sell.
• You have agreed who translates new content, and when.
• Each language has its own URLs, ideally in a folder such as /fr/.
• A language switcher links to the same page in the other language, with no automatic redirects.
• Hreflang tags are present and correct on every page.
• Titles, meta descriptions, forms, emails and legal pages are translated too.
• Page speed is still good after adding the language.

Where to start

Start with the evidence, not the build. Spend half an hour in Search Console and your inbox and decide whether a second language is a real audience or a nice idea. If it is real, get the structure right first: it is cheap at the start and expensive to fix later.

We build and host bilingual sites for businesses in the UK and abroad, including e-commerce stores like MxR Racing, and we work remotely with international clients as a matter of course. If you would like a straight answer on whether your business needs a second language and what it would cost, get in touch for a free 20-minute scoping call. We reply to every enquiry within one working day, and build prices are on our pricing page.