Hi @sdagency,
Thank you for sharing the link to the site, that was very helpful.
I can see a few issues on the site, all which may be affecting marker creation and serving those markers on the site. I’m going to separate each into sections below.
Google Maps Billing
Google Maps requires a valid billing account to be linked to your API key, this is not controlled by us, but instead is a part of your Google Maps API key creation requirements.
On the page, we can see the following error:
- You must enable Billing on the Google Cloud Project at Billing
I can see the API key is being appended on the page, and from my tests the key has been set up correctly, which means the error does seem to be accurate in stating that the billing account is either not connected or is no longer valid.
Background Data Requests Denied
I can see multiple 403 (Forbidden Access) errors on our data background requests. Specifically, when the map is loaded, our core systems will make requests to your server to load the markers into the map and show them to visitors.
The 403 error here indicates that your site is actively rejecting those requests. In most cases, this is due to security plugins/services which have been setup to prevent access to the WordPress REST API. For example, you may be using something like Wordfence, which can actively reject requests like this, preventing the marker data from being returned.
To solve this, you may need to put your security systems into Learning Mode, allowing it to whitelist these requests, or you may find settings specifically related to the REST API.
Alternatively, some users have had success in simple disabling compressed paths within our plugin. These can be found under Maps > Settings > Advanced Settings > Disable Compressed Paths.
