The short answer: translate a complete journey, not a percentage
You do not need to translate the entire website by default. You need to cover the journey an English-speaking visitor must complete to understand an offer, decide whether it fits and take the next step without meeting an unexpected language barrier. If that journey crosses the homepage, service, evidence, terms and contact, those pieces belong together even if the blog and secondary services remain in the original language.
Translate the full site when both audiences need broadly the same information and the business can support, review and update both versions. Start with a bounded journey when you are testing a specific demand. Delay English when nobody can answer enquiries, deliver the service or maintain information in that language. A language selector does not create an international offer on its own.
Confirm a business need before commissioning translation
Look for evidence: enquiries already arriving in English, prospects dropping out because the process is unclear, partners sharing the site with another audience, planned campaigns or a service already delivered across markets. Visits from other countries are not enough on their own. They may represent residents, bots, informational searches or people the business cannot actually serve.
Then define the decision this audience must be able to make. Checking a service area, requesting an international proposal, booking an activity and receiving post-purchase support are different journeys. Language must follow the chosen decision to completion. If the website promises English service but confirmations, agreements or follow-up revert to another language without warning, the investment creates an expectation operations cannot meet.
- Demand: which real enquiries arrive, and from which page or channel?
- Offer: what specific service can this audience request or buy?
- Service: who responds before and after the purchase?
- Operations: can you deliver and resolve issues in that language?
- Maintenance: who updates prices, terms, people and messages?
Three valid scopes—and the limit of each
Priority journey: translate the pages required for one offer and one defined action. This can test demand or support a specific segment without duplicating the whole inventory. Its limit is continuity: it must not end in an unexplained form, document or response in another language.
Full website: adapt navigation, services, company information, relevant resources, forms and operational content. This suits businesses where both audiences use most of the site and long-term capacity exists. The cost does not end at launch; every future change needs a decision and review in both languages.
No English version yet: keep a strong website in the primary language and handle exceptional requests through an agreed channel. This is reasonable when demand is weak or operations are not ready. The limit is honesty—do not present automatic translation or scattered fragments as an experience the business cannot yet support.
Prioritise the journey, not the navigation menu
Draw three columns: entry, decision and continuity. Under entry, note how someone arrives—referral, search, advert, event or partner. Under decision, include the service explanation, scope, relevant evidence, questions, terms and action. Under continuity, include confirmation, contact, documents, support and later messages. Translate every essential part of one row before opening another.
An English homepage without its service page is a shop window without a product. A translated service with an incomprehensible contact step leaves the decision unfinished. Translating dozens of articles cannot compensate for inaccessible terms or follow-up. Google recommends content for an existing or intended audience and a useful purpose; priority should follow that audience's need, not an easy page-count target.
Three hypothetical businesses reach different answers
First, imagine a fictional architecture practice receiving two referrals a year from overseas firms. Meetings and documents can be handled in English. It translates its homepage, international service, process, relevant projects and contact route, while local news and domestic-only services remain in the original language. The journey answers the real enquiry without pretending the whole site is duplicated.
Second, consider a hypothetical tour operator that regularly serves English-speaking customers, takes bookings and sends instructions before each activity. One landing page would not be enough. The catalogue, availability, requirements, common questions, booking, confirmations, changes and support need adaptation. A broad English version fits because the operation already works in both languages.
Third, a fictional local installer notices overseas visits but only serves the local area and has no English support. It delays translation, records genuine enquiries for a period and prepares internal responses before investing. All three businesses may be making a sound decision. Scope follows the journey they can fulfil, not the size of the company.
What the multilingual proposal should contain
Ask for an inventory listing every page, language, content owner, adaptation method, reviewer and change frequency. The proposal should distinguish translation, localisation and new content. A fee, service area, unit of measure or example may require adaptation rather than literal replacement. Include forms, emails, downloadable documents, error messages, images containing words and structured information; they are part of the experience too.
The proposal should explain how versions connect without turning the purchase into a technical lesson. Google recommends separate URLs for each language, pages visibly written in one language and links that let people switch versions, while warning against automatic redirects that remove choice. web.dev notes that language declarations help screen readers and that layouts must handle different word lengths. These are acceptance checks, not surprise extras after launch.
- Page map and language pairings.
- Owners for translation, factual adaptation and approval.
- Forms, responses, documents and support included.
- Rules for adding, changing and retiring content.
- Checks for links, language, mobile layout and the complete journey.
When professional help is worthwhile
Bring in help when you cannot identify the priority journey, when translation affects prices, requirements, bookings or integrations, or when several people must maintain the versions. A web professional can turn the commercial decision into a page map and testable flow. An appropriate translator or language reviewer can adapt meaning and flag ambiguity. Neither replaces the business's own subject knowledge.
Before requesting a quote, provide three facts: the audience you want to serve, what they can commission and who will support them afterwards. If the boundary is unclear, ask for two options—the smallest complete journey and the broader version—with exclusions and maintenance for each. You can then compare an investment that solves a real need, rather than a price per word or a count of duplicated pages.
Sources and documentation
- Google Search Central: Managing multi-regional and multilingual sites ↗
- Google Search Central: Tell Google about localized versions of your page ↗
- web.dev: Internationalization ↗
- Google Search Central: Creating helpful, reliable, people-first content ↗
Content created with AI assistance. Check the sources, date and scope of each guide.