Language and regional website planning
One English website or localized versions?
Use one English-language website when your intended customers can make an informed buying decision in English and the offer is substantially the same. Consider language versions when the audience needs another language. Consider regional versions when the service, buying journey or essential information genuinely differs by country or region.
Those decisions can overlap. The right starting point is the information your customers need and your ability to keep it accurate, not the number of flags you could add to a menu.
Language, region and currency answer different questions
Google distinguishes multilingual sites, which offer more than one language, from multi-regional sites, which address different countries. A site can do both. Google's international-site guidance.
The table scrolls sideways on smaller screens.
| Choice | The question it answers | What it does not establish |
|---|---|---|
| Content language | Can this reader understand the offer and take the next step? | Where you have an office or can legally supply a service. |
| Regional content | Does this version explain the offer that applies in this market? | That every other page needs a duplicate for the same place. |
| Display or billing currency | What amount is shown or paid, and in which currency? | A translated buying journey, local support or country-specific search visibility. |
| Service area | Where can the business actually deliver? | That the page must be written in a different language. |
For example, an English-speaking consultancy may offer the same remote service to buyers in several countries. One clear site may cover that offer well. A manufacturer may need different specifications, distributors or availability by market even when all the pages use English. These are illustrative situations, not customer case studies.
Start with three decisions
1. Can the buyer use English throughout the journey?
Look beyond the headline. Consider the service explanation, examples, enquiry form, confirmation message, documents and the response that follows. A translated landing page creates an expectation that the next step will also be understandable.
Use real evidence where you have it: customer questions, the languages used in enquiries, your sales team's experience and relevant first-party search data. When that evidence is missing, record the uncertainty. A country's population alone does not tell you the language preference of your particular buyers.
2. What actually changes between markets?
Write down the differences before choosing a URL structure. They might concern availability, product names, units, delivery methods, a regional contact or approved terms. A different currency symbol alone is a much smaller requirement than a separate regional sales operation.
If the same answer serves everyone, keep one useful answer. If a buyer needs a different answer, give that information a clear home. A regional page should explain the actual service coverage and information that helps someone buy in that market.
3. Who can maintain each version?
Name someone who can approve the language and someone who can approve the business facts. Decide how an update to pricing, scope or a contact route reaches every affected version. Include forms, messages and downloads in that responsibility.
A translation that was correct at launch can become misleading when the underlying offer changes. Maintenance belongs in the scope before extra versions are commissioned.
Choose a scope your business can support
The table scrolls sideways on smaller screens.
| Your situation | A useful starting scope | What must be resolved before expanding |
|---|---|---|
| The audience uses English and receives the same offer | One English-language site with clear service coverage and buying information. | Evidence that another language or regional answer is needed. |
| Customers need another language, while the service is the same | A defined set of translated pages and a complete route to the next step. | Qualified language review, translated forms/messages and an update owner. |
| The offer or fulfilment differs by country | Specific regional content for those real differences. | Which pages differ, which stay shared, and who confirms local facts. |
| Both language and offer vary | A map of the actual language/market combinations you will maintain. | Coverage, review capacity, version relationships and ongoing cost. |
| You are testing an audience with little evidence | A bounded first version based on the buyers you can serve now. | What observation would justify a further version and who will evaluate it. |
This is a decision framework, not a rule that every international business must translate. A smaller, accurate scope can be a better first step than a wide collection of pages nobody owns.
What to ask the website provider to implement
Separate versions need deliberate navigation and search handling. Ask for the actual page map and a demonstration of switching versions before approving the work.
Google recommends separate URLs for language versions and links that let people choose between them. It cautions against automatically redirecting people based on an assumed language or location, because users and crawlers may be prevented from reaching other versions. A visitor's apparent country should not be treated as proof of the language or market they want. Google's guidance on language versions and user choice.
For real language or regional alternatives, hreflang can identify the relationship between pages. Ask the provider to check the supported language/region values, each page's self-reference and return links between alternatives. A country code alone is not a language code, and adding annotations does not create the content or guarantee a search result. Google's localized-version documentation.
HTML's lang attribute identifies the language of the document or a passage. It is part of presenting content correctly to software that uses language information; it is not a substitute for writing or reviewing a translation. W3C language declaration guidance.
The table scrolls sideways on smaller screens.
| Ask to see | What you should be able to verify |
|---|---|
| A page/version map | Every proposed version has a purpose and an owner; shared pages are identified. |
| A version selector | You can choose the intended language or region without being forced back elsewhere. |
| The complete enquiry journey | Labels, validation, confirmation and the business response make sense to the intended reader. |
| A representative long-content page | Real translated text fits the design, navigation and mobile layout. |
| An update example | The provider can explain which versions change when the business changes one fact. |
| Search implementation notes | Alternate URLs, canonical decisions, internal links and sitemap coverage have been considered together. |
Give every additional version an owner
Copy this small record for each proposed version. An empty answer identifies work to agree; it is not approval to fill the gap automatically.
The table scrolls sideways on smaller screens.
| Decision | Your answer |
|---|---|
| Intended audience and the service they can buy | |
| Language and region, if region matters | |
| What differs from the shared version | |
| Pages, forms, messages and downloads in scope | |
| Person approving the language | |
| Person approving business and technical claims | |
| Who receives and answers enquiries | |
| Who maintains the version after launch | |
| Evidence that would justify the next version |
For a larger procurement, attach these records to a common set of website RFP requirements. That lets each provider quote the same actual work.
Questions that often change the scope
Do we need a separate domain for every country?
Not automatically. Agree the audiences and meaningful content differences first, then ask the provider to explain the proposed address structure and its maintenance implications. Buying extra domains does not resolve missing content, delivery capability or language review.
Can we translate only the homepage?
You can commission a limited set of pages, but be explicit about where that journey ends. A reader should know if the enquiry response, documentation or service is available only in English. Include those transitions in the review instead of implying a fully translated service.
Can automated translation remove the review work?
It can be part of a drafting workflow, but someone still needs to confirm meaning, terminology and the business commitments being made. Ask who accepts responsibility for the final wording and for later updates. A generated version is not evidence that a service is available in that language.
Will more language versions guarantee AI visibility?
No. Versions should serve a real audience need. Google's current AI-search guidance applies ordinary search foundations rather than special AI markup or text-file requirements, and inclusion is not guaranteed. Google's AI-feature guidance.
Decide the first version before buying every version
UpOnUp creates English-language business websites for international audiences. Tell us who needs to use the site, which market differences are real and what material or reviewers you already have. Multilingual publishing and region-specific functionality need an explicit scope agreement; this guide is not a promise that every translation or local service is included.
Discuss your website scope · Explore international website design · Prepare the website brief