Google has just made major changes to the Maps API terms. This will most likely affect you.
I am afraid to report that the announcement is not good news. It has already caused some headaches.
Google has slashed the free usage limits for their Maps API and raised the price of their Maps API significantly since 11 June. The cost of using Google Maps API is $200 per month. Prices have increased by approximately 1400%.
You will also need to set up a billing account, and enter credit card details, to continue using their API.
Google Maps API updates will impact anyone using their website – even an embedded map. Your company probably has a website.
Below are some key points and links to all relevant articles.
What Is It?
Google is announcing the launch of their Google Maps Platform, “the next generation [they’re] Google Maps business”.
They have combined 18 APIs into three core products: Maps, Routes, and Places. These updates won’t affect any existing code.
They claim they have simplified their pricing structure. However, it is highly doubtful that this has been achieved.
The most important changes are:
1. You will need to create a Google Cloud Platform bill account with credit card details to continue using the API
2. The monthly API call limit is $200. Dynamic Maps can be used on pages to load around 28000 pages per month, a decrease from 25000 per day.
3. The prices have risen dramatically. Google has not officially provided any comparisons, but some sources have estimated it at around 1400%.
Who Will It Affect?
Almost everyone. Nearly all websites include an embedded Google Map on their website. Since Google removed keyless API usage two years ago, this means that you will need to call the Maps API.
Even though the $200 limit won’t affect you, you will still need to create a billing account with your credit card details. This is not something everyone can do easily.
You don’t need to worry if you have an embedded map. Google’s pricing page (which is not very simple and offers little explanation for non-technical users), explains that there is no limit. Google estimates that approximately 98% of users should be within the $200 limit.
If you use Advanced Embed, Dynamic Maps, or Maps with Street View, or any other type of Directions functionality or Autocomplete, the price will go up.
If you are currently using Google Maps as a major component of your site functionality, this could make a huge difference.
It is important to note that Mobile Native Static Maps (read Android) and Mobile Native Dynamic Maps are free. Google seems to be protecting Android app developers wisely.
Google has confirmed that you can set quotas to limit your daily usage. This should protect your finances from sudden spikes in traffic or DDoS attacks. This doesn’t change the fact that any map functionality on your website will cease to function once you reach said quota.
What Does Google Maps API Change Mean & Why Should I Care?
Google is making a significant, but unwelcomed change.
Google Maps is the most popular and widely used map software. It is a very useful tool for both end users and businesses. It has been extremely cost-effective for businesses and was free to end users until yesterday.
Google appears to have finally cashed in on Maps, first monopolizing it and then increasing the prices.
Although Google would eventually seek ways to make this cash cow more profitable, the rapidity and aggressiveness of Google’s changes have been surprising. Google has only given a month for preparations to handle changes that could cripple a company’s website functionality.
It is also not surprising that Google has adopted the same self-protection we have come to expect (in this instance protecting Android app developers).
The 98% figure is great on paper but it doesn’t change the fact that these changes could cause major site functionality to be lost for thousands of businesses.
This is a worrying precedent. Google is shifting billing to their Google Cloud platform. Does this mean that we will see increased costs for other Google products and media in the future? We will only know the outcome of this experiment when it is completed.
In short, for digital agencies in Miami and companies around the world, the Google Maps API change was not a good thing to wake up to. It’s proving so unpopular, it’s entirely possible we could see companies shifting away from Google Maps entirely, providing a boost for Bing and others.
This will happen on a large scale. Google will have to reevaluate its position. We are not sure, but we will keep an eye (and be wary) on the developments.