Classic Proxy Geolocation: Choose a Country Without Premium Proxies
Classic proxies can now exit through a selected country, covering more than 40 markets at country level. That lets a single integration collect local prices, search results, catalogues and regional pages without moving to a premium pool when the target does not require one.
Why location changes the answer
A page can look perfectly valid while showing the wrong market. Prices, currency, discounts, stock, shipping, language, redirects and search results may all vary by visitor location. If every request leaves from the United States, a French or Japanese pricing check can silently return American data. Country targeting on the classic pool addresses that mismatch without requiring a different proxy pool for ordinary targets.
How to select a country
Use a lowercase two-letter code defined by ISO 3166-1 alpha-2 and pass it as country_code. For example, fr selects France, jp selects Japan and ca selects Canada. The same choice can be made in the dashboard request builder. The request then leaves through a classic proxy in that country. Before relying on a code, check the classic list: an unsupported code does not produce an error, it falls back to the United States. Premium pools keep a separate, larger list, so a code valid for premium may not be valid for classic.
When to use it, and a pre-flight checklist
Decision checklist: 1) Confirm the country appears on the classic list. 2) Add country_code to an otherwise standard request. 3) Leave premium and stealth options off for classic routing. 4) Verify the detected exit country with an IP-geolocation endpoint. 5) If the country is unsupported or the target needs premium routing, switch pools deliberately rather than assuming the fallback matched your market. Useful cases include cross-market price comparison, local catalogues and stock, regional redirect testing, local search results, one scraper reused across markets by changing only the code, and developer checks that would otherwise need a colleague abroad.
Python example: verify the exit country
No separate endpoint is needed: standard requests use the classic pool unless another proxy type is explicitly enabled. The worked example installs the Requests library (protected module code0001), builds a request to an IP-geolocation endpoint with country_code and render_js set to false (protected module code0002, referenced privately), and sets the credential for bash (code0003) or PowerShell (code0004). Expected output shows FR for fr and JP for jp (code0005). Because neither premium_proxy nor stealth_proxy is enabled, both requests use classic proxies; replace the codes only with classic-supported values.
Try it in your existing scraper
Keep the existing integration and add one parameter. That small change is the point: the rest of the scraper, parsing and storage logic stays untouched while each run can target a different supported market.
| Choice | What to set | Routing result |
|---|---|---|
| Classic country targeting | country_code only | Classic proxy in the selected supported country |
| Premium country targeting | premium_proxy plus country_code (code0006) | Premium proxy in the selected country |
| Unsupported classic country | country_code not on classic list | Falls back to the United States; request still runs |
| Proxy Mode | country_code in proxy password (code0007) | Same request handling; only connection method changes |
Classic and premium pools use separate supported-country lists; check the relevant list before sending.
Frequently asked questions
Is premium access required for country targeting on classic proxies?
No. A standard API request uses the classic pool by default, and country selection works there directly. Premium or stealth options are separate opt-ins.
Does premium geolocation still work?
Yes, that capability is unchanged. Combine the premium opt-in with a country code to request a premium exit in a chosen country.
Are the country lists identical for classic and premium pools?
Not necessarily. Each pool maintains its own supported-country list, so check the list for the pool you intend to use.
What occurs for an unsupported classic country?
The request does not fail; it is routed through the United States instead. Verify support first if the intended market matters.
Can Proxy Mode use classic country targeting?
Yes. Include the country option among the other parameters in the proxy password. Only the connection method changes; request handling stays the same.