Bilingual business websites: when Romanian and English are worth it

Adding English to a Romanian business website can open a real customer journey—or create a second, neglected copy of the site. The difference is not the language switcher. It is whether an identifiable audience needs the English version and whether the business can maintain the complete experience.

A bilingual site is worthwhile when it removes a genuine barrier: international guests reserving a restaurant, foreign residents choosing a clinic, multinational teams evaluating a supplier, tourists planning a visit, donors reviewing an organisation, or candidates considering an employer.

It is less useful when English is added only because it seems prestigious. Translation increases content, review, technical, legal, and operational work. The investment needs a job.

Start with the English-speaking customer

Define who they are and what decision they need to make. “Foreigners” is not a useful audience description. A visitor planning dinner from another country needs different information from an English-speaking resident seeking long-term healthcare or an international company procuring professional services.

Document:

• where the person is located when searching;
• what language they use in search and conversation;
• which services are actually available to them;
• which prices, taxes, delivery areas, or conditions differ;
• who can answer in English;
• what action completes the journey;
• which expectations require clarification.

The English version should not promise support the operation cannot provide. If appointments are available in English only on certain days, say so. If the service is Romania-only, explain the geographic limit before the enquiry.

Decide whether every page needs translation

A complete parallel website is appropriate when both audiences use the same core offer and need equivalent information. Every important Romanian page receives a maintained English counterpart.

A smaller English section may be better when international visitors need only a defined journey: venue information, selected services, investor material, an event, or contact. Translate the pages required to complete that journey, not random highlights.

Avoid a language switcher that leads to one English homepage while every deeper link returns to Romanian. Also avoid translating only marketing headlines while forms, errors, confirmations, policies, booking screens, and email responses remain in the source language.

Translation is not just word replacement

Good localization preserves meaning and adjusts context. It may need to explain Romanian institutions, qualifications, addresses, taxes, measurement units, reservation practices, or legal terminology. Calls to action also change: “Solicită o ofertă” may be “Request a proposal,” “Ask for an estimate,” or “Discuss your project,” depending on the actual process.

Begin with approved Romanian content. Give the translator a terminology list, audience description, page purpose, brand voice, and screenshots. Review the English version in layout rather than only in a spreadsheet, because headings, cards, buttons, and mobile screens have real space limits.

Use a qualified specialist for legal, medical, financial, or other high-risk content. Machine translation can accelerate a draft, but a responsible person must approve the meaning and keep later changes aligned.

Use separate URLs for each language

Each language version needs a stable, crawlable address, such as:

• example.ro/ro/servicii
• example.ro/en/services

Google recommends different URLs for language versions rather than changing all content through cookies or browser settings. Separate URLs can be linked, indexed, shared, measured, and debugged independently.

The path should reflect the language naturally. Translate descriptive slugs when useful, but keep a mapping between counterparts so the language switcher moves to the equivalent page, not always to the homepage.

Connect equivalents with hreflang

hreflang annotations help search engines understand which URLs are language or regional alternatives. Each page should reference itself and its counterparts, and the relationships must be reciprocal.

For a Romanian and English site, language values such as ro and en may be enough when the content is not region-specific. More specific values such as en-GB should be used only when that regional distinction is intentional. An optional x-default can identify a fallback selector or default page.

Hreflang is not a ranking boost and does not repair poor translation. It is routing information. Canonical tags, sitemaps, redirects, and internal links must agree with the language architecture.

Let people choose their language

Automatic detection can offer a helpful suggestion, but do not trap users in a redirect based on IP address or browser language. A Romanian speaker abroad may want Romanian; an English-speaking resident in Bucharest may want English.

Provide a visible language control with names people recognize, such as “RO” and “EN” or “Română” and “English.” Preserve the current page when switching. Remember the choice where appropriate without making the other version inaccessible.

Do not use flags as a substitute for language. English does not belong to one flag, and Romanian speakers are not always located in Romania.

Translate metadata and structured information

The visible page is only part of the version. Translate and verify:

• page titles and search descriptions;
• navigation and breadcrumbs;
• image alternative text;
• form labels, validation, errors, and confirmations;
• cookie and privacy controls;
• structured data fields that contain visible language;
• open graph and social sharing metadata;
• automated emails;
• downloadable documents;
• booking or payment hand-offs where possible.

Keep factual fields consistent: address, coordinates, phone number, service availability, and opening hours should not drift unless the audiences genuinely receive different offers.

Search intent may differ by language

A literal translation may not match the words people use. Romanian customers might search for a local abbreviation, while English speakers use an international category or describe the problem rather than the service title.

Research questions in each language using customer conversations, Search Console, sales notes, and relevant search results. Adapt headings and examples without changing the underlying truth. An English page can explain local context more explicitly, while the Romanian page assumes knowledge that residents already have.

Do not create two different claims merely to target phrases. Both versions represent the same business and must remain factually compatible.

Plan content governance before launch

Every bilingual website needs answers to four questions:

1. Which language is the source of truth?
2. Who approves each language?
3. What happens when one page changes?
4. How quickly must the counterpart be updated?

Maintain a page inventory with the source, counterpart, owner, review date, and status. For urgent changes—hours, prices, safety information, availability—update both versions in the same release.

If the business publishes frequently but cannot translate every article, define the policy openly. It is better to maintain a smaller, accurate English library than fill it with unreviewed machine translations.

Measure the English journey separately

Track discovery, landing pages, service interest, booking or enquiry completion, and lead quality by language. Compare outcomes carefully: a smaller English audience may produce fewer visits but more valuable enquiries.

Review internal search terms, form questions, and abandoned journeys. If English visitors repeatedly ask whether staff speak English, the page has not answered a basic decision. If they reach a Romanian-only booking provider and leave, the website translation stops too early.

A launch checklist

Before publishing:

• every translated page has an approved source counterpart;
• language switching preserves page context;
• titles, descriptions, forms, errors, and emails are translated;
• hreflang and canonical relationships are valid;
• both versions appear in navigation and sitemaps;
• mobile layouts handle text expansion;
• pricing, hours, addresses, and policies agree;
• the English contact path reaches someone who can respond;
• analytics distinguishes the language journeys;
• an owner is assigned for future updates.

A bilingual website is not a translated interface. It is a second complete promise to a defined audience.

Build it when that audience matters, translate the entire decision path, and give the version a long-term owner. That is when Romanian and English become an investment in access rather than a decorative switch in the header.