Geocoding API adjustments for European Economic Area (EEA) customers

Effective 8 July 2025, new EEA-specific Google Maps Platform Terms of Service (EEA terms) will impact how you build applications and experiences for users if your project is linked to an EEA billing account.

We strongly recommend that you read and understand the announcement, as the details potentially impact your existing and new applications that integrate Google Maps Platform.

This document describes usage and Google Maps Platform functionality changes for the Geocoding API.

The information described in this document reflects the EEA terms governing your use of Google Maps Platform Services as of 8 July 2025, which may change over time. For the most recent and binding terms applicable to you, see your Google Maps Platform Agreement with Google.

Geocoding API adjustments for EEA customers

These adjustments apply to (a) projects created after 8 July 2025 that are linked to an account with an EEA billing address, and/or to (b) projects that are no longer in the Unmodified State after 8 July 2025.

The following table summarizes the adjustments, delineated in the EEA Service Specific Terms, for each Google Maps Platform service.

Geocoding API Functionality Adjustments Terms of Service Changes

None

No Use With any Map. Other than latitude, longitude, and place_id, Customer may not use Google Maps Content from the Geocoding API With any Map.

Examples of "With any Map" and "without a map"

The EEA terms changes affect how you use Google Maps Content from this service "With any Map." "With any Map" means to display Google Maps Content on, next to, or in a manner that is visually associated with any map, including a Google map, or to link Google Maps Content to any map or link any map to Google Maps Content (unless the specific map being linked to is the source of the applicable Google Maps Content).

For clarity, you may continue to link to the Google Maps Content source links provided by the Service (for example, googleMapsLinks in the Places API).

The following examples are illustrations of what "With any Map" and "without a map" can look like, to help you comply with the terms of your Agreement. The examples are not comprehensive. Ultimately, you are responsible for complying with the terms of your Agreement.

 

Blue dot that is used in subsequent examples The blue circles in the following examples represent Google Maps Content
from Google Maps Platform Services.

 

A map with a blue dot A map with blue dots next to it A map with a list blue dots separated by text, with a map with blue dots on the other side of the text.
On a map Next to a map Visually associated with a map

 

A map with a blue dot that links to a map in a new window. A list of blue dots with no map being displayed.  
Linked to a map Without a map  

Alternative integrations

If you use the Geocoding API to display Google Maps Content other than latitude, longitude, or place_id (such as addresses) on a map, you must change your integration. You may use Places UI Kit to support your application.

Places UI Kit

Google Maps Platform includes Places UI Kit, which lets you build integrations to help your users visualize Places content with any map, or without any map. The Places API Permitted Uses restrictions don't apply to the Places UI Kit.

For example, Places UI Kit lets you display Place Details on a map or render a List of Places from a search next to a map, as illustrated in the following image.

A list of places next to a map. One marker is selected, and its details are shown on the map.

Use the following resources to help you build with Places UI Kit:

Integration guides

Places UI Kit product documentation

Road safety

EEA customers may now use Google Maps Platform Services, where suitable, in embedded vehicle systems. They may also use Google Maps Platform Services, where suitable, for real-time navigation with a third-party map, as long as that real-time navigation usage complies with Google's safety requirements.

Due to road safety risks that can arise under these new terms, Google now requires that developers adhere to safety requirements in order to, for example, limit the risks of mismatched roads.

What if I have additional questions not covered in this document?

If you have any technical questions not addressed in this document or the General FAQ, you can contact Google Maps Platform Support.

If you have a negotiated agreement with Google and have questions about your contract, you can contact your Google Maps Platform representative. If you are unsure who your account representative is, reach out using our Contact Sales form.