I’m helping test a retail site that changes prices, pickup locations, and special offers based on where the visitor is. We need to check how everything looks in Dallas, Toronto, and London, but the whole QA team works from one office. A VPN changes the IP, yet the site sometimes jumps back to our real city as soon as we allow location access, and a few pages still show the wrong time zone. How can I properly change the location for each test without asking someone in every city to check the site for us?

You don’t need a complicated setup just to check whether the right store or offer appears once. Chrome has a Sensors panel in its developer tools where you can enter coordinates for a city and reload the page as if the browser were there. Use a clean browser profile with no saved permissions or old site data before each test. That should be enough to catch basic problems with maps, pickup points, and local pages.

That works for a quick check, but repeated testing gets messy when the IP says Dallas while the browser still shows your real time zone, language, or WebRTC data. The site can see that those signals don’t belong together and serve a different version of the page. You can read about geolocation spoofing here: https://gologin.com/blog/guide-to-geolocation-spoofing/ . For regular regional testing, keep one antidetect browser profile for each market and connect it to a proxy from the same location. Reopening the same profile each time will also keep cookies and test history from one region out of the others.