Localization Testing With a Proxy: Check Each Market Yourself
Contents

- What does localization testing have to catch?
- What changes with the address, and what does not?
- Why keep one fixed address per market?
- How do I run the same check in every market with Playwright?
- How do I tell a localization bug from an A/B test?
- When do you still need a tester in the market?
- Where does ProxyJam fit?
- Quick answers
In short: Localization testing checks that each market gets its own currency, language, tax display, consent banner and redirects. The server reads the IP address; page scripts read the browser’s language and time zone. So a test needs a proxy in the market and a browser context set to its locale and time zone. Keep one fixed address per market, and leave translation quality and real payments to a tester there.
Localization testing asks one question per market: does a visitor there get the version of your site that was built for them? Translated strings are only part of it. The price has to be in the right currency with the right tax treatment, the consent banner has to be the one planned for that market, and the redirects have to land on the market’s own pages. Most of that is decided from where the visitor connects, so you cannot see it from your own desk. This guide is for teams checking their own site, the job our region testing page describes. It gives a checklist for each market and a Playwright script that runs it the same way every time.
What does localization testing have to catch?
Anything the site changes by market, and the faults that appear when two of those changes disagree. The table “What to check in each market, and what decides it” lists six items. Three of them cause most of the trouble.
- Currency, price and tax. A price can be correct in one currency and wrong in another, and markets differ in what the shown total includes. EU rules expect consumers to see the total price, “including all taxes and additional charges” (Your Europe). Check the product page and the checkout, because a total that is right on one can be wrong on the other.
- Consent banners. Many sites show a cookie banner in some markets and not in others, or offer different choices. The consent tool usually decides from the address, so a banner that is wrong for one market is invisible from every other.
- Redirects. A site that sends visitors to a market version can send them to the wrong one, or bounce them between two. Record every hop with its status code, along with the page where the browser stopped.
Language matters too, and it fails in a quieter way: a page served in the right language with the wrong market’s prices looks finished until someone reads the numbers.
What changes with the address, and what does not?
The server and the CDN in front of it see the IP address and look it up in a
geolocation database. Currency, consent and redirects are usually decided
there. The browser carries the rest. It sends an Accept-Language header
built from its language settings, which servers use as a hint for the language
to serve
(MDN),
and page scripts read the locale and the time zone through the Intl API
(MDN).
Date formats, number formats and delivery cut-off times come from that side.
A proxy changes only the address. Route a browser through
Germany and leave its locale on English (US), and a
site may show euro prices with US dates, a page no visitor in Germany is ever
served. So set three things for every market: the address, the locale and the
time zone. Playwright sets the last two per browser context: its locale option
“will affect navigator.language value, Accept-Language request header value as
well as number and date formatting rules”, and timezone_id changes the time
zone of the context
(Playwright API).
Why keep one fixed address per market?
A comparison means something only when one thing changes at a time. If the address changes between Monday’s run and Thursday’s, a different price can come from the site or from a different geolocation record for the new address, and you cannot tell which. A static address keeps the vantage point the same across runs, so a difference points at the site.
The address can still move, because geolocation databases are updated, and lookup services can disagree about one address; what is my ISP explains why for the network it is on. So the checklist “Check these on every market, every run” starts with the address: open What Is My IP through it and confirm the country before trusting a result. Holding one address and drawing from a rotating pool are compared in ISP vs residential proxies.
How do I run the same check in every market with Playwright?
Give each market its own browser context with its own proxy, locale and time
zone, open the same list of pages in each, and save what you see. This Python
script does that for four markets in the catalogue:
Germany, France,
Japan and Brazil. Each market
reads its proxy from three environment variables, such as PROXY_DE
(http://HOST:PORT), PROXY_DE_USER and PROXY_DE_PASS, so that no password
sits in the file. The example address in the comment comes from a range
reserved for documentation
(RFC 5737).
import json
import os
from datetime import date
from pathlib import Path
from playwright.sync_api import sync_playwright
MARKETS = {
"de": {"locale": "de-DE", "timezone_id": "Europe/Berlin"},
"fr": {"locale": "fr-FR", "timezone_id": "Europe/Paris"},
"jp": {"locale": "ja-JP", "timezone_id": "Asia/Tokyo"},
"br": {"locale": "pt-BR", "timezone_id": "America/Sao_Paulo"},
}
PAGES = {
"home": "https://example.com/",
"pricing": "https://example.com/pricing/",
}
OUT = Path("runs") / date.today().isoformat()
def redirect_chain(response):
hops = []
request = response.request.redirected_from
while request:
hops.insert(0, request.url)
request = request.redirected_from
return hops
with sync_playwright() as p:
browser = p.chromium.launch()
for market, settings in MARKETS.items():
key = market.upper()
context = browser.new_context(
proxy={
"server": os.environ[f"PROXY_{key}"], # http://203.0.113.10:8080
"username": os.environ[f"PROXY_{key}_USER"],
"password": os.environ[f"PROXY_{key}_PASS"],
},
**settings,
)
page = context.new_page()
folder = OUT / market
folder.mkdir(parents=True, exist_ok=True)
records = []
for name, url in PAGES.items():
response = page.goto(url, wait_until="load")
page.screenshot(path=folder / f"{name}.png", full_page=True)
records.append({
"page": name,
"status": response.status,
"redirects": redirect_chain(response),
"final_url": page.url,
"html_lang": page.evaluate("document.documentElement.lang"),
})
(folder / "run.json").write_text(json.dumps(records, indent=2))
context.close()
browser.close()
Each run leaves a folder per date and market, holding a full-page screenshot of
every page (Playwright: Screenshots)
and a run.json with the status code, the redirect chain, the final URL and
the page’s declared language. The chain is rebuilt from each request’s
redirected_from
(Playwright API).
A new context starts with no cookies, so every run looks like a first visit.
To test what a returning visitor sees, keep a context’s storage between runs
and say so in the record. How the proxy object works in Playwright, including
per-context proxies and SOCKS5, is covered in the
Playwright integration guide, and the manual
version of the same check in Chrome is in
viewing your website from another country.
Before the first real run, add a page that echoes the exit address to PAGES
and confirm that each context leaves from the market’s address.
How do I tell a localization bug from an A/B test?
Run the same market twice from the same address with fresh contexts, and compare. An A/B test shows different variations to different visitors, and Google’s documentation describes three ways a site assigns them: a cookie, a redirect to a variation URL, or a script that decides which one to display (Google Search Central). A fresh context has no cookie, so it can be put in a different variation each time.
- The difference comes and goes between runs with the same address, locale and time zone: most likely an experiment. Ask the team that runs it which pages are in a test, or check the testing tool’s cookie in the context.
- The difference holds in every run for one market: most likely a localization bug. Compare with a market that is right, and look up which signal decides the item in the table.
- The difference appeared after the address changed: retest after the What Is My IP check before filing anything.
When do you still need a tester in the market?
A script sees what the site serves to an address in the market. It cannot judge two things.
- Translation quality. A screenshot proves a page is in Japanese. Whether the Japanese reads naturally, uses the right terms and fits the buttons takes a native speaker.
- Payment flows. You can check the checkout up to the choice of payment method: which methods are offered, in which currency, with which total. A real purchase with a local payment method belongs to a person in that market, or to your payment provider’s test mode.
Support channels, delivery promises and local legal text sit in the same group: the script can show that they are there, and a person in the market tells you whether they are right.
Where does ProxyJam fit?
ProxyJam sells static residential (ISP) proxies: an address in the country you choose, on an internet provider’s network, that stays yours for the period you paid for. For localization testing that means one address per market, kept for as long as you compare runs. Testing by region and quality assurance are among the uses that need no prior review under section 2 of our Acceptable Use Policy. The catalogue covers 76 countries on the ISP proxies page, with prices per IP per period on the pricing page. If an address starts to geolocate outside the country you bought, a free replacement is available within the monthly limit set in section 2.5 of the Terms of Service.
Addresses are sold by country, and the city an address geolocates to is not promised, so a difference between two cities in one market is beyond what this setup can show. A team that needs many addresses in one market at the same moment is better served by a rotating residential pool, which ProxyJam lists as Coming soon.
