You can launch a bilingual website without translating the entire archive. Start with a complete route from understanding the offer to making an enquiry in the second language. Translate everything that route depends on, then expand when you have a reason and someone to maintain it.

For a service business, that usually means more than the homepage and less than every old blog post. The useful question for a quote is: what must a prospective customer be able to understand and do without changing language halfway through?

Decide who the second language is for

“We need an English version” leaves important decisions open. Are you helping international customers who already know your business, testing a new advertising audience, or building a long-term source of enquiries from search? Each goal needs different content and follow-up.

Write down the audience, the service they can actually buy and the language in which your team can support them. A translated page should not offer an appointment that nobody can conduct in that language. If the first conversation is available in English but later delivery has limitations, explain those before the visitor submits.

Language and location are separate decisions. In my portfolio, SpainProperty serves Hungarian-speaking people interested in property in Spain. The property's country alone does not tell you which language the buyer needs. Use the audience's circumstances to choose the content, not a flag beside the menu.

Choose a complete first release

Map one journey before creating a translation list. For a service enquiry, I would start with the service explanation, relevant evidence, information about the business, the contact form and its confirmation. Include any conditions, downloads or booking tools needed to make that decision.

Then place the remaining content into three groups:

  • Needed at launch: without it, the visitor cannot assess the offer or complete the next step.
  • Useful later: it answers a genuine question, but the initial journey works without it.
  • Not relevant to this audience: it concerns an unavailable service, an expired offer or a different market.

This is a scope decision, not a fixed page count. An older article can remain in its original language without being presented as a translated resource. If you link to it from the new version, make its language clear. Do not create empty translated pages just to make the navigation look symmetrical.

Full translation becomes more sensible when visitors regularly need the wider catalogue or knowledge base, and the team can keep both versions current. A staged launch is more manageable when you are testing one clearly defined offer.

Adapt the wording, not just the sentences

Give the writer or translator the offer, audience and intended action alongside the original text. Ask them to check the terminology people use when looking for that service. A literal translation of your preferred keyword is a starting point for research, not proof that customers search that way.

For Hungarian copy, agree on tegezés or magázás and use it consistently. Read the page aloud. Replace imported marketing phrases with the action you actually want: “Kérj ajánlatot” for a quote request or “Kérj időpontot egy beszélgetésre” when the visitor is requesting a conversation. Neither should imply an instant confirmed booking if a colleague must approve it.

Review titles, search descriptions, image descriptions, menu labels and downloadable documents as part of the same job. On this portfolio, the English and Hungarian versions of an Insight have separate titles and summaries. The wording can differ while the facts, conditions and intended next step stay aligned.

Machine translation can help prepare a draft. I would still assign a named reviewer who understands both the language and the offer. Check prices, units, dates, availability and promises explicitly; fluent prose can still describe the wrong service.

Give each language a stable address

Ask the developer how someone can link directly to either version. Google recommends separate URLs for languages and advises against automatically redirecting visitors based on an assumed language. A visible language choice lets the person decide. Google's multilingual-site guidance.

For a simple English/Hungarian site, language folders can be a practical structure. You do not need to reorganise a working site merely to match someone else's example. Agree on the addresses before launch and keep existing links in mind if anything changes.

Require these technical checks in the handover:

  • Equivalent pages are connected: hreflang references identify the language alternatives, include the page itself and point back from the counterpart. Google's localized-page guidance.
  • Canonical references are consistent: for distinct translated pages, normally use each page's own preferred URL. Do not point every Hungarian translation at the English page. Google recommends a canonical in the same language when using hreflang. Canonical guidance.
  • The document declares its language: HTML should identify the page language with the lang attribute. This is separate from linking translated alternatives. W3C's language-declaration guidance.

These are implementation checks, not a promise of rankings or enquiries. Have the developer show you the rendered pages and their metadata rather than accept “multilingual SEO included” as the whole specification.

Keep the enquiry in the chosen language

The form needs the same attention as the page copy. Check field labels, choices, validation errors, the submission button and the confirmation. If the booking tool or automated reply changes language unexpectedly, the journey is unfinished.

Record which language the person used so the colleague answering can respond appropriately. That does not require asking visitors a question you already know from the page; decide with the developer how that context reaches the inbox or CRM. See my form-field guide for choosing what to ask explicitly.

Also agree on the failure message. If sending fails, the visitor should understand what happened and what they can do next. Test this separately from the successful submission. A translated thank-you page cannot compensate for an enquiry that never reaches the team.

Ask for a quote you can compare

Give suppliers a list of the pages and supporting steps in each language. Separate reusable design and development from writing, translation, review and content entry. Ask which ongoing costs depend on page count, translated words, software subscriptions or manual work.

I would include these decisions in the brief:

  • Which audience and offer does the second language serve?
  • Which pages and interactions must be ready for the first release?
  • Who approves the meaning and tone of each version?
  • What happens when a page has no equivalent in the other language?
  • Who receives enquiries, and how will they know the preferred language?
  • Who updates both versions when a price, condition or service changes?
  • What access and instructions will the next editor receive?

The answer may be an extension of the current website, not a rebuild. If you are also changing the platform or page structure, use the redesign brief to separate that work from adding a language.

Test the second language as a customer would

Open a service page directly on a phone, without starting at the homepage. Find the information, switch language, return and submit a test enquiry. The switch should take you to the equivalent page where one exists; agree on a clear fallback where it does not.

Check long Hungarian labels, accented characters, narrow buttons and form errors at mobile widths. Try keyboard navigation and enlarged text too. Use the finished copy during review, because short placeholder text can hide layout problems.

Ask a reviewer to explain the offer in their own words and describe what will happen after submission. Then check the actual message received by the business. If those accounts differ, revise the copy or the process before sending traffic.

Plan the next translation from evidence

After launch, look separately at the pages visited in each language, useful enquiries and recurring customer questions. Where available, inspect the relevant search queries and pages in Search Console. Do not treat language as nationality or infer demand from a few visits.

Expand when you can name the unanswered question and the person responsible for the new content. Keep a simple change log for shared facts so that an updated offer does not leave the other language behind. The long-term cost is keeping promises consistent, not just translating words once.

If you are planning a bilingual website, send me the current URL, the intended audience and the first service you want to offer through the contact page or at hello@davidbuka.com. I can help define the first release and the website and enquiry-handling work it needs.

Primary references checked on 22 October 2026. The cover is an original editorial illustration of language adaptation, not a photograph of client materials.