Comparison
Weganar vs. Google Maps Geocoding API
Google's own policy exempts place IDs from its caching restrictions and lets you store those indefinitely. Coordinates are not exempt.
161,303,091
US addresses served
83.9%
resolve to a rooftop point
99.9%
carry a 2020 Census block
Side by side
Every claim about Google Maps Geocoding API is footnoted to their own documentation. Last checked 2026-08-28.
| Google Maps Geocoding API | Weganar | |
|---|---|---|
| Storing the coordinates you get back | Lat/lng may be cached for up to 30 consecutive days, then deleted or refreshed1 | Store them for as long as you like; no caching clause |
| What you may keep forever | Place IDs only — explicitly exempt from the caching restrictions2 | Every field of every result |
| Census geography on a result | Not returned — the response carries address components, not Census GEOIDs3 | 15-digit 2020 Census block on 99.9% of results, plus tract, block group and county FIPS |
Sources
- 1. Google Maps Platform Service Specific Terms, §3.2.3 — read 2026-08-28
- 2. Geocoding API policies — “Exceptions from caching restrictions” — read 2026-08-28
- 3. Geocoding API response — documented response fields — read 2026-08-28
Terms and pricing at Google Maps Geocoding API may have changed since these were read. The dates above are when we last checked, not a guarantee of what is true today — follow the links for the current version.
Compare against something else
Try it against your own addresses
Start free with 5,000 geocodes a month — every result labels how it was resolved and carries its Census block.
Get your API key — 150 free credits