Websites request your location for reasons ranging from genuinely useful (showing nearby restaurants on a maps service) to questionable (collecting location data to build advertising profiles). Chrome handles location requests through a layered permission system that you can configure precisely — blocking all sites by default, allowing only specific trusted ones, or revoking access you’ve already given. For a broader walkthrough, our Chrome How-To Guides is a good next read.
The most important thing to check first: which sites currently have location access. Navigate to chrome://settings/content/location → look at the “Allowed to see your location” list. If you see sites there that have no legitimate reason for your location — news sites, shopping platforms, entertainment — revoke them immediately by clicking the X next to each entry.
How Chrome determines your location
Chrome doesn’t just use GPS. It uses a combination of signals to estimate location:
- GPS (on mobile devices): most accurate, within metres
- Wi-Fi positioning: Chrome can estimate location from nearby Wi-Fi networks and their known positions — accurate to 20-50 metres in urban areas
- IP address geolocation: your internet provider’s IP address maps to a general area — typically accurate to city level, sometimes suburb level
- Bluetooth beacons (on mobile): less common, used in some indoor positioning systems
Sites that request location through Chrome’s permission system get the GPS/Wi-Fi/Bluetooth accuracy. Sites that don’t request a permission but still try to guess your location use IP geolocation only — less accurate but no permission required. Blocking Chrome’s location permission doesn’t prevent IP-based geolocation; that’s handled at the network level.
Changing the global location default
chrome://settings/content/location → the top section shows “Default behaviour.” Three options:
- Sites can ask for your location (default): Chrome prompts you when a site wants access. You approve or deny each time for each new site.
- Don’t allow sites to see your location: no site can request location. The browser returns a “permission denied” error to any site that asks. Prompts never appear.
- Ask before accessing (recommended if you want to keep some sites): same as the first option — still gives you control per-site.
For most users: the default “sites can ask” is appropriate if you’re careful about approvals. If you want to eliminate location access entirely: “Don’t allow” is the setting. You can still add specific exceptions back afterward for sites you trust.
Revoking location access for a specific site right now
While visiting a site you want to revoke location from: click the lock icon in the address bar → Location → change from “Allow” to “Block.” The change takes effect immediately. No refresh needed, though some sites may behave differently until you navigate away.
The same path works in reverse: if you previously blocked a site and now want to allow it, change “Block” to “Allow.” Note that the site won’t re-prompt you automatically after you unblock — you’ll need to trigger the location request again by using the site feature that requires it.
Windows 11 location settings and Chrome
Chrome’s browser-level permission is only one layer. Windows 11 has a system-level location control that sits above it. If Windows location is off: Chrome cannot access location regardless of what you’ve allowed in browser settings.
Settings → Privacy & security → Location → “Location services” must be On for any location sharing to work. Below that: “Let desktop apps access your location” must be enabled for Chrome (a desktop app) to use location. And further down: “Google Chrome” should appear in the list of apps with location access.
This hierarchy means you can disable location entirely at the Windows level and nothing in Chrome settings can override it. Useful if you want to be certain nothing in the browser can share location, without configuring each browser individually.
Location and the Google account — a separate concern
Chrome browser location permissions control what websites can access through the browser. But if you’re signed into Chrome with a Google account: Google may also be collecting location data through Location History (recorded from your devices over time) and Location Sharing (real-time location with specific contacts).
These are separate from browser permissions. Visiting myaccount.google.com → Data & Privacy → Location History → turn off “Location History” stops Google from recording your location timeline. This is different from — and more comprehensive than — just revoking website location access in Chrome.
Our guide on Chrome privacy settings covers the full picture of what Google collects and how to limit it, and our article on Chrome site permissions covers all permission types together. For location-specific privacy, Google’s account privacy dashboard shows what location data has been collected and provides tools to delete it.
Incognito mode and location
Incognito mode doesn’t block location access. Sites can still request your location in incognito windows, and Chrome prompts you just as in normal mode. Location permissions granted in incognito are session-specific — they’re forgotten when you close the incognito window — but the access itself works identically.
If you want to prevent location access specifically in incognito sessions: the same chrome://settings/content/location setting applies globally including incognito. Set the default to “Don’t allow” to block location in both modes.
Which sites legitimately need location
| Site type | Location need? | Recommendation |
| Maps (Google Maps, Apple Maps web) | Yes — core function | Allow |
| Weather services | Yes — local forecasts | Allow or enter location manually |
| Local business search | Yes — “near me” results | Allow only while using |
| News sites | Rarely legitimate | Block |
| E-commerce/shopping | Sometimes (shipping estimation) | Block — enter postcode manually instead |
| Social media | Optional — adds geotag to posts | Block unless you intentionally want geotagging |
| Unknown/unfamiliar sites | No | Always block |
The pattern that emerges: maps and weather have genuine location needs. Most other sites request location for advertising targeting or data collection purposes rather than to deliver a materially better experience. When in doubt, deny — and if the site’s core feature stops working as a result, you can reconsider.
VPNs and location — what they actually change
A common misconception: using a VPN prevents location tracking. VPNs change your IP address, which prevents IP-based geolocation from accurately identifying your location. But if you’ve granted a site permission to use Chrome’s location API: that site still gets GPS/Wi-Fi accuracy regardless of the VPN. The VPN and the browser permission are different systems.
To prevent accurate location sharing: revoke browser permissions as described above. A VPN adds obfuscation for IP-based location (which doesn’t require your permission) but doesn’t help with permission-based location access. If you’ve allowed a site location permission and are using a VPN: the site sees your actual GPS/Wi-Fi location, not the VPN server’s location.
For comprehensive location privacy: revoke Chrome location permissions for sites that don’t need them, turn off Google Location History in your account settings, and optionally use a VPN for IP-level obfuscation. Each of these addresses a different method sites use to determine your location. All three together give you the most complete location privacy available through software controls.
On mobile: Chrome location on Android and iOS
Chrome for Android uses the same permission prompt system, but location accuracy is higher because Android devices often have GPS hardware. Android additionally lets you set location precision independently: when Chrome requests location, you can approve “Precise” (GPS) or “Approximate” (Wi-Fi/cell tower, less accurate). Choosing Approximate gives the site enough accuracy for most legitimate uses (nearest weather station, rough area) while limiting the precision available for tracking.
Android: Settings → Apps → Chrome → Permissions → Location → choose “Allow only while using the app,” “Ask every time,” or “Don’t allow.” The “Ask every time” option is particularly good on mobile — you get prompted each time Chrome needs location, keeping you aware of which specific app features are using it.
iOS (Chrome on iPhone/iPad): Settings → Chrome → Location → choose “Never,” “Ask Next Time Or When I Share,” or “While Using the App.” iOS doesn’t have the Precise/Approximate toggle in all versions; some newer iOS versions do. “While Using the App” is more restrictive than “Always” and prevents Chrome from accessing location when running in the background.
Location and business-critical websites
If you’re on a corporate device and work with tools that use location (field service apps, logistics tools, customer mapping software): your IT department may have configured Chrome’s location settings via policy, with specific sites pre-approved. You may not be able to modify these settings if Chrome shows “Managed by your organisation” in the location settings area.
If location permissions are policy-controlled: check with IT before trying to change them. Pre-approved location access for specific business tools is usually there for operational reasons, and disabling it may break workflows. For personal browsing on the same device: ask IT whether a separate browser profile with different permissions is available for non-work use.
Testing what sites can actually see
If you want to check what information Chrome is sharing when you allow location: visit a site like iplocation.net or browserleaks.com/geo while location is allowed — it shows the exact coordinates Chrome provided, the accuracy in metres, and whether the data came from GPS or from Wi-Fi/IP. Seeing the actual data your browser provides makes the trade-off concrete: it’s often more precise than people expect.
Running the same test after blocking location shows what sites see instead — either an error message, or a fallback to IP-based geolocation (much less precise). This comparison makes the value of the permission revocation tangible rather than abstract.
Location privacy in Chrome boils down to a few simple decisions: know which sites have permission, revoke the ones that don’t need it, and set the global default to “ask” so new sites can’t quietly accumulate access. That’s the entire practical configuration. The deeper Google account settings (Location History, device history) are worth addressing separately, but for browser-level location control, those three steps cover everything that matters.
Location permission vs location data already stored
Revoking a site’s location permission stops future location sharing — it doesn’t delete location data that site has already stored from previous accesses. If a site collected location data during previous sessions when you had permission enabled: that data remains with the site. To address historical data: you’d need to contact the site’s privacy team, submit a data deletion request under applicable privacy law (GDPR for EU residents, CCPA for California residents), or accept that the historical data exists and focus on preventing future collection.
For Google specifically: myaccount.google.com → Data & Privacy → My Activity → filter by “Location” → delete individual entries or all location history. This deletes the stored timeline, though some data may persist temporarily in backup systems. The deletion is effective for most purposes and covers the location history Google has built from your devices over time.
Location accuracy settings
Chrome itself doesn’t let you reduce location accuracy directly — it’s either permitted (at full accuracy from available signals) or blocked. The accuracy reduction happens at a different level:
- Windows: Settings → Privacy & security → Location → location accuracy → turning this off reduces precision by not using Wi-Fi and Bluetooth for positioning (GPS and IP only)
- Android: Settings → Location → Location services → Google Location Accuracy → off (uses GPS only, no Wi-Fi/Bluetooth scanning)
- iOS: individual app precision control or the system location services toggle
Reducing OS-level accuracy affects all applications that use location, not just Chrome. If you rely on precise location for navigation or other apps: this trade-off may not be worth it. For browser-only location privacy: revoking Chrome permissions site-by-site is more targeted than reducing system accuracy.
The notification when location is being accessed
Chrome shows a location pin icon in the address bar when a site has location access enabled. This indicator appears whenever the current page has been granted location permission, not only when it’s actively requesting your location at that moment. It’s a persistent reminder of which sites have access, visible without going into settings. Related: Disable Chrome Automatic Downloads.
If you see the location pin on a site that surprises you: click it → Permissions → you’ll see Location listed with an “Allow” status → change it to “Block” or “Ask” immediately. This address bar shortcut is faster than navigating to the settings page and is the quickest way to revoke access during an active browsing session. If this sounds familiar, Disable Chrome Password Manager is worth a look.
One final practical note for travellers: when visiting a new country, Chrome’s location accuracy may be lower if you’re on an unfamiliar mobile network or in an area with fewer Wi-Fi positioning data points. This is normal — the accuracy of Wi-Fi-based positioning depends on how well-mapped that area’s Wi-Fi networks are. In dense urban areas globally, Chrome’s location estimate is typically within 50 metres even without GPS. In rural or less-mapped areas, it may be accurate only to the city or district level. Our guide on Disable Chrome Auto Sign covers an adjacent issue.
