Connect the visitor journey
Plan the language selector, menu labels and links between pages as part of the design. Check what visitors see when moving from a service page to a related page or enquiry route, including on mobile.
In the current platform, a missing or unpublished translation can show the matching published page in the website’s default language where one is available. That is fallback content, not a translation. Check this behaviour when deciding which language versions are ready for visitors.
Give language versions their own URLs
Language prefixes can distinguish versions, such as /services and /fr/services. These are illustrative paths: we agree your languages, page addresses and existing URL requirements before setup.
Published versions provide language-specific page information and alternate-language links for search engines. We check titles, descriptions, canonical addresses and sitemap entries as part of the implementation. Adding a language does not guarantee search rankings or enquiries in that market.
Google recommends distinct URLs for language versions and links that let visitors choose a language. Read its multilingual website guidance. Website structure and reviewed content need to work together.