Proxies for SEO Rank Tracking: Local SERPs, Volume and Staying Unblocked
SEO rank tracking needs proxies because Google rate-limits automated searches per IP and personalises results by location. Rotating residential proxies with city-level targeting return the same local results a searcher in that city sees, and spread queries thin enough to avoid the unusual-traffic page. Since Google stopped honouring the 100-results parameter in 2025, tracking the top 100 takes around ten requests per keyword instead of one, which makes volume planning and bandwidth cost more important than they used to be.
- seo
- rank tracking
- serp
Table of contents
Why rank tracking needs proxies
Two problems, one tool. Google shows different results in Berlin and Munich, so an accurate ranking needs a searcher's-eye view from the right place. And Google limits automated queries per address; past that, it serves the unusual traffic page. Residential exits in the right city solve both.
What a local SERP depends on
| Factor | How to control it |
|---|---|
| Country | Proxy country targeting plus the gl parameter |
| City | City-level proxy targeting; optionally Google's location parameter |
| Language | hl parameter and Accept-Language header |
| Device | Desktop or mobile user agent — mobile SERPs differ |
| Personalisation | No cookies from previous searches; fresh session per batch |
The IP location and the parameters must agree. A Munich exit with gl=us produces a hybrid page that matches no real searcher, and the ranking you store is fiction.
The 10-results-per-page change
Rank trackers used to append num=100 and get the top 100 results in one request. Google stopped honouring that parameter in September 2025, so tracking positions 1–100 now means paginating through ten result pages. Many tools cut back to the top 10 or top 20 as a result. For your own tracking, decide how deep you actually need to look — the difference between depth 20 and depth 100 is five times the requests.
Sizing a rank tracker
| Keywords × locations | Depth | Requests / day | Transfer / month* | At €1.20/GB |
|---|---|---|---|---|
| 500 × 1 | Top 10 | 500 | ~4.5 GB | ~€5 |
| 500 × 5 | Top 20 | 5,000 | ~45 GB | ~€54 |
| 2,000 × 10 | Top 20 | 40,000 | ~360 GB | ~€430 |
| 2,000 × 10 | Top 100 | 200,000 | ~1,800 GB | ~€1,620 at the €0.90 volume rate |
*Assumes around 300 KB of HTML per result page, fetched without images and scripts, checked daily. Measure your own pages — SERPs vary between roughly 200 and 400 KB depending on features.
City-level residential exits
Residential from €1.20/GB with country and city targeting on every plan; Omni adds ASN targeting and custom session TTL. Volume pricing from 50 GB.
Staying unblocked
- Low volume per exit. A handful of queries per IP, then rotate.
- Human pacing with jitter — seconds between queries, not a burst.
- No cookie carry-over between IPs. Fresh cookie jar per session.
- Detect the block explicitly — a
/sorry/redirect or a 429 — and retire that exit. - Spread schedules across the day rather than running everything at 03:00.
The mechanics of parsing and pagination are in how to scrape Google search results. Google's terms do not allow automated queries; for mission-critical reporting, a commercial SERP API is the lower-risk route, and proxies remain the tool when you need your own control over location and schedule.
Frequently asked questions
Do I need proxies for SEO rank tracking?
Yes, at any meaningful volume. Google limits automated searches per IP address and personalises results by location, so you need many residential exits in the right locations to get accurate, unblocked rankings.
Which proxies are best for rank tracking?
Rotating residential proxies with city-level targeting. Datacenter proxies are flagged by Google very quickly, and mobile proxies are usually more expensive than the job requires.
Why does tracking the top 100 cost more now?
Google stopped honouring the num=100 parameter in September 2025, so the top 100 results require paging through ten result pages. That is roughly ten times the requests and bandwidth per keyword.
How do I track local rankings for a specific city?
Use a proxy exit in that city, set the country and language parameters to match, send a matching Accept-Language header, and start each batch with a fresh cookie jar so earlier searches do not personalise the results.
The seamless team runs residential, ISP and datacenter proxy infrastructure and writes these guides from day-to-day operational experience.
Ready to try seamless proxies?
Residential, ISP and datacenter proxies with no data expiry.
Browse PlansKeep reading
How to Scrape Google Search Results
Which proxies survive Google, the search parameters that control localisation, how to read CAPTCHAs as a rate signal, and a working Python example.
Troubleshooting“Our Systems Have Detected Unusual Traffic”: Why Google Shows It and How to Stop It
Google is not accusing you personally. It is saying the IP address you share has sent more automated-looking searches than it tolerates — and that changes what the fix is.
Buyer GuidesResidential Proxy Pricing Explained: What You Pay For Per Gigabyte
The headline per-GB rate is only one of four numbers that decide your bill. The other three are page weight, validity period and volume.