Proxies for SERP tracking: location, device and pacing

Originally published on proxymint.

Why rank data drifts when the location parameter and exit IP disagree, how to set city-level exits, which proxy type fits, and what Google's rules say.

TL;DR

• The exit IP is part of the measurement. Search engines read the IP's location on every request, so where the proxy exits changes the results a tracker records.
• A location parameter is a hint, not a relocation. Google documents its gl parameter as a boost for results from that country; when it disagrees with the exit IP, rankings drift between runs.
• Local rankings need city-level exits. Map packs follow the searcher's position, but city geolocation is far less certain than country, so verify the location each results page reports.
• Read the engine's terms first. Google's spam policies, updated August 28, 2026, name rank-checking scrapes without permission as machine-generated traffic.

Key takeaways

• Set the parameter and the exit to the same place. Log the exit IP and its city on every check and discard checks where the page's own location disagrees.
• Clear cookies per city. A cached location can persist for hours and carry one city's results into another city's check.
• Treat a block as a stop. Log a captcha as no data, pause that job, and never record it as not ranking or push it through a fresh exit.
• Match the tier to the keyword set. Country-level tracking on engines that tolerate hosting traffic runs on datacenter; local packs need city-level residential.

Read the full guide on proxymint, with the commands, tables and sources.