"Should the site be in English too?" is one of the first questions I hear when a business owner in Bulgaria asks me for a quote — and one of the few where the honest answer really is "it depends". For a guest house in Veliko Tarnovo, a dental clinic that treats patients from Greece, or a workshop that ships to Romania and Germany, a second language can be the difference between an enquiry and a closed tab. For a hair salon whose clients all live within three kilometres, it is usually money better spent on photos and a faster booking form. Here is how I help clients decide, what a proper multilingual site involves, and what to check before you pay for one.
Who actually needs a second language?
Start with your customers, not with the website. Look at the last 50 enquiries, bookings or orders and ask: how many came from people who don't read Bulgarian comfortably? If the answer is "almost none" and your growth plan doesn't change that, a single-language site is fine — you can always add a language later if the site is built properly.
A second (or third) language usually pays off for these businesses:
Tourism & hospitality
Hotels, guest houses, tours, wineries, restaurants in resort towns. Foreign guests research and book before they arrive.
Exporters & B2B
Manufacturers, workshops and suppliers selling to buyers in other EU countries, where the website is the first due-diligence check.
Online shops shipping abroad
If you deliver to Romania, Greece or Germany, shoppers there expect product pages, prices and returns information they can read.
Clinics & services for foreigners
Dental and medical tourism, language schools, legal and accounting services for expats and foreign-owned companies.
What the numbers say
The research on this is consistent: people prefer to buy in their own language. In CSA Research's 2020 "Can't Read, Won't Buy" survey of 8,709 online shoppers in 29 countries, a clear majority preferred product information in their native language, and a large share said they never buy from sites in other languages. Germany, one of the biggest markets for Bulgarian exporters, was the strictest of all.
That last number matters if you are in tourism: more than six million holiday visits from abroad in 2025, up about 4% on 2024. Many of those visitors search, compare and book on their phones — in English, German, Romanian or Greek — long before they reach your door.
"Just add Google Translate" — why that rarely works
The cheapest option is a translate widget that machine-translates the page in the visitor's browser. It feels like a shortcut, but it has real limits:
- Google doesn't index it as a separate version. Search engines see your Bulgarian page, so you won't appear when someone in Vienna searches in German.
- Mistakes land on your brand. Menus, prices, legal terms and medical or technical vocabulary are exactly where machine translation slips.
- Forms, emails and checkout often stay in Bulgarian. The visitor reads a translated homepage, then hits a confirmation email they can't understand.
A translate button in the footer, one Bulgarian URL for everything, English-speaking visitors landing on Bulgarian contact forms and Bulgarian order emails.
A real version per language with its own URLs (e.g. /en/ and /bg/), translated menus, forms, emails and legal pages, and a visible language switch that takes you to the same page in the other language.

How a proper multilingual site is built
I build bilingual sites the same way this journal is built: every page exists in each language at its own address, and the two versions point to each other. This is what Google's own documentation describes for localized versions — "hreflang" annotations that tell search engines which page is the English version and which is the Bulgarian one. A few details that make a real difference:
- Separate URLs per language — a folder such as /en/ or /bg/, so each version can be indexed and ranked on its own.
- hreflang done correctly — every version lists itself and all others, and the links point back to each other. Google notes that if they don't, the annotations may be ignored.
- Translated slugs and metadata — page titles, descriptions and image alt texts in the right language, not just the visible copy.
- No forced redirects by IP — let people choose. A Bulgarian living in Munich may want the Bulgarian site; a tourist in Sofia may want English.
- Every touchpoint translated — contact forms, error messages, confirmation emails, cookie banner, privacy policy and (for shops) terms and returns.
Translation: who writes the second language?
This is where most multilingual projects slip. The design and code are rarely the bottleneck — the text is. You have three realistic options:
- Professional translator or native speaker. Best for shops, clinics and anything with legal or technical language. Budget for it separately from the website.
- Machine translation, then human review. A sensible middle ground for small sites: draft with a translation tool, then have a fluent speaker edit the result, especially headlines, calls to action and prices.
- Write it natively. If your English-speaking customers have different questions (parking, payment by card, arrival times), write a slightly different page for them rather than translating word for word.
A tip from projects I've delivered: translate fewer pages, but translate them fully. A five-page English version that answers the questions foreign customers actually ask beats a 40-page version where half the text is still in Bulgarian.

What it does to cost and timeline
A second language is not a 2× price tag, but it isn't free either. Design is shared; what grows is setup (language structure, switch, hreflang, translated forms and emails), content entry, testing, and later maintenance — every new page or offer now needs to go up twice.
My websites start from €890, go live in 2–5 weeks and include 3 months of free care. When a client needs a second language, I price it as a clear separate line in the quote, depending on the number of pages and whether you supply the translation, so you can see exactly what the extra language costs and decide with real numbers. The timeline usually depends more on when the translated text is ready than on the build itself.
Translate fewer pages, but translate them fully.— a rule I use on every bilingual project
Checklist: decide in 20 minutes
- Count how many of your last 50 enquiries or orders came from people who don't read Bulgarian.
- Check Google Analytics or Search Console: which countries and browser languages do your visitors come from?
- List the 3–6 pages a foreign customer really needs (homepage, services or rooms, prices, contact, terms).
- Decide who will write or review the translation — and when it will be ready.
- Make sure forms, emails and legal pages will exist in every language you add.
- Ask your web designer how the site handles hreflang, URLs and the language switch — before you sign.
Next step
If you already have a site and you're wondering whether it's ready for foreign visitors, run the free website check — it takes a minute and shows speed, mobile and SEO basics you'd want fixed before adding a language. If you're planning a new bilingual site for your business, have a look at how I work on web design for small businesses, or read more about working with a web designer in Bulgaria if you're based elsewhere in the EU. I'm happy to tell you honestly whether a second language is worth it for you — sometimes the answer is "not yet".
