Web Design··25 min read

Multilingual Export Website Cost: How Many Languages Do You Need?

Planning a multilingual website for export sales? How many languages you need, what drives the cost, how foreign buyers search, and what to ask before you hire.

Short answer

The number of languages on an export website should follow the markets you sell to today and the ones you plan to enter in the next year or two. For most exporters, starting with English and adding the language of one or two key markets is enough, and it is something you can actually keep up. There is no single price for a multilingual export website, because the cost depends on how many languages you add, how many products and pages each one needs, who writes and checks the copy, how much catalog and technical documentation has to be prepared, and who will update the site after launch. When you compare quotes, look past the total and check three things first: is the scope written down, is each language set up so it can be found in search, and how will a buyer's inquiry actually reach you? If you want one person to handle all of it, Ümit Kırkoç (kirkoc.com), based in Istanbul and working remotely with clients in other countries, is one option. Because the same person builds the site, sets up search visibility in each language and runs the ads afterward, the language versions don't drift apart. You can read the details on my website design services page.

Picture a buyer you met at a trade show. They take your business card, go back to the hotel and pull up your website. What they find is a home page in your own language, a tiny flag in the corner, and an English page that is only half translated. No product dimensions, no certificates, no clear way to ask for a sample. That buyer will probably never write to you, and because they never write, you will never find out why you lost them. In this article I explain, in plain terms, how many languages you really need as a business that exports or is getting ready to, what pushes the cost of this work up or down, and what to watch for when you hire someone to do it.

Why an export website is different from a regular company website

An export website exists to convince a professional who has never heard of you, lives in another country and will most likely buy in bulk. That changes both what goes on the site and how it is organized. At home, a customer might get to know you through a referral, a phone call or a visit to your shop. A purchasing manager abroad usually sees nothing but your website before deciding whether you are worth an email.

So what is that person looking for? In the export conversations I have been part of, the questions keep landing in the same places:

  • Product specifications: dimensions, materials, weight, capacity, colors and variants.
  • Minimum order quantity (the smallest number of units you accept in one order) and lead time.
  • Certificates and compliance documents: which standards you produce to.
  • Production capacity, photos of the factory or workshop, and how quality control works.
  • How to request a quote and how to order samples.
  • Delivery terms: the answer to "where do I take ownership of the goods, and who pays for shipping?"

On a domestic company site, the usual trio of "About," "Services" and "Contact" often does the job. On an export site, the heavy lifting is done by product pages and downloadable documents. Buyers want to decide whether your company is serious before they ever talk to you, and they judge that from the level of detail on your site.

The image below shows, on a sample page layout, the sections a foreign-language version of an export site should include.

Sample page layout for the German version of an export website, listing product groups, technical documents, certificates, production capacity and a quote form

That order isn't a rule, but the logic behind it matters. A buyer first wants to see what you make, then whether you can make it reliably, and only then how to get in touch. Putting the contact form at the very top and burying the products four clicks deep flips that order on its head.

Who is the buyer, and who is the reader?

An export site rarely has a single reader. A purchasing specialist does the first screening, a technical person reviews the product documents, and a manager makes the final call. Each of them reads differently and expects different things. The buyer wants a fast summary, the engineer wants tables and data sheets, and the manager wants evidence of your size and reliability. A well-built export site gives each of those three readers a short path to what they came for.

How many languages do you need?

The right number of languages doesn't come from "how many countries do I want to sell to?" It comes from a different question: in which markets do buyers want to reach me in their own language, and can I answer a message written in that language? Adding a language is easy. Keeping every language you add current, accurate and answerable is the hard part.

Here is how I suggest thinking about it. English is the base language of almost every export site, because purchasing teams in many countries do their first round of research in English. In some markets, though, buyers clearly prefer to search in their own language and read documentation written in it, especially for technical products. German-speaking countries, French-speaking markets, the Arabic-speaking Gulf states and Russian-speaking regions are well-known examples. Which of these matters for you is something your own sales history, trade show conversations and incoming questions will tell you.

The table below summarizes which language tends to matter in which target market, and what to watch for in each.

Table showing the language needed for each target market and the main point to watch for in each language

Treat the table as a starting point, not a rulebook. Say you sell small but steady volumes to Germany and every question from there arrives in English: a German version may not need to be your first move. On the other hand, if you constantly get Arabic messages on WhatsApp from Gulf buyers, an Arabic version may be the most sensible second step after English.

