The Map facet

To bring FacetWP up-to-date with the latest Google Maps developments, FacetWP v4.4 (released on April 23, 2025) significantly changes how Google Maps and the needed Google APIs are integrated.

These changes affect the Proximity facet and the Map facet.

This page describes what has changed, why we did this and what you need to do. It also explains why you should consider migrating to the new facet types, how to do that, and what new documentation is available.

What has changed?

A lot. To prevent broken sites from a plugin update containing all these changes, we decided to split the Proximity and Map facet types into two versions.

Both facet types now have a “legacy” version without the changes, and a “new” version with the changes. If you are an existing user, and you update to FacetWP v4.4+, you will automatically still be using the legacy facets, and can migrate to the new versions at a time of your convenience.

Two Proximity facet types

To use the new Proximity facet, disable the 'Use Legacy Proximity facet' setting, enable 'Places API (New)', and disable the legacy 'Places API' in the Google Cloud Console.
To use the new Proximity facet, disable the “Use Legacy Proximity facet” setting, enable “Places API (New)”, and disable the legacy “Places API” in the Google Cloud Console.

In FacetWP v4.4 and newer, you can now choose between two Proximity facet types:

The Proximity facet can be switched with the new “Use Legacy Proximity facet” setting located in FacetWP > Settings. But before touching that switch, read about how to migrate.

Two Map facet types

In FacetWP v4.4 and newer, there are also two Map facet types:

The new Map facet is now built into the main FacetWP plugin. It can be enabled by deactivating the Legacy Map facet add-on. But before you do that, read about how to migrate. Because there are many potentially breaking changes, especially if you have many code customizations.

With this split, the Map facet add-on has reached its last version ever (v1.2) and will not be updated anymore.

New and changed features

In FacetWP v4.4 and newer, if the new Proximity and Map facets are used, the following features are new or changed:

Why all these changes? And why now?

The main reason for making all these changes now, is that the Google Maps Platform itself changed a number of things, a few with hard deadlines. Some of these changes were already resulting in deprecation warnings in the browser console for a long time (some for over a year). Some of the new features required other changes:

We decided to tackle all of these changes in one big update, so that FacetWP’s Google Maps integration is now entirely up-to-date again with the latest Google Maps developments.

What do I need to do?

New Proximity/Map facet users

If you are a new FacetWP user (starting at v4.4 or later), or if you want to start using the Proximity and/or Map facet for the first time, there is nothing to migrate. Just start using the new facet types, as documented on the Proximity facet and Map facet pages. Don’t install the Map facet add-on, as this will switch you back to the Legacy Map facet.

Existing Proximity/Map facet users

As an existing Proximity/Map facet user, after updating to FacetWP v4.4+, you will still automatically be using the legacy Proximity and Map facet versions, which remain fully working, including any custom code snippets you may be using.

You can decide to migrate to the new versions at a time of your convenience. While migrating to the new version is recommended, it is completely optional at this point in time, and can be postponed (but not indefinitely).

Migrating to the new facet versions is easy, if you have no code customizations (meaning code snippets from any of the Legacy documentation pages you have in your functions.php or code snippets plugin). To migrate the Proximity facet you only need to disable the “Use Legacy Proximity facet” setting, and switch your site to the “Places API (New)” in the Google Cloud Console. For the Map facet, you only need to deactivate the Map facet add-on.

However, many documented custom code snippets will not work anymore after migration. If you are using any of these, we have you covered with detailed migration info on each legacy snippet, but going through them all one by one could cost considerable time and effort, depending on how many you have. Make sure to plan accordingly.

Can I choose not to migrate?

Yes, you can decide to keep using both legacy facet versions for now. But, to future-proof your site, we recommend taking the time to migrate to the new Proximity and Map facets. Consider that eventually, you’ll need to migrate anyway, when Google inevitably discontinues the below-mentioned features. You may want to prevent a forced and stressful migration at the moment this happens in the future.

We will keep the legacy versions available as long as they keep working, which will not be indefinitely. The Legacy Proximity facet will keep working until Google decides to discontinue the legacy “Places API”. The Legacy Map facet (with the Map facet add-on installed) will keep working until Google discontinues either the (synchronous) direct script loading tag (which already shows a warning in the browser console), or legacy markers (which are already deprecated since February 21st, 2024).

When the mentioned features will be discontinued exactly is unknown at the time of writing. We recommend keeping an eye on Google’s legacy and deprecations pages.

Why should I consider migrating?

Because eventually, you’ll need to migrate anyway: when Google discontinues Places API, legacy markers, or the legacy (synchronous) direct script loading tag, at an unknown point in the future.

On the positive side: migrating to the new versions will give you access to all new features mentioned above. Here is a shortlist of the things we are most excited about:

How do I migrate?

How to migrate depends on your exact situation. Make sure to carefully read, and follow the steps outlined in these migration guides:

Available documentation

The Map and Proximity facets now have two sets of documentation: the new current one, and the “Legacy” documentation:

New documentation

For FacetWP v4.4 or newer, without the Map facet add-on installed, use:

For FacetWP version 4.4 or newer, with the “Use Legacy Proximity facet” setting disabled, use:

Legacy documentation

For FacetWP (any version), with the Map facet add-on (any version) installed, use the following pages. Where relevant we added purple banners with migration information about what changed, with links to the relevant new documentation sections and snippets. If a legacy snippet does not have a purple banner, you can safely assume it still works and does not need adapting.

For FacetWP versions older than v4.4, and for version 4.4 or newer with the “Use Legacy Proximity facet” setting enabled, use: