Geo-targeting
Deliberately choosing a proxy in a specific country, region or city so your traffic originates exactly where you need it to.
Geo-targeting is geo-blocking used deliberately and in your favour. Where a site changes what it shows based on where you appear to be, you choose where you appear to be, selecting an exit in the country, and sometimes the city, whose view of the site you actually need to see.
The reason to do it is that a great deal of the web is quietly different depending on who is looking. Prices and currencies vary by market. Search results are localised. Product availability, delivery estimates, promotions and even which items exist at all change by region. Verifying that your own campaign renders correctly in Brazil, or collecting the prices a Japanese customer really sees, both require standing where they stand.
Precision costs supply, and matching the two is the practical skill. Most sites vary by country and nothing finer, so a country-level exit is the complete answer and anything narrower is wasted effort. A minority key on region or city, typically local search, store stock and delivery windows, and only those justify city targeting.
That matters because coverage thins sharply as you narrow. Country-level residential coverage is broad and stable. City-level coverage is genuinely fluid, because it depends on which households happen to be online in one place at one moment, and no provider can promise a specific city on a specific day the way it can promise a country.
So the question to ask a provider is not whether they support city targeting but what happens when the city is empty. The honest behaviour is a documented fallback to the country, or an error you can handle. The damaging behaviour is a silent substitution, because your job then completes successfully while collecting data from the wrong place, and nothing in your logs will tell you.
Two failure modes are worth pre-empting on your side. The first is a fingerprint contradiction: an exit in Frankfurt while your browser reports an American time zone and English locale, which is not a plausible German visitor and is trivially detectable. The second is DNS resolving at home while you exit abroad, which can route you to infrastructure near you and quietly undo the geography. Neither is a proxy fault, and both defeat the purpose.
Frequently asked questions
Do I need city-level targeting or is country enough?
Country is enough for the large majority of work, because most sites vary by market and nothing finer. Reach for city targeting only when the thing you are measuring is genuinely local: local search results, store-level stock, delivery estimates or region-specific promotions. Test whether the page actually changes between two cities in the same country before paying for the precision.
Why does my geo-targeted proxy show the wrong location?
Three usual causes, in order of likelihood. You measured the gateway rather than the exit. The pool could not fill your request and fell back to a nearby location. Or the geolocation database the site uses is out of date for that address, which happens with recently reassigned ranges. Testing several exits separates a pool problem from a database problem.
Can a site tell I am using geo-targeting?
Not from the address alone if it is a genuine residential IP in that country. It can tell from the contradictions around it: a browser reporting a time zone or language that does not match the country, a system locale that disagrees, or DNS resolving somewhere else entirely. The address is only convincing when everything else agrees with it.
Does geo-targeting work for checking search results?
It is one of the strongest use cases, since search is heavily localised and results genuinely differ by country and often by city. Use a residential exit rather than datacenter, because search engines screen network type aggressively, and align your language and locale settings with the country you are presenting or you will get an odd hybrid of both.
Back to the full glossary.