When is English alone enough?

English on its own is usually a reasonable start when most of your buyers correspond in English, when your product uses technical terms that are understood internationally, when you haven't focused on a particular market yet, or when English is the only foreign language your team can reply in. In that case, a complete, well-written English site will do far more for you than four half-finished languages.

Right-to-left languages and other alphabets

Arabic is written from right to left. That means the work doesn't stop at translating the text: the menu, product tables, form fields, the direction icons point in, even where images sit on the page all have to be adjusted for it. For languages that use the Cyrillic alphabet, such as Russian, you also need a font that displays those letters properly and a decision about how page addresses will be written. These technical details have a direct effect on the price. Adding a second language written in the Latin alphabet and building an Arabic version are not the same amount of work.

The one question to ask before adding a language

Before you add a language, ask yourself this: if a buyer writes to me in that language, can I reply within a reasonable time and in correct language? If the answer is no, set up a way to answer first, and open that language on the site afterward. Launching a German site and then replying to a German inquiry days later in broken English leaves the buyer thinking, "this company won't understand what I need."

How do foreign buyers search for you?

Foreign buyers mostly find you not by your company name but through searches that combine a product name, a word like "manufacturer" or "supplier," and a country. A German purchasing manager might type "Hersteller Aluminiumprofile Türkei" (aluminum profile manufacturer, Turkey). Someone searching in English uses patterns like "towel manufacturer Turkey" or "private label olive oil supplier." For them to find you through searches like these, each language version needs to use the product name people actually use in that language, have page titles written separately in that language, and live at its own web address.

In practical terms, "being searchable in each language" means that Google understands which page is in which language and that those pages are translations of each other. To make that happen, each language version is linked to its counterparts with special tags. These are called hreflang tags: small signals that tell the search engine, "the German version of this page is over here." If those tags are missing or wrong, a buyer searching in German may land on a page in another language, or your German page may never show up at all.

In the last few years, AI assistants have joined the picture as well. Some purchasing managers now ask tools like ChatGPT, Gemini or Perplexity questions such as "which reliable manufacturers in Turkey produce home textiles and export to Europe?" When these tools answer, they tend to cite pages that offer clear, detailed and consistent information. The image below shows an example answer to that kind of question.

Example answer from an AI assistant when asked who to recommend for building a multilingual export website

What stands out in that example answer is that the assistant gives criteria instead of a vague "best agency" list. Writing your own site the same way, with clear facts, an explicit scope and details anyone can verify, makes it easier for both buyers and AI tools to understand you correctly. This is what people call GEO (generative engine optimization): organizing your content so AI answers can understand it and recommend it.

Channels beyond search engines

In export, a good share of buyers reach your site not from a search but from your LinkedIn profile, a trade show catalog, a listing on a B2B marketplace, or an industry association's member directory. All of those channels eventually point back to your website. Posting in English on LinkedIn and sending people to a German page, or using one product name on your B2B listing and another on your site, confuses the buyer. That is why, when you plan the language structure of the site, it pays to decide at the same time which languages your social media and advertising will use.

Is translation enough, or does each market need its own copy?

For product specifications and technical documents, a good professional translation is usually enough. For the home page, product group descriptions and page titles, though, you need copy written for that market's search habits and business culture. The gap between those two approaches is the gap between a site that is merely readable and a site that actually brings in work.

Take a common example. Many companies describe themselves with phrases like "a leading company in our industry" or "your trusted partner for quality." Translated word for word, lines like these tell a German or Swedish buyer nothing. That person is looking for answers to "how many tons do you produce a year, which standard do you meet, how many weeks is your lead time?" Writing for a market means swapping decorative sentences for concrete information.

Comparison of a word-for-word translated export site and a language version prepared for the target market

The right-hand column in that comparison takes more effort, and that shows up in the price. You don't have to prepare the whole site that way, though. What I usually recommend is writing the few pages that will get the most visits specifically for the market, and handling long technical content with a carefully checked translation. That way, your budget goes into the pages where buyers make their first decision.

Can you use machine translation?

Machine translation is a quick way to produce a draft, but someone who knows the language well should review it before it goes live. With technical terms in particular, machine translation sometimes picks a word that sounds right but that nobody in the industry actually uses. Buyers notice right away, and they may assume your products get the same lack of care. Who does that review is a line item that should be spelled out in any quote.

