Multilingual website in 2026: what it costs and how to structure languages for Google

What does each extra language cost?

Budget each language as three lines that fall due at different times. Translation is paid per word, and again for every word you change later. Set-up is paid once: the extra pages, their titles, the switcher and the hreflang tags. Upkeep never stops: every new service or price change needs a translated twin, or the editions drift apart.

Worked example: a service site holding 3,000 words costs $90–$360 per language with post-edited machine translation and $300–$900 with professional translators. Transphere's own case, a 2,000-word site in five languages, totals about $2,600 with engineering, testing and project management, roughly $525 per language. Its list also shows the pair matters: $0.10 a word from English into Spanish, $0.16 into Japanese.

Quotes also move with the number of page templates, translated URL slugs, right-to-left scripts such as Arabic that mirror the layout, and booking or payment tools that must work in every language.

Subfolders, subdomains or country domains: which structure fits?

Google's first rule is simple: give every language version its own URL, rather than switching the language by cookie or browser setting. After that you pick one of three structures.

Subfolders usually win: one domain gathers every link and one release ships every language. Our projects use them. SB Excursions keeps each language in a folder such as /bali/ru/, and viton13.com serves English at the root and other editions under /ru, /es, /fr and /hi; its subdomains split company sections, not languages. Language and country are separate choices too: one Spanish edition can serve Spain and Mexico until prices or delivery differ.

What must hreflang and the language switcher get right?

Hreflang tags tell search engines which pages translate each other, so a French searcher lands on the French page. Google reads them in the page head, an HTTP header or the sitemap. The rules that break most often:

• Return links: each edition lists itself and all the others; a one-way pair may be ignored.
• Full addresses with https:// and the domain, never relative paths.
• Codes: ISO 639-1 for the language (fr), optionally an ISO 3166-1 region (fr-CA).
• x-default: one fallback page for visitors whose language you do not serve.
• Closed editions: a noindex page stays out of the set; our technical SEO audit checklist covers this.
• Yandex reads hreflang in the page head but no longer from sitemaps, so keep the tags in the HTML if Russian-language search matters.

Hreflang does not set a page's language: Google detects it with its own algorithms, so a French URL with English body text counts as English. The switcher should open the same page in the other language, not the home page, and Google advises against redirecting visitors to another language automatically.

Machine translation or a human translator: where is each enough?

• Home page, service pages, prices and forms: a human translator, or thorough post-editing by a native speaker. These pages sell.
• Terms, privacy notice and refund rules: a professional translator, plus a local lawyer where the law differs.
• Blog posts and help articles: post-edited machine translation, with a native reader for anything that ranks.
• Reviews and user messages: raw machine output, labelled as automatic.

Search needs more than translation. People in each market type their own phrases, often not the literal rendering of your English headline, so check local search terms before translating titles.

Google's spam policies count translating scraped content into pages at scale as abuse; your own text is not scraped, yet unreviewed bulk output adds little for readers. We apply the same caution at home: Spanish and French editions of newer VITON¹³ service pages written by AI agents stay noindex, outside the sitemap and the hreflang set, until a native speaker reviews them. Hindi service pages wait for that review too.

What does each language need before it goes live?

A translated page is not yet a working edition. Check that a customer can finish the whole journey in it:

• Prices in a currency that market understands, or one currency stated plainly everywhere.
• An enquiry form whose messages reach someone who can reply in that language.
• The contact channel that market actually uses, with the time zone of whoever answers.
• Privacy notice, terms and refund rules translated and checked. France, for example, requires French for the offer and description of goods and services sold to its consumers, sales websites included.
• Dates, numbers, addresses and phone numbers in local formats.
• A translated title, description and alt text on every page, and the edition's URLs in the sitemap.

SB Excursions takes the simplest route: tour prices stay in US dollars and every edition sends enquiries to one WhatsApp number. A shop selling into several countries usually needs local currency and delivery terms per market.

What does VITON¹³ charge for a multilingual build?

Our prices are published, and a multilingual site is assembled from the same parts. The business website package covers one language edition; each further language is priced in the written estimate before work starts.

The cheapest order is usually: markets and structure first, then the first language built with that structure, then one language at a time as each market proves itself. AI-assisted means AI drafts and a developer reviews every page before sign-off; human-led means a specialist builds by hand with AI as a helper. For the business website that is $113 against $173.

When is a multilingual site the wrong investment?

• Nobody on your side can answer an enquiry in that language or deliver the service there.
• There is no sign of demand yet; one landing page in the language is a cheaper test.
• Content changes daily and nobody is budgeted to keep translations current.
• That market buys through marketplaces or partners, where a local listing reaches buyers sooner.