Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

International Marketing › Localisation

Localising Websites and Campaigns

How to localise a website and its campaigns: site structure, local landing pages, currency, payment and legal content, imagery, and campaign assets by market.
Guideintermediate9 min readUpdated

One site or many: structure options in brief

The first asset decision is where each market's pages live. The options are well established, and Google Search Central's documentation on managing multi-regional and multilingual sites describes how search engines treat each. The detailed trade-offs, and how to signal language and region, belong to the international SEO section; this summary covers the marketing consequences.

StructureMarketing strengthMarketing costFits when
Country-code domain per marketStrong local signal and trust; clear separation for legal and pricingEach domain built, maintained and promoted separatelyMarkets are large, offers differ, or a local entity sells
Subdomain per marketSeparation with one brand domain; can be hosted separatelySome separation of authority; more operational overheadMarkets run on different platforms or by different teams
Subdirectory per market or languageOne domain, shared authority, simplest to maintainLess local signal; one platform must handle every market's needsMost businesses entering their first few markets
One page with language switcher onlyCheapestCannot vary prices, offers or legal content by countryContent sites with no commercial difference between markets

Two marketing rules sit on top of the technical choice. First, separate editions by market when the offer differs (price, payment, delivery, legal), not only by language; a French-language edition for France and one for Belgium or Switzerland may need different prices and legal content even when the copy is shared. Second, do not redirect visitors automatically based on location without letting them choose; people travel, use VPNs and buy for other countries, and a forced redirect makes the other editions unreachable for them and for search crawlers alike.

Whatever the structure, each edition must be tied to its alternates with hreflang so that search engines show the right version to the right audience, and the hreflang guide covers its implementation. The localisation task is to keep the set complete: every new localised page added to every edition's alternates when it goes live.

Local pages, landing pages and message match

The pages that need local work fall into three groups. Core pages (home, category, product, pricing, about, contact) must exist in every market edition and carry local proof: reviews from local customers, logos of local clients, local press and contact details that reach someone in the market's time zone and language. Market-specific pages exist only where a market needs them, such as a page explaining a local payment option, a local regulation or a local partner. Campaign landing pages are built for traffic from paid and email campaigns.

Campaign landing pages are where localisation most often fails. An ad written in the local language that lands on the home-market page breaks the promise the ad made, and the visitor leaves. The principle of matching the landing page to the ad's promise, wording and offer is covered in the message match guide; internationally it adds a requirement that the page be in the same language, show the same currency and offer as the ad, and use the same search terms the ad was written around. The keyword work done in the translation and transcreation guide feeds both the ad and the page, which is why language and asset work have to share one term list. The research that produces that list is set out in the tutorial on keyword research for a new market.

Local proof matters more abroad than at home, because the brand is unknown. A page with reviews only from another country tells the visitor that people like them have not bought yet. Where local proof does not exist yet, say so honestly and use proof that travels: independent certifications, security standards, recognisable international clients and a clear guarantee.

These are the details that decide whether a visitor who wants to buy can buy, and they rarely appear in a translation brief because they are not language. A localisation brief gives them a row of their own, so the currency, sizes, delivery, returns and legal requirements reach the people producing each page.

Currency and price. Show prices in the local currency from the first page, not only at checkout, and make the charged currency explicit. Format prices the local way (symbol position, decimal and thousands separators), and state whether taxes are included in the way local consumers expect; in some markets displayed prices conventionally include tax and in others they do not.

Payment. Payment preferences vary widely between markets. Cards dominate in some; bank transfers, local wallets, buy-now-pay-later services or cash on delivery matter in others. Offering the methods people expect is often a bigger lever on conversion rate (CVR) than any copy change, and the checkout should show those methods' logos early, because recognition reassures.

Delivery and returns. State delivery times, costs, duties and returns terms that are true for the market. Duties collected on delivery are a common cause of refused parcels and angry reviews; if they apply, say so and, where possible, include them in the price. Each market's delivery promise should be one operations can keep, stated the same way on pages, feeds and emails, as the guide to setting and keeping delivery promises sets out.

Legal content. Terms, privacy notices, cookie notices, imprint or company-information requirements and consumer-rights wording differ by jurisdiction. In the European Union, the General Data Protection Regulation sets the framework for processing personal data, and national rules add consent requirements for cookies and direct marketing. These pages need local legal review, not translation of the home versions. This is general direction, not legal advice.

Imagery, colour and cultural checks

Imagery tells a visitor whether a brand understands their world faster than any copy. Stock photography of people, homes, streets, weather, food and money all carry local signals. A page whose people, settings and everyday objects all look foreign tells the visitor the page was made elsewhere, even when the copy is flawless.

A cultural check reviews each localised asset for meaning beyond words. Colours carry different associations in different cultures; gestures, animals, numbers and symbols can be neutral at home and loaded elsewhere; dates and seasons may be reversed; holidays and shopping peaks differ; and some product categories, body imagery or alcohol references are restricted by law or custom. The check is done by an in-country reviewer who looks at the asset in context, and it should be part of the same review that covers language so it adds no extra round. The tutorial on reviewing localised copy in a language you do not speak sets out what the central owner checks alongside that reviewer without reading the language.

