ZenRows Scraping Browser enables precise country-level targeting for your web scraping operations, letting you access content as if you were browsing from a specific country. This is essential for geo-restricted content, localized pricing, and market research across nations.

​
What is Country Targeting?

Country-targeting routes your scraping requests through residential IP addresses from a specific country, providing the most precise geolocation control available. Unlike world region targeting, which covers broad areas, country targeting gives you IPs from individual nations.

Key benefits:

  • Access country-specific content and services
  • Accurate localized pricing and product data
  • Compliance testing for legal jurisdictions
  • Ad verification and fraud prevention by country
  • Market research with country-level precision

Auto-rotate and Residential IPs are pre-configured and enabled by default for all ZenRows Scraping Browser users. Country targeting works seamlessly with these features to provide optimal performance.

​
How to Configure Country Targeting

You can configure country targeting in two ways:

  • ZenRows SDK: Recommended for most users (simplest, most robust)
  • Direct WebSocket URL: For advanced or custom integrations

For custom integrations or direct control, specify the country using the proxy_country parameter in the WebSocket URL.

wss://browser.zenrows.com?apikey=YOUR_ZENROWS_API_KEY&proxy_country=es

const puppeteer = require('puppeteer-core');
const wsUrl = 'wss://browser.zenrows.com?apikey=YOUR_ZENROWS_API_KEY&proxy_country=es';

(async () => {
    const browser = await puppeteer.connect({ browserWSEndpoint: wsUrl });
    const page = await browser.newPage();
    await page.goto('https://example.com');
    console.log(await page.title());
    await browser.close();
})();

ZenRows supports residential IPs from over 100 countries worldwide. For the complete list and codes, see our Premium Proxy Countries List.

Most Popular:

  • us - United States
  • gb - United Kingdom
  • br - Brazil
  • de - Germany
  • ca - Canada
  • au - Australia
  • fr - France
  • in - India
  • es - Spain
  • it - Italy
  • nl - Netherlands
Country Targeting Configuration Interface

​
Best Practices

Choosing the Right Country:

  • Select countries based on your target market or content
  • Consider local business hours and time zones for time-sensitive scraping
  • Test with multiple countries to understand regional content differences

SDK vs Direct Connection:

  • Use the SDK for most projects. It offers better error handling and automatic retries
  • Direct WebSocket is for custom frameworks or specific connection control

Performance Optimization:

  • Some countries have larger IP pools and better performance
  • Monitor success rates and adjust the country selection accordingly
  • Use fallback countries if your primary choice has issues

​
Troubleshooting

Common Issues and Solutions:

Country Code Errors:

  • Use the correct ISO country code (e.g., ‘es’ for Spain)
  • Check the country list to ensure support
  • Use lowercase codes in direct WebSocket connections

No Content Differences:

  • Some sites may not vary by country. Test manually by accessing the website
  • Try different countries to verify geo-targeting
  • Some sites use detection beyond IP geolocation

Connection Issues:

  • Some countries may have smaller IP pools. Try alternative countries
  • Monitor the response error for indications that may help
  • Use world region targeting if country-level access is problematic

You cannot use both world region and country targeting at the same time. Select the level of precision you require, whether broad regional coverage or targeted to a specific country.

​
Next Steps