The GBP Safety Charter: the rules an AI tool should show you before it touches a profile
Anyone who manages Google Business Profiles has been told to keep AI away from them. The advice was earned. Here are the five rules Commander runs on, and which ones the product enforces today.
If you manage Google Business Profiles for other people, you have heard the warning. Keep AI away from the profile. Tools that post on their own, in bulk, from a template, are how a profile gets suspended, and a suspension appeal is a week of someone's life that nobody pays for.
The warning was earned. But it answers the wrong question. The question is not whether to use an agent on a profile. It is whether the agent has rules, and whether you can read them.
So we wrote ours down. The full page is at /gbp-safety-charter. This is the short version, with the reasoning.
The five rules
Drafts only. Every post, profile edit, and review reply the agent writes is a draft. It cannot publish to a profile by itself. This is not a setting you turn on. There is no other mode.
A person approves. Each draft waits in the review queue until someone on your team approves it, edits it, or sends it back. The queue is one list across every client, so approving thirty profiles' worth of work is one sitting, not thirty logins.
A record of everything. What was proposed, what changed, who approved it, and when. If Google asks what happened to a profile last Tuesday, you can answer.
Paced edits. Profile changes go out at a human pace. A category, a set of services, new hours: one change at a time, with a reason, not a burst that looks like an account takeover.
No mass changes on a new profile. A newly connected or newly verified profile gets no bulk edits. It is the profile most likely to be suspended and the one where patience costs least.
Which of these the product enforces today
The first three are enforced in software. Drafting is the only thing the agent can do to a profile, the review queue is the only path to publishing, and the log is written whether you read it or not.
The last two are how we operate and are being built into the product. We say that on the charter page too, because a rule that is really a habit should be labelled as one. When pacing and new-profile protection are enforced rather than practised, the label changes.
Why publish it
Two reasons. The first is that a profile manager choosing a tool deserves to know what the tool can do without asking. Most AI profile tools describe what they can do. Very few describe what they will not.
The second is that we run our own clients' profiles on these rules first. Publishing them means we cannot quietly relax them when it would be convenient. If a rule changes, it changes here before it changes anywhere else.