# Proxy for rank tracking: checking local Google results by country

URL: https://cloudj.net/blog/local-seo-rank-tracking-proxy
Published: 2026-11-11 · Updated: 2026-11-11

> How to use a proxy for rank tracking in the US, UK, Japan and Singapore: localized results, gl and hl parameters, sensible request rates and compliant tools.

A proxy for rank tracking answers a simple question that your office connection cannot: what does Google show to a searcher in another country? If your team sits in Hanoi and your client sells in London, the results you see at your desk are not the results that matter. A country IP, combined with the right search parameters, lets you spot-check local rankings in the US, UK, Japan or Singapore. This guide explains what actually localizes search results, how to set up a check, and where the limits are, both technical and contractual.

## Why your own results are misleading

Search engines personalize and localize results using several signals at once:

- **IP location**: the country and often the city the request appears to come from.
- **Interface language and country settings**: set by parameters in the search URL or by account preferences.
- **Signed-in history**: a logged-in browser can see results shaped by past activity.
- **Device type**: mobile and desktop results can differ.

A proxy handles the first signal. The others you control yourself: use a clean browser profile that is not signed in, set language and country explicitly, and decide whether you are checking mobile or desktop. Changing only one signal and expecting a perfect local view is the most common mistake.

## The gl and hl parameters

Google's search URL accepts parameters that state the country and language you want results for. Two are worth knowing:

- `gl` sets the country, as a two-letter code, for example `gl=us`, `gl=gb`, `gl=jp`, `gl=sg`.
- `hl` sets the interface language, for example `hl=en` or `hl=ja`.

A manual UK check might use a URL like this:

```text
https://www.google.com/search?q=project+management+software&gl=gb&hl=en
```

Parameters alone tell Google which market you want, but the request still comes from your real IP. Pairing `gl=gb` with a UK IP gives a more consistent picture, and lets you check results on the local domain, such as `google.co.uk`, as a British searcher would. City-level differences, such as local packs in Manchester versus London, are harder to reproduce; treat country-level checks as reliable and city-level checks as indicative.

## Choosing the country IPs

Cloudj offers dedicated proxies in seven countries, including the four most rank-tracking teams ask about:

| Market | Proxy type available | Where to order |
|---|---|---|
| United States | Static residential ISP or dedicated IPv4 (static ISP) | [US proxies](https://cloudj.net/proxy-ipv4/united-states) |
| United Kingdom | Dedicated IPv4 (static ISP) | [Proxy overview](https://cloudj.net/proxy-ipv4) and the console |
| Japan | Dedicated IPv4 (static ISP) | [Proxy overview](https://cloudj.net/proxy-ipv4) and the console |
| Singapore | Dedicated IPv4 (static ISP) | [Proxy overview](https://cloudj.net/proxy-ipv4) and the console |

Vietnam, South Korea and Hong Kong are also available. Stock can vary by location, and the console shows what is in stock.

Static residential ISP proxies are residential IPs from a home internet provider that stay the same, so they look like a regular user. Some teams prefer them for US checks; read [US static ISP proxies](https://cloudj.net/blog/us-static-isp-proxy) for the trade-offs, and [buying a US proxy](https://cloudj.net/blog/buy-us-proxy) for sizing. For the other markets, a dedicated IPv4 static ISP proxy, registered to an ISP and assigned only to you, is fast, stable and usually fine for occasional manual checks. Country guides cover each market: [UK proxy](https://cloudj.net/blog/uk-proxy), [Japan proxy](https://cloudj.net/blog/japan-proxy) and [Singapore proxy](https://cloudj.net/blog/singapore-proxy).

## Setting up a proxy for rank tracking, step by step

1. Order one IP per market in the [Cloudj console](https://app.cloudj.net). Orders run from 1 to 1,000 IPs, for 1, 3, 6 or 12 months, paid from your account balance, and are usually ready in a few minutes.
2. Copy the host, port, username and password. Choose HTTP or SOCKS5 where the location supports it.
3. Create one browser profile per market, signed out of every Google account, and add that market's proxy to it. The guide on [setting up a proxy in Chrome and Firefox](https://cloudj.net/blog/setup-proxy-chrome-firefox) shows where.
4. Confirm the IP from the terminal before you start:

```bash
curl -x http://USERNAME:PASSWORD@HOST:PORT https://ifconfig.me
```

5. Run each keyword with explicit `gl` and `hl`, record the position, the URL ranking and any local features such as maps or shopping results.
6. Repeat at the same time of week, from the same profile, so results are comparable over time.

## Rate limits and the rules

Here is where many rank-tracking setups go wrong. Google's terms of service restrict automated querying of its search results, and search engines throttle or challenge traffic that sends many queries quickly from one IP. A dedicated proxy is one fixed IP; it is not designed to send thousands of automated searches, and it should not be used to get around CAPTCHAs or other access controls.

Practical guidance:

- **Manual spot checks** of a modest keyword list, at a human pace, are a normal use of a country IP.
- **Your own site's data** is best taken from Google Search Console, whose performance report can be filtered by country. It shows real impressions and average position from Google, with no proxy needed.
- **Large keyword sets** belong in a rank-tracking tool or data provider that collects results in line with the search engine's terms. Check the tool's documentation on how it gathers data.
- **Your own scripts** against other websites should respect robots.txt and each site's terms, run from a server, and keep request rates low. The guide on [web scraping from a US VPS](https://cloudj.net/blog/web-scraping-vps-united-states) covers the server side.

## When something looks wrong

| Symptom | Likely cause | Fix |
|---|---|---|
| Results still look local to your office | Proxy not applied to the profile | Check the profile proxy settings, then test the IP |
| Results in the wrong language | `hl` missing or overridden by a signed-in account | Sign out and set `hl` explicitly |
| CAPTCHA or "unusual traffic" page | Too many queries too quickly | Slow down; move bulk tracking to a compliant tool |
| Results differ day to day | Normal ranking movement or personalization | Compare trends over weeks, not single checks |

For the basics of dedicated proxies, including authentication by password or by an IP whitelist of up to 20 addresses, start with the [dedicated proxy guide](https://cloudj.net/blog/dedicated-proxy-guide).

## FAQ

### Do I need a proxy if I use the gl parameter?

Not strictly, but `gl` alone still sends the request from your real location. A country IP makes the check closer to what a local searcher sees.

### Can I run an automated rank tracker through one dedicated proxy?

That is not a good fit. Search engines restrict automated queries, and one fixed IP will hit limits quickly. Use a compliant rank-tracking tool for volume.

### Which markets can I check with Cloudj proxies?

Vietnam, the United States, Japan, South Korea, Singapore, Hong Kong and the United Kingdom. The console shows current stock.

### Can I stop an order if it does not suit my workflow?

Within 24 hours of ordering you can stop an order and get the unused part back to your balance.

## See the results your customers see

Start with one IP in each market you report on, keep checks manual and modest, and use Search Console and compliant tools for volume. Live prices are on the [pricing page](https://cloudj.net/pricing), and you can order in the [Cloudj console](https://app.cloudj.net).