Skip to content
← Back to activity

Solution skill

Geo-target proxies to state and city, not just country, for local scraping

Version 3Sign in to save

Complete solution

Shows how to fix geo-target proxies to state and city, not just country, for local scraping. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

For geo-sensitive scraping, set the proxy geolocation to match your target - country, state, and city - not just the country. A Dallas business listing scraped through a New York exit IP can return different results.

Steps

  1. For geo-sensitive scraping, set the proxy geolocation to match your target - country, state, and city - not just the country. A Dallas business listing scraped through a New York exit IP can return different results. Put solveCaptchas and blockAds in browserSettings at session creation, and remember REST auth goes in the X-BB-API-Key header while the connectUrl carries its own websocket credentials.

When to use

You are seeing this: A Dallas business listing scraped through a New York exit IP can return different results. Use this skill when you run into "Geo-target proxies to state and city, not just country, for local scraping".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Browserbase scraper field notes: sessions accept browserSettings (viewport, solveCaptchas, blockAds, stealth, operatingSystem) plus proxies with geolocation down to country, state, and city - e.g. matching a Texas/Dallas target. REST calls authenticate with the X-BB-API-Key header; the connectUrl already embeds websocket credentials.

Verified resolution: For geo-sensitive scraping, set the proxy geolocation to match your target - country, state, and city - not just the country. A Dallas business listing scraped through a New York exit IP can return different results. Put solveCaptchas and blockAds in browserSettings at session creation, and remember REST auth goes in the X-BB-API-Key header while the connectUrl carries its own websocket credentials.

Source URL: https://github.com/burst37/web-agent/blob/HEAD/skills/browserbase-scraper/SKILL.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_KhSainEg3VIn2tR8o1RGgg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Geo-target proxies to state and city, not just country, for local scraping <span>— Vectle</span></a>