Test a Website From Different Locations With a Proxy

A product page in Berlin can look nothing like the same page in Boston. The price, currency, language, cookie banner and ads can all change, and your office IP will never show you any of it.

Key takeaways

• Set the test location with the country tag in the proxy username, and copy the exact tag format from the client area because names can differ by plan.
• Check the exit IP and country with the What's My IP tool before reading any page, and note which tool you used since IP location databases can disagree.
• Use a clean browser profile for each location, because a proxy changes the IP only and old cookies, consent choices and currency settings can change what the page shows.
• Add a 10-minute session tag for checkouts, multi-page forms and logged-in QA on sites and accounts you own or are authorized to test, since default rotation changes the IP mid-flow.
• Log price, language, redirects, banners, ads and region notices per page and per location, and treat a block or an unchanged page as a result, not a failure of the method.

A proxy closes that gap. You route a browser or test script through an exit IP in the target country, then read what a visitor there actually gets.

This guide works one example from start to finish: a first-time visitor in Germany landing on a product page. You will end with a verified German exit, a clean browser profile and a record format you can reuse for every other location.

Set Up a Country-Specific Testing Proxy and Confirm the Exit First

Before the first connection, gather four things: an active ColdProxy plan, its connection details from the client area (gateway, port, username and password), the page URL, and a browser or script to drive the test. Start the German example on Residential IPv4 (Unmetered). It is sold by speed tier, where Mbps is a speed limit, and it includes unlimited traffic for the purchased period. You can buy it by the hour as well as daily, weekly or monthly, and automatic setup takes up to 10 minutes after payment clears, so buy it before you sit down to test.

Choose the proxy from the target, not from habit. Residential IPv4 covers 195+ countries and suits targets that weigh IP reputation, which makes it the default for country tests.

The two IPv6 plans are narrower. Residential IPv6 is USA only. Datacenter IPv6 spans 45+ listed locations, Berlin and Frankfurt among them, but both fit only targets that publish IPv6 addresses or sit behind a supported CDN. Run your target through the free IPv6 Checker before you pick either one.

Here is where it goes wrong: a detected CDN alone does not confirm support, because not every CDN is on the supported list. If the checker result is unclear, test on the shortest paid window, which is hourly on Residential IPv6 and daily on Datacenter IPv6. If the target fits neither plan, use Residential IPv4.

Connect Through the Location Tag and Check the Exit

The test location lives in the proxy username. A country tag sets the country, and on Residential IPv4 a city tag works only where local ISP supply exists. Tag names can differ by plan, so copy the exact format from the client area instead of typing it from memory; the ColdProxy geo-targeting documentation shows how each tag works.

Two examples of the pattern look like this:

1user-country-de
2user-country-us-city-chicago

For the German test, build your username with the country tag for Germany. The full proxy URL then follows the standard format, with your own proxy username in place of user and your own gateway, port and password in place of the examples:

1http://user-country-de:PASSWORD@gw-2312.coldproxy.com:30000

Now connect the way you will test. In a browser, keep the proxy inside a separate test profile, because a system-wide proxy drags every other app along with it. In a new Firefox profile, enter the host and port below under Manual proxy configuration and tick Also use this proxy for HTTPS, so HTTPS pages go through the proxy too. Chrome's own proxy menu opens the system-wide setting, so start Chrome with its own profile folder and the host and port on its command line instead. Either browser then asks for the username and password on the first request; the manual browser setup guide shows the exact steps for both.

1Type:     HTTP
2Host:     gw-2312.coldproxy.com
3Port:     30000
4Username: user-country-de
5Password: PASSWORD

With curl, the proxy flag takes the same URL. The -I flag fetches only the response headers, which suits a quick look at redirects; drop it to see the raw HTML:

1curl -x "http://user-country-de:PASSWORD@gw-2312.coldproxy.com:30000" -I https://example.com/product

In Playwright, set the proxy option when you launch the browser. The Playwright setup guide covers the details. A fresh context gives you a clean profile for free, but every context uses the proxy set at launch. To test several locations in one script, set the proxy per context instead, as that guide shows. For one location per run:

1const { chromium } = require('playwright');
2
3(async () => {
4  const browser = await chromium.launch({
5    proxy: {
6      server: 'http://gw-2312.coldproxy.com:30000',
7      username: 'user-country-de',
8      password: 'PASSWORD'
9    }
10  });
11  const context = await browser.newContext();
12  const page = await context.newPage();
13  await page.goto('https://example.com/product');
14  console.log(await page.title());
15  await browser.close();
16})();

A second browser or script started without the proxy sends its traffic from your own IP. That is the most common way a "German" test turns out to be a test from your desk, so make sure every tool you use for this run points at the proxy.

Confirm the exit before you read any page. Open ColdProxy's free What's My IP tool through that same connection and check that the exit IP and country read Germany. The site you test will see a German exit IP, not yours; without a session tag it can be a different address from the one the tool shows. The tool runs its lookup with page scripts, which curl does not run, so from a terminal, query ColdProxy's public IP lookup endpoint directly and read the ip and country fields in its reply:

