A search for "emergency plumber" in Dallas and the same search in Denver return different businesses, different map results and different ads. From your own office you only ever see one of those pages. This guide explains why Google changes results by location, why the usual workarounds give misleading answers, and how to see what searchers in any US city actually see, with a short workflow you can run today.
Google tries to answer the question the searcher means, and for many searches that depends on where they are. Several parts of the results page are local:
Your office connection resolves to one city, so every search you run shows that city's version of Google. Your account history and cookies push results further toward your usual location. To see another market, the search has to come from that market.
Mobile vs Residential vs Datacenter Proxy vs VPN explains in detail why datacenter and VPN traffic is treated differently from real user connections.
A city-targeted mobile proxy sends your searches through a phone connection on Verizon, AT&T or T-Mobile in the city you choose. To Google, the search arrives from the same kind of address that local phone users search from every day, so the location signal is real rather than approximated.
The IP only does part of the job. Keep the rest of the browser consistent with the location:
America/Denver for Denver). A browser in Eastern time with an IP in Mountain time is an obvious mismatch.en-US, and Google opened on google.com in English.Check where Google thinks you are. Mobile carrier IPs are sometimes geolocated to a nearby hub instead of the exact city. Before recording anything, run a local search such as "pizza near me" and check that the map pack and the location shown at the bottom of the results page match the city. If not, switch the proxy to a nearby city and check again.
Agencies that also manage several ad accounts should keep each account's environment separate as well; see How to Run Multiple Ad Accounts Without Getting Banned.
denver, dallas). A RelayKit cloud browser profile works well: attach the city's proxy, and the profile keeps its own cookies and fingerprint, separate from your everyday browser and from the other cities.denver profile with the Denver proxy attached.dallas and atlanta.If you script part of this, for example with Playwright to take screenshots, set the browser context to match the city. Keep it to the same small, spaced-out set of searches you would run by hand:
Stay within the rules. Automated, high-volume querying of Google Search is against Google's terms. For daily tracking of large keyword lists, use a rank-tracking tool or a search results API, and keep the proxy for spot checks, screenshots and visual review. Never click ads you are only researching. If you build an AI agent that browses search results, the same limits apply; see Mobile Proxies for AI Agents.
Google sees an IP address from a US mobile carrier in that area, the same kind of address real phone users in the city search from. It does not see your office IP. It can still notice automated behavior: hundreds of searches in a few minutes, identical timing, or a browser whose time zone and language do not match the location. Search the way a person would and keep the browser consistent with the city.
For manual checks, a few dozen searches an hour per IP with natural gaps between them is comfortable. If Google shows an "unusual traffic" page or a CAPTCHA, stop for a while and slow down. Automated querying of Google Search is against Google's terms, so for daily tracking of hundreds of keywords use a rank-tracking tool or a search results API, and use a proxy for spot checks and visual review.
Yes. Rankings, the number of ads, the size of the map pack and other features often differ between mobile and desktop. Check the device your customers actually use. A phone-sized browser window with a mobile user agent shows mobile results; a normal desktop window shows desktop results.
Viewing an ad does not cost you a click, but repeated searches that show your ad without a click can lower its click-through rate. Google Ads has a built-in Ad Preview and Diagnosis tool that shows your ads by location without counting impressions; use it for routine checks. Never click your own or a competitor's ads to test them.
Mobile carrier IPs are sometimes geolocated to a nearby hub rather than the exact city, and a signed-in Google account or old cookies can pull results toward your usual location. Use a signed-out, clean profile, check what location Google shows at the bottom of the results page, and pick a nearby city on the proxy if the geolocation is off.
Dedicated 4G/5G mobile proxies on Verizon, AT&T and T-Mobile, with Multi Location plans you can switch between US cities from the dashboard. Pay as you go, no monthly commitment.