Download websites that use WP Google Map Plugin

About WP Google Map Plugin

A map embedded in a page is a small confession that the business exists somewhere physical. Shops, clinics, restaurants, garages, churches and estate agents put a map on the contact page because a customer eventually has to arrive in person, and the plugin that draws it is close to a machine-readable statement that the site belongs to a local business.

WP Google Map Plugin has done that job on WordPress since 2012. Written in PHP like the platform it extends, the plugin wraps the mapping provider's JavaScript API so a site owner can place markers, routes and information windows from an admin screen instead of writing code. The Freemium model splits the audience usefully. A free tier covers the single location on a contact page, while the paid tier tends to be bought by sites with branches, dealers or property listings to display.

As of September 2026 we detect WP Google Map Plugin on 22,485 sites, 10,686 of them in United States, with .com the most frequent domain ending. Concentration in commercial domain space fits the profile. A plugin bought to show where the shop is belongs to sites that sell something locally rather than to publishers or personal blogs.

Version data turns the population into something more interesting than a count. We track 225 distinct releases, and 4.9.8 occurs more often than the rest. Fragmentation on that scale is characteristic of the WordPress plugin ecosystem, where updating depends on somebody logging into an admin panel, and where sites built once for a client and then abandoned keep running whatever was current on launch day. The version a site reports is a decent proxy for when anyone last maintained it, which matters for agencies selling maintenance retainers, for security teams scoping plugin vulnerabilities, and for anyone trying to separate live businesses from sites that merely have not been taken down yet.

Detection depends on the plugin leaving its assets in the delivered page, which the standard shortcode does. A site aggressively optimised, with scripts merged, renamed and inlined by a caching or performance layer, can hide the fingerprint completely. Undercounting is therefore expected, and the bias is not random. The sites most likely to go missing are the ones maintained well enough to run an optimisation layer at all, which tilts what remains toward the neglected end of the spectrum. Any conclusion about update discipline should carry that caveat with it.

The export exists for questions that start from the population rather than from a domain. Which local business sectors run this plugin, in which countries, at which release, alongside which theme, booking system or review widget. A per-domain lookup confirms one site's stack. A list tells you the size of a segment, the shape of its neglect, and where a competing product or a maintenance service would find customers who have already demonstrated they need one.