Comparisons

Google Maps plugins for WordPress: an honest comparison

◉ OCT 6, 2026 13 MIN

You have already decided that a plugin is the answer. What you want now is a shortlist and somebody willing to name one. Here is the call, before the table.

If you want the deepest free feature set and do not mind an admin screen with a lot of settings in it, install WP Go Maps. If you want a keyless map that matches your design and lives entirely in the block editor, install Modern Maps, which is ours. And if you genuinely need Google’s own data (Street View, live traffic, reviews and business listings, place autocomplete, routing), then you need a Google Maps Platform key, and either WP Go Maps or MapPress will take one.

That last case is the one most roundups bury, so it goes first here: a large share of people searching for a “Google Maps plugin” do not need Google at all. They need a map. The next section is a thirty second test for which one you are.

Everything after that is the reasoning, one section per plugin, with our row held to the same standard as everyone else’s.

◉ COMPARISON MATRIX · field-notes / comparisons

Five WordPress map plugins, five questions

Alphabetical order. Ours is a row like any other, with its limits in the same columns as everyone else’s.

Plugin Google API key required Block editor native Free version Markers on the free version Best at
Map Block for Google Maps Yes Yes, block only Whole plugin is free 1 per block One address, one block
MapPress No, unless you pick Google or Mapbox Yes, plus classic and shortcode Free, with a paid Pro Unlimited Per-post maps for listings
Maps Widget for Google Maps Yes No, widget only Free, with a paid Pro 1 (extra pins are Pro) A sidebar thumbnail map
Modern Maps No, never Yes, block only Both builds free to install Unlimited (WP.org Lite) / 2 (self-hosted) A map that matches the page
WP Go Maps No, unless you pick the Google engine Yes, plus shortcode and widget Free, with a paid Pro Unlimited The most features for free

Last checked 26 July 2026 against each plugin’s own WordPress.org listing. Tiers move. Re-verify before you rely on a cell.

◉ modernmapswp.com / field-notes / comparisons
Every row has a limit in it, including ours.

First, do you actually need Google?

“Google Maps plugin” is usually shorthand for “map plugin”. Google is the brand most people attach to the idea of a map, so it is the word they type. It is worth thirty seconds to work out which one you meant.

You need Google’s data if your map has to show:

  • Street View
  • live traffic or transit layers
  • Google reviews, ratings, opening hours, or business listing data
  • place autocomplete inside a form
  • turn-by-turn directions or routing

Any map can do the rest:

  • show visitors where you are
  • show a handful of locations at once
  • style the map so it does not clash with the page around it
  • attach a popup with your own words, an image, and a link
  • sit inside a post or page and behave

If everything you need is in the second list, then the API key, the Google Cloud project, and the billing account in your name are cost with nothing coming back the other way. Several plugins in this comparison will render a perfectly good map without any of it, using tiles drawn from OpenStreetMap data instead. That is the single most useful thing to know before you install anything.

If you have not settled on a plugin at all, how to add a map in WordPress covers the two non-plugin routes as well, since for a single address on a quiet page an iframe embed is still a defensible answer.


How we compared

Four questions, asked of every plugin including ours.

  1. Does it need a Google Maps API key? Not “can it use one,” but “will it show a map without one.”
  2. Is it native to the block editor? A map block you add next to your content, rather than a map you build in a separate admin screen and then reference.
  3. What does the free version actually do? Specifically what it does before any upsell, and where its ceiling is.
  4. What is it best at? Every one of these is good at something. Naming that is more useful than scoring them out of ten.

We deliberately did not compare speed, page weight, or Lighthouse scores. Nobody has measured those under conditions worth publishing, and a comparison table with an invented performance column is the fastest way to lose the readers who know better.

Install counts, versions, and feature tiers below were read from each plugin’s own WordPress.org listing on 26 July 2026. Plugins move things between tiers. The date is on the table for a reason.


WP Go Maps

