Location-accurate results
Route each check through an exit in the country or city you track, with locale and timezone kept consistent so local packs and regional results render normally.
use case
Track search rankings from any location, at scale
Rankings are local, personalised and increasingly rendered by JavaScript. Xymotrone loads public result pages in real Chrome from the market you specify, on a schedule, and stores the page it saw alongside the positions it read.
Publicly available result pages only · rate-limited collection · respect for site terms
Rendered, not guessed
Result pages are read after JavaScript runs, so features that load client-side are captured instead of missed.
Scheduled cadence
Daily, weekly or custom schedules per keyword set, queued inside your concurrency ceiling rather than fired all at once.
Rotating IP network
Bring your own residential or ISP pool; exits rotate per session and are validated before the first request.
Screenshot per observation
Every ranking data point keeps the result page image, so a disputed movement can be checked against what was actually served.
Pipeline-ready output
Structured run output slots into a warehouse or reporting stack as a data pipeline browser step.
Questions people ask
How do I track search rankings from another country?
Assign a proxy pool with exits in that country to the task. The session's locale and timezone are aligned to the exit, so the result page reflects that market rather than your office location.
Can I monitor JavaScript-heavy result features?
Yes. Because the page runs in real Chrome, client-rendered modules are present in the DOM and in the screenshot when the page is read.
How do you keep collection polite?
Concurrency ceilings and run budgets are enforced per plan, schedules spread load over time, and volumetric patterns are prohibited. Customers are expected to honour the terms and robots directives of the sites they configure.