Ce guide est disponible en anglais.
How Google Business Profile Synchronization Works
Google Business Profile sync rests on an owner's OAuth consent, matching a location to the right Google listing, then a write-and-verify loop.
En bref
- Ce que ce guide permet
- Explain the consent, listing-matching and update-and-verify steps behind keeping a Google Business Profile in sync.
- API utilisées
- get
/api/v1/connections/google/connect-urlObtenir une URL de connexion Google - get
/api/v1/connectionsLister les comptes connectés - post
/api/v1/connections/locations/confirm-matchConfirmer une correspondance suggérée - patch
/api/v1/locations/{id}Mettre à jour un établissement
- get
- Référence
- ConnexionsLocations
- Prérequis
- None. This is a concept page; the guides linked from it have the code.
- Cas d'usage typiques
- Understanding what the Google connect flow actually does
- Designing onboarding around Google's consent screen
- Explaining why a change is not instantly on Google
A Google Business Profile does not sync until three things are true, and only the last is a normal API write. The owner has to grant access. The right Google listing has to be paired with your location. Then, and only then, changes flow, and even those publish on Google's schedule rather than yours.
Consent comes first, and it is a person
Google's profile belongs to the business owner. No API touches it without an OAuth grant from their Google account, and that grant is an interactive screen a human completes. You cannot automate it. In Synup's API you start it with the URL from GET /api/v1/connections/google/connect-url, hand that to the owner, and they consent. Nothing else works until they have.
Matching the listing to your location
Consent gives access to a Google account, and that account may manage one listing or many. Synchronisation still needs to know which Google listing is this location. Synup proposes matches, and you confirm the right one with POST /api/v1/connections/locations/confirm-match. Get it wrong and you push a business's data onto the wrong Google profile, so a human should confirm whenever the match is not obvious. GET /api/v1/connections shows the current connection state per location.
The update-and-verify loop
Once a location is connected and matched, a change through PATCH /api/v1/locations/{id} is translated into Google's format and submitted through Google's Business Profile API, under Synup's approved project. Then you verify, because Google does not always apply a change straight away.
Google publishes on its own clock
Two delays stack up here. Google reviews some edits before they show, especially on sensitive fields, and verifying a newly connected location takes its own time. Neither is something the API can hurry. That is why sync status on Google is a value you read, not one you assume from a successful write. If you are still choosing between building on Google's API directly and going through a listings API, the comparison page lays out the trade, and this same asynchronous reality shows up across listing syndication generally.