Choosing the right software
Define the map provider, expected traffic and location data before comparing marker or locator interfaces. Check API-key restrictions, usage charges and consent requirements with the provider. Test a visitor who declines location access and one who navigates only by keyboard. A map should have an address or directions fallback so the page remains useful when external tiles fail.
This shortlist covers 5 currently listed WordPress options selected from 45 catalog records with supported evidence for this use case. Each included record has an official directory URL, a recent metadata check and a recorded upstream update within two years. The selection prioritizes a matching stated purpose, then reported adoption as a tie-breaker. It is not a hands-on performance ranking or a security endorsement. The snapshot was prepared on 2026-10-02.
1. WP Go Maps. Source description: “The easiest to use WordPress map plugin! Create a custom map, map block, store locator or map widget…”. Deployment: WordPress 6.0 / PHP 7.0. Listed version 10.1.10. 300,000 active installations reported by WordPress.org. The source identifies the developer as WPGMaps. Its directory metadata records testing through WordPress 7.1.2; this is an upstream compatibility declaration, not a BuyPHP test. Compare the listed 10.1.10 release with the version available when you install. The upstream update recorded for this candidate is 2026-09-28. Open its product record for the attributed facts and official download route before adding it to your implementation plan.
2. WP Maps. Source description: “WordPress map plugin for Google Maps, OpenStreetMap & Mapbox with custom markers, filters, searchable listings and store”. Deployment: WordPress 6.0 / PHP 7.0. Listed version 5.0.1. 60,000 active installations reported by WordPress.org. The source identifies the developer as Flipper Code - WordPress Development Company. Its directory metadata records testing through WordPress 7.1.2; this is an upstream compatibility declaration, not a BuyPHP test. Compare the listed 5.0.1 release with the version available when you install. The upstream update recorded for this candidate is 2026-09-24. Open its product record for the attributed facts and official download route before adding it to your implementation plan.
3. MapGeo. Source description: “Create interactive vector maps of the world, continents, any country in the world and specific regions, including individual…”. Deployment: WordPress 5.0 / PHP 7.4. Listed version 1.6.30. 40,000 active installations reported by WordPress.org. The source identifies the developer as MapGeo. Its directory metadata records testing through WordPress 7.0.6; this is an upstream compatibility declaration, not a BuyPHP test. Compare the listed 1.6.30 release with the version available when you install. The upstream update recorded for this candidate is 2026-08-07. Open its product record for the attributed facts and official download route before adding it to your implementation plan.
4. Leaflet Map. Source description: “Interactive maps and markers on your posts and pages with simple”. Deployment: WordPress 4.6 / PHP. Listed version 3.4.7. 30,000 active installations reported by WordPress.org. The source identifies the developer as bozdoz. Its directory metadata records testing through WordPress 7.1.2; this is an upstream compatibility declaration, not a BuyPHP test. Compare the listed 3.4.7 release with the version available when you install. The upstream update recorded for this candidate is 2026-08-22. Open its product record for the attributed facts and official download route before adding it to your implementation plan.
5. MapPress. Source description: “Unlimited maps and markers. Free, no API key, no setup. Google Maps, Leaflet, OpenStreetMap & Mapbox. Map editor,…”. Deployment: WordPress 6.3 / PHP 7.0. Listed version 2.97.14. 30,000 active installations reported by WordPress.org. The source identifies the developer as chrisvrichardson. Its directory metadata records testing through WordPress 7.1.2; this is an upstream compatibility declaration, not a BuyPHP test. Compare the listed 2.97.14 release with the version available when you install. The upstream update recorded for this candidate is 2026-09-28. Open its product record for the attributed facts and official download route before adding it to your implementation plan.
Compatibility comparison: 4 distinct prerequisite statements are recorded across this shortlist. WordPress 6.0 / PHP 7.0; WordPress 5.0 / PHP 7.4; WordPress 4.6 / PHP; WordPress 6.3 / PHP 7.0. Match these minimum requirements to your actual PHP and WordPress versions, then test the specific workflow on a copy of your site. A minimum version is not a promise that every theme, extension or newer runtime combination works. Missing integration evidence should remain a question for the developer.
Before choosing, use the linked product records to check current prerequisites and source timestamps. Ask the developer about edition-specific capabilities, update support and any external service account needed. Source metadata helps create a practical shortlist, but deployment quality still depends on your configuration, content and integrations. No price or feature should be treated as verified unless its source is recorded.