Multilingual websites
Multilingual WordPress websites: pages, navigation and forms in each language
A translated page should also help people choose a service and contact you. Gloria plans multilingual WordPress content with the navigation, forms and practical information needed for the markets you want to serve.
Your project in practice
Example language review
- Service page
- Same actual service, explained naturally for the chosen audience
- Form
- Labels, help text and error messages in the selected language
- Confirmation
- A clear explanation of what happens next
- Follow-up
- A team able to respond in the language offered
What it can change
Translate priority pages, test customer journeys and plan content updates
Translate what helps customers choose
Priority pages follow the offer and intended audience, with consistent terminology and relevant practical information.
Review navigation, forms and confirmations in every agreed language
Navigation, buttons, forms and confirmations are reviewed in each language included in the project.
Define who updates translated pages when your offer changes
The scope identifies the content to maintain and the review process when the offer changes.
In practice
Add a new language or review existing WordPress translations
You are entering another market
We choose useful pages and languages before assessing an appropriate solution for your WordPress website.
You already have several language versions
We examine inconsistencies, connections between versions and how the information is maintained.
The scope
Multilingual WordPress scope, translation review and ongoing updates
Open the sections below to explore the scope, deliverables and practical requirements.
Start with the pages your audience needs
Decide which markets and visitors you want to reach. Your services, practical information and prospective customers’ questions define a useful starting scope. Stabilise the French pages before adapting them.
An editorial website can keep articles in French while offering its service pages in English. The selection should reflect the content’s value to the intended audience and your capacity to keep it up to date.
Translate the whole journey
A carefully translated service page can still lead to a form that is difficult to use. Menus, buttons, fields and error messages are part of the same job.
- Adapt titles, descriptions and navigation labels.
- Translate forms, instructions and submission confirmations.
- Review useful text within images and their descriptions.
- Make contact information and applicable terms accessible.
- Connect equivalent pages and clearly identify content available in only one language.
Choose a solution that fits the website
The choice of plugins depends on the theme, content, features and update process. A small service website, a catalogue and an editorial publication have different requirements.
Consider the integration work, licence and translation costs, editorial review and maintenance. If you use an external translation service, also examine which content it will receive and how its terms cover that data.
Preserve the meaning and check the details
Assisted translation can provide a first draft. Review then checks the meaning, tone and statements that commit the business. A shared vocabulary keeps service names consistent.
Examples, date formats and commercial expressions may need adapting. The finished text should remain faithful to the actual offer, including its scope and conditions.
Check the pages before opening them to visitors
The final checks cover links, language-specific URLs, metadata and the journey on desktop and mobile. Switching languages should lead to a relevant page.
Plan what happens next: who updates each page, who reviews the translation and how will an outdated version be spotted? Changes to an offer in French need to reach the other languages in which that offer appears.
Practical guide
Choose a language version you can support beyond the page
Before translating the whole website, identify the audience, services available to them and the way enquiries will be handled. A page in another language creates an expectation that the form, confirmation and subsequent conversation will be understandable. If only part of your offer is available, make that boundary visible.
Swipe across the table to see every column.
| Question | Effect on the project |
|---|---|
| Which services are genuinely available? | Choose pages to adapt and exclusions to explain |
| Who can answer enquiries in this language? | Set an appropriate contact route and confirmation |
| Which specialist terms need consistency? | Prepare a short approved glossary |
| Who will review later changes? | Plan ownership of ongoing updates |
Language and country are not interchangeable. People using the same language may face different delivery arrangements, terminology and commercial conditions. The website should follow the service you actually provide, rather than assume that selecting a flag makes the offer suitable for that market.
Practical guide
Illustrative example: a manufacturer introduces an English enquiry journey
A fictional manufacturer wants to explain its made-to-measure equipment in English. It can discuss selected products internationally, but does not yet support direct online ordering or every option in those markets. Translating an existing “Order now” route literally could create an expectation the business cannot meet.
Translate product information and the enquiry form for the target market
The English version can identify the available ranges, explain what information is needed and offer a feasibility enquiry. Units, downloadable documents and form questions should support that route. Prices and currencies should follow an approved commercial decision; a translated page does not automatically imply local billing or a converted fixed offer.
A glossary can establish product names, specialist terms and wording to avoid. A review record connects each source page with its translated version and the person approving its business information. This scenario is fictional, not a Gloria client case. It illustrates how localisation can prevent misleading expectations instead of merely replacing one set of paragraphs with another.
Practical guide
Plan missing equivalents and later content changes
Define the languages, page types and interface elements included, together with who supplies and reviews translations. Integrating approved text is a different scope from full adaptation with specialist review. Software licences, existing website features and content organisation also affect the work and budget.
Agree how to handle a page without an equivalent, a document available in one language only or an offer withdrawn after launch. A language selector should not imply that a missing version exists. When a commercial detail changes, a version register helps identify every place that needs review instead of leaving inconsistent conditions online.
- Test switching language on representative page types, not only the homepage.
- Follow the journey through form labels, validation errors and confirmation messages.
- Review documents, links and commercial information with the responsible person.
- Check the agreed URL and language signals, and record anything still awaiting translation.
You continue to buy and renew your own domain. Adding a language does not automatically require another domain, and hosting remains a separate decision. The structure should fit the business and the existing website, while remaining understandable for the people who will maintain it after launch.
Questions about translation priorities and machine translation
Does every article need translating?
No. Prioritise content that serves the intended audience. Make it clear in the navigation when an article is available in only one language.
Is machine translation enough?
It can help produce a first draft. Review is still needed for meaning, the terms of the offer and the visitor journey. The depth of review should reflect the page’s purpose.
Discuss your multilingual website
For an enquiry about GloriaTranslate or your website, tell us which languages, priority pages and features are involved.
Discuss your multilingual website