You already have the “how” from @byteguru and @techchizkid, so I’ll focus on which approach to pick and a couple of pitfalls they did not really dig into.
1. Think about maintenance first, not just the first embed
Iframe is quick, sure, but ask yourself:
- Will your address, phone or branding change soon?
- Do you plan to add more branches later?
- Are non‑technical people going to edit this page?
If the answer to any of those is “yes,” then hard‑pasting iframes in multiple places gets annoying. In that case I prefer a reusable solution:
- One centralized map (via shortcode or a builder widget).
- Drop that shortcode wherever you want a location.
- Update once, everywhere changes.
That is where a small map helper or generator like the unnamed “easy Google Map embed generator for your site” becomes useful. You generate one consistent snippet and use it across pages instead of grabbing slightly different iframe codes from Google each time.
Pros of using that type of generator:
- Cleaner iframe code than what many page builders leave you with.
- You can pre‑set width, height, zoom so all maps match your design.
- Non‑dev users only copy and paste one simple snippet.
Cons:
- Still static. If you want dynamic features later, you will likely redo it with an API or plugin.
- Another external tool in your workflow instead of configuring it all inside WordPress.
- Limited to what Google’s standard embed allows. No fancy clustering or deep customization.
2. Security & performance gotchas they only hinted at
A couple of things that commonly bite WordPress users:
-
Security plugins stripping iframes:
If you paste the map and it vanishes on save, check things like Content Security Policy rules or “disallow iframes” in your hardening plugin. Whitelisting the domain that serves the map is often better than disabling the protection altogether. -
Scroll hijacking on mobile:
Embedded maps can trap scroll, which frustrates visitors. To avoid that, some setups show a static image first. When the user taps it, then the iframe loads. This is especially important on small screens and helps performance. -
Lazy loading & Core Web Vitals:
@byteguru mentioned lazy loading in passing, but I would treat it as mandatory. If your theme or plugin does not handle this, look for an optimization plugin that can lazy load iframes. That keeps your LCP and CLS from tanking just because of one map.
3. When to skip a “real” map entirely
Hot take: if you just want to show “We are here” and most of your users hit you from mobile, a clickable static image that opens Google Maps or the Maps app can be better than an embedded map.
Workflow:
- Take a screenshot of your map.
- Insert the image in WordPress.
- Link it to the actual map URL.
Pros:
- Very fast, no Google scripts.
- No issues with security plugins or theme stripping.
- Cleaner UX on slow connections.
Cons:
- No interaction on the page itself.
- One extra tap for the user.
- You must update the image if your location changes.
For a simple business site, that tradeoff is often worth it.
4. Picking between iframe, builder widget, and API
Given what @techchizkid and @byteguru already laid out, here is a quick decision guide:
-
Single office, rarely changing, simple layout:
Use a straight iframe or a generator snippet. Keep it lazy loaded and maybe wrap it in a responsive container. -
More than one location or map reused in several spots:
Go for a shortcode‑based map plugin or your theme/builder’s map module. You update once, everything stays in sync. -
Complex needs like many markers, filters, stylized maps:
This is where the Google Maps JavaScript API and a serious plugin make sense, even if the setup feels heavier initially.
In short, their methods work, but do not only think “what is fastest to drop in today.” Think “what will be least painful when I have to touch this again in a year.”