Home/Global practice/One brand, two market websites
Guide
Translating the whole site is the expensive mistake
The brand and the product truth travel. The proof, the pricing logic and the search structure do not, and those are the parts that convert.
Get a structure review See the services
- Share
- Brand, positioning, product truth
- Adapt
- Proof, references, pricing signals
- Build separately
- Search structure and content calendar
- Usually
- Subfolder, not separate domain
The four decisions
Taken once, in week one, and they save an enormous amount of argument later.
The top row is identical everywhere. The second row is where most companies over-share and under-adapt. The bottom two rows have to be built market by market.
Companies that translate everything and see poor results have almost always translated the untranslatable rows.
Structural decisions
Subfolder, subdomain or separate domain
Usually a subfolder, because it inherits domain authority and is simpler to maintain. A separate country domain makes sense when the business is structurally separate or a local domain carries trust weight.
Language versus market
These are different. A single English site can serve several markets; a market-specific site may still be in English. Decide the market first, then the language.
hreflang and canonicals
Set correctly so search engines serve the right version and the two do not compete with each other.
One content source
Product data, specifications and certifications maintained once and pulled into both. Numbers that disagree across sites damage credibility badly.
Separate search strategy
Different queries, different competitors, different content calendar. This is the part that is genuinely built rather than adapted.
Enquiry routing
By market, to someone who answers in the right hours and language.
When one site is enough
For many B2B exporters, a single well-structured English site with market-specific application pages serves several markets adequately and costs far less to maintain.
The case for separate market sites strengthens when local language is genuinely required, when the proof and reference set is entirely different, or when a local entity owns the market relationship.
Building three sites you cannot maintain is worse than one you can. That is a resourcing decision as much as a strategic one.
Questions overseas teams ask
Do we need hreflang?
If you have more than one language or market version, yes, and it is frequently implemented incorrectly. Wrong hreflang is worse than none.
Should the export site be in English or local language?
For B2B and industrial, English is usually sufficient and often preferred. For consumer, local language is generally necessary in Europe and optional in India.
Can we just translate the home site?
You can, and it will underperform for reasons unrelated to translation quality. The proof and the search structure have to be rebuilt.
Send me both URLs, or the one you have
I will tell you which of the four rows you are getting wrong, which usually explains the performance gap.
Get a structure review See case studies
Kunal Waghmare · Padmavati Hills, Mokai Vasti, Bavdhan, Pune, Maharashtra 411021, India
office@quiamo.com · +91 90216 02686 · English