All posts
How to Add a User to Google Search Console (And Which Permission to Give)
Google Search ConsoleSearch Console PermissionsSEO ToolsSEO

How to Add a User to Google Search Console (And Which Permission to Give)

How to add a user to Google Search Console, which level to pick (Owner, Full, or Restricted), the per-property limits, and how to remove access safely.

November 16, 2026 · 9 min read

To add a user to Google Search Console, open the property, go to Settings → Users and permissions, click Add user, enter the person's Google Account email, choose a permission level, and save. Only an owner can do this. The clicks take thirty seconds; the part worth thinking about is the permission level, because the default most people reach for ("just make them an owner") hands over far more than a freelancer, a VA, or an SEO tool actually needs.

This guide covers the exact steps, what each permission level can and can't do, the limits Google puts on a property, and how to remove someone cleanly — including the one removal step people miss that lets a former owner walk straight back in.

How Do I Add a User to Google Search Console?

Google's own help page lists the steps:

  1. Open the property in Search Console. You must be an owner of this property (or of a parent property — more on that below).
  2. In the left menu, go to Settings, then Users and permissions.
  3. Click Add user.
  4. Enter the person's Google Account email address. Google is explicit that an email group cannot be added as a user — it has to be an individual account.
  5. Choose a permission level: Owner, Full, or Restricted.
  6. Save.

Once saved, the person appears in the Users list with the level you chose. If you can't add anyone, check your own level on that screen: full and restricted users can't grant access — only an owner can.

If you're adding the person so they can work on one specific problem — say, a sitemap error or a batch of pages stuck in "Crawled — currently not indexed" — decide what that job actually requires before you choose the level. The table in the next section is the quickest way to do that.

Owner vs Full vs Restricted: What Each Permission Can Do

Search Console has three permission levels for people who log in, plus a fourth category ("associates") for linked accounts like Google Analytics that never open Search Console at all. Here's what the three login levels can do, taken from Google's permissions table:

| Action | Owner | Full user | Restricted user | |---|---|---|---| | View all reports (Performance, Links, rich results) | Yes | Yes | Yes | | Add or remove users and owners | Yes | No | No | | Submit a sitemap | Yes | Yes | No | | URL Inspection | Yes | Yes | Fetch only | | Remove URLs (Removals tool) | Yes | Yes | View only | | Disavow links | Yes | Yes | No | | Reconsideration request | Yes | Yes | No | | Share report links | Yes | Yes | No | | Change of Address | Yes | View only | View only | | Link a Google Analytics account | Yes | No | No |

Three rows in that table do most of the deciding:

  • Change of Address is owner-only. If someone is helping you move domains, they'll need owner access for that one step — or you do that step yourself. (Our website migration checklist covers where it fits in the sequence.)
  • The Removals tool and Disavow are available to full users. Both can take pages out of Google or change how your link profile is treated. That's the main reason not to give "full" by default to someone who only needs to look.
  • Restricted users can still read every report. Performance data, the Links report, indexing status — a restricted user sees it. What they can't do is change anything. For anyone whose job is analysis, restricted is enough.

Verified owner vs delegated owner

"Owner" itself comes in two kinds with identical permissions. A verified owner proved ownership with their own token — an HTML file, a meta tag, a DNS record, and so on. A delegated owner was promoted by an existing owner from the Users and permissions screen, with no token of their own. The difference only matters when you remove them, which is covered below.

Which Permission Should You Give?

A simple rule: give the lowest level that lets the person finish the task, and raise it later if they hit a wall. In practice:

| Who you're adding | Level to start with | Why | |---|---|---| | A writer or client who wants to see their numbers | Restricted | They need the Performance report, nothing else | | An SEO freelancer doing an audit | Restricted, then Full | Auditing is reading; fixing (sitemaps, inspection requests) needs Full | | A developer fixing a sitemap that couldn't be read | Full | Resubmitting the sitemap requires Full | | An agency running a domain migration | Owner, temporarily | Change of Address is owner-only | | A co-founder or business partner | Owner | They should be able to recover access if you can't |

The last row is the one solo bloggers skip. If your Google account is the only owner and you lose access to it, nobody can get back into the property without re-verifying from scratch. A second owner — ideally a verified one — is cheap insurance.

Adding an SEO Tool or AI Assistant: Two Different Kinds of Access

Plenty of "add user" moments aren't about people at all. They come from setting up a tool that wants your Search Console data, and the setup instructions usually take one of two routes.

Route 1: you add the tool's account as a user. Scripts, dashboards, and the community-built Search Console MCP servers often run as a Google Cloud service account — an email address that ends in iam.gserviceaccount.com. Their instructions tell you to add that address under Users and permissions, exactly like a person. Here the permission level you choose is the tool's power over your property, so if it only reads data, choose Restricted.

Route 2: the tool asks you to sign in with Google. Instead of being added as a user, the tool requests OAuth access to your account, and it can only reach the properties your own account can reach. The Search Console API defines two OAuth scopes for this: webmasters (read and write) and webmasters.readonly (read only). The consent screen tells you which one a tool is asking for — and for a monitoring or reporting tool, there's no reason to accept more than read-only. Our guide to the Google Search Console API covers what that read access actually exposes.

Traffic Monitor uses the second route: you sign in with Google, it requests read-only access to your Search Console data, and it pulls clicks, impressions, and CTR per post every day. It never appears in your Users list, and there's nothing to remove from the property if you stop using it — you revoke it from your Google account's third-party access settings instead.

Limits: How Many Users Can a Property Have?

Google sets these caps per property:

  • 100 non-owners in total — full, restricted, and associate users combined.
  • Delegated owners can be added until the property reaches 500 owners of any type.
  • Verified owners have no cap; you can add them even when the property already has 500 owners.

For a blog, you'll never come close. The limit that actually trips people up is a different one: if you try to add someone as Full or Restricted on a URL-prefix property and they already own a parent property (for example, the Domain property that contains it), Search Console returns the error "This user may only be added as 'Owner'". Ownership flows down from the parent, and you can't demote someone below what they already have. The fix is to manage that person on the parent property instead.

How to Remove a User (And the Step Everyone Misses)

To remove someone, open Settings → Users and permissions, open the menu next to their name, and choose Remove access. For full users, restricted users, and delegated owners, that's the whole job.

Verified owners are different. Their access comes from a verification token that still lives on your site — the HTML file in your root folder, the meta tag in your theme, or the TXT record at your DNS provider. If you remove them from the list but leave the token in place, Search Console warns that they may regain access, because they can simply re-verify. Delete every token listed for that person, then remove them.

This matters most when:

  • You've finished with an agency or freelancer who verified the site themselves during setup.
  • You've bought or taken over a blog and the previous owner's tokens are still in the theme.
  • Every verified owner is gone. Google says that if all verified owners are removed, the remaining users and delegated owners lose access after a grace period. Data keeps being collected, but nobody can see it until someone verifies ownership again.

If you're auditing a site you've inherited, checking the Users and permissions screen belongs on the same list as the rest of the technical SEO checklist — a stranger with owner access can submit removals or a change of address on your domain.

Quick Answers

Can I add someone without a Gmail address? Google asks for a Google Account email, and a Google Account doesn't have to be a Gmail address. What can't be added is an email group or distribution list.

Can a full user add other users? No. Only owners can add or remove users.

Do I have to add users separately to each property? Permissions are set per property. An owner of a Domain property can also manage users on the URL-prefix properties inside it.

Does a restricted user see the same performance data I do? Yes. Reports aren't trimmed for restricted users; the restriction is on actions, not data.

Track your blog rankings automatically

Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.

Start free →