Skip to main content

Search Engine Optimization (SEO),Social Media, Article Submission

Google My Business API v4.2 released Today

 Google My Business API v4.2 has been released

Google announced the release of version 4.2 of the Google My Business API, a way for developers to quickly make modifications to Google My Business listings programmatically. The API can be accessed here but is not open to all. You need to request and be granted access to this API in order to use it.

The new features include:


Verification

Third-party platforms integrated with Google My Business can now offer their merchants the ability to verify their Google My Business listing directly on their native platform. This includes pulling the list of verification options available for a listing, triggering Google My Business verification such as sending a postcard, getting a phone call, and submitting a PIN code for verification. Third party platforms will now be able to fully onboard and verify merchants directly on their platform instead of interrupting their workflow and forcing merchants to Google My Business.

Google Locations

API users are now able to better identify if a listing already exists on Google My Business and whether that listing is already claimed due to the new GoogleLocations endpoint. When the listing is already claimed, partners can provide the merchant with a link to request access to the claimed location.

Search

Version 4.2 of the Google My Business API includes expanded search functionality of the existing Locations.List filters, allowing API users to better search for listings in their account based on full or partial match of more location fields.

Chain membership

This version of the Google My Business API provides a new endpoint to search for chains by full or partial name, and to associate a particular location with that chain.

Product posts

Google My Business API users can now create a new type of post: product posts! These new posts highlight a business’s product offerings, which also display in the “Products” tab on the business listing.

Comments

Popular posts from this blog

Google Image Search updates guidelines, adding structured data, speed and more

Google updated the Google Image Publishing Guidelines document today, adding more details around structured data, page speed, title management and user experience details. The old documentation can be viewed in this screen shot I captured previously. The new guidelines have updated content around creating a better user experience with your images, including adding good context, optimizing placement, embedding tips, device-friendly sites and good URL structure for your images . In addition, Google has explained how the image titles work since the change. Google also added sections for adding structured data for product, video and recipe markup. There is a new section for speed, including information about their PageSpeeds Insights tool, AMP and responsive image techniques. You can check out the new guidelines over here and compare them to the old guidelines over here .

Google updates user management and rights in Google Search Console

Google  announced  some important changes to how user management and rights work within the  Google Search Console . Here are the important changes happening now and in the near future: All users, no matter if they only have the lowest level of permissions or the highest, will be able to see critical site messages. Google added better history tracking to show which individual performed which significant property-affecting modifications. These modifications include changes such as changing a setting, validating an issue or submitting a new sitemap. The new Search Console enables you to share a read-only view of many reports, including Index coverage, AMP, and Mobile Usability. A new user management interface enables all users to see and manage (if they have rights to do so) user roles for all property users. A simpler permission model where Google will limit the “restricted” user role to read-only status. Read-only users will no longer be able to perform any state-changing...