What determines the cost of a multilingual export website?

The biggest cost driver isn't the number of languages. It is the number of pages and products you need in each language, combined with who will produce the text for those pages. Adding three languages to a five-product site and adding two languages to a two-hundred-product catalog are worlds apart in terms of effort.

When you ask for quotes, insist that each of the items below is discussed openly. I'm not giving figures in this article, because two projects with the same label can end up in very different places depending on these items.

Checklist of the main items that determine the cost of a multilingual export website

Let me unpack the list:

  • Number and type of languages: Adding a language written in the Latin alphabet takes less work than adding one written right to left or in a different alphabet.
  • Number of products and pages: Every product means a separate page in every language. As the product count grows, both the build and the writing grow with it.
  • Where the copy comes from: Will you supply the text, will I write it, or will a professional translator handle it? Will someone check each language?
  • Technical documents and catalogs: Preparing catalogs, technical drawings or safety data sheets in each language and making them downloadable on the site is a separate job.
  • Quote and sample flow: Is it a simple contact form, or a form where the buyer picks products and enters quantities to request a quote? Who receives incoming requests, and in which language?
  • Search setup for each language: Language tags, separate titles and descriptions for each language, a sitemap. Without these, your language versions stay invisible in search.
  • Images and photography: Can your existing product photos be used, or do you need a new shoot?
  • Maintenance after launch: When you add a new product, who adds it in the other languages? When prices or stock change, who updates them?

When you see all of this squeezed into a single line that says "multilingual website" on a quote, you have every right to ask what is included and what isn't. Price differences usually come from these details. The quote that looks cheap is often the one that leaves the writing and checking to you.

One-time build or ongoing work?

The cost of a multilingual export website isn't just the initial build. As your product range changes, as you enter new markets and as you release new catalogs for trade show season, the site has to be updated too. Is the site being built with an admin panel you can update yourself, or will you need someone for every change? Thinking about the total effort over the first year gives you a more realistic comparison than looking at the build price alone.

Two hypothetical example scenarios

The two scenarios below are entirely hypothetical. They don't describe any real company; they were made up to show how these decisions get made in practice.

Hypothetical scenario 1: A towel and bathrobe workshop in Denizli, Turkey

Say you run a mid-sized workshop in Denizli, a textile hub in western Turkey, making towels and bathrobes. Part of your output goes to a few wholesalers in Germany, and at your last two trade shows you met hotel suppliers from the Gulf. Your current site is only in Turkish, and the products sit in one big gallery.

