[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Add a user to many Search Console properties

> Give an SEO, freelancer or agency access to every Search Console property you own in one run, skip existing users and watch the 100-user limit.

Source: https://cotlet.dev/integrations/google-search-console-api-mcp-server/add-user-to-many-properties

A new agency or freelancer needs access to ten Search Console properties, and each one has its own Users and permissions screen to open, fill in and save.

Cotlet does it in your own Google Search Console account with list\_users and add\_user, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=google-search-console) [All Google Search Console tools](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Google Search Console do this on its own?

The Search Console API has no methods for users and permissions (checked 16 Oct 2026); its sites methods add and delete a property in your account but do not share it. Google documents adding users only in Settings > Users and permissions.

## How you do it in Google Search Console today

1. Switch to the property in Search Console and open Settings > Users and permissions.
2. Click Add user, enter the person's Google Account email (an email group cannot be added) and choose a permission: Owner, Full or Restricted.
3. Save, then switch to the next property and repeat the same steps.
4. Only a property owner, or an owner of the parent property, can add or remove users.
5. The 100 non-owner limit is per property, and nothing warns you in advance when a busy property is close to it.

## How to add a user to many Search Console properties

Prompt

```
Add seo@agency.example as a Full user to every property in this list: example.com, example.org, shop.example.com. Skip the ones where she already has access and tell me if any property is close to its user limit.
```

1. 01  
### Read each property's users  
list\_users runs for every property in your prompt, so the agent sees who already has access and with which permission before changing anything.
2. 02  
### Skip and flag, never downgrade  
Where the person is already a user, the agent leaves the property alone and says so. A different existing permission is reported, not silently changed, since a verified owner cannot be lowered.
3. 03  
### Check the user limit  
The agent counts the non-owner users on each property and flags one that is near Google's limit of 100, instead of failing halfway through the list.
4. 04  
### Add with the permission you named  
add\_user runs per property with the permission you chose and waits for your OK on each call, because it changes who can see the property.
5. 05  
### Report a per-property result  
The agent lists added, already present, refused and over the limit, so you can paste the result into the client onboarding ticket.

### What you get back

Example data

```
seo@agency.example as Full user:
example.com: added (8 non-owner users)
example.org: already a Full user, skipped
shop.example.com: added (97 non-owner users, 3 left before the limit)
Refused: 0
```

### Other ways to ask

- Remove jane@oldagency.example from every property where she has access, and list the ones she was an owner on.
- List all users with Owner permission on example.com and example.org.
- Add this client as a Restricted user to the three properties that start with client-.

## What Google Search Console allows, and what to know first

- Google says you can grant permissions only if you are a property owner, or an owner of a parent property.
- Google lists three permission levels in Settings: Owner has full control, Full user has view rights to all data and can take some actions, Restricted user has simple view rights on most data.
- A property can have at most 100 non-owner users; delegated owners can be added until the property reaches 500 verified and delegated owners.
- Users need a valid Google Account, and an email group cannot be added as a user.
- A verified owner proved ownership with a token, and their access level cannot be lowered, only removed by removing that token from the site.

add\_user asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: [Search Console Help: Users and permissions](https://support.google.com/webmasters/answer/7687615) · [Search Console API: resources and methods](https://developers.google.com/webmaster-tools/v1/api%5Freference%5Findex)

## Call add\_user from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/google-search-console/users \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"property":"sc-domain:example.com","email":"seo@agency.example","permission":"full"}'
```

Example response

```
{
"property": "sc-domain:example.com",
"email": "seo@agency.example",
"permission": "full",
"status": "added",
"non_owner_users": 8
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is google\_search\_console\_write → add\_user. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md#automations)

## Google Search Console tools this automation uses

__Cotlet Google Search Console tools used to add a user to many Search Console properties__
| Tool | Parameters |
| ----------- | --------------------------- |
| list\_users | property |
| add\_user | property, email, permission |

[All 15 Google Search Console tools with descriptions](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Google Search Console to Cotlet?

Yes. You sign in to Google Search Console yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Google Search Console once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Google Search Console automations

- [Request indexing in Google Search Console in bulk](https://cotlet.dev/integrations/google-search-console-api-mcp-server/request-indexing-in-bulk.md)
- [Remove many URLs from Google Search in bulk](https://cotlet.dev/integrations/google-search-console-api-mcp-server/remove-urls-from-google-in-bulk.md)
- [Export all not-indexed URLs from Google Search Console](https://cotlet.dev/integrations/google-search-console-api-mcp-server/export-not-indexed-urls.md)
- [Google Search Console API and MCP server: every tool](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Google Search Console.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Google Search Console.

[Sign up free](https://cotlet.dev/app/signup?app=google-search-console)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.