1curl -x "http://user-country-de:PASSWORD@gw-2312.coldproxy.com:30000" https://api.vipv6proxy.com/api/checker/my-ip

If the country is wrong, fix the tag and check again. Write down which lookup tool you used, because IP location databases can disagree about the same address. Treat the result as confirmation of this run's exit, not a promise of how any site will judge that location.

One more trap sits in the browser itself. A proxy changes the IP only. It does not touch cookies, logins or browser fingerprints, so a profile that still holds a consent choice or a currency preference from an earlier visit will show you your history, not Germany. Clear that state, or open a clean profile, for each location. Now you have a verified German exit on a clean profile, ready for the page walk.

What to Check When You Test a Website From Each Location

The exit check proves where the test ran from. The page walk shows what that location gets. First decide whether your flow spans several pages, such as a checkout, a multi-page form or logged-in QA, on a site or account you own or are authorized to test.

If it does, add a session tag with a 10-minute window so one pool IP holds across those pages. Here is the username with the tag added, with the digits as an example; confirm the exact format in your client area:

1user-country-de-session-12345-time-10m

Residential IPv4 sticky sessions run from 5 seconds up to 24 hours. The ColdProxy sticky session settings keep the same exit IP for the window while that IP keeps working, and if it stops working, the IP may change. So a sticky session is not a guarantee of one address for the whole window, and it is not a dedicated IP. For a deeper look at when each mode fits, see sticky and rotating proxy sessions compared.

Skip the session tag and requests rotate IPs by default. That is fine for a single page load, but it breaks a flow: the IP changes mid-checkout, and the test no longer follows one visitor.

Then log what the page does. For each page in the German walk, write down:

• price and currency
• page language
• any redirect, with its destination
• the consent banner: whether it appears and what it offers
• the ads that load
• any region notice or block

Record what drove each result, too. Some sites take language or currency from a browser setting or a saved cookie rather than from the IP. If your clean profile sends an English language header and the page comes back in English, that tells you about the header, not about Germany.

This method does not guarantee a local version. Some sites show the same page everywhere, and some show a region notice or refuse the request. Log those as results. A proxy helps you see the visitor's view, but it does not promise to get past a block.

curl is fast for redirects and raw HTML, yet it does not run page scripts. If your prices or banners load with JavaScript, use a browser or Playwright to read them. Finish with one record per page for that location.

Repeat the Test From Other Locations and Choose a Plan

Run the same checks from each location with the same session settings, then log the records side by side. That is what makes a difference visible: the German price next to the French one, the banner wording next to the redirect target. Change only the location tag between runs, and clear the profile each time.

Check the tag before you plan anything finer than a country. On Residential IPv4, state or region targeting works only in the United States, United Kingdom, Germany, Brazil, India and Canada, and city targeting only where local ISP supply exists. If your test needs a city, confirm it in the client area first.

Choose the plan by the job:

• Residential IPv4 (Unmetered): the plan this walkthrough starts on, and the natural pick for a page walk across many locations, because traffic is unlimited for the purchased period and you switch countries with the location tag on the same plan. The Residential IPv4 (Unmetered) plan page shows the speed tiers, and the hourly window is the shortest paid way to test it.
• Residential IPv4 (GB Based): a monthly traffic pack, where GB is an amount of traffic. It suits smaller jobs budgeted by traffic, but the pack is finite, so a large page walk across many locations uses it up.
• Datacenter IPv6: suits speed, scale and cost on targets on IPv6 or a supported CDN, across its listed locations. It bills daily, weekly or monthly, with no hourly option. Open the Datacenter IPv6 plan page once the IPv6 Checker shows your target publishes IPv6 addresses; if it only detects a CDN, validate on a daily plan first.

For a wider view of how teams plan this work, the guide on proxies for localization testing is a good next read. Pricing for every plan is public on the ColdProxy pricing page, so you can buy without a sales call.

Need a different speed or traffic allowance? Contact us through the channels on our website so we can assess whether a custom plan is possible.

If a setup step stalls, 24/7 support is open through Telegram and support tickets. Response times vary, so send your service ID, the page URL and the tag you used with your first message.

Frequently asked questions

How do I test a website from another country?

Route a browser or test script through a proxy whose username carries the target country's tag. Confirm the exit IP and country with a lookup tool, then load the page from a clean profile. Log what you see, since some sites show the same page everywhere.

How can I find out where a website is located?

This method does not show where a site's server sits. It shows what the site returns to a visitor at your chosen exit location. For the visitor's view, change the location tag and compare the records.

Is it normal for websites to track you?

Sites commonly read your IP address and set cookies. A proxy swaps the IP the site sees for the proxy's exit IP, but accounts, cookies and browser fingerprints can still identify you. ColdProxy does not log visited websites or traffic content.

How do I give a website my location?

Most sites infer location from your IP address, which the proxy controls. A browser location prompt is a separate permission that the proxy does not change, so decline it or record your answer in the test log.

Why does my German test still show the page in English?

Some sites take language from the browser's language setting or a saved cookie instead of the IP. Check your browser's language setting and clear the profile, then note which one drove the result.