Google Business Profile channel guide
Connect a managed location, publish updates, events, and offers, and interpret location performance.
- Documentation owner:
- BlendDuck Documentation
- Last reviewed:
Google Business Profile posts belong to a specific location, not merely to the Google account used to sign in. Confirm the location before a first publish.
Before you start
- Sign in with a Google account that manages the intended Business Profile.
- Check that the location is verified and visible in Google Business Profile.
- Prepare no more than one JPEG or PNG photo with a public HTTPS URL.
- Decide whether the post is an update, event, or offer.
Connect a location
- Open Dashboard → Channels.
- Choose Google Business Profile → Connect and approve business-management access.
- Select the intended location from the manageable locations BlendDuck discovers.
- Confirm the location name and create a low-risk standard update.
If no location appears, verify the signed-in account's role in Google and then reconnect. Connecting a different Google service does not grant Business Profile location access.
Build the post
| Type | Required details | Optional details |
|---|---|---|
| Standard update | Text, photo, or both; BlendDuck safety ceiling: 1,500 characters | One photo and a call to action |
| Event | Event title, start, and end | Text, one photo, and a call to action |
| Offer | Offer title, start, and end | Coupon code, redemption URL, terms, text, and one photo |
BlendDuck supports Book, Order, Shop, Learn more, Sign up, and Call actions. Actions other than Call require a destination URL on standard and event posts. Use the language code that matches the post.
After submission, a post can remain processing or be rejected by Google's content policy. Do not create a duplicate while its status is still changing. Google's current Local Post reference does not publish an exact summary limit, counting method, media-count maximum, or complete photo processing matrix. The 1,500-character, one-photo, JPEG/PNG, and 5 MiB limits are BlendDuck safety and implementation boundaries. The v4 publishing contract supports photos only, so BlendDuck does not offer Local Post video.
Use Analytics
Analytics combines location, audience, and post data. Depending on Google's response, it can include Search and Maps impressions, calls, directions, website clicks, conversations, bookings, food actions, and post engagement. Data refreshes daily. Inbox separately supports verified-location reviews and owner replies; it does not expose Local Post comments or replies because Google publishes no such Local Post API surface.
You are done when
- the correct location appears under Channels;
- a test update reaches a live state and opens on Google; and
- Analytics shows the location without an authorization error.
If something blocks you
| Symptom | Next action |
|---|---|
| No manageable location is found | Check the Google account's location role and verification, then reconnect. |
| Event or offer validation fails | Add a title plus both start and end times. |
| A call to action is rejected | Add a valid destination URL, unless the action is Call. |
| Media is rejected | Use one publicly reachable HTTPS JPEG or PNG photo and retry once. |
| Post is rejected | Read the provider reason, revise the content to meet Google's policy, and create a new post. |
| Analytics is empty | Check the date range and allow for the daily refresh before reconnecting. |
See Media preparation and Analytics for the shared publishing and reporting workflows.