If you manage Google Business Profiles for a business with several locations, or for several clients, posts are the part that quietly eats the week. Each location needs its own update, the wording has to fit each place, and one stray phone number or link in the text can get a post rejected.
This post walks through how posting works in OpenGMB, the open-source Google Business Profile manager we build at Synectus, and why every post goes through a check and an approval before it is sent.
Write once, send to one location or many
A post can be a Standard update, an Event or an Offer. You add one image and a button: Book, Order, Shop, Learn more, Sign up or Call. The text can run up to 1,500 characters. That is our own limit, because Google does not state one.
When you write the post, you pick the locations it goes to. One post can go to several locations of the same client, and you get a separate result for each location.
Bulk drafts from a CSV
For bigger batches you can import up to 500 drafts from a CSV. Variables such as {name} and {city} fill in each location's own details, so one line of text becomes a different post for every row.
Imported rows become drafts, not sent posts. Each one still needs approval.
If you would rather start from AI, it can write a different post for up to 20 locations at a time. Each one lands in the approval queue as its own post.
Rules run before approval
Every post is checked before anyone can approve it, and again for each location just before it is sent. A few examples of what the rules block:
- A phone number in the post text (rule P.phone). Use the Call button instead, which uses the location's own phone.
- Links and email addresses in the text (rules U7.url and U7.email). Put the link on the button.
- Event and offer details are checked as well (P.event).
So this draft for a cleaning company is blocked:
Spring cleaning special this month. Call 555-0142 to book.
and the editor says why: the summary contains a phone number, so remove it and use the Call button instead.
Approval, every time
Posts have no auto-approve. After the rules pass, someone with approval rights approves the post. An agency's team can draft, and the client's approver can approve in the client portal. The audit log shows who approved which post.
A change to a post that is already live is a new proposal, and nothing reaches Google until it is approved again.
Scheduling in the client's time zone
You can send a post now or pick a time in the client's time zone. A schedule can repeat weekly or monthly, and it needs an end date or a count, so nothing repeats forever. A repeating series keeps its local time when daylight saving changes. OpenGMB does the sending, so a post can go out up to about a minute after its scheduled time.
Scheduled and sent posts show on a month calendar, along with the future dates of repeating posts. Posts made outside OpenGMB are synced in, so they show on the calendar too, but you cannot edit them in OpenGMB.
Templates and images
You can save a post as a template: the post type, text, button, event or offer details and one library image. Library images are JPG or PNG, up to 5 MB each, and storage is 50 MB per account, shared by all of its clients.
What it costs
As of 2026-10-24, OpenGMB costs $10 a month per account, and the $10 is usage credit. Drafting, approving and scheduling posts is free, and publishing a post to a location is free under fair use. Only AI drafts and rank scans use the credit.
The full walkthrough with screenshots is on the OpenGMB posts page. The community edition is MIT-licensed on GitHub at synectus/OpenGMB.
Disclosure: this post is from the OpenGMB team at Synectus.
Top comments (0)