Skip to content
Climb Google Maps: Google Business Profile optimization.

Technical SEOGuide

How to Add a User to Google Search Console, Which Permission to Give, and How to Remove Access for Good

Only an owner can add users in Search Console, and removing an owner doesn't always end their access. Here are Google's steps, what each permission level can do, and a short script that lists every property you can see and your role on each.

One person handing a set of keys to another across an office desk

Key takeaways

  • To add a user to Google Search Console, an owner opens Settings, then Users and permissions, selects Add user, enters a Google Account email and picks Owner, Full or Restricted.
  • Full users can submit sitemaps, request removals and disavow links; restricted users mostly view data; only owners can add users or link Google Analytics.
  • A Search Console property can have at most 100 non-owner users, and an email group cannot be added as a user, according to Google.
  • Removing a verified owner doesn't delete their verification token, so they can re-verify later unless you also remove their HTML file, meta tag or DNS record.
  • The Search Console API lists every property your account can see with your permission level, which helps anyone managing many sites check their access.

To add a user to Google Search Console, you must be an owner of the property: open it, go to Settings, then Users and permissions, select Add user, enter the person's Google Account email and choose a permission level. The change takes effect almost at once. The harder questions are which level to give, and how to take access back so it stays gone.

This came up again this week on the Local Search Forum, where a local SEO asked how others manage Search Console for many clients, since there is no equivalent of a Google Ads manager account or a Business Profile agency dashboard. Everything below comes from Google's Search Console help page on owners, users and permissions, read on November 16, 2026, plus a script we tested.

How do I add a user to Google Search Console?

Google's steps, with the menu names as Google writes them:

  1. Open the property in Search Console.
  2. Go to Settings, then Users and permissions. You only see this page if you are an owner.
  3. Click Add user.
  4. Enter the Google Account email of the new user.
  5. Choose the permission: Owner, Full or Restricted.
  6. Save.

Three rules from the same page trip people up:

  • It must be a Google Account. The person needs a valid Google Account, and an email group (a shared list address) cannot be added.
  • There is a cap. A property can have at most 100 users who are not owners. Delegated owners can be added until a property reaches 500 owners in total.
  • "This user may only be added as 'Owner'." You see this error when the person already owns a larger property that contains this one, for example the Domain property example.com when you are adding them to https://shop.example.com/. They already have owner rights here, and Google won't let you demote them on the smaller property.

What can owners, full users and restricted users do?

Google's permission table, condensed:

WhatOwnerFull userRestricted user
View Performance, Links and rich result reportsYesYesYes
Index Coverage (Pages report)YesYesView only
URL InspectionYesYesFetch only
Submit sitemapsYesYesNo
Remove URLsYesYesView only
Disavow links, reconsideration requestsYesYesNo
Verify fixesYesYesNo
Share report linksYesYesNo
Link Merchant CenterYesYesView only
Link Google AnalyticsYesNoNo
Change of AddressYesView onlyView only
Add users, add or remove ownersYesNoNo

Restricted users also only receive the messages that "specifically affect them", Google says, so a restricted user may miss a manual action or security notice an owner sees.

