First, compare the edition with home on the same page type and walk the visitor's path
Start by putting the edition and the home site side by side on the same page type and the same traffic source: paid search visitors landing on product pages, say, or paid social visitors landing on a campaign page. The conversion rate calculator gives the two rates, and the localising websites and campaigns guide asks for this comparison before spend is scaled, because a large gap on the same page type usually traces to price, payment, delivery or trust rather than to the ad. Split by device too. A gap only on phones is a layout or checkout problem; a gap for one campaign is a landing page problem; a gap that holds across every source, device and page type is a market problem, and the rest of this page is about those.
Then walk the path as a visitor from the market would: the ad, the page it opens, the price and what it includes, the payment methods, the delivery, duties and returns terms, the reviews and contact details, the headline and buttons, and the support page. At each step, note what looks foreign, missing or different from a local competitor. The expectation-disconfirmation framework explains why the walk finds the lost sale: the visitor judges every step against an expectation built from the ad and from the local shops they know, so an odd price ending, a tax that appears on the last screen or a missing wallet logo is the moment the page stops looking like somewhere people like them buy.
Two readings save time. First, check who is arriving: if the market's searchers reach the home edition, or the reverse, the diagnosis of the wrong country version ranking comes first, because nothing here helps until the right people reach the right edition. Second, read where visitors leave: at the landing page points at the first cause below, at payment or delivery at the second and third, browsing without adding anything at proof and copy. Traffic up and sales flat on a single site belongs to the general diagnosis of traffic up and sales flat, one page's bounce to the landing page bounce rate diagnosis, words that are the whole complaint to the page on translated marketing copy that reads wrong, and an edition flat inside a multi-market campaign to the page on a global campaign underperforming in some markets. The troubleshooting hub for international marketing lists the neighbouring symptoms.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Paid visitors leave the first page at once; the gap is largest for one campaign or channel | Click each live ad and read the page it opens, in the ad's language, against the ad's promise and offer | Ads in the local language landing on a home-market page, or a page that does not repeat the ad's promise and offer | Build a same-language landing page per campaign that repeats the ad's promise, offer, currency and search terms |
| Visitors reach product pages and leave; support asks why the price changed or what it includes | The price on the product page, the cart and the checkout, its ending, its format and whether tax is shown as local shops show it | Prices converted automatically, formatted the home way or shown without the tax convention the market expects | Set local price points inside the corridor with local endings, currency from the first page and the tax display the market expects |
| Carts are started and abandoned at payment or delivery; parcels refused; delivery contacts dominate support | The payment methods offered against what local shops offer; delivery, duties and returns wording against what is true for the market | Payment methods, delivery times, duties and returns terms not the ones the market expects or not stated | Add the methods people use and show them early; state delivery, duties and returns terms that operations can keep, the same everywhere |
| Visitors browse widely and buy nothing; the brand is unknown in the market | The reviews, client logos, press and contact details on the edition's core pages, and which country they come from | No local proof: reviews, clients and contact details all from another country | Gather local reviews and clients, show local contact details, and use proof that travels where none exists yet |
| The reviewer says the copy is correct, yet readers describe it as stiff or odd | Each persuasive asset's label on the spectrum and the brief it was commissioned from | Copy translated literally where it needed transcreation, so it reads as foreign | Transcreate headlines, taglines and ad copy from a brief by a native copywriter and rewrite around local search terms |
| Pre-sale questions go unanswered; satisfaction lags on the same contact reasons; complaints mention hours or language | The contact page's promised languages and hours against who answers, in which language, at which local times | Support promised in a language nobody answers, or hours published in head-office time | Publish the level of support each channel gives in each language, with hours in local time and an acknowledgement in the customer's language |
Fix, verify and prevent each cause
Ads in the local language landing on a home-market page
The localising guide names campaign landing pages as the place localisation most often fails, and the mechanism is the one the glossary entry for message match describes: a visitor decides within moments whether the page is the one the click promised. Abroad, message matchHow closely a landing page repeats the promise and wording of the ad or link that sent the visitor. also means the ad's language, currency, offer and search terms carry onto the page. An ad in the local language that opens the home-market category page breaks all of them at once.
Fix: build a landing pageThe page a visitor arrives on from a campaign, built to turn that visit into one action. per campaign in the market's language that repeats the ad's promise, offer and wording in its first screen, with local price, currency, proof and contact details; where a campaign cannot have its own page, send it to the edition's matching product or category page rather than to home.
Verify: click every live ad and read where it lands; then compare paid visitors' conversion rate by landing page and watch bounce on the new destinations fall against the same campaign before the change.
Prevent: brief the landing page with the ad, keep the destination in the campaign's copy document, and tick the launch checklist's landing page row before any spend.
Prices converted rather than set
The guide to setting and showing prices across markets explains why a converted price looks foreign: the ending is wrong, it drifts with the exchange rate, and it is often formatted the home way with the home tax convention. The guide accepts automatic conversion for testing demand, not for selling once the market matters, and asks for local currency from the first page, local formats, and tax shown as local customers expect, confirmed with local advice. A price that changes between page and cart, or tax added at the last step where shown prices normally include it, costs trust in both figures.
Fix: set a deliberate local price point inside the global corridor for each product, with the ending local shops use and checked against that market's own contribution margin; show it in local currency and format from the first page with what it includes; and agree an exchange-rate rule with finance so the price holds until the rate crosses a band.
Verify: walk from landing page to order confirmation and confirm the price never changes or gains a surprise; then read the market's support messages for price questions and watch conversion rateShare of visits or clicks that convert. on product pages against the earlier period.
Prevent: keep one source of truth for each market's prices, release every change to the site, feed, priced ads and emails together, and diary the band and review dates before the first movement.
Payment, delivery, duties and returns not what the market expects
The localising guide calls the payment methods people expect often a bigger lever on conversion than any copy change, because preferences vary widely between markets. It asks that delivery times, costs, duties and returns terms be true for the market, and names duties collected on delivery as a common cause of refused parcels and angry reviews. The guide to setting and keeping delivery promises adds the rule behind the wording: operations set the promise from their own dispatch and delivery records, marketing states it, and it reads the same on product pages, checkout, feed, ads and emails, with cost and date shown early.
Fix: add the payment methods local shops offer and show their logos early; set a delivery promise operations can keep on nearly every order, not an average day; state duties plainly where they apply and, where possible, include them in the price; and put the market's returns terms on the product page.
Verify: complete a test transaction with each payment method; confirm delivery cost and date match across product page, checkout and confirmation email; then read, by market, promises kept, refused parcels and the share of support contacts about delivery or payment, which the support guide treats as a site or offer problem that support is absorbing.
Prevent: keep each market's delivery promise as a short statement owned by operations, check every channel against it when it changes, and make payment, delivery and returns rows of the launch gate.
No local proof on the edition
A brand well known at home is unknown abroad, and the localising guide is direct about what that does to proof: reviews only from another country tell the visitor that people like them have not bought yet. The guide asks every edition's core pages to carry local proof, meaning local reviews, client logos, press and contact details that reach someone in the market's time zone and language, and applies the same test to imagery, because foreign-looking people, homes and streets say the page was made elsewhere.
Fix: gather local reviews deliberately, through a sampling campaign, an early-customer programme or a review request in the market's language; show the local clients, partners and press the market has; give the contact page a local address, phone number or at least a local-language route; and where none exists yet, lean honestly on proof that travels, such as independent certifications, recognisable international clients and a clear guarantee.
Verify: read the edition's home, category, product and contact pages as a first-time visitor from the market and count the local signals; then compare conversion for product page visitors before and after.
Prevent: make review gathering part of every launch plan, keep an approved local image library per market, and put the cultural check in the same in-country review that covers language.
Copy translated literally where it needed transcreation
The translation and transcreation guide places marketing copy on a spectrum: specifications, terms and help content are translated; most web and email copy is localised; headlines, taglines, ad copy and campaign ideas are rewritten from a brief by a native copywriter, which is transcreationRewriting marketing copy for another language or market from the original brief, so the intended effect survives even when the words change.. A headline sent for translation comes back accurate and lifeless. The guide also warns against translating keywords, because pages built on translated home-market terms miss the words people in the market actually search.
Fix: label every persuasive asset on the edition for transcreation, brief it with the objective, the market's audience and the single thought the reader should take away, and have a native copywriter rewrite it; rebuild headings and ad copy around terms researched in the target language.
Verify: have the named in-country reviewer read the rewritten pages in context, against the market rather than the source, and compare conversion on the same page type again once landing pages and prices are fixed, so the copy is judged on its own.
Prevent: label each asset on the spectrum in every localisation request, keep the termbase and style guide current, and check claims locally rather than translating them.
Support promised in a language nobody answers
The guide to supporting customers in several languages and time zones starts from two lines elsewhere on the site: the localising guide asks for contact details that reach someone in the market's time zone and language, and the launch checklist confirms support can answer in the local language. Its rule is that the level of support is a promise, chosen per market and channel and published: which channels answer in which languages, at what hours in the market's local time, and what happens outside them. A customer who writes in their language and gets an English reply, or is answered "within a day" while they sleep, has learned something about the brand before buying.
Fix: decide a level for the market, from full support by fluent speakers down to written support with translated replies reviewed by a fluent person, and say which on the contact page; publish hours in local time; send an automatic acknowledgement in the customer's language saying when a person will reply; and route contacts by language and market from the first touch.
Verify: write to the edition's contact address in the market's language during its working day and read what comes back and when; then report time to first reply in local hours and satisfaction by market.
Prevent: make the support level and hours a line in the launch gate, translate the most-asked help articles first, and review the contact page's promises whenever cover changes.
Prevention: the launch checklist before spend and a monthly edition-versus-home comparison
Most causes above are rows of the localising guide's per-market launch checklist, and the new market launch checklist wraps those site-level rows in the wider go-live gate that adds search, media, consent, reporting and support readiness. Run both before traffic is bought, not after the first month's report, and run them as a walk through the edition rather than as a form: open each campaign's ad and land where it lands, read the price on the first page and the last, try each payment method, read the delivery and returns wording, count the local reviews, read the headline aloud with the in-country reviewer, and write to the support address. The localising checklist assumes the language work has been signed off; the walk checks what the language review could not.
Three structural checks belong in the same pass because they decide whether visitors reach the right edition at all. First, each edition sits in the agreed structure and is tied to its alternates with hreflangAnnotation for language/region versions.; Google Search Central's documentation on managing multi-regional and multilingual sites, as the localising guide states it, describes the structure options and how alternates are signalled, and the localisation hub shows where that technical work sits beside the language and asset work. Second, nobody is forced onto an edition by location without a choice, because people travel, buy for other countries and use other editions deliberately. Third, the legal pages were reviewed for the market rather than translated from home; the localising guide records that in the European Union the GDPR sets the framework for processing personal data and that national rules add their own consent requirements, which is general direction and not legal advice, so terms, privacy and cookie pages need local review, not a translator.
Then make the comparison a habit. Once a month, put the edition and home side by side on the same page type, source and device with the conversion rate calculator. A gap that narrows after each fix is the edition catching up; one that opens again points at a change, most often a new campaign landing on the wrong page, a price release that reached the site and not the feed, a promotion copied from home, or a delivery promise lengthened without the page being updated. Read the market's support contact reasons in the same sitting and send a pattern of delivery, payment or price questions to the market owner, as the support guide asks.
Finally, keep ownership plain. The market owner owns the edition's price point, offer and proof; operations own the delivery promise; the in-country reviewer owns language and the cultural check; the market's compliance owner owns the legal pages and claims. When the walk finds a broken promise, the fix goes to its owner and the checklist row is re-ticked. A market still flat after the whole path is fixed, with the right people arriving and the right offer shown, has a demand or positioning problem rather than a conversion problem, which is a question for the market's roadmap rather than a page to repair.
An ergonomic chair maker finds its checkout looked foreign (illustrative)
Wrackenby Seating
Wrackenby Seating, an invented maker of ergonomic office chairs, launches an edition for a new market and buys search and social traffic for 10 weeks. The edition receives 48,000 visits in that time and converts at 0.4% against 2.1% for the home site on the same product pages. The copy had passed in-country review a month before launch, so the market owner walks the path instead of reopening the translation.
The walk finds five broken promises. All 14 search ads land on the home-market category page, in the right language but with the home currency. Product prices were converted at the day's rate and show endings such as 417.63, with tax added only at checkout in a market where shown prices normally include it. The checkout offers cards and one wallet, while the three local competitors the owner checks all offer the bank-transfer method most shoppers there use. The delivery page says nothing about duties, and 31 of the first 190 parcels were refused on delivery when a duty was charged at the door. Every review on the edition is from the home country.
Wrackenby builds 6 same-language landing pages that repeat each ad's offer in local currency, sets local price points ending the way local shops end them with tax included on the page, adds the bank-transfer method and shows its logo on the product page, adds a one-line duties statement and includes the duty in the price for the two best-selling chairs, and runs a sampling campaign that gathers 52 local reviews in 6 weeks. It reruns the launch checklist with the support line added, publishes the market's support hours in local time, and sets a monthly comparison with the home site on the same page types. Over the following 10 weeks the edition converts at 1.6% on the same product pages, refused parcels fall to 3, and delivery questions fall from 44% of the market's support contacts to 12%.
Common mistakes
- Reopening the translation when the copy passed review. The words were checked; the price, the checkout and the proof were not.
- Comparing the edition with home across all traffic. Cold social traffic trails returning customers. Compare the same page type, source and device.
- Ads in the local language, landing pages at home. The promise breaks at the click, before anything else on the edition gets a chance.
- Leaving converted prices in place. Odd endings, a drifting rate and tax added at the last step look foreign. Set local points once a market matters.
- Letting marketing write the delivery promise for the market. Operations set what can be kept; the page states it, duties included.
- Treating home-country reviews as proof. They tell the visitor that people like them have not bought yet.
- Publishing hours in head-office time. The customer reads them in their own time and concludes nobody is there.
- Fixing the path once and never walking it again. A new campaign, a price release or a lengthened promise reopens the gap quietly; the monthly comparison is what catches it.
