The name of the Bright Data proxy zone you configure in RankGear, sent along with each organic-result request so scraping traffic routes through that specific zone in your Bright Data account.
| Term | Bright Data Zone |
|---|---|
| Category | APIs, Reliability and Publishing |
| Also known as | Proxy Zone |
| Where it appears | Settings → APIs |
What it means in RankGear
A zone is Bright Data’s unit of proxy configuration: inside your Bright Data account you create a named zone that fixes the network type, rotation behaviour, and access credentials for a pool of proxy IPs. When RankGear fetches Google organic results on your behalf, it attaches this zone name to each request so the traffic is drawn from the pool you set up. You enter the value once under Settings → APIs, and it is stored with the rest of your provider credentials.
How to interpret it
Treat the zone name as configuration, not as a live signal. If organic fetches start failing, the zone value is the first thing to verify: read the visible connection status, check the diagnostics for the request, and run the credential test rather than assuming the pages themselves are broken. A timed-out fetch and an authorization failure look different here, and the distinction tells you whether to retry or to correct the setup. A blank or misspelled zone name, or one that no longer exists in your Bright Data account, produces authorization errors on every request until it is fixed.
Example
You maintain a residential zone in Bright Data named rankgear_serp and paste that exact string into Settings → APIs. A single result page times out under load, so RankGear allows it one bounded longer retry through the same zone. Later, someone renames the zone in the Bright Data dashboard without updating RankGear; the next run returns authorization failures and stops rather than hammering the endpoint with repeated paid calls, and the credential test points straight at the stale zone name.
Important considerations
- The zone name is an account credential. Keep it accurate and treat it as sensitive; RankGear redacts it in logs and diagnostics, and credential tests should stay read-only where possible.
- Proxy requests through a zone are billed by Bright Data. Invalid configuration is stopped early precisely to avoid burning paid calls on requests that cannot succeed.
- The zone controls how organic-result traffic is routed, not what the results mean. It has no bearing on any ranking factor or score, and changing zones does not change the correlations RankGear reports.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.