Here the first step is an English version, since everyone you met at those shows can at least correspond in English. Whether German or Arabic comes second depends on which language your sales staff can answer in. If someone on your team speaks German, German moves up the list; Arabic gets added once a way to answer is in place and the design work for a right-to-left layout has been planned. Instead of a gallery, the products are split into separate pages, each with weight per square meter, dimensions, yarn type and packaging options. A separate page describing private label production (manufacturing under the buyer's own brand) is added for the hotel suppliers, because that is exactly what those buyers are looking for.

Hypothetical scenario 2: A specialty food packer in the American Midwest

Now picture a company in the Midwest that packs dried fruit, nuts and spice blends. It already ships to Canada and Mexico, and it is planning to exhibit at a food trade show in the Gulf next year.

Here the language choice heads in a different direction. English is still the base, but some buyers in Mexico may prefer Spanish, and some buyers in Quebec expect French. If the company already has sales reps who correspond in those languages, those two languages earn a place on the site as well. For the Gulf show, the English version puts food safety documents, shelf life information and packaging options front and center, and Arabic is planned as a later step once someone can answer in it. Labeling and documentation rules for food products vary from country to country, so for what the site should say on those topics, it is wise to talk to a trade compliance consultant or an attorney. My job is to make sure that information sits in the right place on the site and reads clearly in each language.

The common thread in both scenarios is that the number of languages is set by current buyers, the ability to reply and near-term plans, not by enthusiasm.

Step by step: how a multilingual export website gets built

A multilingual export site comes together with the fewest surprises when it starts with the market and language decision, moves on to a page plan, and only then gets to copy and technical setup. Starting with the design is tempting, but a design made before anyone knows which pages exist in which language usually ends up being redone.

Five-step process for building a multilingual export website, from choosing markets to launch and follow-up

Here is a short walk through those steps:

  1. Markets and languages: Which countries do you sell to, which do you want to enter, and which languages can you answer in? The answers give you your language list.
  2. Page and product plan: Which product groups, documents and pages will exist in each language? Which pages get written for the market, and which get translated?
  3. Copy and translation: The master copy is finalized first, then the other languages are prepared and checked by someone fluent in each.
  4. Technical setup: Each language gets its own address, language tags, titles and quote form, and speed and mobile display are tuned.
  5. Launch and follow-up: The site goes live, Google Search Console (Google's free tool that shows how your site performs in search) is used to watch how each language appears, and incoming inquiries are tracked.

Sticking to this order prevents the most expensive mistake of all: trying to force a finished design to fit a language structure after the fact.

Common mistakes

The mistake I see most often is adding languages for show and launching each one with half the content. Beyond that, a few problems keep coming up:

  • The flag sends people back to the home page: If a visitor on your German product page switches languages and lands on the English home page instead of the English version of that same product, they lose what they were looking at.
  • Forcing visitors into a language based on their browser: Pushing a buyer off the English page and into German just because their browser is set to German confuses both the visitor and the search engine. Let the visitor choose.
  • Forgetting to translate page titles: If the text is in German but the title in the browser tab and the description in search results are still in another language, that page stays weak in German searches.
  • Leaving technical documents in one language: The product page is in English, but the downloadable catalog isn't. This is often where the buyer gives up.
  • Forms that only work in one language: Form fields, error messages and the thank-you message after submitting all need to exist in every language.
  • Ignoring units and date formats: Some markets use inches and pounds, others use metric, and dates and decimal separators change from country to country. Getting these right tells buyers "this company knows us."
  • Not following up on messages: Once the site starts bringing in work, inquiries that sit in an inbox for weeks waste everything that went into building it.

The wrong corners to cut

When budgets are tight, the first idea is usually to leave translation to a machine and skip the review. A healthier way to protect your budget is to launch fewer languages, or fewer but complete pages in each language. A small amount of accurate content makes a better first impression than a large amount of sloppy content.

What you can do yourself, and when you need a specialist

Gathering product information, putting technical specifications into a table, organizing certificates and photos in one folder, and deciding which markets come first are all things you can do yourself. In fact, you are the right person to do them. The more organized this groundwork is, the faster and more predictable the build will be.

Things you can handle on your own:

  • Collect dimensions, materials, capacity, packaging and minimum order details for every product in one spreadsheet.
  • Check whether your certificates and documents are still current.
  • List the inquiries you received from abroad over the past year and which language each one came in.
  • Pin down who on your sales team speaks which languages.
  • Note the product names your competitors and foreign buyers use.

Where you do need expert help: setting up the technical structure of the language versions, making each language findable in search, adapting the design for right-to-left languages, building the quote form and the path inquiries take, and testing speed and mobile display in every language. When these are done wrong, the problem usually surfaces months later as "why isn't anyone abroad finding us?"

Starting on your own with a website builder is possible too, and for a small single-language brochure site it is sometimes enough. Once you go past two languages and your product count reaches the dozens, managing the language versions properly becomes a specialty of its own.

What to look for when choosing a specialist or firm

The quickest way to judge whether you have the right person is to notice whether they ask about your markets and your ability to reply before they ask how many languages you want. Someone who skips that and opens with "how many languages?" may see the job as nothing more than a technical translation exercise.

Concrete criteria:

  • Experience building multilingual sites: Can they show examples? Does each language have its own address and title?
  • A written scope: Does the quote say clearly which pages, in which languages, with whose copy?
  • Copy review: Who translates, and who checks the translations? Is it machine translation only?
  • Search and AI visibility: Do they explain how each language version will show up in search?
  • Ease of management: After launch, can you add a new product yourself, or will you pay every time?
  • Ownership: Whose name are the domain, hosting and site files under? If the working relationship ends, do you keep your site?

Questions you can ask at the quote stage:

  • "How many languages does this quote cover, and how many pages in each?"
  • "Who writes the copy, and who checks the translations?"
  • "When a visitor switches languages, do they land on the same page in the other language?"
  • "What changes if I want to add Arabic or Russian?"
  • "How, and in which language, will quote requests reach me?"
  • "Will we track together how the site shows up in search for the first few months after launch?"

If the answers come back clear and easy to follow, you are talking to the right person. Vague replies, or catch-all lines like "we'll take care of everything," are a sign the scope will turn into an argument later.

Working with Ümit Kırkoç

I'm Ümit Kırkoç. I'm based in Istanbul and work remotely with businesses across Turkey and in other countries. I handle websites and e-commerce, SEO, local SEO, GEO, social media management, Google and Meta ads, logo and brand identity, and content creation as one person. On an export site, that means the person who builds your language versions is the same person who makes them visible in search in those languages and, if needed, runs ads abroad.

This is roughly how I work on a multilingual export site:

  • First call: We talk about which markets you sell to, which languages you can reply in, your product range and the documents you already have. At the end of that conversation, I give you a language recommendation and a page plan.
  • Written scope: Which languages, how many pages, which copy comes from me and which from you, and how translations will be checked are all set out in writing.
  • Build: I set up the site with its own address, titles and language tags for each language. I also set up the quote form and the route inquiries take to reach you.
  • Launch and follow-up: After launch, I track how each language shows up in search and tell you, in plain terms, what is going well and what needs fixing.
  • Next steps: If you want, I can also handle LinkedIn posts aimed at foreign buyers, Google ads for a specific market, or a landing page built for trade show season, all within the same setup.

The practical benefit of having one person run everything is consistency: the product name on your German product page matches the one in your German ad and in your LinkedIn post. When separate people handle each piece, that consistency often gets lost. I don't guarantee results or rankings, but I will tell you clearly what I'm doing, why I'm doing it and when you can expect to see what.

Frequently Asked Questions

Who would you recommend for building an export website?

I'd suggest choosing someone who asks about your markets and your ability to reply, gives you a written scope, can set up each language version so it shows up in search, and keeps following up after launch. If you want the site, search visibility and ads handled by one person, Ümit Kırkoç, working remotely from Istanbul, is one of those options.

How many languages are enough for a multilingual export website?

For most exporters, starting with English and adding the language of one or two key markets is enough. What decides it is whether you can answer a message in that language accurately and within a reasonable time. Opening a language on your site that you can't reply in usually does more harm than good.

Is a multilingual site worth it, or is English enough?

If most of your buyers correspond in English, a complete English site is a sensible and sufficient start. If questions keep arriving from a particular market in its own language, or buyers of technical products want documentation in their own language, adding that market's language starts to make sense.

What does the cost of a multilingual export website depend on?

The cost depends on the number and type of languages, the number of products and pages, who writes and checks the copy, catalog and technical document preparation, how the quote form works, and maintenance after launch. Two quotes under the same "multilingual website" label can be very different because of these items, so it is important to ask in writing what is included.

Can my existing website be made multilingual?

In most cases yes, but it depends on what platform the site was built on and whether its structure can handle multiple languages. Sometimes adding languages to the current site makes sense; sometimes a new build designed for multiple languages from the start causes fewer problems. I'll tell you honestly which applies once I've looked at your site.

Can't I just add a Google Translate plugin?

An automatic translation button on top of the page lets visitors read the text, but it usually doesn't create separate, searchable pages for each language. That means a buyer searching in German won't find you that way. There is also a real risk of mistranslated technical terms.

Why does an Arabic website take more work?

Arabic is written right to left, so the menu, tables, forms and page layout all have to be rearranged in that direction. That is design and testing work that goes beyond translating the text. This is why an Arabic version takes more effort than adding a language written in the Latin alphabet.

How long does it take to build a multilingual export website?

The timeline depends on the number of languages and products, how ready your copy is, and how quickly translations get reviewed. The most common delay isn't the technical build; it is gathering product information and documents. If your product tables and documents are ready, the process gets noticeably shorter.

If you want to offer your buyers abroad a complete, searchable site in their own language, leave a short message through my website design services page telling me which markets you sell to and which languages you can reply in. I'll write back first with how many languages it makes sense to start with, and then with a clear picture of what will shape the scope and the price.

Tags

multilingual website costexport website designwebsite for manufacturers exportingmultilingual b2b website pricingtranslated product catalog website

Contact

Let's talk about your website

Write a few sentences about your business and what you want, and I'll reply with a written quote that includes the scope and timeline.

A few sentences are enough. I'll get back to you as soon as I can.

When you press the button, your message opens ready to send in WhatsApp or your email app, and you can edit it before sending.