Start with markets and buying behaviour
Define the countries and languages that matter commercially. The same language can serve different markets with different delivery areas, currencies, product names and buying requirements. Ask customer-facing staff which questions recur and research actual search language. A literal translation of an English keyword list can miss local terminology or reflect an intent that does not lead to the same service.
Choose a manageable launch scope rather than translating every page into every language immediately.
Translate the full customer journey
A translated landing page is incomplete if the form, confirmation, checkout, support or contractual information unexpectedly returns to another language. Map the pages and systems needed for an actual enquiry or purchase. Assign translation ownership to menus, validation messages, emails, documents and important product attributes as well as the main copy.
Use appropriate language expertise for important terminology. Machine translation can assist a workflow, but its output still needs a defined quality process.
Compare the work involved
| Translation task | Additional SEO/localisation decision |
|---|---|
| Translate the service description | Confirm local terminology, demand and buying intent |
| Translate page titles | Preserve meaning while matching the page’s market purpose |
| Create language versions | Choose URLs, navigation and appropriate language annotations |
| Translate a form | Route enquiries to someone able to respond |
The distinction is operational as well as editorial. More translated pages can create more maintenance work without producing a usable market offer.
Use explicit, crawlable language versions
Give users clear language navigation and make important versions accessible through links. Google documents several ways to identify localised versions, including hreflang. Implement the chosen method consistently and validate that alternate references resolve to the intended pages. Language annotations help explain relationships; they do not replace quality content or automatically create rankings in a new country.
Do not rely on a browser-language redirect as the only way to discover a version. Consider what happens when a visitor chooses another language deliberately.
Plan differences and maintenance
Some pages will have no equivalent because an offer is unavailable in a market. Other pages need different examples, prices or conditions. Do not force a false one-to-one relationship simply to fill a template. Record what should stay aligned and what is deliberately local.
- Name an owner for each language.
- Define how source changes trigger review.
- Check translated links, structured data and social metadata.
- Review enquiry quality and the team’s ability to respond.
Measure each market separately
Track discovery, useful enquiries and completed sales by relevant market and language. Consider seasonality, availability and media spend before comparing performance. A lower-volume specialist market can be valuable if enquiries fit the business; a high-traffic translation can be unhelpful if the service cannot be delivered there. We use the evidence to decide which journeys to improve or expand, rather than assuming that the largest translation programme is the best investment.
Common questions
Do we need a different domain for each language?
Not necessarily. The right structure depends on markets, ownership and maintenance. Country domains, subdomains and subdirectories have different practical trade-offs.
Does hreflang fix poor translation?
No. It describes relationships between versions. The page still needs accurate language, a useful offer and a complete customer journey.