Use cases
Proxies for SEO and SERP Tracking
Search results are personalised and localised by design. A rank tracked from the wrong country, language, or device is not measuring the ranking anyone else actually sees.
What breaks without the right network
Search engines vary results by geography, language, and device, and they rate-limit or block scripted checks aggressively — a tracker running from one origin gets a distorted result, then gets blocked for asking too often.
- Results that differ by country, language, and device, sometimes down to the city
- Rate limits and CAPTCHA challenges triggered by repeated automated queries
- Outright blocks on origins the search engine has already flagged
- A share-of-voice number skewed by whichever market the checks actually ran from
What actually changes the outcome
Consumer-grade origins for a consumer-facing query
Residential addresses carry the same consumer-ISP reputation a real searcher's connection has, which matters for a target that treats data-centre traffic differently from the start.
Enough volume for a real keyword set
38M+ residential addresses across 190+ countries means a large keyword-by-market matrix can run without repeating the same handful of origins.
A cheaper lane for bulk rank checks
Datacenter addresses, dedicated and unmetered at 10 Gbps, are the practical choice once the job is a large batch of rank checks rather than a handful of high-value queries.
One credential format across both
Residential and datacenter sit behind the same gateway, so a tracker can split easy, high-volume keywords to datacenter and sensitive ones to residential without two integrations.
Coming soon
A dedicated SERP API — locale, language, and device as parameters, parsed rows back instead of markup — is coming soon. Until it opens, run rank tracking on the proxy lines above; the API is not yet priced or available.
Which network to put this on
Primary
Residential
A search result checked from a consumer-grade address is closer to what an actual searcher sees, and is less likely to be treated as automated traffic from the first request.
from $1.75 / GB
Alternative
Datacenter
For a large keyword set where cost per check matters more than blending in, dedicated datacenter throughput runs the batch at a lower rate.
from $1.50 / IP / month
A workflow this fits into
- 01Build the keyword-by-market-by-device matrix the tracker needs to cover
- 02Run each query through the network with the country and language the result should reflect
- 03Parse the returned page into ranking rows rather than storing raw markup
- 04Feed rows into a reporting pipeline and re-run on whatever cadence the tracking programme needs
Publicly available data, used lawfully
Every recommendation above assumes lawful collection of publicly available data. Our acceptable use policy governs what is and is not permitted on this network, and sourcing and compliance explains where the addresses themselves come from.
Questions we get about this
- Is there a SERP API I can call directly?
- Not yet. A SERP API is coming soon, billed on the same request meter as the rest of the data products, but it carries no price and is not on general sale today. Track rankings on the proxy lines above in the meantime.
- Can I get results as they would appear in a specific city?
- ISP and datacenter support country-level targeting. Residential and mobile give broad international coverage without a per-request city or country selector at checkout, so city-level personalisation is not something either line can guarantee today.
- How do you avoid getting blocked by the search engine?
- Rotation across a large, diverse pool is the main defence — a request that looks like one of millions of ordinary consumer connections is a poor target for a block list built around repeat automated origins.
- Can I track rankings on mobile search separately from desktop?
- Yes. Mobile addresses reach the target from a genuine carrier connection across 100+ countries, which is the right origin for a mobile-specific ranking check rather than a desktop residential or datacenter address.
- Is scraping search results against the rules?
- It has to be a use our acceptable use policy permits, and it is subject to the target's own terms and applicable law. Publicly available search results are generally fine to collect; read the acceptable use policy before scoping a large tracking programme.
Other use cases
Ad Verification
Confirm creatives render where they were bought, from a real consumer vantage point.
View use case
Market Research
Collect a representative sample without one origin defining what you see.
View use case
Brand Protection
Sweep marketplaces and platforms for misuse the way a real buyer would find it.
View use case
Ready to run seo and serp tracking on the right network?
Create an account and order from 1 GB or 1 IP, or talk to sales if you want the volume ladder priced against your own numbers first.
One business day, from a named engineer.