Skip to content

A website in Romanian, Hungarian and English: what to decide first

Three languages also need an editorial process. Agree who needs each version, who checks the wording and how the information will stay up to date.

Pop Robert · Updated:

A website in Romanian, Hungarian and English needs to explain the same commercial offer in all three languages. Translating the menu is not enough if service details, conditions or forms remain difficult to understand. Before requesting a quote, agree what content you need and how it will be maintained.

Start with the audience, not the number of languages

Identify who uses each version and what they need to do: compare a service, request a quote or find instructions. Language does not automatically determine the country, currency or delivery area. A Hungarian-speaking reader in Romania may need the same commercial conditions as a Romanian-speaking reader.

For a business website, choose the pages that support that decision first. Do not add pages simply to fill each version.

Make a content inventory for every language

Include headings, descriptions, buttons, forms, confirmation messages, downloadable documents and product or service information. Record whether each item exists, needs writing or requires review. If a page is unavailable in a language, decide what the reader will see without presenting another page as its translation.

Agree who writes and who approves

Choose a working version and a person responsible for the commercial meaning. Review each language for terminology, tone and conditions, rather than spelling alone. Machine translation can provide a draft; it does not replace approval by someone who understands the offer.

Keep a shared list of terms for services, units and actions. An order should not become an “enquiry” on one screen and a “booking” on another if these are different operations.

A fictional example of organising the work

In this invented example, a workshop describes the same repairs in three languages. The service owner confirms what can be repaired, then each editor adapts the explanation. This is not a customer or a completed project.

  1. Approve the service description and its limits.
  2. Check every version in context, including the form.
  3. Record who approves publication.
  4. Reopen the other languages for review whenever the information changes.

Decide on URLs and language switching

Google recommends separate URLs for language versions and links that let readers choose their language. Ask for the switcher to open the equivalent page where one exists, and for alternatives to be identified through hreflang. This helps discovery of the versions; it does not guarantee rankings.

Include updates in the editorial workflow

When a service changes, mark every affected item: the page, frequently asked questions, form and documents. Agree who checks translations before publication and what happens when a version falls behind. Clarify responsibility for technical maintenance separately.

Prepare a quote request that can be checked

Provide the page list by language, available materials, approvers and preferred editing process. For the choice of editing tools, see CMS or custom website. Compare what content is included and what is quoted separately alongside the service prices.

Contact

Let’s talk about your project

Tell us what you need. We’ll get back to you with a clear proposal, including timelines and costs.

What are you interested in?
Approximate budget (optional)

We use your details only to reply to you. Privacy policy

WhatsApp: Message us now (opens in a new tab)