A localized site picks its version from several signals: the IP country, the browser language (Accept-Language), a saved choice such as a cookie or a language selector, and the URL itself.
A proxy changes only the IP country, so change one signal per test run and open each run in a fresh browser context.
Google says its crawler's default IPs appear to be in the USA and that it sends no Accept-Language, and it recommends separate locale URLs with hreflang. Rotating residential proxies start at US$1.50 per GB and cover 195+ countries and regions.
Example addresses (203.0.113.0/24), not real exits
01 / 09What decides the version a visitor sees
Which signals a localized site reads, how to change each one in a test, and what to check in the redirect and hreflang.
01
What decides the version a visitor sees
When a store redirects you to /de/ or shows euros instead of dollars, it has read one or more signals. The usual ones are the country of your IP address, the language your browser asks for, a choice you made earlier, and the URL you typed.
MDN describes Accept-Language as a hint that the server uses when it cannot tell the language otherwise, and says the server should never override an explicit user language choice. That gives you the rule to test: an IP or a header may suggest a version, but a visitor who picks one should keep it.
Use a proxy that exits in the market, and check the exit before the run
Browser language
The Accept-Language header and the browser UI language
Set the locale of the browser context, for example de-DE
Time zone
The time zone the browser reports
Set the time zone of the context, for example Europe/Berlin
Saved choice
A cookie, a stored selector value or a language in the URL path
Open every run in a fresh context, then test the selector on purpose
hreflang annotations
Alternate language and region URLs listed in the page head, headers or sitemap
Read the HTML or sitemap; this check needs no proxy
Sources: MDN and the Playwright emulation page, read on 20 November 2026. Whether a given site reads each signal is something you find out by testing it.
Pass 1: exit in the market with that market's browser language. Record the final URL, the page language, the currency, the prices, the consent banner and the forms. This is what a local visitor sees first.
Pass 2: exit in the market with a different browser language, for example a German IP with an English browser. Record what changes. The result tells you which signal your site trusts more, and whether the visitor can still reach the other language.
Pass 3: choose a language in the site's own selector, reload, and then reload through a different exit. The choice should stay. If the site sends the visitor back to the IP market, it is overriding an explicit choice.
Google says hreflang annotations must point to each other or they are ignored, and each page should also list itself. The fallback x-default is meant for visitors whose language does not match any listed version. Only ISO 639-1 language codes and ISO 3166-1 Alpha 2 region codes are supported, and you can give the annotations in HTML tags, HTTP headers or a sitemap.
Redirects by IP deserve one more check. Google says its crawler's default IPs appear to be in the USA, that it sends requests without Accept-Language, and that it also crawls from IPs outside the USA. If your site sends every visitor to one version by IP or language, confirm that each locale URL is still reachable. Google recommends separate locale URLs annotated with hreflang.
import os
from playwright.sync_api import sync_playwright
URL = "https://www.example.com/"
MARKETS = [ # country code, browser language, time zone
("DE", "de-DE", "Europe/Berlin"),
("FR", "fr-FR", "Europe/Paris"),
("JP", "ja-JP", "Asia/Tokyo"),
]
with sync_playwright() as p:
for cc, locale, tz in MARKETS:
browser = p.chromium.launch(proxy={
"server": os.environ[cc + "_SERVER"], # http://HOST:PORT from My assets
"username": os.environ[cc + "_USER"],
"password": os.environ[cc + "_PASS"],
})
context = browser.new_context(locale=locale, timezone_id=tz) # fresh context: no saved choice
page = context.new_page()
page.goto("https://ipinfo.io/json")
exit_info = page.inner_text("body")
page.goto(URL)
print(cc, "| exit:", exit_info.replace("\n", " ")[:120])
print(cc, "| final URL:", page.url, "| lang:", page.evaluate("document.documentElement.lang"))
browser.close()
Example only: replace the URL and the environment variables with your own. Each market uses its own proxy, browser language and time zone, and a fresh context.
06
How to do it with Proxy302
Step 1
Open the rotating residential page and generate one proxy for each market, choosing the country. The Budget line takes a country only; the Premium line also takes a state or city.
Copy HOST, PORT, USERNAME and PASSWORD from My assets for each proxy. Use the HTTP line on port 2222 for Playwright, which takes authenticated proxies over HTTP.
Step 3
For a flow with several pages, such as add to cart and checkout, set a session so the IP stays the same. Without a session, a rotating line gives each new connection a new IP.
Step 4
Run the script, read the exit country it prints for each market, and only then read the page results. If the exit is not in the market, fix that first.
07
When the result looks wrong
The site shows the wrong market for the exit
Check Open https://ipinfo.io/json through the proxy and read the country, then compare with another lookup. Databases can disagree about an address.
Fix Generate the proxy again for the country, or choose a state or city on the Premium line.
Stop when If two lookups still disagree, stop and note it in the test report instead of rerunning the same pass.
The language is right but the currency is not
Check Check whether the site reads the IP country, the language or a cookie for currency, using the three passes above.
Fix Record which signal sets the currency and report it as the site's rule.
Stop when Do not change several signals at once, or you cannot tell which one did it.
The first run redirects, the second does not
Check The first run probably saved a choice in a cookie.
Fix Use a fresh browser context for every run.
Stop when If a fresh context still differs between runs, test with a fixed session so the IP stays the same.
FAQ
How do I test a geo redirect?
Exit in the target market with a proxy, set the browser language to that market's, open the page in a fresh browser context and record the final URL. Then change one signal at a time to see which one the site follows.
Does a proxy change the browser language?
No. A proxy changes the IP country. Set the language and time zone on the browser context yourself, for example locale de-DE and time zone Europe/Berlin in Playwright.
Do I need a proxy to check hreflang?
No. hreflang lives in the page head, headers or sitemap, so you can read it directly. A proxy matters for redirects and content that depend on the visitor's country.
Why does Google see a different version than my users?
Google says the default IPs of its crawler appear to be in the USA and that it sends no Accept-Language, so a site that adapts by IP or language may show it a default version. Its advice is separate locale URLs annotated with hreflang.
How much does testing cost?
Rotating residential traffic on the Budget line costs from US$1.50 per GB, and a page check uses little traffic. There is no free trial: the smallest purchase is 1 GB.
Test your website from different countries: language, currency, prices, forms and redirects as local visitors see them. Residential IPs with country, state and major-city choice, HTTP and SOCKS5.
Geo proxies for testing: see your website as visitors in other countries and major cities see it — prices, language, banners — with matching locale and time zone.
Real household IPs in 195+ countries; the Premium line adds state and major-city targeting. A new IP on every new connection, or keep sticky sessions. From US$1.50/GB, US$1.35/GB at 100 GB. HTTP and SOCKS5.
Read on 20 November 2026: the default IP addresses of the Googlebot crawler appear to be based in the USA, the crawler sends requests without Accept-Language, it also crawls from IPs outside the USA, and Google recommends separate locale URLs annotated with hreflang.
Read on 20 November 2026: hreflang annotations must point to each other or they are ignored, each page should list itself, x-default is the fallback for unmatched users, only ISO 639-1 language codes and ISO 3166-1 Alpha 2 region codes are supported, and there are three equivalent ways to give the annotations (HTML tags, HTTP headers, sitemap).
Read on 20 November 2026: Accept-Language states the language and locale the client prefers and is a hint when the server cannot tell the content language otherwise; the server should never override an explicit user language choice; browsers may list only one language for privacy.
Read on 20 November 2026: a browser context takes locale (for example de-DE) and timezone_id (for example Europe/Berlin) options.
Proxy302 product facts and price list
Product observation · Confirmed on:
Product facts file of the site, checked 10 November 2026 against the console, the backend and the price table: per-IP lease prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, quantity limits, no free trial.
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.