Proxies for SEO and SERP checking
Search results differ by region, and positions have to be checked regularly across many queries. From a single address such a run quickly hits limits, and the results come back tied to that address's location. A pool with country selection solves both problems: volume and geography.
From 1 375 ₽ a month for 100 threads.
Threads in the plan
Choice of exit region
The address is held for a set time
Both protocols
The request region determines the result
Positions, snippets and the composition of results depend on where the request came from. Checking from one location describes only that location, and it will not match what a user in another country sees. For data to reflect your target market, the request has to come from an address in that market.
Working with SEO tools
Key Collector, A-Parser, Netpeak Checker, Screaming Frog and similar programs accept either proxy lists or a single rotating gateway. The second option is easier to maintain: one address goes into the settings and the service handles IP changes. There are no lists to refresh or prune of dead entries.
Position tracking versus technical audits
These have different profiles. Position tracking is many short requests, where thread count matters. Crawling your own site is a long sequence against one domain, where a stable address is usually preferable so you don't distort logs or confuse analytics. The first calls for rotation, the second for a static address.
What people take for this
Three products. The difference is the address type and whether it changes: some jobs need a pool, others a single fixed IP.
- 10 different /29 networks
- Rotation: per-request or time-based
- Connections as you need
- HTTP, SOCKS5
- User/pass and IP — at once
- 10,000+ rotating IPs
- Rotation: per-request
- Connections as you need
- HTTP, SOCKS5
- User/pass and IP — at once
- 15,000+ static IPv4
- Dedicated stable IPs
- HTTP, HTTPS, SOCKS5
- User/pass and IP — at once
How to connect
Setup fits in one line: the program only needs a gateway host and port. Rotation happens on our side — the program never has to know about it.
- 1Pick a plan
The plan's thread count must be at least what the program is set to, or some connections will sit waiting for a free slot.
- 2Get the credentials
Gateway host, HTTP and SOCKS5 ports, login and password appear in the dashboard right after payment.
- 3Paste it into the program
One address instead of a list: any field that takes a normal proxy server with authentication will do.
Frequently asked questions
Short answers to what gets asked before ordering. Everything else goes to support, which answers around the clock.
How many threads does position tracking need?
It depends on keyword volume and check frequency. A thousand queries once a day runs comfortably on 50 threads. Checking tens of thousands of queries daily across several regions needs several hundred. Multiply queries by regions and divide by the collection time you can accept.Do I need proxies to check my own site?
For a technical audit, usually not — the crawler walks your domain from your address. Proxies matter in two cases: when the site serves different content by region and you need to verify that, and when the crawl is large enough to hit limits on your hosting or CDN.Which countries are available for regional checks?
The distinction that matters here is between choosing and merely having. On rotating IPv6 the country is selectable: Germany, the Netherlands, Austria, Russia, plus a mixed mode where it is not pinned; it can be changed later from the dashboard or through the API. On rotating IPv4 there is no country selection at all: addresses are assigned at random from a pool that spans Germany, the Netherlands, the United Kingdom, France, the United States, Canada, Italy, Spain, Austria, Brazil and Thailand. On static datacenter addresses you tick countries in the configurator (Canada, Germany, the United Kingdom, the Netherlands, the United States), but distribution across them is random too. If a check has to originate from one specific country, IPv6 is the only fit.How is timed rotation useful for SEO work?
It matters when a check consists of several linked steps: moving to the second results page, refining a query, working inside one session. With per-request rotation those chains fall apart, because each step arrives from a new address and the server sees unrelated requests.
Other use cases
- For multi-threaded software
- For parsing and scraping
- For marketplaces
- For antidetect browsers
- For captcha software
- Rotating IPv6 and IPv4
- IPv6 proxies
- Static datacenter IPv4
Covered in the blog
- SetupProxies in Key Collector: why account modules need static addresses, not rotationThe program splits into modules, and the right proxy differs per module. An account pins one address until restart, Google.Ads rejects IPv6 and SOCKS, and the browser handler drops SOCKS entirely.Read
- Deep diveChecking search positions: regional results, official limits and honest sizingWhy a single-address measurement shows nothing, how Yandex's lr differs from Google's lr, and which collection methods the engines themselves permit.Read
A pool for SERP checking
Country selection is available on rotating IPv6, from 650 ₽ for 50 threads. Rotating IPv4 is from 1375 ₽ for 100 threads, with pool countries assigned at random.