Updated
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 Full or Restricted, and click Add. Only owners can do this. The person gets access straight away, with no invitation to accept, as long as the email is a Google Account.
How to add a user to Google Search Console, step by step
- Sign in to Search Console with an account that owns the property (verified or delegated owner).
- Pick the property from the menu at the top left. If you have both a Domain property and URL-prefix properties, choose the one you want to share (see below).
- Click Settings at the bottom of the left menu, then Users and permissions. If you don’t see this page, you are not an owner.
- Click Add user.
- Type the person’s email. It must be a Google Account: a Gmail address, a Google Workspace address, or any email registered as a Google Account. Google groups can’t be added (Google).
- Choose the permission: Full or Restricted. To make someone an owner, see the owner section below.
- Click Add. They will see the property the next time they open Search Console.
Google Search Console permissions
Search Console has three kinds of people with access, plus associates (Google’s permissions page):
| Action | Owner | Full user | Restricted user |
|---|---|---|---|
| View Performance, indexing and all reports | Yes | Yes | Yes (most data) |
| URL Inspection | Yes | Yes | Fetch only |
| Submit sitemaps, validate fixes, share report links | Yes | Yes | No |
| Remove URLs | Yes | Yes | View only |
| Disavow links, reconsideration requests | Yes | Yes | No |
| Change of address, property settings | Yes | View only | View only |
| Add and remove users and owners | Yes | No | No |
| Link Google Analytics and other products | Yes | No | No |
Verified owner vs delegated owner
A verified owner proved ownership with a token: an HTML file, meta tag, DNS record, Google Analytics or Tag Manager. A delegated owner was made an owner by another owner, without a token of their own. Both can do everything, including adding users. The difference shows when people leave: if every verified owner is removed, the others lose access after a grace period until someone verifies again. Keep at least two verified owners, and use a company account rather than one person’s.
Associates
Associates are accounts or products linked to the property (for example a Google Analytics property or a YouTube channel). They can’t open Search Console for the property at all.
Which permission to give
- Restricted: clients, managers and anyone who only needs to read reports.
- Full: an SEO or developer who submits sitemaps, validates fixes and uses removals.
- Owner: only people who must manage users or change settings. An owner can remove you.
How to add someone as an owner
Owners add a delegated owner from the same Users and permissions screen, choosing Owner as the permission, with no verification token needed. To become a verified owner instead, the person verifies the property themselves with their own token. A property can have up to 100 non-owner users and up to 500 verified plus delegated owners (Google).
Domain vs URL-prefix properties
Which property you add someone to decides what they see (Google):
| Domain property | URL-prefix property | |
|---|---|---|
| Looks like | example.com | https://www.example.com/ |
| Covers | Every subdomain and http and https | Only URLs starting with that exact prefix |
| Verification | DNS record only | HTML file, meta tag, Analytics, Tag Manager or DNS |
Owners of a Domain property are automatically owners of every URL-prefix property under it. That is why Search Console sometimes says “This user may only be added as ‘Owner’”: the person already owns the parent property, so they can’t be added to a child property at a lower level.
Adding someone to many properties
There is no bulk option in Search Console: you add the user to each property one at a time. Two ways to save time:
- Use Domain properties. One Domain property covers every subdomain and protocol, so one invite replaces several.
- For tools, connect the tool with your own Google account instead (next section). It then sees every property your account can see, with no user added anywhere.
Why adding a user fails
| Problem | Cause | Fix |
|---|---|---|
| No Users and permissions page | You are a full or restricted user, not an owner | Ask an owner, or verify ownership yourself |
| Search Console won’t accept the email | The address isn’t a Google Account, or it is a group | Have them create a Google Account with that email, or use their Gmail |
| “May only be added as Owner” | They already own a parent Domain property | Nothing to fix; they already have access, or add them as owner |
| They can’t see the property | You added them to a different property (URL-prefix vs Domain, www vs non-www) | Check the exact property in the top-left menu and add them there |
| They see no data | The property is new, or it is a URL-prefix property that doesn’t match the live site | Use the property that matches the URLs Google actually shows, or a Domain property |
| Limit reached | 100 non-owner users already | Remove old users first |
Giving access to an agency or freelancer
- Add them as Full, not Owner, unless they must manage users. Full covers sitemaps, validation and removals.
- Add them to the Domain property if you have one, so they see every subdomain and protocol.
- Keep ownership on a company Google account, with at least two verified owners.
- Search Console access doesn’t include Google Analytics: add them separately in GA4 under Admin > Property access management.
- Write down what you added and when, so you can remove it all when the work ends.
How to remove a user
In Settings > Users and permissions, open the menu next to the user and choose Remove access. For a verified owner, also remove their verification token (the HTML file, meta tag or DNS record); otherwise they can verify again and regain access (Google). When an agency or freelancer finishes, remove both their users and any tools they connected.
Connect a tool instead of adding a user
Many tools don’t need to be added as a user. They ask you to sign in with Google and grant access through Google’s own consent screen (OAuth). The tool then reads the properties your account can read, and you can revoke it any time in your Google Account under third-party connections. Check the scope it asks for: a reporting tool only needs read-only access.
That is how DirectoryLens works. You sign in with Google and it asks for read-only access to Search Console (and, if you link them, Google Analytics and Bing). Any Google account with access to the property can connect it. Nothing gets added to Users and permissions, and DirectoryLens can’t change your Search Console settings.
To share the reports with your team, invite them to your DirectoryLens workspace by email instead of adding each one in Search Console. Roles are owner (billing and everything else), admin (sites, settings, invites), and member or viewer (read the reports). Invites work for 14 days and only for the Google account with that email. Teammates see the reports without needing their own Search Console access. Starter includes 2 team members, Growth 5 and Agency 15.
To share numbers with someone outside the team (a client, an advertiser, a buyer), DirectoryLens can create a public, read-only link instead: see SEO reports for clients and the Search Console dashboard guide.
How do I add my site to Google Search Console?
If there is no property to share yet: in Search Console, open the property menu, choose Add property, pick Domain (enter example.com and add the DNS TXT record it gives you) or URL prefix (enter the full address and verify with an HTML file, meta tag, Analytics or Tag Manager). Once verified you are the owner, and you can add users as above. Then submit your sitemap, ideally also listed in robots.txt; see sitemap in robots.txt.