Formerly WP Google Maps, on WordPress.org since 2012, and at 300,000+ active installs it is the category leader by a wide margin.

It supports a long list of map engines: Google Maps, Leaflet, OpenLayers, Stadia Maps, MapTiler, LocationIQ, Azure, and a “Zero Cost” Leaflet option. Its own FAQ answers the key question directly: you need a Google API key only if you choose Google as the engine, and you can switch engines later without losing your markers.

The free version is unusually generous. As many markers as you want, a map block, a shortcode, a classic widget, nine map themes, polygons and polylines, and basic store locator search. The Professional Edition is where marker categories and filtering, custom marker icons, directions, CSV import, and the ability to create more than one map live.

The tradeoff is where the work happens. You build a map in a top-level “Maps” admin screen and then place it on a page. If your mental model is “add a block, type an address, done”, that is a detour, and the settings surface is large enough that you will meet options you did not want to have an opinion about.

Pick it if you want the most map features available in a free plugin, you can live in a settings-heavy admin area, and there is a chance you will want a store locator later.


Maps Widget for Google Maps

By WebFactory, 30,000+ active installs. It is the narrow, deliberate option, and it is refreshingly clear about being one.

It renders a static thumbnail map that opens an interactive map in a lightbox when a visitor clicks it. It needs a Google Maps API key, and its FAQ says so bluntly: without the key, maps will not work.

It is a widget, configured under Appearance then Widgets. There is no map block. The shortcode is a Pro feature, and so are multiple pins. The same author ships a separate plugin, Map Block for Google Maps, for block editor users, which tells you exactly where the line is drawn.

Pick it if you want one Google map in a sidebar or footer, one address, almost nothing to configure, and you already have an API key or do not mind making one.


MapPress

On WordPress.org since 2009 and still shipping updates this month, at 30,000+ active installs.

MapPress sits between the two above. It supports Google Maps and Mapbox, both of which want keys, and free keyless Leaflet maps built on OpenStreetMap and OpenFreeMap tiles. It ships a Gutenberg map block, classic editor support, a shortcode, and a PHP function, and its listing states unlimited maps and unlimited markers in the free version. Very few plugins in this category put it that plainly. The free version also covers KML overlays, GPX tracks, and drawing polygons, circles, and lines.

Its real strength is attaching maps to content. If you run a directory, a property site, or a travel blog where every post has its own location, MapPress is shaped around that job. Search, filtering, geolocation, custom marker uploads, and the store locator block are Pro.

Pick it if you want a map per post, you want to stay keyless, and a long maintenance history matters to you.


Map Block for Google Maps

Also by WebFactory, 20,000+ active installs. It is one block with four settings: an address or a pair of coordinates, a zoom level, a height, and an API key that is saved once and then reused by every other block.

It needs a Google Maps API key. That is the whole plugin, and its listing does not pretend otherwise. No marker list, no popup editor, no styling past Google’s defaults.

Pick it if you want a Google map, in the block editor, at one address, and nothing more. If you want more than that, you will outgrow it inside a week.


When you need a store locator

If what you actually need is a searchable map with hundreds of pins, distance search from a visitor’s postcode, category filters, and a results list that updates as the map moves, you are shopping in a different product category. It is worth saying that out loud early, because general-purpose map plugins will carry you most of the way there and then stop.

WP Go Maps includes basic store locator search in its free version and puts the store locator block in Pro. MapPress puts search and filtering in Pro. Past those two, there are dedicated store-locator products built for this exact job, with import tooling, custom fields per location, and lead capture. They cost more and they take longer to set up, and that is the correct price for what you are asking for.

Modern Maps does not do this at all. No clustering, no distance search, no filtering, no import. That is not coyness about a roadmap; there is no code for any of it.


Modern Maps

Ours. Same columns, same standard.

