Back to Community
Home / Community / Plugin → Wp go maps (formerly wp google maps)

Understanding Google Maps API Costs and Billing with WP Go Maps

23 threads Sep 16, 2025 Plugin → Wp go maps (formerly wp google maps)

Content

Many WordPress users are surprised to discover that their map plugin can lead to unexpected charges from Google. This is a common point of confusion, especially for those using the WP Go Maps (formerly WP Google Maps) plugin. This guide explains the relationship between the plugin and Google's billing, and how you can manage your costs effectively.

Why You Might Get a Bill from Google

It's important to understand that WP Go Maps itself does not charge you for map views. The plugin acts as a bridge between your website and Google's mapping services. Whenever a visitor loads a map on your site, your website sends a request to Google's servers using your unique API key. Google then processes this request and serves the map tiles, directions, or other data. It is this usage of Google's services that is subject to their pricing.

Does the Number of Markers Affect the Cost?

Based on community discussions, the number of markers on a map is not the primary factor in API costs. The main driver of cost is the number of times the map is loaded (a "map load") and the use of additional services like the JavaScript API, Geocoding (for converting addresses to coordinates), and Directions. A store locator feature, for example, would likely use the Geocoding API, which has its own separate pricing and free quota.

Static Maps vs. Dynamic Maps: Is There a Difference?

A common misconception is that using the Static Maps API would eliminate costs. However, according to responses from the WP Go Maps team, their plugin only supports dynamic maps. Furthermore, Google also bills for Static API requests, though the pricing structure is different. There is no completely free tier for either service, but both offer a monthly free quota that covers most small to medium-sized websites.

How to Protect Yourself from Unexpected Charges

You are not helpless against potential bills. Google provides robust tools to control spending:

  1. Set Up Billing Alerts: In your Google Cloud Console, you can configure budgets and alerts to notify you via email if your usage approaches a certain threshold.
  2. Implement Usage Quotas: You can set hard quotas to cap your API usage. Once the quota is reached, the API will stop serving requests, preventing any further charges for that month.
  3. Monitor Your Usage: Regularly check the dashboard in your Google Cloud Console to see your current API usage and forecasted costs.

What About the Free Monthly Quota?

Google provides a recurring monthly credit. As noted in forum threads, this is typically enough for the vast majority of website owners, often covering up to 28,000 map loads per month. The key requirement is that you must have a billing account with a credit card on file with Google to access this free tier, even if you never exceed the limit and incur a charge.

An Alternative: The OpenLayers Engine

If you prefer to avoid Google's ecosystem entirely, WP Go Maps offers a solution. The plugin includes support for the OpenLayers API, an open-source mapping engine. Switching to OpenLayers in your map settings (found under Maps -> Settings) allows your maps to function without a Google API key and will not generate any charges through Google.

Ultimately, while configuring API keys and billing can seem daunting, taking these proactive steps allows you to use powerful mapping features on your WordPress site with complete financial control and peace of mind.

Related Support Threads Support