A website in two languages needs more than translated paragraphs. Visitors need to find the right version, understand the service and complete the same important tasks. Your team needs to maintain both versions when prices, services or contact details change. Search engines also need clear signals about which pages are equivalent alternatives.
Plan those requirements together before commissioning translation or building a language switcher. A useful bilingual SEO plan connects customer demand, page structure, local wording and a maintainable relationship between language versions. It should explain what the business can support as well as what the website can display.
Define the audience behind the second language
Start with the people you want to reach and the tasks they need to complete. Are you serving customers in another country, people who prefer another language within your existing market, or both? Language and location are related considerations, but they are different. Someone reading a French page may still be enquiring about a service delivered in Britain.
Record the practical boundaries: service areas, delivery arrangements, opening hours and the languages available for replies. A translated enquiry form can create an expectation of support in that language. If support is limited, explain the available arrangements clearly and decide how the team will handle enquiries before promoting the new pages.
Identify evidence for demand through existing enquiries, customer conversations and relevant search research. Avoid assuming that translating your strongest English keyword gives the best phrase in another language. Customers may use different service categories, abbreviations or ways of describing the same problem.
Choose the pages that enable a complete journey
Begin with a page inventory and prioritise useful journeys. A translated service page needs a destination for its call to action, appropriate contact information and any essential explanation of the process. Translating the homepage while leaving every practical next step in English can produce an inconsistent experience.
For each proposed page, record its purpose, audience, associated English page and supporting pages. Mark content that is truly shared and content that needs adaptation. A case study may be relevant to both audiences, while a delivery explanation may need different details for a particular market.
You do not have to launch every page at once. A focused first release can work if its limits are clear and the included journeys are complete. Avoid presenting a second language as comprehensive when most navigation leads to untranslated material without explanation.
Give each language version a stable address
Use distinct, stable URLs for maintained language versions. Identifiable addresses can be linked, shared, inspected and maintained. Ensure the destination corresponds to the language version the visitor actually selected. Our international website and localisation guide provides the related checks.
Agree the URL pattern with your developer before creating pages. For example, a clear language directory can provide a consistent home for translated material. Check how the pattern will work for services, articles, contact pages and future additions. The important operational question is whether staff can identify and maintain each version reliably.
Avoid treating a temporary browser preference as the only way to access another language. A visitor may need to change their choice, use a shared device or follow a link sent by someone else. Provide an understandable language selector and preserve access to the original version.
Translate the meaning and the buying context
Give the translator a brief that explains the service, the intended reader and the action the page should support. Include agreed terminology, examples of customer questions and phrases that require particular care. A literal translation can preserve every sentence while losing the meaning a customer needs.
Review page titles, headings, navigation, image captions and form labels alongside the main copy. These smaller elements often carry the most practical instructions. A beautifully translated article is of limited use if the enquiry button or error message becomes confusing.
Use a reviewer who understands the target language and the business context. Ask them to check whether the page makes the same accurate commitments and whether terminology is natural for the intended audience. Where the meaning changes intentionally, record the reason so that future updates do not accidentally erase the adaptation.
Maintain a register of equivalent pages
Create a simple relationship register with the English URL, alternative URL, page owner and review status. Pair pages by purpose, rather than assuming that any translated page can act as an alternative to any English one. An English service overview and a narrow article in another language may discuss similar topics without being equivalent pages.
This register helps the developer implement language annotations and helps editors keep the website coherent. It also reveals gaps: a translated service page without a corresponding contact route, an English article whose alternative has been removed, or a language switcher that sends every visitor back to the homepage.
Choose a clear behaviour for pages without an alternative. You might provide a link to the relevant language homepage with wording that explains the destination. Test that behaviour with users. An unexplained jump to unrelated content can make the language selector feel broken.
Use hreflang accurately and consistently
Hreflang sets should identify the page itself and its equivalent alternatives through fully qualified URLs and reciprocal relationships. Google supports HTML, HTTP headers or sitemaps for these annotations. Choose a method the team can maintain consistently. Our hreflang and localised content guide provides the related checks.
Language codes need careful checking. A regional variation uses the appropriate country code where it is relevant; for Britain, the country code is GB rather than UK. Do not add a region merely because the business has an address there. Decide what each page actually serves.
Hreflang does not translate content or establish the language of a page. Check that the visible main content and navigation match the intended version. Ask the developer to validate annotations against the relationship register, including renamed, redirected and removed pages. Keep these checks part of publishing rather than relying on a single launch inspection.
Check indexing and page relationships separately
Ask your developer to review whether the intended language pages can be accessed and indexed, and whether other technical settings send consistent signals. Inspect redirects, canonical settings and internal links alongside the annotations. A page may have an apparently correct language annotation while another setting prevents it from serving its intended purpose.
Use a small sample covering different templates and page states. Include service pages, articles, a page with an alternative and one without. Check the final rendered output as well as the values in the CMS, particularly where templates generate language information automatically.
Keep findings specific. Record the affected URL, the observed behaviour, the intended relationship and the change required. This gives the developer something verifiable and avoids a vague instruction to fix international SEO.
Test the full enquiry journey in both languages
Follow a realistic customer task from a search landing page to a response. Check the navigation, form choices, validation messages, confirmation page and confirmation email. Examine whether the language choice reaches staff so that they can respond appropriately.
Include mobile use and unfamiliar visitors in the review. Translated phrases can be longer than their English equivalents, affecting menus, buttons and form layouts. A technical implementation that is correct in the page source can still become difficult to use on a narrow screen.
Make sure customers can understand when they are leaving translated content. If an external booking tool supports fewer languages, explain the transition and provide a workable help route. The journey includes those dependencies, even when your business does not control their interface.
Plan updates before the second language goes live
Assign responsibility for detecting changes that affect both versions. A service amendment should create a translation review task with an owner and a clear state. Record whether the alternative is current, awaiting review or temporarily unavailable, rather than letting it silently drift.
Measure the journeys separately where your tools allow, and interpret the results with context. Different traffic volumes, audiences and enquiry routes make simple comparisons unreliable. Look for practical problems, such as visitors reaching a translated service page but struggling to complete its next step.
Giraffe Digital's search engine optimisation service can help connect language research, page planning and technical checks. A bilingual website becomes sustainable when its language versions remain useful, accurate and connected throughout the customer's journey.
Frequently asked questions
How should we define the audience behind the second language?
Start with the people you want to reach and the tasks they need to complete. Are you serving customers in another country, people who prefer another language within your existing market, or both? Language and location are related considerations, but they are different. Someone reading a French page may still be enquiring about a service delivered in Britain. Record the practical boundaries: service areas, delivery arrangements, opening hours and the languages available for replies. A translated enquiry form can create an expectation of support in that language. If support is limited, explain the available arrangements clearly and decide how the team will handle enquiries before promoting the new pages. Identify evidence for demand through existing enquiries, customer conversations and relevant search research.
How should we give each language version a stable address?
Use distinct, stable URLs for maintained language versions. Identifiable addresses can be linked, shared, inspected and maintained. Ensure the destination corresponds to the language version the visitor actually selected. Our international website and localisation guide provides the related checks. Agree the URL pattern with your developer before creating pages. For example, a clear language directory can provide a consistent home for translated material. Check how the pattern will work for services, articles, contact pages and future additions. The important operational question is whether staff can identify and maintain each version reliably. Avoid treating a temporary browser preference as the only way to access another language. A visitor may need to change their choice, use a shared device or follow a link sent by someone else.
How should we maintain a register of equivalent pages?
Create a simple relationship register with the English URL, alternative URL, page owner and review status. Pair pages by purpose, rather than assuming that any translated page can act as an alternative to any English one. An English service overview and a narrow article in another language may discuss similar topics without being equivalent pages. This register helps the developer implement language annotations and helps editors keep the website coherent. It also reveals gaps: a translated service page without a corresponding contact route, an English article whose alternative has been removed, or a language switcher that sends every visitor back to the homepage. Choose a clear behaviour for pages without an alternative. You might provide a link to the relevant language homepage with wording that explains the destination.
How should we check indexing and page relationships separately?
Ask your developer to review whether the intended language pages can be accessed and indexed, and whether other technical settings send consistent signals. Inspect redirects, canonical settings and internal links alongside the annotations. A page may have an apparently correct language annotation while another setting prevents it from serving its intended purpose. Use a small sample covering different templates and page states. Include service pages, articles, a page with an alternative and one without. Check the final rendered output as well as the values in the CMS, particularly where templates generate language information automatically. Keep findings specific. Record the affected URL, the observed behaviour, the intended relationship and the change required. This gives the developer something verifiable and avoids a vague instruction to fix international SEO.
How should we plan updates before the second language goes live?
Assign responsibility for detecting changes that affect both versions. A service amendment should create a translation review task with an owner and a clear state. Record whether the alternative is current, awaiting review or temporarily unavailable, rather than letting it silently drift. Measure the journeys separately where your tools allow, and interpret the results with context. Different traffic volumes, audiences and enquiry routes make simple comparisons unreliable. Look for practical problems, such as visitors reaching a translated service page but struggling to complete its next step. Giraffe Digital's search engine optimisation service can help connect language research, page planning and technical checks. A bilingual website becomes sustainable when its language versions remain useful, accurate and connected throughout the customer's journey.


