Pick a proxy by the job it has to do
Everyday residential
Location-aware browsing
Advanced identity
Priority pools and ASN control
What teams run on Ludax
Collect
Gather public data at volume
Verify
Confirm what each market sees
Understand
Turn signals into decisions
Enter a keyword, choose the market and device, and read the search results exactly as someone there would see them — the Google results shown in Austin on mobile, not the ones shown to your office.
What Ludax provides: the location you check from and a consistent network and device profile, so repeat checks stay comparable. What you provide: the rank tracker, parser, browser or SEO tool that collects and stores the rankings. Ludax is not a hosted rank-tracking dashboard.
Try it — sample results. Change the keyword, market or device and watch the results reorder, the way they do when the check runs from that place.
VISIBILITY, LAST 8 CHECKS · US / AUSTIN · MOBILE
Sample data for illustration. Every panel and figure on this page is an example of what a localized check returns — not a measured result or a ranking promise.
The same keyword can rank #4 nationally, #11 in Austin and #2 in Denver — so where you check from is part of the result. Most unreliable rank data is not a parser bug. It is a collection bug: the check ran from the wrong place, on the wrong device profile, or across an address that changed halfway through.
Search engines localize on the requesting address, and a hosting range is not where your customers are. Country is the baseline; city is what makes local-pack data meaningful.
One keyword, three answers: US national #4 · Austin #11 · Denver #2.
A mobile result page carries more paid and feature modules above the organic block, so the same position number occupies less screen. Averaging the two hides both.
Keep one device profile per series, and match the TLS profile to the user agent you send.
Query, then page two, then a refinement — if the exit rotates between steps the engine sees three unrelated visitors and the sequence stops being comparable.
Hold one sticky session per keyword walk: -session-kw118-time-5.
Positions also wobble a place or two between identical checks. Compare against a rolling median rather than treating every check as news.
Compare the same keyword across cities and the pages barely match: different language, currency, domains and a different order of blocks on the page. Pick a market to see what a searcher there is served, and the gateway setting that reads it.
WHAT FILLS THE TOP OF THE RESULTS PAGE · AUSTIN, US · MOBILE
STYLIZED LAYOUT VIEW · SAMPLE DATA
YOUR_PASSWORD-country-us-city-austinYOUR_PASSWORD-country-gb-city-londonYOUR_PASSWORD-country-de-city-berlinYOUR_PASSWORD-country-jp-city-tokyoYOUR_PASSWORD-country-br-city-sao-pauloAdd the country — and the city when the keyword has local intent — to the password field, then pin one device profile per series.
Browse locationsRotate between keywords so each query is read fresh, but hold a sticky session for the steps inside a single check. Five minutes is usually enough; retry on a new token rather than reusing one that failed.
Parameter referenceCheck the shape of the document before you store a row, keep the SERP features that surrounded each position, and alert on sustained movement instead of single checks.
Residential TLS detailsLUDAX delivers the localized page; your parser decides what to record. Pick a signal to see the settings we would start with.
The core series. Rotate an exit per keyword so no single address carries the whole set, and keep the device profile fixed so the trend line stays comparable.
SAMPLE DATA · POSITION BY MARKET
Pack membership changes with the searcher's city, so a national check cannot see it. Target the city and hold the session for the whole check, including a map expansion if you read one.
SAMPLE DATA · PACK POSITION BY CITY
A new module above the organic block pushes you down the screen without changing your number. Record the features present on every check — snippet owner, paid slots, carousels — and the drop explains itself.
SAMPLE DATA · PAID SLOTS ABOVE ORGANIC
Store the whole first page, not just your row. Share of results tells you whether a drop was your page losing ground or a new entrant taking two slots at once.
SAMPLE DATA · SHARE OF PAGE ONE, US
Country targeting is the reliable baseline; city targeting narrows the exit to a metro area and is what makes local-pack monitoring meaningful. Availability varies by market and by moment — treat a city parameter as a strong preference, log the exit's reported region with each check, and discard rows that do not match.
Run a series at the same local hour so you are not comparing a morning page with an evening one. Spread queries with jitter instead of firing a keyword list in a tight loop, and rotate the exit between keywords. Daily suits money terms; weekly is enough for the long tail.
Assert the shape of the document before you trust it: a minimum count of organic nodes, the expected locale, and no interstitial markers. An interstitial returns HTTP 200 and parses cleanly, so without that check it lands in your warehouse as a day when you ranked nowhere.
Read public result pages at a reasonable pace, for your own measurement. Do not use the network to click competitors' ads, manipulate engagement signals, or circumvent access controls — the acceptable use policy prohibits it and accounts are terminated for it.
import requests
USER, PASS = "YOUR_USERNAME", "YOUR_PASSWORD"
def proxy(country, city=None, session=None, profile="chrome145"):
pw = f"{PASS}-country-{country}"
if city: pw += f"-city-{city}"
if session: pw += f"-session-{session}-time-5"
pw += f"-profile-{profile}"
url = f"http://{USER}:{pw}@gw.ludaxproxy.com:9999"
return {"http": url, "https": url}
# one sticky context per keyword walk, rotate between keywords
r = requests.get("https://www.google.com/search",
params={"q": "best standing desk", "num": 20, "hl": "en"},
proxies=proxy("us", city="austin", session="kw118"),
timeout=30)
# validate the shape before storing the row
assert r.status_code == 200 and r.text.count("<h3") >= 8gw.ludaxproxy.com:9999 (Residential TLS · HTTP and HTTPS)Full parameter reference in the documentation.
Daily for the terms that drive revenue, weekly for the long tail. Compare each check against a rolling median and alert only on movement that survives two consecutive checks.
Yes. Add -city-austin to the password field on residential exits. City availability varies by market, so log the exit’s reported region with every check and discard rows that do not match.
Whichever your customers use, kept as separate series. Mobile result pages carry more paid and feature modules above the organic block, so the same position number means less screen space.
That is your parser’s job. LUDAX delivers the localized page; recording which modules appeared explains traffic changes on days when the position number did not move.
Residential TLS is the product priced on this page: $1.49 for 1 GB, down to $0.74 per GB at 1 TB. Standard Residential is a separate product from $0.49 per GB, without pinned browser handshakes. Neither can promise a challenge-free check.
Buy the smallest amount of traffic, run your keyword set from inside the market you sell in, and compare it with whatever you are reporting today.
$1.49/ 1 GB · $0.74 / GB at 1 TB