Google Maps Without an API Key in WordPress
Short answer: you only need a Google Maps API key for Google’s JavaScript API and Maps Embed API — not for the standard share-embed iframe. This guide explains the difference, shows the manual no-key method, and how to automate it in WordPress.
The three ways Google Maps gets on a website
| Method | API key | Billing card | Custom markers/overlays |
|---|---|---|---|
| Maps JavaScript API | Required | Required | Yes |
Maps Embed API (/maps/embed/v1/) |
Required | Required (free usage, but card on file) | Limited |
Share-embed iframe (output=embed) |
Not required | Not required | No |
Google’s own documentation says an API key is required — because it documents the first two methods. The third is the iframe Google generates for anyone via Maps’ Share → Embed a map button, and it has never required a key.
The manual method (no plugin)
- Open google.com/maps and search your address.
- Click Share → Embed a map.
- Copy the
<iframe>HTML. - In WordPress, add a Custom HTML block and paste it.
This works, but it has friction: the embed code is long, the fixed pixel size isn’t responsive, there’s no lazy loading unless you add it by hand, and every new map means another trip to Google Maps.
The automated method (Quick Maps)
The Quick Maps plugin generates the same kind of embed iframe from a shortcode:
[quick-maps]Orlando, Florida[/quick-maps]
Same no-key embed, plus the parts you’d otherwise hand-roll: responsive width, native loading="lazy", an accessible iframe title, sizing attributes, and site-wide defaults. The plugin adds no JavaScript or CSS of its own.
What you give up without a key
Honesty over marketing: the embed iframe shows standard Google Maps with a single search-pin. If you need custom marker icons, multiple plotted locations on one map, drawn overlays, or data layers, you need the JavaScript API — and its key, Cloud project, and billing setup. For the most common case (“show visitors where we are”), the embed covers it entirely.
Is the no-key method allowed?
Yes. The embed iframe is generated by Google’s own Share button for exactly this purpose — public embedding. It is not a quota workaround or scraping trick; it’s the consumer embed path Google has offered for years.
FAQ
Does the free embed have usage limits?
Google doesn’t publish quotas for the share-embed iframe. It’s the same embed millions of sites use; for normal website traffic there is no practical limit.
Will this slow my site down?
The iframe is the heaviest part of any map method — but with lazy loading it costs nothing until a visitor scrolls to it. Quick Maps applies loading="lazy" automatically.
What about visitor privacy?
When the map loads, the visitor’s browser talks to google.com, which may set cookies. That’s true of every Google Maps method, keyed or not. Lazy loading actually helps here: no Google request happens unless the visitor scrolls the map into view.
Keep reading
- How to add Google Maps to WordPress — the step-by-step, plugin and manual.
- Google Maps API pricing, and when you don’t need a key
- Is a map plugin slowing down your WordPress site?