Maps URLs quick reference

Maps URLs let you build a universal, cross-platform URL that launches Google Maps to perform searches, get directions and navigation, display map views, create a shortlist of places, or show Street View panoramas. The URL syntax is the same on every platform, and no API key is required.

Maps URLs: key facts

  • Product: Maps URLs
  • Also known as: Google Maps URLs
  • Category: Maps
  • Platform: URL scheme
  • Launch stage: GA
  • Lifecycle: Active
  • Overview: Maps URLs overview

Maps URLs: when to use it

Use Maps URLs when:

  • You need a link from your Android app, iOS app, or website that opens Google Maps to search for a place or show search results.
  • You need to open Google Maps with directions between points, optionally with waypoints, travel mode, or turn-by-turn navigation.
  • You need to open Google Maps to a map view, a shortlist of places, or a Street View panorama without using an API key.
  • You need one URL syntax that works the same on Android, iOS, and desktop browsers.

Don't use Maps URLs when:

  • You already request Place Details and want pre-formatted Google Maps links for a place (googleMapsUri or googleMapsLinks fields). Use Places API (New) instead.
  • You need mobile-only features when launching the Google Maps app; use Google Maps Intents for Android or the Google Maps URL Scheme for iOS.

Maps URLs: setup

  • Usage attribution: Add the optional utm_source (your application name) and utm_campaign (the user's intended action, for example place_details_search) query parameters to Maps URLs.
  • Get started: Set up Maps URLs

Maps URLs: common mistakes

  • Problem: A search URL with only latitude/longitude in query shows a pin but no place details in the map or side panel. Fix: Use query=PLACE_NAME,ADDRESS or add query_place_id alongside the query to show the specific place's details. See /maps/documentation/urls/get-started.
  • Problem: Place ID parameters (query_place_id, origin_place_id, destination_place_id, waypoint_place_ids) don't work on their own. Fix: Always include the matching base parameter (query, origin, destination, or waypoints) when you pass a place ID parameter. See /maps/documentation/urls/get-started.
  • Problem: The waypoints parameter is ignored on Google Maps products that don't support waypoints and has platform-dependent count limits, and dir_action=navigate is ignored where navigation isn't available. Fix: Use no more than three waypoints for links that open in mobile browsers (nine otherwise), and don't depend on waypoints or dir_action=navigate working on every Google Maps product or route. See /maps/documentation/urls/get-started#directions-action.
  • Problem: Maps and Street View share the same @ endpoint, so a map URL without the right action may not display a map. Fix: Set map_action=map for map views and map_action=pano for Street View panoramas. See /maps/documentation/urls/get-started.
  • Problem: If api=1 is missing from a Maps URL, all parameters are ignored and Google Maps opens its default view. Fix: Include api=1 in every Maps URL (1 is the only valid value). See /maps/documentation/urls/get-started#forming-the-url.