A multilingual website is genuinely necessary only when there's real demand from foreign customers β you export goods, you operate in a tourist destination, or you regularly serve foreign patients or clients. Adding a second language just to 'look more professional' often costs you money and hurts your SEO instead of helping it. This distinction might look like a small detail, but it directly affects your annual budget and how your site performs on Google.
In consulting conversations, we hear one request constantly: 'Let's add English too, since people from abroad might check us out.' The instinct is understandable, but the cost is far higher than most business owners expect β because adding a language isn't a one-time translation job; it means that language needs upkeep with every single update for the rest of the site's life. In this article, we cover the real demand signals, the true cost of the 'just in case' reflex, the SEO damage machine translation causes, and what a properly built setup should look like.
What Are the Real Demand Signals for a Multilingual Site?
There are three concrete signals that show a business genuinely needs a second language; if none of them apply to you, a multilingual site is probably a premature investment.
You Export Products or Services
If you sell β or aim to sell β your product or service abroad, a site in the target market's language (often paired with a country-specific domain extension or subdirectory) is a real business tool. Language choice here isn't random; it follows the target market: a manufacturer exporting to Germany should prioritize German, not English. The assumption that 'everyone understands English' ignores the fact that your real audience searches in its own language.
You Operate in a Tourist Destination
For a restaurant, hotel, or tour operator in a touristic area β think coastal resort towns or a historic city center β foreign visitors are already walking through the door. The site's job is to inform that visitor before they book. Here, a second language isn't a luxury; it's part of daily operations.
You Serve Foreign Patients or Clients
For a clinic that accepts international patients through medical tourism, or a service business that regularly gets inquiries from abroad, a second language is how you build trust and set the right expectations before treatment or service begins. Here too, language choice should match the target country β not just English, but often the language of the country most patients actually come from (Arabic, Russian, and so on), which frequently converts better than English.
If none of these three signals apply β meaning your customers are effectively local, speaking your own language β a second language becomes an investment that reaches a tiny fraction of your visitors while doubling your maintenance burden.
What Does the 'Let's Add English Too' Reflex Really Cost?
This cost doesn't end with translation β it starts there. Moving a corporate site into a second language means every update for the rest of the site's life doubles in effort: every new service you add, every price change, every blog post you publish has to be updated in the second language too β or you accept living with an outdated second-language page.
Here's a concrete example: professional translation for a 15-page corporate site typically adds $150-400 per page in extra cost (at 2026 rates, depending on page length and technical complexity) β roughly $2,250-6,000 as an initial investment. But the real ongoing cost is maintenance: for a business publishing 10-15 content updates a year, keeping the second language current through an agency runs a few thousand dollars annually β and these updates are often neglected, leaving a site where 'the English version is stuck two years in the past' while the original language stays current. That impression is worse than having no second language at all: visitors read it as an abandoned site.
What Damage Does Machine-Translated Content Do to SEO?
Pages mass-produced with automatic translation tools risk being flagged by Google's quality systems as low-value, non-original content β and that doesn't just hurt those pages, it can drag down the site's overall trust signal. The reason is simple: machine translation may be grammatically correct, but it fails to capture the real search habits, local phrasing, and cultural context of the target language. The result reads technically fine but matches no real search query β text that 'sounds like nobody actually wrote it.'
The practical consequence: your English pages barely show up on Google.com or the target country's version of Google, because competitors in that language have produced real, human-written content matched to local search behavior. In other words, a second language added through machine translation often brings no traffic while dragging down the site's overall quality signal. We cover the technical infrastructure needed for a multilingual site to send the right signals to search engines (like hreflang tags) in detail in our multilingual SEO and hreflang guide.
What Does a Proper Setup Look Like?
If at least one real demand signal applies to you, a multilingual site should be built on three principles:
- Each language should live on its own URL. Instead of swapping content on the same page with a language toggle, each language needs its own address (like /en/ or a separate domain). This lets Google index each language separately and lets users share a link directly to the right language.
- hreflang tags must be set up correctly. These technical tags tell Google 'the German version of this page lives at this address,' preventing the wrong-language page from ranking in the wrong country.
- Translation should be done by a professional who knows the industry. Especially for healthcare, legal, and technical product descriptions, having someone who understands the field review the translation β instead of relying on machine translation β makes a real difference for both trust and SEO.
Once these three principles come together, the second language stops being decoration and becomes a genuine, healthy door into a real market. A properly built multilingual structure requires a more complex web design and development process than a single-language site; the information architecture and content planning should follow the same principles we cover in how a corporate website should be built. That's why it's worth weighing the three signals above together with the maintenance burden before deciding.
4 Questions to Ask Before You Decide
Before you decide whether to invest in a second language, ask yourself these four questions in order β your answers to the first two will usually settle most of the decision. These questions are essentially a language-specific extension of our questions to ask before building a website list.
- How many foreign customer or patient inquiries did you get in the last 12 months? If you don't have this number handy, you're probably not tracking it β which is itself a signal: real demand usually shows up clearly by phone, WhatsApp, or in person.
- Which country are they coming from? If the answer is 'mixed, from everywhere,' English is a reasonable first step. If it's concentrated in one country (Germany, Russia, the Gulf states), the right investment is that country's language directly, not English β English often doesn't reduce the need for a second language here, it doubles the cost.
- Who will update the content, and how often? If your answer is 'I don't know' or 'now and then,' the second-language page will likely go stale within a few months. If update responsibility isn't clearly assigned, delaying the investment is usually the smarter call.
- Is annual maintenance budgeted for? Covering the initial translation cost is easy; the real question is whether year two and three's maintenance cost is already written into the budget. If it isn't, the second language quietly gets abandoned by the end of year one.
If you can't answer at least two of these four questions positively, postponing the multilingual site and focusing instead on building a stronger, deeper single-language site β then adding the second language once real demand is clear β is usually the healthier order for most businesses. Take a law firm as an example: for a firm that gets one or two foreign client inquiries a year, an English page risks looking outdated rather than adding visibility, unless it's properly translated and regularly updated β whereas for a firm that works with a foreign client portfolio most of the year, this investment is necessary from day one.
A Phased Rollout: You Don't Have to Translate Everything at Once
Building a multilingual site doesn't have to mean 'translate every page completely'; a phased approach reduces both risk and upfront cost. A clinic that's just starting to accept foreign patients, for example, can publish only the homepage, a services summary, and a contact page in the second language first, then add treatment detail pages one by one as demand grows. The advantage of this approach is that the maintenance burden grows gradually too β a five-page second language is far easier to keep current than a fifty-page one.
A similar sequence works for an exporting company: start with an English (or target-market-language) summary of the product catalog, then add technical documents and certification pages as demand appears. This builds a structure that grows with real demand instead of an all-or-nothing decision β making both the budget and the content team's workload far more predictable.
Another advantage of a phased rollout is that you move forward by measuring what actually gets interest. After publishing the first few pages in the second language, check your analytics to see which pages get visits and which barely get viewed; this data shows you far more reliably than guesswork which pages are worth translating next.
One last note: when adding a second language, revisit your design and site structure too. Languages like German and French typically run 20-30% longer than English text; if menu widths and buttons aren't planned with that in mind, the second-language site can look visually broken. This might seem like a small detail, but it directly affects the trust a foreign visitor forms on first impression.
Summary
Only invest in a second language when there's a concrete signal β export, a tourist location, or foreign patients or clients. The 'just in case' reflex carries a permanent maintenance burden far larger than the translation cost, plus the SEO risk of machine translation. The right question when deciding isn't 'how many languages should the site have,' but 'which language's real customer demand am I meeting.' If you've seen the right signals, delaying the investment is a missed opportunity; if you haven't, an early investment usually turns into a neglected, trust-damaging burden.
If you'd like to work out together whether your site genuinely needs a multilingual structure, the Welda team can put together a concrete picture for you. Get in touch for a free initial consultation.