There is a fourth role, associate, for linked services and apps (Google's example is the Chrome Web Store). Associates can act for the site but can't open Search Console data.

Which permission should you give?

Our view, for site owners working with an agency, a freelancer or a developer:

  • An SEO doing the work: Full user. They need to submit sitemaps, inspect URLs and validate fixes. Full user covers all of that without letting them add or remove anyone.
  • Someone who only reads reports: Restricted user. A manager, a client contact or a content writer. If they only need one report once, Google's own advice (in its February 2023 post) is to use the report's share link instead of adding a user.
  • Owner: only people who would rebuild the property if everyone else left. That usually means the business itself, on an account the business controls. If you hire an agency, they can be a delegated owner while they work, then be removed or downgraded when the work ends.

And one structural tip for anyone with many sites: verify a Domain property (sc-domain:example.com) with a DNS record. Ownership of the Domain property carries down to every URL-prefix property under it, so one verification covers www, http, https and every subdomain.

How do I transfer ownership or remove someone for good?

There are two kinds of owner, and they are removed differently:

  • Delegated owner: added by another owner on the Users and permissions page. Remove them there, from the menu next to their name, with Remove access.
  • Verified owner: proved ownership with their own token (an HTML file, a meta tag, a DNS record, or their Google Analytics or Tag Manager access). Removing them from the list ends their access, but Google says their token is not deleted. "As long as these tokens remain," the removed owner can re-verify and get back in. All current owners are notified if they do.

So to remove a verified owner for good, also remove their token. Google lists them under Unused ownership tokens on the Users and permissions page. For an HTML file, delete their file from the site's root; for a meta tag, remove their google-site-verification tag; for DNS, delete their TXT record; for Analytics or Tag Manager, remove their edit, Publish or Admin rights there. Google warns that one token can verify other services too, such as Merchant Center, so check before deleting.

To transfer a property to a new owner, the order matters: the new owner verifies (or is added as an owner) first, then the old owner is removed. If every verified owner is removed, everyone else loses access after a grace period. The data keeps being collected, but no one can see it until someone verifies again.

Ownership history, a link on the same page, shows every owner added or removed and every verification attempt. If you find an owner you don't recognize, Google's advice is to treat it as a possible hack.

How do I see every property I have access to?

When you manage many sites, the Search Console property list doesn't make it easy to see your role on each. The Search Console API does: its sites.list method returns every property your Google account can see and your permissionLevel on it. This Node.js script (version 18 or later, no packages) prints them as a table:

// List every Search Console property your Google account can see,
// with your permission level on each. Node 18+, no packages.
// Usage: ACCESS_TOKEN=ya29... node gsc-access.mjs
const API = process.env.GSC_API || 'https://www.googleapis.com/webmasters/v3/sites';
const token = process.env.ACCESS_TOKEN;
if (!token) { console.error('Set ACCESS_TOKEN (scope webmasters.readonly).'); process.exit(1); }
 
const res = await fetch(API, { headers: { Authorization: `Bearer ${token}` } });
if (!res.ok) { console.error(`API error ${res.status}: ${await res.text()}`); process.exit(1); }
const { siteEntry = [] } = await res.json();
 
const label = {
  siteOwner: 'Owner',
  siteFullUser: 'Full user',
  siteRestrictedUser: 'Restricted user',
  siteUnverifiedUser: 'No access (unverified)',
};
const rows = siteEntry
  .map((s) => ({
    property: s.siteUrl,
    type: s.siteUrl.startsWith('sc-domain:') ? 'Domain' : 'URL prefix',
    access: label[s.permissionLevel] || s.permissionLevel,
  }))
  .sort((a, b) => a.access.localeCompare(b.access) || a.property.localeCompare(b.property));
 
console.table(rows);
const count = (a) => rows.filter((r) => r.access === a).length;
console.log(`${rows.length} properties: ${count('Owner')} owner, ${count('Full user')} full, ` +
  `${count('Restricted user')} restricted, ${count('No access (unverified)')} with no access.`);

It needs an OAuth access token with the webmasters.readonly scope, which you can get from Google's OAuth 2.0 Playground or your own Google Cloud project. Tokens expire after about an hour.

How we tested it: we have no client Search Console accounts to run it on, so on November 16 we ran it against a local test server returning five example properties (one per permission level, plus a second Domain property) and against Google's live endpoint with an invalid token. The table and counts came out right, the live endpoint answered with a 401 error that the script printed, and a missing token stopped it with a clear message. The four permissionLevel values it labels are the ones Google's API reference lists.

Rows marked "No access (unverified)" are properties you once added but no longer own or were never verified for. They are worth a look: either re-verify, or remove them from your list.

What we don't know

  • Whether Google will add a manager account for Search Console like the ones Google Ads and Business Profile have. Google hasn't said.
  • Whether the API will ever manage users. Today it can list, add and remove properties for your own account, but not add other people.

Sources

Photo of Kiran Dasgupta

About the author

Kiran Dasgupta, Editor

Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.