docs.example.dev
Residential proxy integration guide
Configuration, session policy, validation, and failure handling.
Scheduled search observation
Rank tracking proxies for location-aware SERP checks with explainable results
Record query, market, device assumptions, route, timestamp, result markers, and retry reason so ranking changes are separated from collection failures.
residential proxy api
capturedresearch.example.org
Location-aware data collection workflow
A reproducible method for collecting and reviewing public search pages.
status.example.net
Proxy route and response diagnostics
Record route, response status, retry reason, and accepted-page evidence.
A repeatable rank-tracking run
Use the same acceptance rules across scheduled checks so a challenge page or wrong locale never becomes ranking data.
Define query and location
Store keyword, country, region or city, language, device profile, search engine, and schedule.
Create an independent observation
Use rotation for independent queries and a short sticky session only when several requests form one check.
Validate the SERP
Confirm status, locale, expected search markers, final URL, and challenge-page signals.
Extract and normalize positions
Record result URL, domain, position, feature type, and page depth using a stable schema.
Publish with collection context
Store route mode, timestamp, retries, and failure class alongside the accepted ranking observation.
Rank changes and collection failures must be separated
A useful tracking system records why an observation was accepted or rejected.
Feature
✕Unvalidated check
✓Validated check
Requested location recorded
May be assumed
✓Explicit market context
Observed locale verified
Can silently drift
✓Checked before parsing
Challenge page rejected
Can become false rank loss
✓Classified as collection error
Retry reason stored
Missing evidence
✓Auditable schedule
Guarantee identical SERPs
Search results vary
Results still vary
Rank tracking proxy FAQ
Why can rankings differ for the same keyword?+
Location, language, device, personalization, search experiments, time, and index changes can all affect results. Store the observation context and compare like with like.
Should each keyword use a new IP?+
Independent checks can rotate, but route policy should be bounded and consistent. A multi-page check may use a short sticky session to keep one observation coherent.
How is a blocked SERP handled?+
Reject it as a collection failure, store the response class and retry reason, and do not convert missing results into rank loss.
Do proxies replace a SERP parser?+
No. The proxy provides network routing. You still need response validation, parsing, normalization, scheduling, storage, and reporting.