Stay organized with collections Save and categorize content based on your preferences.
This FAQ covers questions specific to the Geocoding API. Refer to the Google Maps Platform FAQ for questions common to all Google Maps Platform. See also Best Practices When Geocoding Addresses.
TroubleshootingIn the geocoder, ambiguous, incomplete and badly formatted queries, such as misspelled or nonexistent addresses, are prone to produce ZERO_RESULTS. If the address cannot be found, ZERO_RESULTS is preferable to a partial result (for example returning only the suburb in lieu of an address).
If your application deals with user input of addresses, the Place Autocomplete feature in the Places API may produce better quality results. Place Autocomplete allows users to select from a set of results based on what they've typed, which allows users to choose between similarly named results, and to adjust their query if they misspell an address.
If you have an application dealing with ambiguous or incomplete queries or queries that may contain errors, we recommend you use the Place Autocomplete feature in the Places API rather than the forward geocoder available in the Geocoding API. For more details, see Best Practices When Geocoding Addresses and the Address Geocoding in the Google Maps APIs blog post.
We recommend that applications that respond to user input, and therefore are highly latency-sensitive, use the Place Autocomplete feature in the Places API (also available in JavaScript, Android, or iOS) rather than address geocoding. Place Autocomplete is optimized to be used interactively, and thus has very low latency.
Address geocoding in the Geocoding API is optimized for use with complete, unambiguous, well formatted addresses, such as delivery addresses entered into online forms, and thus has higher latency than Place Autocomplete. The forward geocoder has greater coverage and better result quality, but with somewhat higher latency.
Instead of addresses, use place IDs to specify waypoints, origin, and destination. Place IDs are best obtained from the Place Autocomplete feature in the Places API or the Places library in the Maps JavaScript API. See also the information on the placeIdOnly option, which can be used to reduce the cost of Place Autocomplete.
When the Directions API (Legacy) or Distance Matrix API (Legacy) is queried with an address string rather than a place ID or latlng, they use the same backend as the Geocoding API to convert that address into a place ID prior to calculating directions. Place Autocomplete is faster than address geocoding. For applications that use the Directions API (Legacy) or Distance Matrix API (Legacy) in highly latency-sensitive situations, such as responding to user input, we recommended you use Place Autocomplete to get the place IDs corresponding to those addresses, and pass the place IDs to the Directions API (Legacy) or Distance Matrix API (Legacy). This approach reduces latency significantly. See our documentation for an example of how to use Place Autocomplete with directions.
If you have any bug reports or feature requests for the forward geocoder service, let us know using our public issue tracker.
Let us know using our public issue tracker, sharing a few specific queries, so we can investigate to see if there are any bugs or systemic issues causing problems with result quality, or if there are any changes we can make to the best practices guide to help developers get better results.
In the geocoder, component filtering enforces only postal_code and country restrictions. The following examples illustrate how best to use component filtering, depending on the results you need. In the sample request URLs, be sure to replace `YOUR_API_KEY` with your actual API key.
components=country:CH|postal_code:8000 returns "8000 Zürich, Switzerland".
https://maps.googleapis.com/maps/api/geocode/json?components=country:CH%7Cpostal_code:8000&key=YOUR_API_KEY
Examples:
components=country:FRA|locality:gallus returns the sublocality of Gallus in Frankfurt am Main, Germany. This is because the 3-letter country code for France (FRA) isn't supported, thus results in any country are allowed and the result in Frankfurt is a better fit than anything in France.
https://maps.googleapis.com/maps/api/geocode/json?components=country:FRA%7Clocality:gallus&key=YOUR_API_KEY
Examples:
components=country:US|locality:madrid returns "Madrid, NM 87010, USA" but none of the other cities in the USA named "Madrid".
https://maps.googleapis.com/maps/api/geocode/json?components=country:US%7Clocality:madrid&key=YOUR_API_KEY
input=madrid&components=country:us&types=(regions), and also specifying a viewport using location and radius to bias the location results, generates a response with several cities in the USA named "Madrid".
https://maps.googleapis.com/maps/api/place/autocomplete/json?location=37.386052,-122.083851&radius=10000&input=madrid&components=country:us&types=(regions)&key=YOUR_API_KEY
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-09 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-09 UTC."],[[["This FAQ addresses questions about the Geocoding API; for general Google Maps Platform questions, refer to the Google Maps Platform FAQ."],["For applications with user input and latency sensitivity, Google recommends using Place Autocomplete instead of address geocoding for better results and speed."],["To improve latency with the Directions or Distance Matrix APIs, use place IDs obtained from Place Autocomplete instead of addresses."],["You can report bugs or request features for the Geocoding API through the public issue tracker."],["Component filtering in the Geocoding API is primarily used to restrict results by country and postal code."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4