Practical routines help. Keep a library of approved local imagery per market so creative teams do not reach for home-market stock. Record the findings of each cultural check in the market's style guide, so the lesson is learned once. Design layouts that tolerate text expansion and right-to-left scripts where needed, because many languages run longer than English and a layout built for short English headlines breaks when localised.

Localising paid campaign assets and tracking

Paid campaigns are where localised pages earn or waste money, so the assets need the same care. Ad copy is transcreated rather than translated, as the sibling guide explains, and written around the local search terms. Creative is adapted for local imagery and formats, and offers are set per market rather than copied from a home promotion that may not make sense locally (a seasonal sale in the wrong season, a free-delivery threshold in the wrong currency).

Tracking must separate markets from the first click. Use a consistent UTM convention that records the market alongside source, medium and campaign, so analytics can attribute traffic and conversions to a market without guessing from location data. Campaign names should follow a naming standard that includes the market code. Conversion events should fire on every market edition, including on localised thank-you pages that are easy to miss.

Before scaling spend, compare each market's landing pages with the home equivalent on conversion rate; the conversion rate calculator is enough for a first comparison. A large gap usually traces back to price, payment, delivery or trust content rather than to the ad. When an edition that has passed review still converts far below home, the diagnosis of an international site edition that is not converting walks the visitor's path cause by cause. How media is chosen for each market and how results are reported across markets are covered in the operations section, and search engine optimisation (SEO) for the same pages is covered by the international SEO section.

A per-market launch checklist

Run this list for every new market edition before traffic is bought. It assumes the language work has been signed off.

AreaCheck
StructureEdition sits in the agreed structure; no forced geo-redirect; language and market selector works
AlternatesEvery page added to the hreflang set of every other edition
Core pagesHome, category, product, pricing, about and contact exist and carry local proof and contact details
PricesLocal currency throughout; local formats; tax display matches local convention
PaymentExpected local methods offered and shown early; test transactions completed
Delivery and returnsTimes, costs, duties and returns terms true for the market
LegalTerms, privacy, cookie and company information reviewed for the jurisdiction
ImageryCultural check passed; local imagery used; layout survives text expansion
Landing pagesEach campaign has a same-language page matching the ad's promise and offer
TrackingUTM convention includes market; conversion events fire on the edition

These site-level checks sit inside the wider new market launch checklist, which adds search, media, consent, reporting and support readiness to the same go-live decision.

Illustrative example — not a real result

A skincare brand finds its conversion gap in checkout

Saltmarsh Botanicals, a UK skincare brand, launched a German edition in a subdirectory and spent £15,000 on search and social ads in its first two months. Traffic arrived as planned, but the German edition converted at 0.9% against 2.6% for the UK site. The copy had passed in-country review, so the team ran the launch checklist again. The checkout offered cards and one wallet, while the brand's research showed many German shoppers expected to pay by invoice or bank transfer; prices were shown with tax added at checkout; and the landing pages carried only UK reviews. After adding invoice payment, showing tax-inclusive prices and featuring 40 German reviews gathered from a sampling campaign, the edition converted at 2.0% over the next two months.

Common mistakes

  • Localising by language instead of by market. One edition for every speaker of a language ignores differences in price, payment and law. Separate editions by market where the offer differs.
  • Forcing geo-redirects. Visitors and crawlers lose access to other editions. Suggest the local edition and let people choose.
  • Ads in the local language, landing pages in English. The promise breaks at the click. Build same-language landing pages that match the ad.
  • Converting prices automatically and leaving them. Odd prices that drift with exchange rates look foreign. Set local prices once a market matters.
  • Translating the legal pages. Home-market terms translated into another language are still home-market terms. Get local review.
  • Home-market stock imagery everywhere. It tells visitors the page was made elsewhere. Build an approved local image library.
  • Tracking without a market dimension. Without a market in the UTM convention and campaign names, reports guess at market from location data. Record the market at the source.

Frequently asked questions

Do we need a separate site for every country?

Not usually. Many businesses serve several markets from one domain with a subdirectory per country or language, which keeps authority and maintenance in one place. Separate country domains make sense when local trust, legal entities or very different offers justify the extra cost, and the international SEO section covers the trade-offs in detail.

Should prices be converted automatically or set per market?

Automatic conversion is a reasonable start for testing demand, but it produces awkward prices that look foreign and drift with exchange rates. Once a market matters, set local prices deliberately, ending in the way local prices usually end and reflecting local taxes, delivery costs and competitors. Show the currency the customer will be charged in, throughout the journey.

Can one global campaign be run with translated ads?

It can, but translated ads pointing at a home-market page usually underperform. Each market's ads should use the terms local people search for and land on a page in the same language that repeats the ad's promise, with local prices and delivery. The central team can own the concept while each market owns the final copy, offer and landing page.

Terms used on this page

Tools to try

Where this page is used

Also related

Sources

  1. Managing multi-regional and multilingual sites — Google Search Central
  2. Regulation (EU) 2016/679 (GDPR) — EUR-Lex

Related