One B2B website, five languages: keeping every market in step.
How service firms that sell across borders can plan language versions, move an established website safely and keep enquiries reaching the right team.
The idea in brief
Plan each language as a complete journey with its own addresses, reviewed translation and a reply in the same language. Keep every established address working when the site moves.
A certification consultancy in Dubai wins clients in Germany, Italy and Brazil. Its website was written in English some years ago, with a few translated pages added whenever a salesperson asked for one. A buyer in Milan now finds an Italian service page, clicks “Contact” and receives an English form and an English reply.
We made that firm up, but the pattern is common among companies that sell services across borders. The languages were added page by page, and nobody planned the route through them. This article covers the decisions we make when a B2B website has to work in several markets at once.
Give each language its own address
Every language version of a page needs its own URL. Google’s guidance on multilingual sites recommends different URLs for each language instead of changing the content with cookies or browser settings. It also advises against redirecting visitors automatically to the language you think they want, because that can stop people and search engines from reaching the other versions.
Offer a visible language switch that leads to the same page in the other language. A switch that always returns to the homepage makes a buyer find the service a second time. If a page has no translation yet, say so and link to the closest related page.
Connect the versions to each other
Search engines need to be told that the German and Italian pages are versions of the same content. The hreflang annotation does that. Google’s documentation on localised versions says each language version must list itself and all the other versions, and that tags are ignored when two pages do not point to each other.
The reserved x-default value names the fallback page for visitors whose language matches none of your versions. None of this promises a better position. It helps Google show each searcher the appropriate version, which matters when the same service has five pages.
Generate these annotations from the content structure. Hand-typed lists drift as soon as someone adds a sixth language or renames a page.
Translate for the buyer
Google’s spam policies describe scaled content abuse as generating many pages that provide little value to users, “no matter how it’s created”. The policy is about value, and it does not name a translation method as acceptable or forbidden. Our own advice goes further: have someone who knows the service and the market review every page that a customer might rely on.
Technical buyers notice the details. Names of standards, units, document titles and the authorities involved differ by country. A page that translates the words and keeps the wrong regulator loses the reader it was written for.
Carry the language through the whole enquiry. The form labels, error messages, confirmation and first reply should match the page. Record the language with the enquiry so it reaches a colleague who can answer in it.
Move without losing pages
Established B2B sites often hold years of articles that still bring in search visitors. When the site is rebuilt, each of those addresses needs a decision: keep it, or redirect it to a specific replacement.
Google’s guide to moving a site recommends mapping old URLs to new ones and using permanent server-side redirects, such as 301 and 308, straight to the final destination. It suggests keeping redirects for as long as possible, generally at least a year, and says to expect temporary fluctuation in ranking during the move. It also warns against sending many old URLs to one irrelevant page such as the homepage.
If the site uses hreflang, update the annotations to the new addresses as part of the same release.
How we help B2B service firms
WorldWideBridge handles product testing, certification and market approvals across several regions. Its old site was slow and hard to edit, and years of indexed articles could not be lost. We rebuilt it as a fast static site in English, German, Spanish, Italian and Brazilian Portuguese. All 609 indexed articles kept their original addresses, and contact and callback forms post into the team’s Bitrix24 CRM.
For SolTech, a rooftop solar platform in the UAE, we built the site in English and Russian from the start. We prefer to agree the languages before design begins, because the longest translation decides how much room a heading or a button needs.
- Which pages does this market need first?
- Who will review the translation, and who will keep it current?
- Can the team reply to an enquiry in that language?
- Does every translated page link to its other versions?
- Which existing addresses must keep working?
Our market expansion work starts with those questions, before any page is translated.
