Each update to the Google My Business API makes life easier for those of us managing locations at scale, but columnist Brian Smith notes that gaps in the automation process have yet to be addressed.
Last month, Google released version 3.0 of its Google My Business API, which for those of us managing locations at scale felt like Christmas came early.
Included in the update were a variety of new features, the most important of which were the addition of attributes for locations, the ability to indicate a preferred photo and the ability to match locations between Google Maps and Google My Business listings.
While all of the changes are exceptionally useful (and although one shouldn’t complain about a gift), the fact remains that significant gaps still exist in the API for the needs of enterprise brands, especially when it comes to geocoding and the ability to pull traffic information from a given location.
It’s likely Google will address these issues in future versions of the API, but until that day comes, here’s everything you need to know about the gaps that still exist, how to bridge them and what you should do to optimize your use of the API.
The gap in geocoding