Short answer: use a static residential proxy targeted to the city you want to check, keep one sticky session per city, and open Google in a clean browser profile with the matching country and language. For automated tracking at volume, use a rank-tracking tool or SERP API and feed it residential IPs.
Why local results need a local IP
For searches with local intent ("dentist", "pizza delivery", "plumber near me") Google ranks by the searcher's location. A business can be first in one part of a city and off the first page five kilometres away. Searching from your office, even with the city name in the query, does not show what a local customer sees. The map pack in particular follows the searcher's location closely.
An IP from a home connection in the target city fixes that, because location is one of the strongest signals Google uses when the searcher is not logged in and has not shared GPS.
Which proxy type works best
| Proxy type | For local rank checks |
|---|---|
| Static residential, city-targeted | Best for manual checks. Real home IP in the city, held for the whole check |
| Rotating residential, city-targeted | Best for automated tracking of many keywords |
| ISP proxy | Good if you check the same city every day; city choice is limited |
| Datacenter | Captchas within minutes and often a wrong location |
City targeting accuracy depends on the provider and the country. Networks with large pools in your market, such as Bright Data, Oxylabs and Decodo, offer the most cities. Test a few lookups and compare the city with an IP database first; our guide to checking an IP shows how.
Manual check, step by step
- Create a sticky session for the city. In the proxy username, set country and city plus a session ID, for example
...-cc-us-city-chicago-sessid-chi1. Syntax depends on the provider. - Use a clean browser profile (a new Chrome profile or an antidetect profile) so your own search history and cookies do not influence the results.
- Set the profile's timezone and language to match the city.
- Confirm the location. Visit an IP echo page and check that the city is right before you search.
- Search on the country's Google domain, for example
google.comfor the US orgoogle.defor Germany, with&gl=us&hl=enin the URL to fix country and language. - Record organic position and map pack for each keyword, then move to the next city with a new session.
In the EU and UK you will see a cookie consent page first. Answer it once per session; the choice is stored in the profile's cookies.
What about the uule parameter?
Google supports a uule URL parameter that encodes a location, and many rank trackers use it to simulate a city. It is a useful extra signal, but results with uule alone and results from a real local IP do not always match, especially for the map pack. Using both, a local IP and a matching uule, gives the most consistent picture.
Automated tracking
For dozens of keywords across many cities, use a rank-tracking tool that lets you bring your own proxies, or a SERP API. Point it at a rotating residential endpoint with city targeting, keep the request rate low, and spread checks across the day. Note that automated queries are against Google's terms of service; dedicated SERP APIs exist for exactly this reason, and that risk is yours to weigh.
Traffic per check is small: a Google results page is a few hundred kilobytes when you block images. A few gigabytes of residential traffic covers thousands of manual-style checks. Proxare's GB calculator guide shows the maths.
Tips for reliable local data
- Check at the same time of day; local results shift with opening hours.
- Never mix cities in one session.
- If you get a captcha, end the session and start a new one rather than solving it repeatedly. Repeated captchas usually mean the IP is flagged; see proxy fraud scores.
- Save a screenshot with the IP and time. Clients trust a screenshot more than a number.
Compare every provider on Proxare
Static residential, ISP, rotating and mobile proxies from Oxylabs, Decodo, Bright Data, IPRoyal, Geonode, PacketStream and Proxare's own pools, side by side, at the lowest price we can offer.
Frequently asked questions
How do I see Google results for another city?
Connect through a residential proxy targeted to that city, use a clean browser profile with matching language and timezone, and search on the country's Google domain with the gl and hl parameters set.
Which proxies are best for local SEO?
City-targeted residential proxies. Static residential sessions are best for manual checks, rotating residential for automated tracking. Datacenter proxies get captchas quickly and often show the wrong location.
Is a VPN enough to check local rankings?
Usually not. VPNs offer few cities and use datacenter IPs, which Google often places in the wrong location or challenges with captchas.
How much proxy traffic does rank tracking use?
Very little. A results page is a few hundred kilobytes with images blocked, so a few gigabytes cover thousands of checks.