Guides
Google Play Location Button Policy for Website Apps: What Changes on Jan 27, 2027
Apps targeting Android 17 that ask for precise location for one-time actions must use Android's location button from January 27, 2027. Here is what that means for an app built from a website.
Google Play's location button policy applies to apps that target Android 17 (API level 37) and use precise location only for one-time, user-initiated actions. From January 27, 2027, those apps must use Android's location button and declare ACCESS_FINE_LOCATION with the onlyForLocationButton flag. A website app is only affected if its manifest requests precise location, so the first job is finding out whether yours does.
Who does the Google Play location button policy cover?
Google's rule has two layers. The location button itself is mandatory only for apps that target Android 17 or higher, and Google's help article says it covers new and existing apps alike (source: Play Console Help). The second layer is wider: the same article says all apps requesting precise location (ACCESS_FINE_LOCATION) must complete a declaration in Play Console explaining why coarse location or the button is not enough. It does not tie that declaration to a target level.
If your app targets Android 16 (API 36) or lower, the button is not required yet. Google moves its minimum target level up every year, so expect that to change; our target API level guide has the current dates.
Policy announced
Apr 15, 2026
New minimum scope rules for location
Declaration opens
Nov 2026
For apps using precise location
Compliance mandatory
Jan 27, 2027
Apps in scope face enforcement after this
Self-extension
30 days
Available in Play Console
Which situation is your website app in?
Google's policy is written around an app's manifest and features, not around how the app was built. Reading it that way, a website app lands in one of five places.
| Your app's manifest | What Google's policy asks | What to do |
|---|---|---|
| No location permission | No location rule applies | Nothing to change for this policy. Check that your site does not depend on location. |
| ACCESS_COARSE_LOCATION only | Coarse is the minimum scope when precise is not needed | Confirm your site only needs city-level or nearest-branch results. |
| ACCESS_FINE_LOCATION, targets below API 37 | The button is not required yet, but Google says all apps requesting precise location complete the Play Console declaration | Decide whether coarse location is enough. If so, drop the precise permission. |
| ACCESS_FINE_LOCATION, targets API 37+, one-time lookups | Use the location button and add the onlyForLocationButton flag | This is a change to the app itself. Ask your app builder how it will be done. |
| ACCESS_FINE_LOCATION, continuous tracking or navigation | Keep precise location, with a declaration explaining why the button and coarse are not enough | Prepare a clear description of the persistent feature. |
Does coarse location cover a store locator or a near-me feature?
Often, yes. Google's help article lists store locators as a coarse-location case: a coarse fix is enough to show the three nearest branches within 10 miles, even though precise location helps with walking directions. Local news, regional events, weather and marketplace listings within a few miles are on the same list.
The button side of the line is one-time precise lookups: nearby search, sharing your current location once, tagging a post, and filling in a delivery address. Reading Google's examples, a site that autofills an address at checkout falls on the button side, while a site that shows your closest branch falls on the coarse side. That mapping is our reading, not a Google ruling.
What does Google say about website apps and WebView?
Nothing directly. In the policy article and help pages we reviewed in November 2026, website-in-an-app and WebView apps are not mentioned. The closest entry is "Browser Location Access" in the declaration's use-case list, which describes passing precise location to websites at the user's request, such as a browser handing a retailer a position to fill in shipping details. A website wrapped in an app is not a browser, and Google does not say whether reviewers will treat it as one.
What Android's own documentation does settle is who answers the page's request. The app's WebChromeClient receives the geolocation prompt and must set the permission for that origin, and for apps targeting Android 7 and later the prompt only fires for secure origins such as https; plain-http pages are denied automatically (source: WebChromeClient reference). So location in a website app is governed by the app's manifest and code, not by your site. Our guide to WebView uploads, camera and location covers the functional side.
The unanswered question is how a native button fits with a web page's own geolocation prompt. Google's location button guide describes a system UI element that grants precise location for a single session, and it says nothing about web content. The Jetpack library behind it is labeled experimental, and on Android 16 and lower it falls back to the standard permission prompt. Ask your app builder how it plans to handle this before you rely on it.
Why does the January date differ from older articles?
Earlier Google material, including the April 2026 announcement, pointed to late October 2026, with pre-review checks starting October 27. Google's current policy timeline lists January 27, 2027 for both the Location Permissions and Contacts Permission changes. If an article gives October dates, treat it as out of date. Google's help article also says it expects enforcement for Android 17 apps in late January 2027 and that the timeline may still change, so check Play Console's policy status before planning around the date.
What about the Contacts permission change?
It is a separate rule with the same date. For apps targeting Android 17 or higher, READ_CONTACTS is allowed only when the Android Contact Picker cannot provide the app's core functionality, and apps that keep it must submit a declaration. If your app's manifest does not request READ_CONTACTS, there is nothing to change.
Device location is also personal and sensitive user data under Google's User Data policy, so whatever your app collects has to match your Data safety answers. See our guide to the Data safety form for a WebView app.
How do I check my website app before January 27, 2027?
- 1
Find the target API level
Play Console's App bundle explorer shows the target SDK of each version, as our target API level guide explains.
- 2
List the location permissions
Ask your app builder which of ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION the app declares.
- 3
Map each location feature on your site
Mark every feature as one-time (nearest branch, address autofill) or continuous (live tracking, navigation).
- 4
Pick the lowest scope that works
Coarse if city-level is enough, the location button for one-time precise lookups on API 37+, and a declaration only for persistent precise features.
- 5
Complete the declaration when it opens
Google said it opens in November 2026, and 30-day self-extensions are available in Play Console.
- 6
Re-test on a real phone
Run your location features again after every rebuild, using the test plan in our WebView permissions guide.
Frequently asked questions
- When does Google Play's location button policy take effect?
- Google's help article says compliance is mandatory from January 27, 2027, with 30-day self-extensions in Play Console. It also says it expects enforcement for apps targeting Android 17 in late January 2027, and that the timeline may still change.
- Does my website app have to use the Android location button?
- Only if it targets Android 17 (API 37) or higher and uses precise location for one-time, user-initiated actions. Apps targeting lower levels are not required to use the button yet, but Google says all apps requesting precise location complete a Play Console declaration.
- Can I use coarse location instead of precise location?
- Yes, if your feature does not need precise location. Google's policy says to request the minimum scope, and its examples treat store locators, local news and regional weather as coarse-location cases.
- Does the Contact Picker rule affect a website app?
- Only if the app's manifest requests READ_CONTACTS. For apps targeting Android 17 or higher, Google allows that permission only when the Contact Picker is not enough, and requires a declaration. If the manifest does not request it, there is nothing to change.
- Does Google explain how the location button works with a web page's geolocation prompt?
- Not in the policy and help pages we reviewed in November 2026. Android's reference says the app must answer the page's geolocation prompt, and only for https origins on apps targeting Android 7 and later. How the native button fits with that prompt is a question for your app builder.
- What happens if I miss the January 27, 2027 date?
- Google says apps in scope are subject to enforcement after that date if they are not compliant. It also offers 30-day self-extensions in Play Console, so check what your account allows rather than assuming.