Web scraping
Collect public data at scale without bans, CAPTCHAs or rate limits.
Use case · SEO & SERP tracking
See search results the way searchers in each market see them. Query Google from city-level residential IPs, rotate on every check and keep a complete ranking history without gaps or CAPTCHA pages.
The challenge
The problems every team in SEO & SERP tracking runs into sooner or later.
Google tailors results to the searcher's city, and the local pack can shift within a few miles. One office IP shows a single version of the page, not what your customers see.
Repeated searches from one address quickly lead to the unusual traffic page and CAPTCHAs. Your tracker then returns gaps, and gaps in a daily ranking history are hard to explain to a client.
Keywords times locations times devices times days adds up. Tracking 2,000 keywords in 10 cities every day means 600,000 results pages a month, so the cost of each check decides your coverage.
The solution
Settings you control from the username, with no extra tooling or separate endpoints.
Add -city-chicago or -state-texas to the username and query from IPs registered in that area. Local packs and map results then reflect the market you actually report on.
Without a session parameter, each query leaves from a different residential IP. No single address builds up the query history that triggers throttling, so daily runs complete on schedule.
Skip HTML parsing entirely. Our Google SERP API returns organic results, ads, People Also Ask and local results as JSON for any country or city, from $0.16 per 1,000 requests.
Mobile and desktop results often differ. Send a mobile user agent through residential IPs, or set device=mobile on the SERP API, and track both layouts side by side.
Recommended
Start with the first one. Most teams add a second pool as their targets grow.
Get started
List each keyword with the countries, states or cities that matter to the business. Use two-letter country codes and lowercase city names with underscores, such as new_york.
Send each search through gw.proxonym.com:8000 with the location in the username, or call the SERP API with its location parameter when you prefer parsed JSON.
Record position, URL, SERP features and a timestamp for every check. Daily snapshots make ranking changes, competitor moves and local pack shifts easy to chart and explain.
Best practices for SEO & SERP tracking
# pip install playwright && playwright install chromium
import secrets
from urllib.parse import quote_plus
from playwright.sync_api import sync_playwright
KEYWORD = "emergency plumber"
DOMAIN = "example.com"
CITIES = ["chicago", "houston", "san_diego"] # lowercase, spaces as underscores
def check(p, city):
browser = p.chromium.launch(proxy={
"server": "http://gw.proxonym.com:8000",
# one sticky session per check: the whole page load uses one local IP
"username": f"USERNAME-country-us-city-{city}-session-{secrets.token_hex(4)}",
"password": "PASSWORD",
})
page = browser.new_page(locale="en-US")
page.goto(f"https://www.google.com/search?q={quote_plus(KEYWORD)}&hl=en&gl=us",
wait_until="domcontentloaded")
if "/sorry/" in page.url: # challenge page: slow down and retry later
browser.close()
return "challenge", None
page.wait_for_selector("#search a:has(h3)", timeout=15000)
links = page.locator("#search a:has(h3)").evaluate_all("els => els.map(e => e.href)")
browser.close()
for position, href in enumerate(links, start=1):
if DOMAIN in href:
return position, href
return "-", None
with sync_playwright() as p:
for city in CITIES:
position, url = check(p, city)
print(f"{city:<10} {position:>9} {url or 'not on page 1'}")FAQ
Still unsure? The help center answers billing, setup and account questions.
Open the help centerGoogle tailors results to the searcher's location and limits automated queries from a single IP. Residential proxies let you query from the cities you report on and spread checks across many addresses, so you collect complete, local rankings instead of one office view and a wall of CAPTCHAs.
Yes. Add -city- with a lowercase name and underscores instead of spaces, for example USERNAME-country-us-city-los_angeles, or use -state- for a wider area. Use one or the other, not both. With the SERP API, pass a location such as Chicago,Illinois instead.
Use the SERP API when you want structured data at volume: one request returns one results page as JSON, with organic results, ads, People Also Ask and local results. Use residential proxies when you run your own parser, need screenshots or track search engines other than Google.
On the SERP API, one results page is one request, so checking the top 20 for a keyword in one city takes two requests. Through proxies, you pay for the GB each page load uses. Block images, fonts and media in your browser to keep every check light.
Search results are public, and rank tracking is a long-established SEO practice. Google's terms still restrict automated queries, so keep volumes reasonable, avoid collecting personal data you have no reason to hold and check the rules that apply to your business. Our acceptable use policy applies to every account.
Platforms
Platform guides with targeting tips, ready-to-run code and the proxy types that work best on each site.
Related
Teams often combine these with SEO & SERP tracking on the same account.
Collect public data at scale without bans, CAPTCHAs or rate limits.
Gather localized content, reviews and trends in any market.
Check placements and catch ad fraud through genuine local IPs.
Pick a plan, pay with crypto and send your first request through Proxonym in minutes.