Geo Proxies for Testing: See Your Website from Different Countries

Why geo testing needs local IPs

Sites that adapt to the visitor's location — prices, currency, language, banners, legal notices — decide largely by IP. Cloudflare, for example, adds the visitor's country to every request it forwards, in a CF-IPCountry header, once the site turns on IP geolocation — so the site can branch on it.

That's why you can't QA another market from your office, and why search engines can miss it too: Google says Googlebot's default IPs appear to be in the US and that it may not crawl, index or rank every locale version of a page that adapts by location. Google recommends separate locale URLs with hreflang instead.

Location is more than the IP. Browsers also send a language (Accept-Language) and expose a time zone, so a test that changes only the IP can still get the default language. Change IP, locale and time zone together — Playwright sets locale and timezoneId per browser context.

• Cloudflare docs — IP geolocation (CF-IPCountry header)
• Google Search Central — Locale-adaptive pages
• Playwright docs — Emulation: locale and timezone

Recommended geo testing setup

Scroll horizontally with the arrow keys to read all content.

The button below opens Rotating Residential Proxies with the AI and automation use case. Pick the country and city for each market before you generate.

• Proxy302 console — Rotating Residential Proxies
• Proxy302 pricing

Which Proxy302 proxy to buy

Scroll horizontally with the arrow keys to read all content.

Prices in US dollars. Top up your wallet once and pay any line from it. Nothing renews automatically — renew in My assets to keep an IP.

• Proxy302 pricing

Set up geo testing in 5 steps

1. Open the setup and buy traffic

   The button below opens Rotating Residential Proxies with the AI and automation use case. Choose a Line, then open Add traffic and buy a package or a Custom GB (from 1 GB).

2. Generate one proxy per market

   Under Connection settings set Exit mode to Choose region / sticky IP, pick Region, State and City, keep Protocol on HTTP and click Review cost and generate. Repeat for every market you test.

3. Copy the lines

   In My assets, Copy each proxy and store it as PROXY_US, PROXY_DE, PROXY_JP in the form http://USER:[email protected]:2222.

4. Run the script

   The code below opens the same URL once per market in its own context, with that market's locale and time zone, and saves a screenshot.

   Expected result One screenshot and page title per market; the language matches the market.

5. Compare and file bugs

   Put the screenshots side by side. When a market shows the wrong price, language or banner, note the exit IP from My assets so the team can reproduce it.

Screenshot a page from three markets (Playwright, Node.js)

Scroll horizontally with the arrow keys to read all content.

// npm i playwright   then   npx playwright install chromium
import { chromium } from 'playwright'

const url = 'https://www.example.com/pricing'
// One Proxy302 exit per market (Exit mode "Choose region / sticky IP"), with matching locale and time zone
const markets = [
  { name: 'us', proxy: process.env.PROXY_US, locale: 'en-US', timezoneId: 'America/New_York' },
  { name: 'de', proxy: process.env.PROXY_DE, locale: 'de-DE', timezoneId: 'Europe/Berlin' },
  { name: 'jp', proxy: process.env.PROXY_JP, locale: 'ja-JP', timezoneId: 'Asia/Tokyo' },
]

const browser = await chromium.launch()
for (const m of markets) {
  const { host, username, password } = new URL(m.proxy) // http://USER:PASS@HOST:PORT
  const context = await browser.newContext({
    proxy: { server: `http://${host}`, username: decodeURIComponent(username), password: decodeURIComponent(password) },
    locale: m.locale,
    timezoneId: m.timezoneId,
  })
  const page = await context.newPage()
  await page.goto(url)
  await page.screenshot({ path: `pricing-${m.name}.png`, fullPage: true })
  console.log(m.name, await page.title())
  await context.close()
}
await browser.close()

Checked on 2026-10-18 with Playwright 1.63.0 and Chromium 153 against a local page that echoes the browser language: each context reached it through its proxy with its own Accept-Language (en-US, de-DE, ja-JP) and saved a screenshot.

• Local proxy fixture run
• Playwright docs — Emulation: locale and timezone

Quick fixes

Geo testing proxy FAQ

Related setups

Landing page testing proxies

Test your website from different countries: language, currency, prices, forms and redirects as local visitors see them. Residential IPs with country, state and city choice, HTTP and SOCKS5.

View options and pricing

Uptime monitoring proxies

Uptime monitoring proxies: check your website from different countries on fixed datacenter IPs and alert only when two or more locations fail.

View options and pricing

SERP proxies

SERP proxies for rank tracking: check Google results from the searcher's country and city on household IPs, validate every page and record captchas as unknown.

View options and pricing