Changes to Google Service Areas


Due to Google product changes, the way businesses can define their service areas in Yext is changing on January 24, 2019. This post describes what adjustments developers will need to make to their serviceArea values to accommodate these changes.

What’s changing

Currently, our customers can use the Knowledge API to define their service area in the following ways:

  • A combination of the radius and units subfields of serviceArea, which lets customers describe their service area as a distance around the point described in address
  • A list of postal codes or cities in the places subfield of serviceArea

Starting January 24, 2019, you will no longer be able to set your service area as a radius in the Yext Knowledge Manager or the Knowledge Manager API. Soon after, Google will automatically convert any existing radii to a list of places (ZIP codes or cities).

What you need to do

If you are not using the serviceArea field or are using only the places subfield of serviceArea:

  • No action is required on your part.

If you are using the radius and units subfields of serviceArea:

  • No action is required unless you want to change or add new service area information. In this case, you must begin using the places subfield to define your service area as a set of postal codes or cities, as the radius and units subfields of serviceArea will be removed on January 24.


If you have any questions about this change or need help updating your serviceArea fields, please contact our API support team.