Start with the thing that gets misreported. There are two builds, and they are two separate plugins rather than one plugin with a free tier. That distinction matters for exactly one number.

  • Modern Maps Lite, on WordPress.org, has no marker limit. There has never been one in that codebase, and there is no upgrade path inside it.
  • The build you download from modernmapswp.com adds two markers before it asks for a license key. A key removes the cap.

One detail about that two-marker limit is worth knowing: it never deletes markers that were already there. Only markers added during the current editing session get trimmed. A post authored with a license and later opened by someone without one keeps every marker on the map. The limit is a purchase prompt, not a content shredder.

What it does: no API key, no Cloud Console, no billing account, on either build. Three style presets (Light, Dark, Standard). Alignment set to default, wide, or full. Height in any CSS unit. A viewport that either fits itself to your markers or stays fixed where you put it, with a zoom slider. Address search in the editor. And marker popups built out of ordinary WordPress blocks, so a popup can hold a heading, an image, and a button, because those are just blocks. There are 24 worked examples in the gallery if you want to see the range before installing.

What it does not do: no clustering, no store locator, no GeoJSON, KML, or CSV import, no directions or routing, no shortcode, no WordPress widget, no Elementor, Divi, or Beaver Builder integration, no WPML or Polylang support, no custom marker icons or images. Marker styling is a color, and that is the entire styling surface for a marker.

And the limit to know before you install rather than after: there is no WebGL fallback. A visitor whose browser cannot run WebGL gets an empty container, not a static image and not a message. That is a real gap, and it belongs in this section rather than in a support thread.

Pick it if the map is part of how the page looks, you want it to live in the block editor beside your content instead of in its own admin section, and you do not need Google’s data.


What an API key adds to your job list

If the sections above have landed you on Google, here is the job, factually and briefly.

You create a Google Cloud project, enable the Maps JavaScript API (plus Places if you want autocomplete), and generate a key. You then restrict that key, by HTTP referrer at minimum, because a key sitting unrestricted on a public page is a key anyone can copy and spend against. Google documents both halves in its own guide to getting and restricting an API key. Then you attach a billing account, which means traffic to your public page is metered against a card in your name. There is a free monthly allowance; the numbers move often enough that quoting one here would be irresponsible, so read Google’s current pricing yourself before you commit.

None of it is difficult, and most people get through it in one sitting. It is simply an ongoing operational responsibility that a keyless plugin never asks of you. Being clear-eyed about which side of that trade your site sits on is the whole decision. For the opinionated version of that argument, clearly flagged as opinion rather than comparison, see why we skipped the API key entirely.


The verdict

Six situations, six names.

  • You need Street View, live traffic, Google reviews, or routing. A Google-engine plugin with a key. WP Go Maps or MapPress will both take one.
  • You want the deepest free feature set and will accept a settings-heavy admin. WP Go Maps.
  • You want a map per post for a directory, listings site, or travel blog. MapPress.
  • You want one address and genuinely nothing else. Maps Widget for Google Maps if it belongs in a sidebar, Map Block for Google Maps if it belongs in the post. Both need a key.
  • You need a store locator with hundreds of pins and distance search. A dedicated store-locator product, none of the five above.
  • You want a keyless map that matches your design, built in the block editor. Modern Maps.

Five of those six point somewhere other than us, and one points out of the plugin category entirely. That is not modesty. It is what the answers are.


Where to start

If you landed in the last line of that list, the fastest way to find out whether it is true is to install it and add a block. That takes about a minute, and the 60-second walkthrough is the whole process written down.

Download Modern Maps (free)

A license key changes three things on that self-hosted build, and only three: markers past the second one, the advanced OKLCH color sliders that drive the map’s gradient, and theme palette and marker colors that persist instead of resetting when you change them. Terms are on the pricing page.

If you would rather install from the WordPress dashboard, search the plugin directory for Modern Maps Lite. Same map, no marker cap, and no in-plugin upgrade path, because that build has no license mechanism in it at all.

← Earlier dispatch

A map widget for WordPress: what people mean, and what actually works

Guides ◉ Sep 22, 2026 08 MIN