Guides

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

◉ SEP 22, 2026 08 MIN

Two people type “map widget for WordPress” into a search box and want opposite things.

Most of them mean a small map they can drop somewhere on a site: a page, a footer, a sidebar, wherever it fits. They have no opinion about WordPress’s widget system and no reason to. For that reader the answer is a block, and the fast path starts one section down.

A smaller group means the literal thing, an entry in Appearance → Widgets that slots into a registered sidebar in a classic theme. That reader deserves a straight answer, so here it is up front. Modern Maps registers no WordPress widget. It registers no shortcode either. It registers three blocks, and that is the entire surface area. If a classic registered widget is a hard requirement on your site, skip ahead to “If you need a literal sidebar widget” and decide from there.


In a block theme, the block is the widget

WordPress 5.8 turned the widgets screen block-based, and the job widgets used to do (park a reusable chunk of content somewhere outside the main content area) moved to blocks and template parts. Widgets did not disappear. They stopped being where new features get built. The WordPress developer documentation on widgets still describes the classic API, and it still works, but almost nothing new registers one.

There is a detail here that causes half the confusion. Open the block inserter and the Modern Maps block sits under Widgets. That is because its block.json declares "category": "widgets", which is where WordPress files this class of block, next to Latest Posts and Calendar. It is a shelf label in the inserter. It is not the widget system. Same word, two systems, nothing shared between them.

So when someone asks for a WordPress map widget and means “a map that goes somewhere on the site,” they are asking for the block. It is already there.


Adding the map, the short version

  1. Install the plugin and activate it. There is no setup wizard and no API key step.
  2. Open a page, type /map, press return.
  3. Set the location. For a pin, add a marker and search the address in its Location Settings panel. To move the view without a pin, switch Map Position to “Fixed (Manual)” and use Search Center. Coordinates go in the separate Latitude and Longitude fields, not the search box.
  4. Set Height and alignment.
  5. Publish.

That is the compressed version. The step-by-step with the actual screens is in your first map: a 60-second walkthrough, and there is no point reproducing it here.

Two settings matter more than the rest for widget-shaped placements. Height accepts any CSS unit, but the units are not equally safe. Absolute ones (px, rem, vh) hold up in ordinary layouts, so 320px in a page does what you expect. 100% only resolves if the parent has an explicit height of its own, and in a sidebar or a footer it usually does not, which is the collapse covered in “If the map does not show up” below. Alignment offers default, wide, and full. Beyond that there are three built-in presets (Light, Dark, and Standard); the gallery shows how far the colors can be pushed from there. The viewport either fits itself to the markers automatically or holds a fixed center and zoom.


Where you can actually put it

Placement is the real question behind most map widget searches, and in a block theme none of the answers involve the widgets screen.

  • In page or post content. The common case. Add the block where you want it.
  • In a template part. Appearance → Editor → Patterns → Template Parts. Footer is the usual target. Header works too, though a map in a header is rarely what anyone actually wants.
  • In a template. Add it to Single or to an archive template if every post of a type should carry the same map.
  • In a synced pattern. Use this when the same map appears in several places and needs to change in one edit.
◉ Placement · field-notes / guides

Where a map can actually go

One question, answered for both kinds of theme. The word “Widgets” in the block inserter is a shelf label, not the widget system.

Where you want the mapBlock themeClassic theme
In page or post contentAdd the blockAdd the block
Footer or headerEdit the template partTheme template file
On every post of a typeEdit the Single templateTheme template file
Same map in several placesSynced patternSynced pattern
A sidebar columnSidebar area in a templateBlock widgets screen, verify on the front end
A classic register_widget widgetNone registeredNone registered
Blocks registered3 (map, marker, popup)
Shortcodes registered0
WordPress widgets registered0
Heightany CSS unit
Alignmentdefault / wide / full
◉ block.json · “category”: “widgets”
Same word. Two systems.

If you need a literal sidebar widget

Some sites genuinely need one: a classic theme, a registered sidebar, and a widget that belongs in it. Modern Maps does not have one. There is no register_widget call anywhere in either build, and there is no shortcode to fall back on.

There is one path worth testing. Since 5.8 the Appearance → Widgets screen is itself block-based, so a classic theme with registered widget areas can accept blocks there. Whether the Modern Maps parent block and its marker child behave correctly on that screen has not been verified, because the parent restricts which blocks it accepts and the marker declares a required parent, and nested blocks on the widget screen are their own small world. Try it on a staging site, and judge it by the front end rather than by the widget screen preview.

If it does not hold up, two things do work. Put the map in page content and drop the sidebar requirement for that page. Or move the site to a block theme, where the placement problem stops existing.


What a WordPress map widget will not do here

Worth setting the ceiling before anyone installs anything.

Marker styling is a color, and nothing else. No custom icons, no uploaded images. There is no clustering, no store locator, no directions or routing, no CSV, GeoJSON, or KML import, and no Elementor, Divi, or Beaver Builder widget.

Markers themselves depend on which build you run, and the two are genuinely different. Modern Maps Lite, on WordPress.org, has no marker limit and never has. The build downloaded from modernmapswp.com stops at two markers until a license key is added. That limit only trims markers added during the current editing session, so a post authored with a license keeps every marker if someone later opens it without one.

If two or three of those missing features are exactly what the project needs, this is not the right tool, and the honest move is to compare categories before installing anything. How to add a map in WordPress lays out the options.


If the map does not show up

Two causes account for almost all of it.

Height is set to a relative unit. Leaving Height blank is safe: the block falls back to 300px. The collapse comes from a relative value, almost always 100% (occasionally a vh value inside a transformed wrapper), resolving against a parent with auto height. A percentage of nothing is zero, so the map renders as a zero-pixel strip and reads as “the block is broken.” Switch Height to an absolute unit. If a stubborn theme wrapper is still collapsing it, give the map a floor:

/* give the map a floor inside a narrow column */
.wp-block-create-block-modern-maps .modern-maps__container,
.wp-block-create-block-modernmaps-lite .modernmaps-lite__container {
  min-height: 280px;
}

Target the inner container, not the block wrapper: it is the element that carries the height and holds the map canvas, and min-height on it beats the inline value. The first selector pair is the self-hosted build, the second is Modern Maps Lite. Keeping both means the rule survives a switch between them.

The visitor has no WebGL. The map is drawn with WebGL, and there is no fallback yet, so a hardened browser or a machine with WebGL disabled gets a blank container rather than a static image. Worth knowing before deciding a map belongs in a global footer.


Get the plugin

Download the Modern Maps zip, then upload it at Plugins → Add New → Upload Plugin, and activate. Free to use.

Modern Maps Pro activates in place with a license key, no reinstall, and adds exactly three things: markers above two, advanced color controls (nine OKLCH sliders for lightness, chroma, hue, bounds, and drift), and theme-palette and marker colors that persist instead of resetting. Pricing is here.

If the dashboard install flow is easier, search the plugin directory for Modern Maps Lite. Same map, no marker cap, and no in-plugin upgrade path. The rest of the guides cover the block in more detail.

← Earlier dispatch

Multiple locations on one WordPress map (and how many markers you get)

Guides ◉ Sep 8, 2026 09 MIN