Skip to content

Blog

›

Product

How to build a multilingual website without duplicating your work

PraismaHub team · November 15 2026 · 4 min read

For a Dutch and English website, start with the pages customers use to decide and act. Translate your homepage, main services and contact or booking pages first. That gives visitors a complete journey in each language while you work through the rest.

Make a page and content map

List each page, its owner and the content it relies on. A service page may include navigation, a form, a price note and CMS-driven FAQs. Flag those pieces before translating so the page does not switch languages halfway through a visit.

Translate linked pages in PraismaHub

Open the linked language page in the Site Builder and translate its copy directly on the canvas. Each published language version has its own URL. Preview that version in the editor and localize the button text, page title and description. For collection-driven pages, make sure the entries you want are available in the target language.

Check the whole journey in both languages

  • Switch languages on a service detail page and check the destination.

  • Follow links from navigation to the service, then to the form.

  • Read field errors and the confirmation message in both languages.

  • After publishing, open the public URLs and check that the language variants you intended to launch are discoverable in the sitemap.

Keep one short glossary for terms like offerte and kennismakingsgesprek. When you add a service or update an offer, include both language versions in the review.

Example: launch a Dutch and English service site

Imagine a Roermond studio that serves Dutch speakers and international customers. Start with the Dutch and English homepage, a page for the main service and a contact page. Pick one action to test, such as requesting a consultation. Follow that path in each language from the public homepage through the confirmation message. This reveals unfinished translations that are easy to miss when reviewing a page by itself.

Give each page a job before translating. The homepage introduces the studio and sends visitors to the service. The service page explains the appointment and sends them to contact or booking. The last page tells them what will happen after they submit. If the English version uses a different offer or destination, document that difference so future edits do not accidentally replace it.

Localize the details that affect a decision

  • Navigation and buttons: Use familiar labels in each language. Check that longer labels fit on mobile.

  • Prices, dates and opening hours: Use a format the reader recognizes and make the time zone clear where relevant.

  • Forms: Translate field labels, examples, validation messages and confirmation text.

  • Images: Replace graphics containing embedded text if the text does not match the page language.

  • Metadata: Give each version a title and description that reflect what readers in that language are looking for.

Separate page translation from CMS translation

A page can have fully translated headings and still show content from a collection. Check which entries supply the service description, testimonials or FAQs. If an English FAQ is missing, decide whether to translate it now or leave that answer out of the English launch. Review the public page to verify the result because the editor may still show content you have not published.

Check URLs and language switching after publishing

Open each language’s public URL in a private browser window. On a service page, use the language switcher and confirm that it takes you to the corresponding service. Follow a link from the page to the next step and check that it stays in the chosen language. For links in a campaign email, test the exact destination you will send.

In PraismaHub, published language versions have their own addresses. When reviewing the sitemap, look for the URLs you actually intended to launch. If a version is missing, first confirm that the correct language page or CMS entry is published.

Keep the languages in sync

Assign someone to review both versions when hours, prices or booking links change. Keep a short list of core pages and their language counterparts. For routine updates, compare the visitor-facing facts first and then read each language version on its own so the wording sounds natural to its audience.

Use the first completed journey as your template for the next service. Check off the same page copy, CMS fields, form messages and search metadata before adding another language or section.

See PraismaHub’s guide to website SEO for the product setup.