Translating a page is only part of a multilingual website. Each version needs a stable address, a relationship to its counterparts and a clear route for visitors to change language without losing the page they were reading.
Related service: Website and ecommerce development- 01Map equivalent content
- 02Assign language URLs
- 03Declare each page's language
- 04Connect valid alternates
- 05Test switching and missing versions
SECTION 01
Create a page-equivalence map before implementation
Give the agency a list of source pages and approved translations. Decide which pages truly correspond and which contain a different regional offer. A language version and a country-specific version are not automatically the same thing. Keep the initial structure understandable: the selected URL pattern should work with your content system, editorial workflow and future additions, rather than being chosen only for appearance.
Google documents alternate-language signals through HTML, headers or sitemaps, with matching references between versions. W3C separately explains declaring the language of an HTML document. These solve different needs. Ask the agency to implement one maintainable alternate-reference method and accurate document language, then test the generated output. Adding multiple conflicting implementations can create more maintenance work without making the translation clearer.
SECTION 02
Illustrative example: a bilingual equipment supplier
Consider a supplier publishing an English installation-service page and its reviewed Spanish equivalent. A visitor switches languages while reading that service. The control opens the matching translated service page, keeping the topic intact. The quotation form's labels and confirmation text also match the selected language, while the submitted request records the customer's preference for the team handling it.
A technical document is not yet translated. Rather than pretending a Spanish version exists, the page labels the available document's language and provides an appropriate contact route. The first release includes only approved translations in its alternate mapping. When the missing version is later published, the content team adds the relationship through the same structured workflow instead of manually patching several unrelated templates.
SECTION 03
Test real counterparts, not just the switcher
Acceptance should cover every supported language, a page missing one translation, a renamed translated URL and direct entry from an external link. Confirm that alternate references resolve to valid counterparts and that language choices work without trapping visitors in forced redirects. Check document language, form messages, navigation labels and any shared content that can remain accidentally untranslated.
A smaller complete language set is easier to maintain than a broad collection of stale machine-translated pages. Handoff should record who approves translations, how changed source content is flagged and what happens when a version is withdrawn. Ask the agency to separate translation work from technical implementation in the estimate. Search visibility depends on the content and site as a whole, not the presence of language tags alone.
SECTION 04
Frequently asked questions
Is an HTML language attribute the same as hreflang?
No. The document language helps software interpret the page; alternate-language references connect equivalent versions for search engines.
Should language switching always return to the homepage?
Prefer the equivalent page when available. If it is missing, explain the fallback instead of silently discarding the visitor's context.
Can we publish language URLs before translation is ready?
Avoid presenting unfinished versions as complete. Publish reviewed content and update alternate relationships when the real version exists.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Localized versions of pagesGoogle Search Central
- Declaring language in HTMLW3C Internationalization
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy