Integrations
Google Maps integration
In depth
Google Maps Platform — Google's enterprise mapping API suite, repositioned in 2018 from consumer Maps to a dedicated developer platform. In 2026 — 5+ million developers, 1.5+ billion monthly active users, powering Uber, Lyft, Airbnb, Booking.com, Tinder. The platform splits into three product groups: Maps (display), Routes (directions), Places (search + business data).
Maps APIs detail: (1) Maps JavaScript API — embed interactive map on any website, custom styling, markers, info windows, layers; (2) Maps Static API — non-interactive map image (no JavaScript needed) — useful for emails, blog posts; (3) Maps Embed API — iframe-based, simplest, no API quota; (4) Street View Static API — 360° panorama embeds.
Routes APIs: (1) Routes API (replaces Directions API + Distance Matrix API + Roads API in 2024) — turn-by-turn directions, traffic-aware ETA, multiple modes (driving, walking, transit, cycling); (2) Time Zone API — timezone for any geo coordinate.
Places APIs: (1) Place Search — find businesses near a location ("restaurants near Tbilisi"); (2) Place Details — full business info (name, address, phone, hours, photos, reviews, rating); (3) Place Autocomplete — typeahead search (used in 95% of modern address forms); (4) Geocoding — convert address ↔ lat/lng; (5) Address Validation — check + standardise addresses (released 2023).
Pricing structure 2026: $200 monthly free credit (covers ~28,000 map loads or ~40,000 Place Details requests). Beyond the credit: Maps JavaScript $7/1,000 loads, Place Details $17/1,000, Routes $5/1,000, Geocoding $5/1,000. Volume discounts at 100K+ requests/month. For Georgian small business — the $200 credit is enough for typical use cases (store locator, contact page map, listing pages).
Next.js integration: `@react-google-maps/api` package — popular, well-maintained; alternatives: `@vis.gl/react-google-maps` (newer, official Google library, better TS support). Server-side: use Place Details API in server actions to avoid exposing the API key client-side. API key restrictions — by HTTP referrer (browser key) or by IP (server key) — security best practice.
Alternatives 2026: (1) Mapbox — developer-friendly, better customisation, free 50K loads/month, $5/1K beyond; (2) OpenStreetMap (OSM) + Leaflet — fully free, community data, great for non-commercial; (3) HERE Maps — automotive industry leader, $200 free credit; (4) Apple MapKit JS — free + native iOS feel; (5) TomTom — last-mile delivery focus. Craftwebstudio recommendation: Google Maps for universal cases, Mapbox for design-heavy custom maps.
Why choose this
- Most complete data — 200M+ businesses, 1B+ user reviews
- $200 free credit/month — sufficient for small business
- Place Autocomplete — standard for 95% of address forms
- Routes API with real-time traffic-aware ETA
- Maps Embed API — zero-quota iframe option
Use cases
- Store locators and branch maps
- Real estate listings with maps
- Directions and route planning
Setup steps
- 1Google Cloud Console — create project + enable billing
- 2Enable Maps + Places + Routes APIs
- 3Generate API key + restrictions (HTTP referrer or IP)
- 4Install @react-google-maps/api + embed Map component
- 5Set up quota monitoring + alerts ($150 threshold)
Frequently asked questions
What does the $200 credit cover?▾
~28K map loads/month or ~40K Place Details. Small business store locator (1K-5K visits/month) — fully covered.
Google Maps vs Mapbox — which is better?▾
Google — better data, more recognisable. Mapbox — better customisation, design-friendly, vector tiles, $5/1K cheaper. Standard map → Google; custom-styled brand map → Mapbox.
How do I store the API key securely?▾
Browser key — HTTP referrer restrictions (mywebsite.com/*); server key — IP restrictions; never commit .env to git; set a daily quota cap in Cloud Console.
More integrations
Related services
Ready for a free consultation?
Get in touch — we reply within 24 hours with a scoped project estimate.