Why rank tracking needs proxies
Rank tracking means checking where pages appear in search results for a list of keywords, usually in specific countries or cities, on a regular schedule. Search engines personalise and localise results, and they're quick to challenge automated queries, particularly from datacenter IP ranges. Run more than a handful of queries from one IP and you'll see CAPTCHAs or empty results.
Proxies solve two problems: they spread queries across many IPs, and they let you query from the locations whose results you care about. Geonode residential proxies can be targeted by country, state, city and ASN, which covers both national and local rank tracking. For high volumes, Geonode's Search API is an alternative that returns structured results per query.
Choosing your approach
| Volume and need | Recommended approach |
|---|---|
| A few dozen keywords, occasional checks | Residential proxies, rotating, low rate |
| Hundreds of keywords daily, national | Residential proxies with careful pacing, or a search API |
| Thousands of keywords, many locations | A search API priced per query |
| Visual checks of SERP features | A browser through a residential exit |
Many SEO teams combine them: an API for the bulk of tracking and residential proxies in a browser for audits and spot checks.
Settings that work for SERP collection
- Rotate per query. Each query from a new IP avoids building up a query history on one address.
- Target the location you're measuring: country for national rankings, city for local results.
- Use the search engine's own parameters for language, country and, where available, location, in addition to the exit location. Exit location alone doesn't always determine results.
- Keep rates low. Space queries out and add jitter. Bursts of queries are the fastest way to get challenged.
- Use a realistic client. Search engines check headers and fingerprints, not just IPs. A bare script with default headers is challenged far more often than a properly configured client or browser.
- Detect challenges by looking for the expected results container, and retry later from a new IP rather than immediately.
See Google SERP scraping proxies for detail on result pages and parameters.
Getting accurate results
Rank data is only useful if it reflects what real searchers see.
- Disable personalisation by using clean sessions with no cookies or history.
- Match language and location settings to the market.
- Repeat important checks. Results vary slightly between queries; for key keywords, take a few samples and use the median position.
- Record SERP features (maps, shopping, videos, answer boxes), because a "position 3" under a large map pack is very different from position 3 on a plain page.
- Spot-check visually through a browser on the same exit location.
Proxy tip: You can try every step in this guide with a small balance: Geonode bills residential bandwidth per GB with no expiry, so testing costs very little. See our complete Geonode guide for the full product overview.
Cost considerations
Search result pages are relatively light in HTML, so residential bandwidth per query is modest if you fetch HTML only. Costs rise when you load full pages in a browser or retry a lot. At high volume, compare your cost per successful query on residential proxies (including retries and engineering time) with a per-query API. Geonode states that its API requests aren't multiplied for features such as geo-targeting, which makes that comparison easier. See the Geonode Scraper API.
A simple rank tracking setup
- A list of keywords per market, with the target URL for each.
- A daily job that queries each keyword once through a rotating residential exit in that market, at a slow, jittered rate.
- A parser that records position, URL and SERP features.
- Retries for challenged queries, later in the run, from new IPs.
- Weekly visual spot checks of the top keywords.
For local rankings, see Geonode for local SEO.
Rules and good practice
Search engines' terms restrict automated queries, which is one reason many commercial rank trackers use official or licensed data sources. Keep volumes reasonable, avoid hammering, and consider an API for scale. See are proxies legal?.
Reporting rankings so they're useful
- Group keywords by intent and page, not just alphabetically.
- Report visibility, a weighted score across keywords, alongside individual positions.
- Show SERP features next to positions, because a top result below a map pack and shopping carousel gets fewer clicks.
- Compare markets side by side when you track several countries.
- Annotate changes such as site updates, algorithm updates and competitor moves.
A monthly report built this way, from data collected through Geonode residential exits or a search API, gives stakeholders a clear picture without drowning them in numbers. For local visibility specifically, see Geonode for local SEO.
FAQ
Can I track rankings with datacenter proxies?
Only at very low volumes. Search engines challenge datacenter IPs quickly. Residential proxies or a search API are more reliable.
How do I track rankings in a specific city?
Use city-targeted residential exits and the search engine's location settings together, then verify with a visual check.
Why do my tracked rankings differ from what I see?
Your own searches are personalised by history, location and device. Tracked results from clean sessions are closer to what a new searcher sees.
Is a search API better than proxies?
At high volumes, usually. For small volumes, audits and visual checks, proxies are flexible and cheap.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.