A website can sometimes place you in the wrong city even though a map app on the same device knows exactly where you are. That can affect local news, store suggestions, search results, language choices, or other location-based features.
The apparent contradiction usually has a simple explanation: there is more than one way to estimate where a device is. A site that has access to your device’s location can receive a fairly precise position. A site that does not may make a rough guess from your internet connection instead.
Understanding which kind of location a site is using makes these errors much easier to diagnose. It also explains why changing a browser permission can fix one problem while doing nothing to another.
Start with two different kinds of location
For everyday troubleshooting, it helps to separate location into two broad methods.
Device location is a position estimated by the phone, tablet, or computer. Depending on the device and its settings, location services can combine information from satellite navigation systems, nearby Wi-Fi networks, mobile networks, Bluetooth signals, and device sensors. The exact mix varies by platform and situation.
IP-based location is an estimate based on the public Internet Protocol address that a website sees when your connection reaches it. An IP address is needed for internet communication, but it is not a set of GPS coordinates. Location databases associate address ranges with approximate geographic areas using information gathered from network operators and other sources.
These methods answer the same practical question — roughly, “Where is this user?” — from very different evidence. They should not be expected to produce identical results.
A website does not automatically receive your phone’s GPS position
Modern browsers provide a geolocation feature that websites can request. When a site asks for this kind of location, the browser normally requires your permission before sharing it.
If you allow the request, the browser asks the device’s location system for a position. On a phone, that system may use GPS or other satellite signals, but it can also combine them with Wi-Fi, mobile-network, Bluetooth, and sensor information. The browser does not necessarily choose one positioning technology itself; it receives a location from the underlying device services.
This is why the familiar browser prompt matters. A site that you allow to use location may be able to place you close to your real position, subject to the device’s available signals and accuracy. A site that you deny does not simply get the same precise coordinates by another route.
However, denying location permission does not make your connection geographically anonymous. The website still sees network information needed to communicate with you, including a public IP address, and it can use that address for an approximate location estimate.
Why an IP address can point to the wrong place
An IP address identifies a network endpoint for routing traffic; geographic location is not built into the address itself. IP-location services therefore rely on databases that map address ranges to estimated places.
That estimate can be wrong for several reasons.
An internet provider may route customers through infrastructure in another city. A mobile carrier may have many users whose traffic reaches the wider internet through a smaller number of network gateways. An address range may also have been reassigned, while a location database still contains older information.
The result can look surprisingly specific. A website might confidently show the name of a city, but the city is still an estimate associated with the network address rather than a measurement of your physical position.
This distinction is important when judging the error. If an IP lookup places you 100 kilometres away, that does not mean your phone’s location sensor is wrong. The website may never have asked the phone for its location at all.
Why phones can often provide a better position
Satellite positioning works by receiving precisely timed radio signals from navigation satellites and using them to calculate a position. It works especially well when the device has a clear enough view of the sky, but signals can be weak or obstructed indoors and around dense buildings.
Phones can improve the practical location experience by using additional information. Nearby Wi-Fi networks and mobile-network information can help provide a position when satellite signals are unavailable or while the device is still obtaining a satellite fix. Sensors can also help the device interpret movement.
The important mental model is that modern phone location is often a combined estimate, not simply a GPS receiver reporting coordinates in isolation.
That also explains why a laptop without dedicated satellite-positioning hardware can sometimes provide a useful location. If its operating system and network environment provide other positioning information, the browser may still receive coordinates. Accuracy depends on the hardware, operating system, available signals, and location service.
Why the same website can behave differently on two devices
Suppose you open a store website on your phone and laptop while both use the same home internet connection.
On the phone, you allow the site to access location. The browser receives a position from the phone’s location services, and the site suggests a nearby branch.
On the laptop, you previously denied location access. The site falls back to an IP-based estimate. Because both devices share the same home internet connection, the public IP may be the same, but its database entry points to a neighbouring city. The laptop therefore suggests a different branch.
Nothing about this requires either device to be broken. The website is simply working with different location evidence.
A similar difference can happen within one device. A mapping site that has location permission may show your actual position, while an advertising or content system on the same page uses an IP-derived region for another purpose.
VPNs and some network setups change the IP location seen by websites
A virtual private network, or VPN, sends internet traffic through another network before it reaches the destination. To the website, the visible public IP address is then typically associated with the VPN connection point rather than your ordinary internet connection.
As a result, IP-based location may shift to the city or country associated with that VPN endpoint. This is normal for IP geolocation and does not mean the device itself believes it has physically moved.
Other network arrangements can create similar effects. Corporate networks, carrier networks, satellite internet services, and some internet providers can route traffic through infrastructure far from the user. The details vary, so an IP-derived city should be treated as an approximation rather than proof of physical location.
If a site has permission to obtain device location, it may still receive device-derived coordinates while your web traffic exits elsewhere. That is another reason different parts of an online service can appear to disagree about where you are.
What to check when a website has the wrong location
First, notice what the site is actually showing. A map marker that follows your movement is likely using device location, while a preselected city on a home page may simply come from an IP estimate or an account preference.
If the site has a “use my location” feature, check whether the browser has permission to provide location to that site. Browser labels and menus vary, so look for the site’s permissions or location access rather than following a platform-specific path from an unrelated guide.
If permission is already allowed but the position is inaccurate, compare the result with another app that uses device location. Poor satellite reception, disabled location services, restricted Wi-Fi or Bluetooth scanning, or platform-specific settings can affect the position available to apps and browsers.
If the site never requests location and merely guesses your city, changing GPS settings is unlikely to help. Check whether a VPN or work network is changing your internet exit point. If not, the IP-location database may simply be inaccurate. Some services let you choose a city manually, which is often the most practical workaround.
Also check whether the website has saved an old location in your account, browser storage, or site preferences. A remembered city can look like a failed location estimate even when no new estimate is being made.
Precise and approximate location are different expectations
It is useful to match the method to the job.
Turn-by-turn navigation needs a position precise enough to follow movement along streets, so device location services are appropriate. A news site that only needs to choose a national edition may not need precise coordinates at all; a broad IP-based region can be sufficient.
More precision is not automatically necessary for every service. Browsers and operating systems may also provide controls that limit or approximate the location shared with apps or websites. The available controls and their exact behavior depend on the platform.
For troubleshooting, the key question is therefore not only “Is the location correct?” but also “What kind of location is this feature trying to use?”
The practical takeaway
A website showing the wrong city does not automatically mean GPS is failing. Websites can receive device-derived coordinates when you grant location access, or they can estimate a region from the public IP address they see. Those two methods use different evidence and have different levels of accuracy.
When a location looks wrong, identify the method before changing settings. Check browser permission and device location services for features that need precise positioning. Check VPNs, network routing, saved site preferences, and the limitations of IP-location databases when the site is only making a regional guess.
Once you separate precise device location from approximate network location, many apparently mysterious location errors become ordinary differences between two estimation methods.