Google Business Profile organization accounts, for agencies

A Google Business Profile organization account is the account an agency signs in with to manage its clients' listings. The client stays the owner of each listing and shares it with the agency's organization; the agency never signs in as the client. It replaces the oldest habit in local marketing, a spreadsheet of clients' Google passwords, with access that each side can see and either side can end.

How an organization account is laid out

Google's help pages describe four levels, and they are easier to hold in your head as folders:

1. The organization is the agency itself, and an agency normally needs only one. Its owners are the agency's own people, signed in with addresses on the agency's domain.
2. Business groups sit inside it, and each holds a set of listings. Most agencies make one group per client, or one per brand for a franchise.
3. The listings are the clients' Business Profiles. They arrive in a group because the owner shared them, either by inviting the group or by accepting the agency's request for access.
4. User groups decide which of the agency's staff can work on which business groups, so an account manager sees their own clients' listings and not the whole book.

Two details catch people at sign-up. The address you create the organization with should be on your agency's domain, not a Gmail account, and it should not already be managing Business Profiles; the same goes for staff you add. And if a client's listing does not turn up when you search for it to request access, the client can add the agency from their side instead.

How it works: Bulk actions

Why not just sign in as the client

Plenty of agencies still do, because it is faster on day one. Every reason against it shows up later.

A Google account is not a listing. The client's login usually opens their Gmail, their Drive, their Ads billing and their Analytics too. Signing in as them to answer a review hands your agency the keys to all of it, which neither side wanted to sign up for.

Google also notices the sign-in. A login from an agency's office, in another city, on a device the client has never used, is the kind of sign-in Google's account security asks questions about. The usual result is a verification prompt on the client's phone at the moment your colleague is trying to post an update, and a client asking why Google says someone signed in from somewhere they have never been.

Then the relationship ends. With a shared password, offboarding is a password change the client has to remember to make, and until they do the agency still holds the account. With an organization account, the client removes the agency's access and that is the whole job. We wrote up the rest of that day in offboarding a client's browser profiles.

The same reasoning runs through every platform an agency touches. Meta, Seller Central and Google each have a way to add a person under their own login with chosen permissions, and giving a virtual assistant access without the password walks through all three. A spreadsheet of passwords is the fallback when a platform has nothing better, and the shared password spreadsheet has why it fails.

Setting one up for an existing client list

The order that keeps a migration tidy:

1. Create the organization with an agency-domain address that manages nothing yet, and add a second owner from your agency so the organization never depends on one person.
2. Make a business group for each client, named the way your client list names them.
3. Send each client the request for access, or give them the group's ID so they can invite it. A one-line email explaining why ("so we stop signing in as you") gets most of them done in a day.
4. Once a listing appears in its group, remove any old personal logins of yours from that client's profile, and ask the client to change any password you were given.
5. Set up user groups so each account manager reaches only their own clients.

The first hour with a new client, including where this request fits among the other access you need, is in client onboarding: the first hour.

Where an anti-detect browser fits

Not in the Business Profile part. An organization account is the right tool there, and nothing about a browser improves on access Google grants on purpose.

Mosaic fits around it. An agency's people still have sign-ins that have no organization equivalent, such as a client's website admin or a directory listing, and those are cleaner kept apart: one profile per client, with that client's logins and two-factor codes in its own Credentials, so a session from one client never sits in the same cookie jar as another's. And checking how a listing looks to a searcher in the client's town is a job for a profile whose proxy exits there, with the timezone and language matched to that exit.

Your agency's own organization login belongs in one profile of its own. That way it is never mixed with any client's cookies.