What Chrome location permissions are (and what sites actually get) .
This guide reflects current Chrome behavior and permission design (desktop + mobile), not legacy menus.
Chrome location permissions control whether a website (or web app) can request your device’s location using your browser. When a site asks for location, Chrome acts like a gatekeeper: it can ask every time, allow, or block. This setting matters for obvious cases like maps and ride-hailing, but it also affects: local search (“near me”), delivery time estimates, fraud checks on banking sites, and even corporate web apps that use location for on-site access rules.
The key idea: a website usually doesn’t “magically know” where you are. It learns location in two main ways: (1) a precise device location (GPS / Wi-Fi / Bluetooth signals) when you grant permission, or (2) an approximate location inferred from your IP address, network, or regional settings. Blocking the permission request prevents a site from using the browser’s location APIs, but it does not prevent basic IP-based approximation. If your goal is maximum privacy, you’ll combine permission control with broader privacy settings (and sometimes network tools).
Chrome also separates “default rules” from “per-site rules.” This is important because users often change the default to “Ask,” but one site still doesn’t work—because that site is saved under “Blocked” or “Allowed” and overrides the default. Think of your default as your policy, and per-site entries as exceptions.
Related: Location is one of many site permissions. If you want the full control panel, start here: Chrome Site Permissions Settings.
Key terms (quick definitions) .
- Geolocation API: The browser feature websites use to request your device’s location (only after permission).
- Default permission: Your global setting for Location (Ask/Allow/Block).
- Per-site permission: An exception stored for one website that overrides the default.
- Precise vs approximate: “Precise” uses device signals (GPS/Wi-Fi/Bluetooth); “approximate” can be inferred by IP/network.
- Profile: A separate Chrome user space (work vs personal). Permissions can differ per profile.
What a site can learn when you click “Allow” .
When you allow location, Chrome may provide coordinates (latitude/longitude) and accuracy data to the site—how close the estimate is. On phones, this can be very accurate. On desktops, accuracy varies: it can be excellent on Wi-Fi networks in cities, and less precise on wired networks. Most modern sites only request location when it’s needed, but some ask early because it increases conversions (local pricing, “nearest store,” etc.). That’s why a strong default (“Ask”) is usually the best balance for most people.
Location + tracking: Location data becomes much more identifying when combined with other signals (cookies, device fingerprinting, login identity). If you’re tightening privacy overall, see Chrome Privacy Settings and Chrome Fingerprint Protection.
Before you start (fast checks that prevent wasted time) .
Most “Chrome location not working” issues come from one of three places: your browser setting, your operating system permission, or a stored per-site rule that overrides the default. Do these fast checks first so you don’t chase the wrong problem.
- Fast check #1 (per-site override): Open the site → click the padlock icon (left of the URL) → Site settings → check Location.
- Fast check #2 (OS permission): If you’re on macOS/Windows/Android/iPhone, verify the OS allows location for Chrome (details below).
- Fast check #3 (private window / extensions): Try Incognito. If it works there, an extension or cached site data may be interfering.
- Fast check #4 (VPN / proxy / DNS): If sites show the wrong city/country, you may be seeing an IP-based location. That’s not a “permission” problem.
- Fast check #5 (managed browser): If you’re on a work device, Chrome may be controlled by policy. You’ll see “Managed by your organization.”
Related: If you’re reviewing permissions across the board, use the full checklist: Chrome Privacy Settings Checklist.
Where location can be blocked (so you know where to look) .
- Chrome default setting: the global rule for all sites.
- Chrome per-site rule: an exception you saved earlier (common).
- OS permission: your computer/phone blocks Chrome from using location services.
- Device-level location toggle: location services are off entirely (especially on laptops and phones).
- Enterprise policy: an admin locks geolocation on/off or allows it only for specific URLs.
- Extensions: privacy blockers can suppress prompts or break scripts on the page.
Step-by-step: allow, block, or reset location permissions .
Use the steps that match your goal. If you’re not sure, choose the recommended baseline: Default = Ask, then allow only trusted sites (maps, delivery, work tools) when you actually need them.
A. Change your default Location permission (Desktop) .
- 1 Open Chrome → click ⋮ (top-right) → Settings.
- 2 Go to Privacy and security → Site settings.
- 3 Under “Permissions,” choose Location.
- 4 Pick your default:
- Sites can ask (recommended): prompts appear when needed.
- Don’t allow: blocks the prompt and denies location access via browser APIs.
What “success” looks like: When you visit a site that uses location, Chrome shows a location prompt (Ask mode), or it quietly denies access (Block mode) and the site may show a “turn on location” message.
B. Allow or block Location for one specific site (fastest fix) .
- 1 Open the website in Chrome.
- 2 Click the padlock (or site controls icon) to the left of the address bar.
- 3 Click Site settings.
- 4 Find Location and set it to:
- Allow (only if you trust the site and it truly needs location).
- Block (if it’s asking unnecessarily).
- Ask (default) to restore prompting behavior.
- 5 Refresh the page (or close/reopen the tab) and test again.
C. Reset ALL saved Location decisions (Allowed/Blocked lists) .
If you’ve been clicking “Block” for years, you may have a long Blocked list. That list overrides your default setting. Resetting it is often the single best fix for missing prompts.
- 1 Chrome → Settings → Privacy and security → Site settings → Location.
- 2 Review Not allowed (blocked sites) and Allowed (exceptions).
- 3 Remove the site entry you want to reset (trash/remove icon).
- 4 Set default to Sites can ask, then revisit the site and choose again.
Related: Doing a broader permissions cleanup? Pair this with Chrome Clear Browsing Data (and use site-by-site clearing when possible).
D. Android: allow/block location in Chrome (and the device) .
On Android there are two layers: (1) Android’s permission for the Chrome app, and (2) Chrome’s own per-site rules. If either layer blocks, location won’t work.
- 1 In Chrome (Android): ⋮ → Settings → Site settings → Location.
- 2 Toggle Location on/off (or set per-site exceptions).
- 3 On Android device: Settings → Location (ensure it’s ON).
- 4 Android app permission: Settings → Apps → Chrome → Permissions → Location → allow while in use (recommended).
E. iPhone/iPad: Chrome location permissions work differently .
On iOS/iPadOS, Chrome is more tightly integrated with system controls. If location doesn’t work on iPhone/iPad, the first place to check is the iOS Settings app: Settings → Privacy & Security → Location Services → Chrome. If iOS blocks Chrome, the browser cannot provide location to websites even if the site itself “should” be allowed.
Common variations .
- Windows / ChromeOS: OS location services can be disabled globally; enable Location in system settings if prompts appear but location stays blank.
- macOS: macOS can block location for Chrome under system privacy controls; allow Chrome and try again.
- Android / iPhone: App-level permission must be allowed, and device location services must be on.
Advanced: precision, profiles, enterprise policies, and safer baselines .
If you’re here, you probably want more than “click allow/block.” The real control comes from understanding precision, profiles, and the difference between a “works everywhere” setup vs a “privacy-first” setup. This section also covers enterprise scenarios where location permissions are set by policy.
Related: If you’re building a hardened browser configuration, see Chrome Hardening Guide and Chrome Privacy Best Practices.
1) Precise vs approximate location: what you’re really allowing .
Location on the web isn’t a single “on/off.” Sites might request location for different reasons, and your device might provide different quality depending on signals. On phones, precise location can be accurate enough for neighborhood-level results. On desktops, accuracy depends heavily on Wi-Fi and network mapping. If you’re privacy-sensitive, the best practice is: default Ask + allow only when the site clearly needs it (maps, delivery, local emergency services portals, certain work apps).
2) Profiles: why work vs personal permissions can “disagree” .
Chrome profiles maintain separate storage for many settings, including some permissions and site data. That’s why location can work in your personal profile but fail in your work profile. If you suspect this: switch profiles and test the same site. If only the work profile fails, you may be dealing with policy restrictions, blocked site rules saved long ago, or an extension installed only in that profile.
Related: If you’re also using Chrome Sync, remember that some settings and site data can sync across devices. See Chrome Account & Sync Settings or How to Disable Chrome Sync.
3) Enterprise & managed Chrome: policy-controlled geolocation .
In organizations, IT admins can lock down location permissions to meet privacy, security, or compliance requirements. If you see “Managed by your organization,” your choices may be limited. Common policy patterns include: blocking location globally, allowing location only for trusted internal URLs, or allowing “precise” location only for specific sites.
Here are the enterprise policy names you’ll commonly encounter (useful for IT teams and audits):
- DefaultGeolocationSetting: sets the default behavior for location (allow/block/ask) across the browser.
- GeolocationAllowedForUrls: allowlist of sites that can use location.
- GeolocationBlockedForUrls: blocklist of sites that cannot use location.
- PreciseGeolocationAllowedForUrls: allow precise geolocation only for specific sites (when supported).
Related: If you’re in a managed environment, the larger privacy framework matters: Enterprise Chrome Privacy Settings and Chrome Enterprise Privacy Controls.
4) Recommended baselines (choose one) .
Your best setting depends on what you’re optimizing for: convenience, privacy, or strict compliance. These baselines are practical and easy to maintain over time.
- Baseline A (balanced, recommended): Default = Sites can ask. Allow per-site only when needed. Review the “Blocked” list monthly.
- Baseline B (privacy-first): Default = Blocked. Manually allow only a short allowlist (maps/delivery/work). Pair with tracking controls.
- Baseline C (compatibility): Default = Ask, but do not block system-wide location services. Focus on per-site rules to avoid breaking banking/workflows.
Common alternatives users compare .
- Chrome built-in permission controls vs privacy extensions (which can break prompts)
- Blocking location vs relying on “approximate by IP”
- Browser permissions vs OS-level location controls
- Manual configuration vs enterprise policy management
Privacy & security notes .
Location is a high-signal identifier. A single precise coordinate is often more revealing than most people expect, especially when combined with: login identity (Google account), browser fingerprinting, and a long-lived set of cookies. The goal isn’t to “never use location”—it’s to make sure you only share it with sites you trust, at the moment you need it.
Impact: Affects geolocation API access, app workflows (maps/delivery), and can influence personalization and fraud checks.
Undo: Reset the site’s Location setting to Ask or remove the site from Allowed/Blocked lists.
Related: If you’re auditing broader tracking controls, see How to Stop Chrome Tracking, Chrome Ad Privacy Settings, and Chrome Privacy Sandbox Explained.
Recommended baseline settings .
- Option A (balanced): Default = Sites can ask. Allow per-site only when needed. Keep the Allowed list short.
- Option B (maximum privacy): Default = Don’t allow. Allow only essential sites, and consider stronger tracking protections.
- Option C (compatibility): Default = Sites can ask and OS location services ON, then tune per-site rules instead of global blocking.
Recommended settings by goal .
| Goal | Recommended setting | Tradeoff | Best for |
|---|---|---|---|
| Balanced | Default: Sites can ask + per-site allow when needed | Occasional prompts | Most users |
| Maximum privacy | Default: Don’t allow + very short allowlist | Some sites lose features (maps/delivery) | Privacy-sensitive users |
| Compatibility | Default: Ask + OS location ON + exceptions tuned | Requires occasional reviews | Banking / enterprise / older web apps |
Troubleshooting: location not working, prompts missing, or wrong location .
Related: If you’re debugging other permissions too, use Chrome Site Permissions Settings as your “master map.”
If the site never shows a location prompt .
This usually means Chrome already has a saved rule for that site (often “Blocked”). Fix it by opening the site → padlock icon → Site settings → set Location to Ask or Allow. Then refresh. If you don’t see the padlock options, go directly to: Settings → Privacy and security → Site settings → Location and remove the site from “Not allowed.”
If Chrome says location is blocked, but you think you allowed it .
Check for an OS-level block. On laptops and phones, the operating system can deny Chrome access to location services. If the OS denies Chrome, the browser may still show “Allow” in-site settings but return no location data to the website. Turn on device location services and allow Chrome at the OS permission layer, then test again.
If a site gets the wrong city or country .
That’s often IP-based geolocation, not a Chrome permission issue. Common causes: VPN/proxy use, corporate networks routing traffic through another region, mobile carrier gateways, or an ISP whose IP blocks are registered in a different city. If the site is using precise device location, granting permission usually fixes accuracy. If the site ignores device location and uses IP, you’ll need to adjust your network path.
Network angle: If you’re changing network privacy settings, do it intentionally. Start with Secure DNS Setup and DNS over HTTPS Settings.
If it works in Incognito but not in normal mode .
That’s a strong signal that an extension or cached site data is interfering. Try: (1) disable privacy/ad-block extensions temporarily for that site, (2) clear only that site’s data, and (3) retest. If a single extension breaks permission prompts, it may be injecting scripts or blocking APIs.
Related: Extension issues are common in permission bugs. See Chrome Extension Security Check and Chrome Extension Permissions Guide.
If you’re on a work device and can’t change the setting .
Your browser may be controlled by enterprise policy. You’ll often see “Managed by your organization” in Chrome settings. In that case, the effective setting can be locked, or allowlisted/blocked for specific sites. If you’re the admin, review geolocation policies (DefaultGeolocationSetting, GeolocationAllowedForUrls, GeolocationBlockedForUrls). If you’re a user, your best option is to request an exception for the specific site that requires location.
If you need to reset safely (without deleting everything) .
Avoid the “nuke it from orbit” approach unless you have to. Start small: reset Location for the problem site, then clear only that site’s data. If the issue persists, check OS permissions and extensions. Only then consider broader steps like a profile reset.
Related: If permissions and behavior feel “corrupted,” you may be dealing with a profile issue. See Chrome Profile Reset Guide.
FAQ .
-
helpShould I set Chrome location to Allow, Ask, or Block?For most people, Ask is the best default because it prevents silent location sharing and still allows maps/delivery sites to work when needed. Use Allow only for sites you trust and use frequently (for example, your primary maps or ride-hailing service). Use Block if you want maximum privacy, but expect some sites to lose features.
-
helpWhy does Chrome location not work even after I click “Allow”?The most common cause is an OS-level block (your computer/phone denies Chrome access to location services). Another common cause is a saved per-site rule overriding your default setting. Verify OS permissions for Chrome, then check the site’s Location setting via the padlock icon → Site settings.
-
helpCan websites still know my location if I block location permission?Yes—many sites can still estimate your region using your IP address and network information. Blocking Chrome location permissions stops the site from using the browser’s device location APIs, but it doesn’t prevent IP-based approximation. To reduce IP-based location accuracy, you need network-level changes (VPN/proxy/private DNS), not just permissions.
-
helpHow do I remove a site from the “Blocked” list so it can ask again?Go to Settings → Privacy and security → Site settings → Location. Under “Not allowed” (blocked sites), remove the site entry. Then revisit the site: Chrome will prompt again (if your default is “Sites can ask”).
Sources & further reading .
- Google Chrome Help: Manage your location settings (Desktop)
- Google Chrome Help: Manage your location settings (Android)
- Google Chrome Help: Change site settings permissions
- Chrome Enterprise: Policy list
- Chrome Enterprise: Atomic policy groups (includes geolocation policies)
- Chrome Releases: Stable Channel Update (version reference)
Disclosure: Some pages may mention tools or services. Recommendations are editorial and based on testing.