Why Is My Location Wrong? IP, Wi-Fi and GPS Location Explained
Why is my location wrong? Google, your browser and your phone guess where you are from GPS, Wi-Fi, cell towers or your IP address. How each fails, plus fixes.
In this guide
Your location is wrong because the site or app uses a weaker source than you expect. With permission, a device uses GPS, nearby Wi-Fi networks or cell towers. Without it, Google and most websites have only your IP address, which points to the area your network uses, not where you stand. A VPN, carrier network or wired desktop widens that.
Test it now
Cloudflare edgeRead at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.
Show detailsHow does a website or app decide where you are?
A website gets your position through the browser’s Geolocation API. The browser gets it from the operating system, which combines whatever signals the hardware has. The W3C specification says “the API itself is agnostic of the underlying location information sources” and gives no assurance that the result is the device’s actual location. Its usual inputs are GPS and location “inferred from network signals such as IP address, RFID, WiFi and Bluetooth MAC addresses, and GSM/CDMA cell IDs, as well as user input.”
Two rules in that specification explain most wrong-location complaints:
- Permission. Geolocation “requires express permission from an end-user,” and a request from a plain-http page fails with PERMISSION_DENIED. If you never saw a prompt, or you blocked it, the site never got a device position and is working from your IP address instead.
- Accuracy is a radius, not a promise. Every position carries an accuracy value, which the W3C spec defines as a 95% confidence radius in meters. A result with an accuracy of 2,000 meters is not a bug; the browser is telling the site that it only had coarse signals. Sites can ask for better data with enableHighAccuracy, but the spec calls that a “hint” the browser may ignore.
The spec also says the browser “always attempts to return a cached position so long as it has a previously acquired position” unless the site asks for a fresh one, so a map showing where you were ten minutes ago may be serving that cached fix.
What feeds the API differs by platform. Apple says an iPhone positions itself “from GPS networks, your Bluetooth connections, your local Wi-Fi networks, and your cellular network.” Android’s Location Accuracy service “uses information from wireless signals, such as Wi-Fi access points, cellular network towers, and GPS, along with device sensor data.” On a Mac, Apple’s guide says: “Your Mac determines its location using information from local Wi-Fi networks.” Windows, per Microsoft, uses “a combination of global positioning service (GPS), nearby wireless access points and routers, cell towers, IP address, or default location.” A device with no GPS and no visible Wi-Fi networks is left with the IP address, and that is where the wrong city comes from.
Why does Google think I am in a different city?
Google Search picks the best source it has and tells you which one it used. Its help page says your location “is estimated from several sources, depending on their availability”: your device’s precise location if you granted permission, your Home or Work address “when it’s likely that you’re at one of these places,” the general area from past activity, and finally your IP address. The bottom of any results page says “From your device,” “Based on your places (Home) or (Work),” “Based on your past activity” or “From your internet address.”
The last one is the usual cause of a wrong city. Google states that “IP addresses are roughly based on geography,” which gives it only “some information about your general area.” Google defines that general area as “larger than 3 sq km” with “at least 1000 users,” and notes it is “typically much larger than 3 sq km outside of cities.” Even when the IP estimate is right, it is deliberately not your neighborhood.
Two details on that page catch people out. Google keeps your last device location “in a cookie set to expire after 6 hours,” so after you travel, Search can keep using the old position for a while. And on a VPN, mobile data or an office network, “From your internet address” means Google places you wherever that network’s address block is registered; how blocks get their location is covered in why your IP location is wrong.
Why is my phone’s location wrong?
A phone has every sensor the API can use, so a wrong result almost always means one source is switched off or blocked. Google’s Maps help page gives the only vendor figures worth quoting. GPS can fix your position “up to around 20 meters,” but “when you’re inside buildings or underground, the GPS is sometimes inaccurate.” Nearby Wi-Fi networks help Maps “know where you are.” A cell connection “can be accurate up to a few thousand meters.” When Maps is unsure, “a light blue circle shows around the blue dot” and “you could be anywhere within the light blue circle.”
The typical phone failures, in order of how often they come up:
- Indoors or underground with no Wi-Fi fix, so the phone falls back to cell towers or IP.
- Android: Improve Location Accuracy or Wi-Fi scanning is off, so the phone cannot use Google’s access-point database and relies on raw GPS, which is slow and poor indoors.
- iPhone: Precise Location is off for that app, so it gets an approximate position by design.
- The app never got location permission and is using the IP address of your carrier’s gateway, which may sit in another city. Carriers put many subscribers behind shared address space (RFC 6598 reserves 100.64.0.0/10 for this) and one public exit, so the estimate reflects the gateway.
- Compass drift: if the blue dot’s beam “is wide or points in the wrong direction,” Google says to move the phone in a figure 8 to calibrate the compass. That fixes heading, not position.
Why is my location wrong on my computer?
Most laptops and desktops have no GPS receiver, so the operating system positions them from Wi-Fi networks it can see; a desktop on Ethernet with no Wi-Fi adapter cannot even do that. Apple’s macOS guide says a Mac uses “information from local Wi-Fi networks,” and that with Location Services off, “Apple may use the IP address of your internet connection to approximate your location by matching it to a geographic region.” It adds that “third-party applications and websites may still use other ways to determine your location,” which in practice means the IP estimate.
Windows lists the same chain, ending in “IP address, or default location.” The default location is a value you choose for the device, which Windows, apps and services “can use when a more exact location can’t be detected using GPS or other methods.” Microsoft calls it “highly recommended for devices that do not have Wi-Fi and for desktop computers.” If you set it once while traveling and forgot, every app that falls through to it will show that place.
The browser adds its own step. Chrome’s help page says that when you allow a site to use your location, “Chrome sends information to Google Location Services to get an estimate of where you are.” Firefox “uses information like your device’s IP address and nearby Wi-Fi networks to estimate your location.” On a wired desktop the list of nearby Wi-Fi networks is empty, so both browsers are effectively doing an IP lookup, and a desktop can land in a regional hub thirty kilometers away while the phone next to it is exact.
How VPNs, proxies, CGNAT and carrier gateways move the IP layer
Only the IP layer depends on how your traffic reaches the internet, but that is the layer used without permission, so it is the one most people see. A VPN or proxy replaces your public address with the server’s, so the IP estimate becomes the server’s city; the device position, if a site has permission, is unchanged. Carrier-grade NAT and corporate networks put many users behind one exit address, so the estimate is the exit’s location. For how geolocation databases place an address block, how accurate they are, and how to get a block corrected, see why your IP location is wrong and what CGNAT is.
How to check which layer is wrong
The fastest diagnosis is to look at both layers side by side.
- Open What is my location. The page shows the IP-based estimate immediately: country, region, best-guess city, how many geolocation sources agree, and the connection type. Nothing is requested from your device yet.
- Press Use precise location and allow the browser prompt. The page then shows your device position on the same map. The coordinates stay in your browser and are not sent to the server.
- Compare. If the device position is right and the IP estimate is off, the sites that are wrong are the ones without permission. If the device position is wrong or missing, the problem is in your device or browser settings, and the platform fixes below apply. A large distance between the two usually means a VPN, a mobile carrier gateway or an out-of-date database.
- Open IP location finder to see what each geolocation source says about your address individually and whether they agree. If they disagree by hundreds of kilometers, no website using IP alone can get your city right.
- Open IP lookup for the same address to see the ISP and ASN, the connection type and whether the address is on a VPN, proxy or relay list. A datacenter or VPN classification explains a far-away IP location by itself.
- If times are also off, What time zone am I in compares your device’s zone with the zone of your IP; a mismatch is another sign the IP layer points elsewhere.
Location sources compared
The figures are Google’s own; where a vendor gives no number, the table says so.
| Source | Needs your permission? | Typical result | Where it fails |
|---|---|---|---|
| GPS (phones, some tablets) | Yes | “Up to around 20 meters” (Google Maps help) | Indoors, underground; slow first fix |
| Wi-Fi access-point database | Yes | No vendor figure; Google says nearby networks help it “know where you are” | No Wi-Fi adapter, Wi-Fi scanning off, unknown or moved network |
| Cell towers | Yes | “Up to a few thousand meters” (Google Maps help) | Sparse coverage; needs a cellular modem |
| IP address | No | A “general area” (Google Search help); city at best | VPN, proxy, CGNAT, carrier gateways, stale databases |
| Default or saved location (Windows, Google Home/Work) | Set by you | Whatever you entered | Forgetting you set it |
How to fix a wrong location, platform by platform
Menu names follow each vendor’s current documentation.
Android (Google’s steps, some only on Android 12 and up)
- Open Settings, tap Location, and turn Use location on.
- Tap Location, then Location Services, then Location Accuracy, and turn Improve Location Accuracy on. On Android 11 and lower the path goes through Advanced before Location Accuracy.
- Tap Location, then Location Services, and turn Wi-Fi scanning on (and Bluetooth scanning if you want positioning from nearby devices). Google says this lets apps “get better location info.”
- If Maps shows a wide beam, move the phone in a figure 8 to calibrate the compass.
- In Chrome for Android, tap More, Settings, Site settings, Location, and check the site is under Allowed.
iPhone and iPad (iOS 27 user guide)
- Go to Settings > Privacy & Security > Location Services and turn Location Services on.
- Tap the app in the list, choose an access level, and leave Precise Location turned on. Apple says turning it off shares “only your approximate location.”
- With Location Services off, Apple says “apps can’t use your location from Location Services in the foreground or background,” which leaves them with the IP estimate.
Mac (macOS 27 user guide)
- Choose Apple menu > System Settings, click Privacy & Security in the sidebar, then click Location Services, and turn it on.
- Turn Location Services on for each app in the list that needs it.
- If the Mac is wired and Wi-Fi is off, turn Wi-Fi on even without joining a network; Apple says the Mac positions itself from local Wi-Fi networks, so with the radio off it has only the IP address.
Windows 11 and Windows 10 (Microsoft’s location service page)
- Go to Start > Settings > Privacy & security > Location and turn Location services on, then allow the apps you use.
- On the same page, under Default location, select Set default, pick the point on the map or type your address, and select Save. An old value here is a common cause of the wrong city on a desktop.
- Microsoft Edge asks for permission the first time a site requests your location; if you blocked it, change the permission in Edge’s site settings.
Chrome on a computer (Google’s steps)
- Open Chrome, select More, then Settings, then Privacy and security.
- Select Site settings, then under Permissions select Location, and choose whether sites can ask.
- For one site, use the icon at the left of the address bar to allow or block location for that site, then reload.
Firefox (Mozilla’s steps)
- Click the Permissions icon at the left of the address bar, find Location under Allowed Temporarily, and click the X to remove a wrong decision.
- For saved decisions, open Settings, and under Permissions click the Settings button next to Location to review allowed and blocked sites.
If the device position is now correct but one site still shows the wrong city, that site is not asking for permission; it uses the IP layer, and only the measures in the IP location guide change what it sees.
Sources
- W3C: Geolocation (Candidate Recommendation Snapshot, 26 March 2026)
- Google Search Help: Understand & manage your location when you search on Google
- Google Maps Help: Find & improve your location’s accuracy in Google Maps (Android)
- Android Help: Manage your Android device’s location settings
- Google Chrome Help: Manage your location settings in Chrome (Computer)
- Apple Support: About privacy and Location Services in iOS, iPadOS, and watchOS
- Apple iPhone User Guide (iOS 27): Control the location information you share on iPhone
- Apple macOS User Guide (macOS 27): Control access to the location of your Mac
- Microsoft Support: Windows location service and privacy (Windows 11, Windows 10)
- Mozilla Support: Does Firefox share my location with websites?
- RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space
Questions
Why is my Google location wrong?
Google estimates where you search from using your device location (if you allowed it), your saved Home or Work address, past activity, or your IP address. The note at the bottom of the results page says which one it used. “From your internet address” means Google only had your IP, which places you in a general area, not your street.
Why is my phone's location wrong?
The usual causes are GPS blocked indoors, Location Accuracy or Wi-Fi scanning turned off on Android, Precise Location turned off for the app on iPhone, or an app that only has your IP address. Google says GPS positions a phone to around 20 meters and mobile data to a few thousand meters.
Why is my location wrong on my computer?
Most computers have no GPS. A Mac positions itself from local Wi-Fi networks; Windows uses Wi-Fi access points, cell towers, your IP address or a default location you set. A desktop on Ethernet with no Wi-Fi adapter falls back to the IP estimate, which can be a different city.
Does a VPN change my location?
It changes the IP-based estimate to the VPN server’s area, which is what Google and websites use without permission. It does not change what GPS or Wi-Fi positioning reports when you grant a site location permission, so a browser can still place you in your real city while the IP says elsewhere.
How do I update my location on Google?
Google’s support page says to add the place to your search (for example “coffee shops in Chelsea”), check that your device is sending its location to Google, and set your Home and Work addresses in your Google Account. In Chrome, open site information for google.com, then Permissions, and turn Location on.
Back to your own address: my IP address

