Advanced Google Maps plugin for WordPress is a CodeCanyon utility, sold under the WP Maps Pro name, that turns a WordPress site into a searchable map and store locator. It plots manually entered locations, blog posts or custom post types onto Google Maps or OpenStreetMap, then gives visitors filters, listings, directions and route tools to explore them. It is built for businesses with physical branches, directories and any site that needs to present many places on a map without custom development.
The plugin comes from the developer flippercode and sells for a one-time $59 on CodeCanyon, where it has accumulated 15,876 sales and a 4.67 out of 5 rating across 654 reviews. Those numbers put it among the better-established mapping utilities in the WordPress ecosystem, and the vendor has kept it current, with the last update recorded in September 2026.
What the plugin actually does
The core job is straightforward: take a set of places and make them findable. Locations can be added by hand, imported in bulk from a CSV file, or pulled automatically from existing WordPress content. That last option matters more than it first appears. Any post, page or custom post type can carry a location through a meta box or a custom field, which means a site with hundreds of existing listings can be mapped without re-entering data. The plugin also works with Advanced Custom Fields, so sites that already store coordinates in custom fields can reuse them.
Once locations exist, the front end becomes a small application. Visitors can search by address, city, postcode, country or title, narrow results by category or taxonomy, sort the results, and switch between a grid and a list view. All of that runs over AJAX, meaning the page updates without a full reload. The listing area is template-driven through placeholders, so fields such as phone, fax, email, website, opening hours or any custom value can be arranged without writing PHP.
Directions are handled inside the map rather than by sending visitors to Google. A marker click can pre-fill the starting point, and the route can be returned for driving, cycling, walking or transit, in miles or kilometres. There is also a proximity search that finds locations within a chosen radius, and a separate tool that queries the Google Places API to surface nearby amenities and draw a circle around the results.
For maps with a large number of pins, marker clustering groups nearby markers into a single icon that splits apart as the visitor zooms in. Ten cluster styles are included, and clustering recalculates automatically when filters are applied, which is the detail that usually breaks on cheaper alternatives.
Two features stand out for more ambitious projects. The first is route drawing: an administrator can define routes in the back end with waypoints, stroke colour, opacity and weight, then expose them on the front end with a filter so visitors can toggle each route on or off. The second is shape drawing, where circles, rectangles, polygons and polylines can be added to the map and made clickable, which suits catchment areas, delivery zones or territory maps. A Zapier integration also lets marker click events be forwarded to more than 500 external apps, which opens the door to CRM or analytics workflows.
Where it fits, and where it does not
The clearest fit is a multi-location business: retail chains, clinics, dealerships, gyms, banks, hotel groups, franchises. The plugin ships with demo configurations for more than thirty such niches, which is a reasonable signal of where the vendor sees demand. Directory sites are the second strong fit, particularly ones where listings already exist as a custom post type and need a map layer on top. WooCommerce stores with physical pickup points, BuddyPress communities mapping members, and event or real estate sites with geographically scattered entries all fall inside the same pattern.
It is the wrong choice for a site that needs exactly one map with one pin. The full listing module, filter set and search interface would be dead weight, and a lightweight embed or a free block would do the same job with far less overhead. It is also a poor fit for anyone who wants a fully managed service where the vendor hosts the map data and handles Google API billing, since this is a self-hosted plugin and the site owner remains responsible for the Google Maps API key, its restrictions and its usage costs.
Strengths and limitations
Strengths
- Bulk CSV import supports any number of fields and all common delimiters, so large location sets do not need manual entry.
- Posts, pages and custom post types can be mapped alongside manually created locations, and multiple post types can share one map.
- Infowindow content is built from placeholders, which keeps customisation available to non-developers.
- Marker clustering recalculates after filtering rather than only on initial load, which is the correct behaviour for dense maps.
- Route and shape tools go beyond a standard store locator and cover territory, delivery and logistics use cases.
- Gutenberg support, WPML compatibility and integrations with Elementor, WPBakery, Contact Form 7, Gravity Forms, WooCommerce and BuddyPress reduce friction on sites already built with those tools.
- The source includes JavaScript, JSON, HTML, XML, CSS and PHP files, so the code can be extended rather than only configured.
Limitations
- A Google Maps API key is required, and Google’s per-request pricing applies. On a high-traffic directory the API bill can exceed the plugin’s one-time cost, and the vendor does not state any usage estimate. Sites that want to avoid this can use the OpenStreetMap option, but that drops the Google Places and Google directions features.
- Browser support is declared back to Internet Explorer 8, which reflects a long-lived codebase rather than a modern one. That breadth is useful for legacy audiences but is not a signal of a lean front-end footprint.
- Several features depend on external services staying available and correctly configured. The Places API proximity search and the Zapier forwarding both fail silently from the visitor’s point of view if the key or connection is misconfigured.
- Because the plugin covers locations, posts, routes, shapes, filters and imports in one package, the settings surface is large. Administrators who only need a simple map will spend time working out which options are irrelevant to them.
- Some behaviour is only partly documented in the listing. The vendor does not state how many locations the plugin handles before performance degrades, so capacity has to be tested against the specific hosting setup.
How it compares with the alternatives
Mapping options for WordPress split into three rough groups. The first is free plugins that embed a map and accept a handful of pins; they are quick to set up but usually stop at basic markers and a single infowindow, with no filtering, clustering or directions. The second is hosted store locator services, which charge a recurring fee, handle the infrastructure and the API costs, and offer less control over markup and data ownership. The third is premium self-hosted plugins such as this one.
Against the free tier, the difference is depth rather than polish. Filtering by taxonomy, CSV import, route drawing and marker clustering are the features that separate a map from a locator, and they are rarely present in free options. Against hosted services, the trade-off runs the other way: a one-time $59 purchase plus API usage is cheaper at low volume, but the site owner carries the setup, the key management and the maintenance. The plugin’s breadth of integrations is its main edge within the premium self-hosted group, since it slots into page builders, membership plugins and e-commerce setups that a narrower tool would ignore.
Frequently Asked Questions
Does this plugin need a Google Maps API key?
Yes. Google Maps requires an API key, and the site owner must create one in the Google Cloud Console, enable the relevant APIs and set restrictions. Google then bills per request beyond its free allowance. The plugin also supports OpenStreetMap as an alternative base map, which avoids the key and the billing but removes the Google Places and Google directions features.
Can it map existing posts and custom post types instead of separate locations?
Yes. Any post, page or custom post type can be assigned a location through a meta box, a custom field or the Advanced Custom Fields plugin. Multiple post types can appear on a single map, and infowindows can display titles, excerpts, featured images, categories, tags and custom fields using placeholders rather than code.
How many locations can it handle before the map slows down?
The vendor does not publish a figure. Performance depends on hosting, the number of markers loaded at once and whether clustering is enabled. Marker clustering is the main safeguard, since it groups nearby pins and recalculates after filtering. Large directories should be tested on the target hosting before launch rather than assumed to scale.
Is coding required to build a store locator with it?
No coding is required for the standard setup. Locations are added manually or imported from CSV, filters and search fields are toggled in the back end, and listing layouts are customised through placeholders. Developers who want deeper changes can work with the included PHP, JavaScript, CSS and JSON source files, but that is optional rather than necessary.
Verdict
This is a mature, well-reviewed option for sites that need a real store locator rather than a decorative map. The combination of CSV import, taxonomy filtering, marker clustering, routing and shape drawing covers ground that most competing plugins charge more for or skip entirely, and the integration list is unusually broad. Buyers should go in understanding that the Google API key and its usage costs sit with them, and that the settings surface rewards a project with genuine mapping requirements. A single-location site, or one that wants someone else to manage the infrastructure, should look elsewhere. For multi-branch businesses, directories and franchises on WordPress, it is a defensible purchase at $59.
