ZenRows Scraping Browser empowers you to target specific regions of the world for your web scraping operations, unlocking geo-restricted content and enabling region-specific data collection. This guide shows you how to configure world region targeting using both the ZenRows SDK (recommended) and direct WebSocket connections.

​
What is World Region Targeting?

World region targeting routes your scraping requests through residential IPs from a chosen geographic area. This is crucial when websites display different content, pricing, or availability based on visitor location.

Typical use cases:

  • Accessing geo-locked content or services
  • Price comparison across markets
  • Testing website localization and UX
  • Circumventing geo-blocks for data gathering
  • Ad verification in multiple regions

Auto-rotate and Residential IPs are pre-configured and enabled by default for all ZenRows Scraping Browser users, ensuring optimal performance and reliability.

​
How to Configure World Region

You can configure world region targeting in two ways:

  • ZenRows SDK: Easiest and most robust option for most users
  • Direct WebSocket URL: For advanced or custom integrations

Specify the region in the WebSocket URL with the proxy_region parameter:

wss://browser.zenrows.com?apikey=YOUR_ZENROWS_API_KEY&proxy_region=eu

Examples:

const puppeteer = require('puppeteer-core');
const connectionURL = 'wss://browser.zenrows.com?apikey=YOUR_ZENROWS_API_KEY&proxy_region=eu';

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

Available Region Codes:

  • eu - Europe
  • na - North America
  • ap - Asia Pacific
  • sa - South America
  • af - Africa
  • me - Middle East
World Region Configuration Interface

​
Best Practices

Choosing the Right Region:

  • Select the region closest to your target audience or where the content is most relevant
  • Consider local time zones and business hours for time-sensitive scraping

SDK vs Direct Connection:

  • Use the SDK for most projects (better error handling and connection management)
  • Use direct WebSocket only for fine-grained control or custom framework integration

Testing and Validation:

  • Test your region config with a simple request to verify IP location
  • Monitor scraping results to ensure you’re seeing expected regional content

​
Troubleshooting

Common Issues:

  • Invalid region code: Double-check you’re using the correct region codes
  • No regional content difference: Some sites may not vary by region. Verify with manual testing
  • Connection timeouts: Proxy pools may vary by region; try another if needed

Debugging Tips:

  • Use browser dev tools to inspect the IP address
  • Test the same URL from different regions to confirm content variation
  • Check ZenRows dashboard for logs and error details

For more granular targeting, see Country Targeting.

​
Next Steps