Give each version its own URL
A structure such as /fr/services/ and /en/services/ makes language versions explicit. Main content, navigation and calls to action should match the stated language. On an existing project, preserve a coherent structure rather than changing URLs purely for appearance. URL changes need an accompanying redirect strategy.
Connect exact equivalents
Hreflang annotations identify corresponding language versions. Google asks for consistent references, including return links from the linked page to its counterpart. Prepare a page-pair mapping table. A French service page should connect to that same service in English rather than defaulting to the English homepage.
Translate intent and examples
A word-for-word translation may preserve sentences while losing usefulness. Check customer terminology, examples, units and the final button. A title should explain the page in its own language. Avoid linking to a document available only in the other language without clearly saying so. The complete journey matters as much as the main text.
Test language switching in context
Open a deep page, switch languages and continue the same task. Repeat with an article, a service page and the form. Check canonical links and mappings in the source as well as the visible experience. If a translation does not yet exist, explain that situation instead of presenting an unrelated page as its equivalent.
Your checklist
- Stable, separate URLs.
- A page-by-page French/English map.
- Titles and descriptions written for each language.
- Language links that preserve the current task.
