Track rankings without personalized, biased SERPs.
Clean residential IPs return neutral, location-accurate search results, so rank trackers report what a real searcher in that market actually sees.
Why this needs proxies
Sites vary what they return based on where the request appears to come from, and they rate-limit or block addresses that ask too often. Both problems have the same fix: exit from real consumer IPs in the right places, and spread the load so no single address looks unusual. That is the whole job a proxy does here.
The reason residential IPs succeed where datacenter ones fail is classification by ASN. Hosting networks can be challenged wholesale with a single rule; consumer ISP networks cannot, because doing so would block real customers.
Recommended products
| Product | Price |
|---|---|
| Budget Residential | $1.75/GB |
| Rotating Datacenter | $1.00/GB |
Start with the cheapest option your target tolerates and move up only when it blocks you. Concurrent sessions are unlimited on every plan and country targeting is included in the price. Full tiers are on our pricing page.
How this works in practice
- Pick the cheapest product that works. Test the target on rotating datacenter first; move to residential only when you are actually refused.
- Choose the exit country deliberately. The data you get back is the data that country sees, so record which exit produced every record.
- Decide rotation vs sticky. Per-request rotation suits stateless collection; anything with a login or a multi-step flow needs one IP held for the whole session.
- Pace against the target, not your budget. Back off on 429 responses instead of rotating past them, and randomise intervals rather than hitting on the hour.
Common mistakes
- Rotating inside a session. The single most common cause of empty results and flagged accounts.
- Mismatched signals. An exit in one country with an Accept-Language header for another creates a visitor that does not exist, and some sites respond to the contradiction.
- Paying for residential too early. Plenty of targets never check, and the gap between $1.00/GB and $2.75/GB is substantial at volume.
- Not recording the exit. Data without its point of observation cannot be compared across markets.
Sizing your bandwidth
Work from page weight rather than guesswork. A page averaging 250 KB across 100,000 requests is roughly 25 GB. JSON APIs are far lighter, often a few kilobytes per call, while anything rendered in a headless browser pulls images and scripts too and can be several times heavier. Start at 1 GB, measure your actual average, then buy the package that matches.
Getting set up
Every product speaks HTTP(S) and SOCKS5, so this is a one-line change in most stacks. Credentials are assembled from a variable below rather than pasted inline, because a literal user:pass@host string in page copy can be rewritten by email-obfuscation filters.
import requests
endpoint = "geo.spyderproxy.com:12321"
creds = "USERNAME:PASSWORD"
proxy = f"http://{creds}@{endpoint}"
r = requests.get(
"https://example.com",
proxies={"http": proxy, "https": proxy},
timeout=30,
)
print(r.status_code)Confirm your exit is landing where you expect with the IP lookup tool before starting a long run. Bandwidth products begin at 1 GB, so you can validate for under $2.
Frequently Asked Questions
Why do rank trackers need proxies?
Google personalises by location, search history and device, and it rate-limits repeated automated queries from one IP fast. Clean residential IPs in the target market return the neutral, location-accurate SERP a real searcher would see, which is the only ranking data worth reporting.
Can I track local rankings in specific cities?
Yes. Premium Residential supports city-level targeting, so you can check how a business ranks in Manchester versus London rather than settling for a country-level average. This is essential for multi-location and local SEO work.
How many SERP checks can I run per day?
There is no per-request cap on our side and concurrent sessions are unlimited. In practice you are limited by bandwidth: a SERP page is roughly 300-600 KB, so 10,000 daily checks is about 3-6 GB. Budget Residential at $1.75/GB is usually the right product.
Do I need residential, or will datacenter do?
Google blocks known datacenter ranges aggressively and increasingly serves them altered results rather than an outright block, which is worse because the data looks fine and is wrong. Use residential for SERP work.
Can I track AI search results too?
Yes. The same approach applies to AI Overviews and to AI search engines: they geo-vary, so a neutral local IP is the only way to see what a user in that market is actually shown. See our guide to proxies for SEO and rank tracking.