How to Add a User to Google Search Console
Quick answer: Open Search Console, pick the property, then go to Settings, Users and permissions, and Add user. Enter the person's Google account email and choose Full or Restricted permission. Only verified or delegated owners can add users, so if the button is missing, ask an owner to add you first.
Someone needs to see your Search Console data today: a freelancer you just hired, a client who wants proof, a developer chasing an indexing bug. The sharing flow is buried in a settings page, the permission names do not explain themselves, and picking wrong either blocks the person's work or hands a stranger the keys to the property.
The mechanics take one minute once you know where they live. The decision that deserves the minute is the permission level, because the difference between Restricted and Owner is the difference between reading reports and being able to remove you from your own property.
SEARCH CONSOLE
How to Add a User to Google Search Console
PRIMARY KEYWORD
add user to Google Search Console
READ TIME
7 minutes
How do you add a user to Search Console?
Open Search Console and select the property from the dropdown in the top left. Click Settings in the left navigation, then Users and permissions. Click the Add user button, enter the email address of the person's Google account, choose a permission level, and confirm.
The person gets access immediately and the property appears in their own Search Console the next time they open it. There is no invitation to accept. If they say they cannot see it, they are usually signed into a different Google account than the one you added.
What do the Search Console permission levels actually allow?
Google's documentation defines four roles. A verified owner proved control of the site directly, with a DNS record or an HTML file. A delegated owner was granted ownership by another owner and holds the same powers without their own verification token. Full users see all data and can take some actions. Restricted users mostly just view data.
Ownership is the level that can restructure access itself. Owners can add and remove anyone, including other owners, and change property settings. Nobody you merely work with needs that by default.
- Restricted: view reports and data, which covers most reporting and audit work
- Full: everything Restricted sees, plus actions like submitting sitemaps and requesting indexing
- Delegated owner: full control of users and settings, without a verification token of their own
- Verified owner: full control, anchored by their own verification that survives other owners' removal
Which permission should a client, agency, or developer get?
Give the lowest level that covers the actual work, and upgrade later if a task demands it. A client reviewing results needs Restricted. An agency running your SEO needs Full, since sitemap submission and indexing requests are routine for them. A developer debugging a migration usually needs Full for a bounded period, then removal.
Ownership transfers matter in two situations: selling the site, or hiring someone to manage the property wholesale, access included. Even then, keep your own verified ownership in place. Your verification token is what lets you take the property back if a relationship ends badly.
How do you remove a user or audit who has access?
The same Users and permissions page lists every user and their level. Remove someone from the three-dot menu next to their row. Removal is immediate, and there is no notification sent, so tell the person yourself if the removal is friendly.
Make the review a habit tied to something you already do, like a monthly report. Old freelancers, former employees, and agencies you left keep their access until an owner removes it. Most properties that have existed for a few years are sharing data with someone nobody remembers adding.
TAKEAWAY CHECK
What belongs on the grant search console access cleanly?
- 01Confirm you hold Owner permission on the property, since only owners can add users.
- 02Get the exact Google account email the person will sign in with.
- 03Add them at Restricted unless their work requires actions, then use Full.
- 04Have them confirm they can see the property while you are both looking.
- 05Record why the access exists and when it should end.
- 06Review Users and permissions monthly and remove anyone whose work is done.
- 07Check your Google account's third-party access list for tool grants the page does not show.
What else do people ask about add user to Google Search Console?
Why is the Add user button missing in Search Console?
You are signed in with Full or Restricted permission rather than as an owner. Only verified or delegated owners can manage users. Check Users and permissions to see your own level, then ask an existing owner to either add the person or promote you.
Can you add someone without a Google account to Search Console?
No. Search Console access is granted to Google accounts, so the person needs one, though it can be a Google account created on their existing work email address. The alternative is sharing the data outside the product, through exports, scheduled reports, or a public dashboard you control.
How many users can a Search Console property have?
Google's documentation describes a limit of around one hundred users per property, which ordinary teams never approach. If a large organization does hit the ceiling, the usual fix is granting access to shared group accounts sparingly or narrowing who genuinely needs direct access instead of receiving reports.
Does adding a user to Search Console affect the site or its rankings?
No. User management changes who can see and manage the property's data, and Google does not use it as a ranking input. The practical risk is operational: a Full user can request indexing or submit sitemaps, and an owner can remove other users, so match levels to trust.
Is there a way to share Search Console data without adding a user?
Yes. Export reports to CSV or Sheets, connect the property to Looker Studio, or publish verified summaries through a reporting tool. That path suits clients who want proof rather than access, and it avoids growing the user list you have to audit later.
Which primary sources support this guide?
Product behavior and metric definitions change. These are the official Google references used for this article and checked on August 13, 2026.
- 01Google Search Console: users and permissions
Google's definitions of verified owners, delegated owners, full users, and restricted users.
- 02Google Search Console property types
Official differences between Domain and URL-prefix properties.
- 03Google Account Help: third-party apps and services with account access
Google's instructions for reviewing and removing third-party access to a Google account.
PUT THE CLAIM ON THE RECORD
Your SEO result deserves a source, not a trust-me caption.
Connect an owner-level Search Console property, choose what stays public, and get a receipt with a stable share link.