Same geocoder. New look. See what’s new

Drop-In Google Maps Geocoding API Alternative
for US, Canada, and Mexico

Same request format. Same response structure. No restrictions on storing or reusing results. Up to 80% less expensive.

Google's terms restrict how you can use the data

Here's something that surprises people: Google's geocoding terms don't let you keep the results for more than 30 days. If that's why you're here, welcome.

Google's Terms of Service for the Maps Geocoding API include restrictions that many teams don't discover until deep into a project:

  • 30-day caching limit. Google requires you to delete cached geocoding results after 30 days unless you're displaying them on a Google Map.

  • No data analytics. Google's terms prohibit using geocoded results for data analytics, market research, or database building.

  • Map-brand lock-in. Results from Google's geocoding API cannot be displayed on non-Google maps (OpenStreetMap, Mapbox, Leaflet, Tableau, etc.).

  • No monetization. Building a dataset from Google geocoded results and selling or licensing that data is not permitted.

These restrictions don't affect every use case. If you're geocoding addresses in real time and displaying them on a Google Map, the terms work fine.

But if you're building a database, running analytics, displaying results on dashboards, or doing anything with the data beyond showing it on a Google Map, the terms become a problem.

Google's pricing is hard to predict

Google Maps Platform pricing uses multiple SKUs, tiered rates, and usage multipliers that can make cost estimates unreliable. Teams regularly report bills that jump between billing cycles as usage patterns shift.

We previously had used Google to do our geocoding, however we wanted to expand to our entire customer base. Geocodio presented a very easy-to-use alternative. From the very beginning they showed genuine interest in making their product work with our situation. Top management came on a call with us to answer our questions. You just don't find that sort of customer support anymore.

Robert T., CIO, Medical Practice, Capterra Review

How Geocodio's terms are different

Geocodio's terms are designed to stay out of the way.

Store the data. Use it how you want.

  • No caching limits. Store forward geocoding results permanently. No 30-day deletion requirement.

  • No map-brand lock-in. Display results on any map provider: Google Maps, Mapbox, OpenStreetMap, Leaflet, Tableau, or anything else.

  • Analytics are fine. Use the data for market research, competitive analysis, compliance reporting, dashboards, whatever the job requires.

  • Build on the results. Create derived datasets, combine Geocodio results with other data sources, and use the enriched data across your organization.

The only restriction: you cannot use Geocodio results to create a competing geocoding service.

Geocodio vs. Google Maps Geocoding API Pricing

Simpler and up to 80% less

Geocodio Google Maps
Free tier $1.00 per 1,000 lookups ~10,000 requests/month with credit card
Per-lookup cost $0.50-$1.00 per 1,000 lookups $5.00 per 1,000 requests (after free tier)
High-volume option Unlimited plan: $1,350/month flat No flat-rate option published
Data enrichment Census data, districts, timezones included Separate APIs, separate charges
Billing model Per-lookup or flat monthly rate Per-request with tiered SKUs

Example: 100,000 lookups per month

  • Geocodio (pay-as-you-go): $50-$100

  • Google Maps Platform: ~$500

  • Estimated savings: 80-90%

Geocodio credits do not expire. Use the pricing calculator to estimate costs for your specific volume.

No billing surprises

Geocodio accounts include hard usage caps that you control, a real-time usage dashboard, and alerts before you hit your limit. Flat-rate plans are available for teams that need predictable monthly costs.

Drop-in compatibility

Just swap the host and API key

Geocodio's Google Maps API compatibility mode accepts requests in the same format as the Google Maps Geocoding API and returns results in the same JSON structure. Your existing parsing code keeps working.

Migration in two steps

Step 1: Create a free Geocodio API key at dash.geocod.io/register

Step 2: Change the hostname from maps.googleapis.com to api.geocod.io

The compatibility endpoint at https://api.geocod.io/maps/api/geocode/json translates your Google Maps-formatted requests into Geocodio queries and returns results in the Google Maps response format.

What's supported

  • Forward geocoding (address to coordinates)

  • Reverse geocoding (coordinates to address)

  • address_components, geometry, formatted_address

  • Standard status codes (OK, ZERO_RESULTS, etc.)

  • U.S., Canadian, and Mexican addresses

Limitations

  • place_id is returned but empty

  • viewport is approximated

  • plus_code is not included

  • Coverage is limited to the U.S., Canada, and Mexico

For full implementation details, see the Google Maps API compatibility guide.

Using Geocodio as part of a geocoding waterfall

Many organizations use multiple geocoders in sequence to balance accuracy and cost. Geocodio returns accuracy scores and accuracy types with every result, which makes it straightforward to route lower-confidence results to a secondary provider.

A common setup:

  1. Geocodio as the primary geocoder. Process all addresses through Geocodio first. Filter results by accuracy score (0.8+ recommended) and accuracy type (rooftop or range interpolated).

  2. Google Maps as a fallback. Send addresses that return lower-confidence results to Google for a second pass.

  3. A third provider for remaining gaps. Some teams add Esri or another specialized geocoder for the small number of addresses that neither Geocodio nor Google resolves at a high confidence level.

This approach typically reduces overall geocoding costs by 70-90% compared to running everything through Google, while maintaining the same or better accuracy across the full dataset.

Common questions

No. Geocodio replaces the Google Maps Geocoding API specifically. Geocodio does not offer a Maps JavaScript API, Street View, Places API, or directions. If your application uses those services, you can continue using Google for them and use Geocodio for geocoding.

Geocodio covers the United States, Canada, and Mexico. For addresses outside North America, you'll need a separate provider. Many teams use Geocodio for North American addresses and a global provider for the rest.

Yes. Geocodio places no restrictions on which map provider you use to display results. You can use Google Maps, Mapbox, OpenStreetMap, Leaflet, or any other mapping platform.

Accuracy varies by address and region. Geocodio returns both an accuracy score (0 to 1) and an accuracy type (rooftop, range interpolated, nearest street, etc.) with every result, so you can evaluate quality programmatically.

Start by testing in parallel. Run Geocodio alongside Google on a sample of addresses and compare accuracy, response times, and costs. Then gradually shift traffic as you build confidence. Most teams remove the Google fallback after 30-60 days.

Get started

Create a free account at dash.geocod.io/register. No credit card required. 2,500 free lookups per day.

Most developers complete initial testing in under an hour.

Just Change the Host & API Key