Geo-targeted screenshots:what another country sees
on the same URL
The same URL routinely serves different prices, currencies, languages and offers depending on where the request comes from. Watching from one connection gives you one slice of that, and hides the rest.
One URL, many different pages
Open a competitor's pricing page and you see a price. It is easy to assume that is the price. It frequently is not — it is the price for someone connecting from where you happen to be, in the currency inferred from your location, possibly with a regional promotion attached.
Geographic variation is not exotic any more. It is the default for anything sold internationally: currency conversion, regional pricing, tax-inclusive display, language, legal disclosures, and offers that run in one market and not another.
If you are monitoring a page — your own or someone else's — a single vantage point systematically hides all of that. Worse, it hides it invisibly: nothing about the capture tells you it was regional.
Four things that only show up when you look from elsewhere
- Regional pricing you are being undercut by. A competitor holding a high price in your market while discounting aggressively in another is a strategy you cannot see from home.
- Your own localisation, broken. Currency and language selection is fiddly, and the failure mode is usually silent. Capturing your checkout from each market you sell into catches it.
- Compliance obligations that differ by market. Where a disclosure is required in one country and not another, evidence that it was shown has to come from that country.
- Content that is geo-blocked entirely. Pages that simply do not exist for some visitors are worth knowing about.
How capturing from another location works
The request goes out from the market, and the site does the rest.
The capture request is routed so that it reaches the target site from an address in the country you chose. From the site's point of view it is an ordinary visit from that market, so whatever logic it applies to regional visitors applies normally.
That is deliberately all it does. It does not spoof a language header you did not ask for, or pretend to be a particular device. If you want the German-language page as seen from Germany on a phone, that is a location, a language and a device profile — three settings, set explicitly.
The available locations are listed in our location documentation, and it is a per-plan capability rather than something every tier includes.
Comparing regions without fooling yourself
Regional comparison produces confident-looking conclusions from very little evidence, so a few disciplines are worth adopting early.
- Change one variable at a time. If the German capture is at a different viewport from the British one, you cannot attribute a layout difference to the region.
- Capture the same page at the same moment. Prices move. Two captures a day apart are not a regional comparison, they are a timeline.
- Watch for currency versus price. A converted price and a genuinely different price look identical in a screenshot. Compare against the exchange rate before concluding anything.
- Repeat before you act. Regional experiments and A/B tests exist. A difference that persists across several days is a decision; one that appears once is a test.
A workable regional monitoring setup
The setup that survives contact with reality is smaller than the one people first design.
- Pick the pages where geography actually matters. Pricing, checkout, and any page carrying a regulated disclosure. Most content pages are identical everywhere.
- Pick two or three markets. Your largest, your fastest-growing, and the one where a competitor is most aggressive.
- Use one schedule per page per market, labelled by market, so a review pulls up a coherent set.
- Deliver into folders by market. Comparing two folders is much easier than filtering one.
Grouping by labels is what keeps this manageable once it is more than a handful of schedules.
FAQ
Is capturing from another country the same as using a VPN?
The effect is similar — the request arrives from that country — but it is applied per capture rather than to your whole machine, so a schedule can watch several markets at once without anyone switching anything.
Where does the visit come from?
From an address in that region supplied by one of our proxy providers, so it is an ordinary request from that market. We do not bypass logins or paywalls, and our acceptable use terms rule out circumventing a site's access controls.
Does the language change too?
Only if the site decides it should. Many sites infer language from location; others use the browser's language header. If language matters, set it explicitly rather than assuming.
Can I use this for my own site's localisation testing?
That is one of the best uses for it — regional pricing and currency bugs are notoriously hard to catch from the office.
Which locations are available?
The current list is in the location documentation, and availability depends on your plan.
TL;DR
One URL serves many different pages depending on where the request comes from, and monitoring from a single connection hides that completely. Capture from the markets that matter commercially, change one variable at a time so a difference means something, check currency conversion before concluding a price differs, and wait for a difference to persist before treating it as a decision rather than a test. Two or three markets, on the pages where geography actually changes the content, is enough to start.