Build language support before the content grows.
This service covers a new website or rebuild where language models, components and editing are developed together. We specify page types, genuine counterpart relationships and CMS tasks. Adapting already published copy is a separate content engagement.
A controlled language launch
Prioritize
Choose services and pages the audience needs.
Localize
Review copy, imagery and the whole inquiry journey.
Maintain
Assign responsibility for changes in each language.
Start with the buyer’s task
A manufacturer reaching international procurement teams might need English specifications, delivery information and a useful quotation route. It does not follow that every recruitment page or old company update needs translating. Prioritizing the buyer’s decision makes the first release more useful and easier to maintain.
We start with a page matrix: which services apply to each audience, what questions need answering and which language your team can use in the next conversation. An international English site should not imply offices in London or New York, or introduce local prices and terms that the business has not approved.
Give each language a stable address
Published language versions need clear URLs. Hreflang can connect genuine page equivalents; a missing translation should not be represented as a false equivalent. The language selector should preserve the topic when possible and make its fallback understandable when a matching page does not exist.
The same premium design can serve several languages. The practical checks concern text length, navigation, captions, forms and product interfaces. An English heading does not complete localization if the next button, error message or screenshot still requires another language.
| Decision | Practical check |
|---|---|
| Page coverage | Is this service available to the intended audience? |
| Language switching | Does the matching topic open when it exists? |
| Inquiries | Can the responsible team reply in that language? |
| Maintenance | Who notices an outdated translation? |
Localize the decisions that matter
Examples may differ between markets when the difference reflects real customer needs. Technical facts should remain consistent. Product screenshots require their own review: translating the caption does not translate the controls inside the bitmap. Treat those assets as part of the content, not as decoration.
A useful pilot includes a priority service page, a supporting guide and the complete inquiry journey. Review it on mobile and desktop before expanding the library. That exposes awkward menu labels, misunderstood terminology and missing form feedback while the project is still small enough to adjust.
- Name a content reviewer for each language.
- Separate translation from market-specific terms and factual claims.
- Approve images, forms and metadata together with the main copy.
Commission a release you can maintain
Bring your existing languages, priority pages and available reviewers to the first discussion. We can then define design, development, editing support and quality checks. Ongoing translation and editorial maintenance need their own scope. A technical language feature neither guarantees search rankings nor replaces someone who can judge whether an offer reads naturally to the intended audience.
Test the page model with different language cases
For a fictional delivery, choose a service with English and Spanish versions, a guide available only in English and a long navigation label. Build the same page type with these cases. Review missing translations as well as two ideally matching pages.
Ask the intended editor to create a draft, connect the correct counterpart and change a shared contact detail in testing. Verify what the installation actually shares. Approve the model and workflow before populating the remaining website.
| Exercise | Ready when |
|---|---|
| Page without translation | No false counterpart is created |
| Long heading and menu | Mobile and keyboard work |
| Editing and inquiries | The intended role completes the task |
Sources and further reading
Questions, answered
Must every language contain the same number of pages?
No. Publish what each audience needs. Connect real equivalents and make the fallback in the language selector clear.
Does each language need a different design?
No. A shared design works well when content, imagery and interactions remain understandable and fit the layout in each language.