Bilingual websites: contextual translations and correct URLs

Decide who each version is for

Before translating, describe who will read and what conversations the company can support. An English version might serve partners, international visitors or clients with cross-border processes. Content should explain the work clearly to that audience while preserving the actual service scope.

Review local terms, abbreviations and examples. A familiar Brazilian expression may need a short explanation. Do not turn translation into promises about support, timing or capabilities the company does not have. Business clarity should accompany language choice.

Maintain correspondence between pages

Google documents hreflang as a way to indicate localised versions of a page. Related versions should reference themselves and their counterparts. This annotation makes a relationship explicit; it does not replace translated, navigable content.

Keep an editorial identifier for each pair and record both addresses. A Portuguese article then remains connected to its English equivalent even when slugs differ. Whenever a counterpart exists, the language selector should lead to it rather than force visitors to search again from the home page.

Use AI with a glossary and a defined task

Provide service plan names, brand voice and the page’s purpose. State which proper names should remain unchanged and which technical terms need explanation. Request a translation faithful to the scope, without extra guarantees or benefits absent from the approved version.

Review calls to action and words whose meaning depends on context. A literal button translation can sound awkward or promise an action the link does not perform. Read as someone unfamiliar with the business, rather than only comparing sentences side by side.

Localise the whole journey, including small details

Include navigation, footer, search messages, sharing, missing pages and the privacy policy. An almost-translated experience can still fail when someone needs help. Contact information should also explain consistently how a conversation begins.

Check search titles, descriptions, alternative text and relevant structured information. Avoid reusing a Portuguese description on an English content page for convenience. Review the publication as a whole, including elements outside the first screen.

• Open an internal page directly in each language.
• Use the language selector midway through an article.
• Check search, contact, footer and error handling.
• Review metadata and internal links in both versions.

Choose stable addresses and predictable navigation

Google’s guidance for multilingual sites recommends distinct URLs for language versions and attention to mechanisms that block access to alternatives. People should be able to choose which version they want. The structure needs to support maintenance and discovery.

A language folder can organise this choice on a static website. Maintain the pattern for new pages and avoid accidentally publishing incomplete pairs. If one version is unfinished, record the pending work and do not advertise a counterpart that does not exist.

Plan how versions will be updated

When correcting a service description, record which languages need the same change. A simple review process prevents a plan from having different scopes because a translation became outdated. On the blog, also check references, captions and related-article links.

MissaciWeb presents its services in Portuguese and English to make its proposal easier to understand. In a bilingual project, content organisation belongs to development. When discussing your website, bring approved business information and decide who will review future updates.