---
title: "Test Website From Another Country: A Step-by-Step Guide"
description: "Need to test website from another country? Use a clean browser profile with a proxy exit, match timezone and language, then verify the IP. Learn the method."
url: "https://donutbrowser.com/fr/test-website-from-another-country/"
---

1. [Accueil](https://donutbrowser.com/fr/)

2. [Blog](https://donutbrowser.com/fr/blog)

3. Test Website From Another Country: A Step-by-Step Guide

# Test Website From Another Country: A Step-by-Step Guide

October 26, 2026

geo-testing website-localization proxy-configuration

**To test a website from another country, use a clean browser profile that exits through a proxy in that country. Match the timezone, language and geolocation to the proxy, start with empty cookies, and verify the exit IP before each run. Changing only the IP, or only a browser setting, gives misleading results, because sites compare those signals against each other.**

A pricing page, consent banner or redirect can look right from your office while visitors in Germany get the wrong currency, a broken redirect or no banner at all. You can’t see that from your own IP, so you have to test from the other country on purpose.

You’ll be able to build a repeatable per-country test, run it by hand and in code, and hand findings to developers or legal. I build Donut Browser and earn nothing from proxy providers, so the advice is by trade-off.

> **Key Takeaways**

> - Identical results in two countries usually mean a cached CDN response or an old cookie, not a site that ignores location.

> - hreflang tells search engines which page fits which audience. It doesn’t decide what a visitor sees.

> - Automatic geo-redirects can stop search engines from reaching your localized versions.

> - A simulated location is a close approximation, not what a local ISP or mobile user gets.

## How does a website decide which country you are in?

A website usually starts from your IP address and the Accept-Language header, as [Google’s guide to locale-adaptive pages](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages) describes, then can cross-check browser signals: the timezone your browser reports, cookies from earlier visits and, if you grant permission, the Geolocation API. CDNs and edge rules often apply that decision before the page loads.

![Image generated](https://api.birchseek.com/m/1TpLfBwNLAxLoM1l9bVs713K_NzicvM3.webp)

Each signal behaves differently when you test:

- **IP geolocation** is the first thing the server sees. The server looks your IP up in a database that maps address ranges to countries, and that database can be wrong or out of date for some ranges. A data-center IP may also be treated differently from a home or mobile one.

- **CDN or edge rules** run before your origin server does. [Cloudflare’s IP Geolocation documentation](https://developers.cloudflare.com/network/ip-geolocation/) names a `CF-IPCountry` header for the visitor’s country. A cached response from an earlier test can hide a rule that works.

- **Accept-Language header** is sent with every request. [MDN’s Accept-Language reference](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language) says it “indicates the natural language and locale that the client prefers.” A proxy doesn’t change it; only your browser’s language setting does.

- **Timezone** is readable only by JavaScript, so the server never sees it in the first request. The browser reports an IANA zone name such as `Europe/Berlin` through [resolvedOptions().timeZone](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/resolvedOptions), so matching only the UTC offset isn’t enough.

- **Geolocation API** is also JavaScript only, and separate from your IP. [MDN’s Geolocation API page](https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API) says the user is asked for permission, and the feature works only in secure contexts (HTTPS).

- **Cookies and local storage** persist between visits. A saved region or language choice can override every other signal, so start with an empty profile.

To see your timezone signal, open the browser console on any page and run `Intl.DateTimeFormat().resolvedOptions().timeZone`. [MDN documents this call](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/resolvedOptions).

On a machine in New York it returns `America/New_York`, even when your traffic exits through a Berlin proxy. The page then sees a German IP and a New York timezone.

These browser-side values are part of [browser fingerprinting](https://donutbrowser.com/browser-fingerprinting/), which is how sites tell one device from another.

## Can screenshot tools and DevTools test a website from another country?

Screenshot tools and DevTools overrides can test a website from another country for a quick first look, but they show neither a logged-in session nor a local network. Vendor terms change, so check each page before you rely on this table.

|  | GeoPeeker | Geo Browse | LocaBrowser | PageSpeed Plus |
| --- | --- | --- | --- | --- |
| Locations | not stated on the vendor page | not stated on the vendor page | country picker | 8 countries |
| Platform and user agent | not stated on the vendor page | not stated on the vendor page | you choose both | not stated on the vendor page |
| Free use | not stated on the vendor page | free | not stated on the vendor page | not stated on the vendor page |
| Trial | not stated on the vendor page | not stated on the vendor page | not stated on the vendor page | trial offered, length not stated |

[LocaBrowser’s page](https://www.locabrowser.com/) says you “select a country, platform and user agent”. [Geotargetly’s tool](https://geotargetly.com/geo-browse) is titled “Free Geo Browse”, and its page asks you to allow up to 1 minute for a screenshot.

[PageSpeed Plus’s location test page](https://pagespeedplus.com/tools/test-website-different-locations) is titled “8 Countries” and has a “Start Trial” button. Confirm its location list in the live tool.

In Chrome DevTools, the [Sensors panel](https://developer.chrome.com/docs/devtools/sensors) can override geolocation, and you can override the user agent string. Neither changes the IP the server sees, so IP-based logic is untouched.

The limits are the same across these tools: fixed location lists, mostly a fresh anonymous load, no login or session, and no mobile-carrier view. For anything beyond that, use a proxy.

Use Geo Browse or LocaBrowser for a quick visual check, PageSpeed Plus for a look from its listed countries, and DevTools for layout and language tests.

## VPN, proxy or cloud server: which method fits which test?

A VPN fits a quick one-off look, a proxy fits repeated checks where the IP type matters, and a cloud server fits scripted checks and regional uptime. A per-locale browser profile pairs with any of them to keep cookies, language and timezone consistent for each country.

|  | VPN | Proxy | Cloud server in target country | Per-locale browser profile |
| --- | --- | --- | --- | --- |
| Cost | Subscription | Paid per IP or traffic | Server bill | No extra cost |
| Effort | Low | Medium | High | Medium |
| IP type | Shared, often data center | Data center or residential | Data center | Whatever you attach |
| First limit you hit | Short exit list | Coverage varies by provider | Setup and upkeep | Doesn’t change your IP |

Shared VPN exits are often data-center IPs, and some sites treat those differently from home connections. Residential proxies cost more but look more like ordinary visitors.

A cloud server gives you full control, but you set it up yourself and it still has a data-center IP. The [guide to proxy types for anti-detect browsers](https://donutbrowser.com/proxies-for-anti-detect-browsers/) covers that trade-off in more depth.

All four methods are desktop-oriented. None reproduces a local mobile carrier network, and a simulated location may not match what real users see on local ISPs.

Match the method to the problem:

- **Pricing page:** use a proxy or VPN exit in the target country, plus clean cookies.

- **Consent banner:** exit inside the regulated region and use a fresh profile, so an old consent cookie can’t hide the banner.

- **Geo-redirect:** inspect the redirect chain with a clean session for each country.

- **hreflang audit:** you need no location. Read the markup and check Search Console.

- **Uptime by region:** use a monitoring service, or run a cloud server in each region.

## How do you build a browser profile for each test country?

You build a browser profile for each test country by giving every locale its own isolated profile, a proxy that exits there, and settings that match that exit. Budget about 10 minutes for the first profile and less for each after it.

1. **Get a proxy that exits in the test country.** HTTP, HTTPS or SOCKS5 all work. Check that the provider lists the country you need, and remember that data-center IPs may be treated differently from residential ones.

2. **Create a new profile named for the country**, such as `DE-test`. Don’t reuse your everyday profile, or old cookies will skew the result.

3. **Attach the proxy to that profile only.**

4. **Match timezone, language and geolocation to the exit.** For Germany that means `Europe/Berlin` and `de-DE`. A Berlin proxy with a Prague timezone is still a mismatch, because the browser exposes a named zone, not just an offset.

5. **Verify the exit before every run.** Confirm the IP’s country, then run a [WebRTC leak test](https://donutbrowser.com/tools/webrtc-leak-test/) and a [DNS leak test](https://donutbrowser.com/tools/dns-leak-test/). Success means Germany everywhere and none of your real IP.

6. **Load the page and record what you see:** language, currency, pricing, redirects, consent banner, blocked content, legal text and load behavior.

If a result looks wrong, check for a timezone or language mismatch first. If two countries look identical, clear cookies, re-verify the exit, and retest in a fresh profile.

### How Donut Browser handles this

Donut Browser supports per-profile HTTP, HTTPS and SOCKS proxies on the [free plan](https://donutbrowser.com/pricing). It reads the proxy exit’s location and sets timezone, language and geolocation to match.

For a German test, create `DE-test`, add your German proxy, then open Donut’s what-is-my-ip tool. If it shows Germany and the profile shows `Europe/Berlin` and German, run the two leak tests, then load your pricing page.

Try a first country profile in Donut Browser and compare it with your office view. If separate browser profiles are new to you, [what an anti-detect browser is](https://donutbrowser.com/what-is-an-anti-detect-browser/) explains how they stay apart.

The limits are real. Donut doesn’t sell proxies, so bring your own. The profile simulates a local visitor, not a real user on a local ISP or mobile network. Business use needs the commercial license that [paid plans](https://donutbrowser.com/pricing) include.

## How do you automate a website test from another country with Playwright?

You automate a website test from another country with Playwright by creating one browser context per country, each with its own proxy, locale, timezone and geolocation. Each option maps to one signal:

- **`proxy`** (`server`, `username`, `password`) sets the IP, the strongest signal.

- **`locale`** sets the language.

- **`timezoneId`** sets the named timezone, such as `Europe/Berlin`.

- **`geolocation`** with `permissions: ['geolocation']` answers the browser Geolocation API without a prompt.

```
import { chromium } from 'playwright';
const countries = [{ code: 'DE', locale: 'de-DE', timezoneId: 'Europe/Berlin',
  geolocation: { latitude: 52.52, longitude: 13.405 },
  proxy: { server: 'http://de.proxy.example:8000', username: 'USER', password: 'PASS' } }];
const browser = await chromium.launch();
for (const c of countries) {
  const { code, ...opts } = c;
  const ctx = await browser.newContext({ ...opts, permissions: ['geolocation'] });
  const page = await ctx.newPage();
  await page.goto('https://api.ipify.org?format=json');
  console.log(code, 'exit IP:', await page.textContent('body'));
  await page.goto('https://example.com/pricing');
  console.log(code, 'final URL:', page.url());
  await page.screenshot({ path: `${code}.png`, fullPage: true });
  await ctx.close();
}
```

A wrong proxy still gives wrong results, so assert on the exit IP before anything else.

If two countries come back identical, confirm the exit IPs differ, then check for a cached CDN response. Each new context starts with empty cookies, so an old cookie only matters if you reuse a context.

The script tests desktop Chromium from your proxy’s IP. Attaching Playwright, Puppeteer or Selenium to a Donut Browser profile through a CDP port needs the [Pro plan](https://donutbrowser.com/pricing).

## What should you check, and what if results look identical or wrong?

Check eight things on every page in every country, write them into one row per run, and compare rows before you blame the site. Confirm the exit IP country first, or every other column is unreliable.

- **Language:** page language, and whether it follows `Accept-Language` or the IP.

- **Currency:** symbol and ISO code.

- **Pricing and taxes:** price shown, VAT or sales tax included or not, shipping.

- **Redirect chain:** every hop and the final URL.

- **Consent banner:** shown or not, and which choices it offers. Check whether non-essential cookies are set before you click.

- **Blocked or unavailable content:** error pages, missing media, “not available in your region” notices.

- **Legal text:** terms, privacy notice, imprint.

- **Load behavior:** what renders, and what stalls.

Copy this template, one row per URL and country:

```
URL | country | date and time | verified exit IP country | language | currency | price shown | redirect chain | consent banner | blocked content | legal text | load notes | screenshot filename
```

These rows are sample values, not a measured result. A US profile sees `$49.00` and an English page; a German profile is redirected to the German path, gets a VAT-inclusive euro price and a cookie notice:

```
/p/lamp | US | 2026-10-05 10:02 | US | en-US | USD | $49.00 | none | none | none | US terms | normal | lamp-us.png
/p/lamp | DE | 2026-10-05 10:09 | DE | de-DE | EUR | 45,00 € incl. VAT | /p/lamp > /de/p/lamp | cookie notice | none | DE imprint | normal | lamp-de.png
```

If two rows come back identical or wrong, work through this list:

1. **Cached CDN response:** [MDN’s Vary header reference](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Vary) says the `Vary` header describes request parts that “influenced the content of the response”. If the cache ignores `Accept-Language` or country, it can serve one version to everyone. Ask the developers for the `Cache-Control` and `Vary` headers.

2. **Saved cookies:** an earlier visit may have stored a region or language choice. Use a fresh or ephemeral profile.

3. **Geolocation disagreement:** the site’s IP database may place the proxy somewhere other than the provider says. Record the country you verified, not the one advertised.

4. **Header or timezone mismatch:** a German IP with a US timezone or `en-US` only can trigger a fallback.

5. **Data-center IP:** some sites may challenge it where a home connection passes. If the page is blocked or shows a challenge, run the [bot detection test](https://donutbrowser.com/tools/bot-detection/) in the same profile.

One remote location behind a proxy hop doesn’t match real users’ latency. Treat load notes as hints, and use real-user monitoring for any performance claim.

## How do hreflang and geo-redirects affect SEO when you test by country?

Hreflang and geo-redirects affect SEO because they decide which version of a page search engines can reach, while a per-country test only shows what a human in that country sees.

[Google’s documentation on locale-adaptive pages](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages) says that if your site returns different content based on the perceived country or language of the visitor, Google might not crawl, index, or rank all of it. The stated reason is that Googlebot’s default IP addresses appear to be based in the USA.

A German test profile might show you a page that Google rarely, if ever, sees.

**Hreflang** is the fix Google points to: an annotation that tells search engines which URL serves which language or region, such as `de-DE`. It doesn’t redirect anyone, so your test results won’t change when you add it. Check three details:

- **Self-reference and completeness:** Google’s guide to [localized versions of a page](https://developers.google.com/search/docs/specialty/international/localized-versions) says each language version must list itself as well as all other language versions.

- **Return links:** every page you point to should point back.

- **x-default:** Google describes it as the value used when no other language or region matches the user’s browser setting.

Automatic **geo-redirects** are the common trap. [Google’s multi-regional guidance](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites) advises against automatically redirecting users based on their perceived language, because this could prevent users and search engines from viewing all versions of your site.

If your test shows a redirect from `/` to `/de/`, ask whether a visitor from elsewhere can still reach every version.

**Cloaking** is a different risk. [Google’s spam policies](https://developers.google.com/search/docs/essentials/spam-policies) define it as presenting different content to users and search engines with the intent to manipulate search rankings and mislead users.

Serving euros in Germany and dollars in the US is localization. Serving crawlers a page that no real visitor can get is the pattern to avoid, so make sure Googlebot’s version is one a real visitor can also see.

To compare both views, run the URL through Search Console’s URL Inspection and look at the rendered page. Then put it next to your per-country screenshots and note every difference.

## Frequently asked questions

### How can I test a website from another country for free?

**Combine three free routes: screenshot tools, DevTools overrides and a free-plan browser profile with your own proxy.** Screenshot tools have free limits, so check each vendor’s current terms. DevTools overrides cover client-side checks only and leave your IP unchanged. The profile route is for personal use, and you supply the proxy.

### Is a VPN enough to test a website from another country?

**A VPN changes your IP, but not your browser’s timezone, language or cookies.** Set those to match, start with a clean profile, and verify the exit IP before testing. VPN apps also offer limited location lists.

### Does this work for mobile users?

**Only partly, and never exactly.** [LocaBrowser](https://www.locabrowser.com/) lets you choose a platform and user agent to simulate browsing, but that is a simulation. [Donut Browser is desktop only](https://donutbrowser.com) (macOS, Windows, Linux), and no method here reproduces a local mobile carrier network. Confirm mobile results on real devices.

### Is it allowed to browse a site from another country?

**Testing your own site, a client’s site or a public page is ordinary QA.** It isn’t a way to bypass access controls or licensing restrictions, such as region-locked streaming content. Check the site’s terms first, and ask a lawyer if you’re unsure.

## What should you do next?

You can run your first country test in one sitting, then make it routine.

**Today:** Pick one page and one country. Build one profile with a proxy that exits there, verify the exit IP, and fill in one row of your template.

**This week:** Add two more countries, or script the matrix in Playwright so every run starts clean.

**Ongoing:** Re-run after releases, CDN changes and consent-tool changes. Re-check each vendor’s trial and location terms before you rely on them.

[Download Donut Browser](https://donutbrowser.com) and build your first per-country profile. The free plan covers the setup: no account, macOS, Windows and Linux, [open source under AGPL-3.0](https://donutbrowser.com/alternatives/adspower/), zero telemetry. If it doesn’t fit your workflow, you’ve paid nothing.

## Sources

[IP Geolocation · Cloudflare Network docs](https://developers.cloudflare.com/network/ip-geolocation/) · [Accept-Language header - HTTP | MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language) · [Geolocation API - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API) · [LocaBrowser - Easy Web Browsing From Multiple Locations](https://www.locabrowser.com/) · [Donut Browser pricing](https://donutbrowser.com/open-source-antidetect-browser/) · [How Google crawls locale-adaptive pages | Google Search…](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages) · [Tell Google about localized versions of your page | Google…](https://developers.google.com/search/docs/specialty/international/localized-versions) · [Private anti-detect browser — Donut Browser](https://donutbrowser.com). Every other source is linked where the article cites it.

## Voyez-nous plus souvent sur Google

En un clic, ajoutez Donut Browser aux sources préférées de votre compte Google : nos articles auront plus de chances d'apparaître dans vos À la une, le Mode IA et les Aperçus IA.

Préférez-nous sur Google

## On this page

- How does a website decide which country you are in?

- Can screenshot tools and DevTools test a website from another country?

- VPN, proxy or cloud server: which method fits which test?

- How do you build a browser profile for each test country?

- How Donut Browser handles this

- How do you automate a website test from another country with Playwright?

- What should you check, and what if results look identical or wrong?

- How do hreflang and geo-redirects affect SEO when you test by country?

- Frequently asked questions

- How can I test a website from another country for free?

- Is a VPN enough to test a website from another country?

- Does this work for mobile users?

- Is it allowed to browse a site from another country?

- What should you do next?

- Sources
