Getting someone else into your Google Search Console sounds like a two-click job. And technically it is. The problem is that most people hand over access without thinking about what they’re actually giving away, and then they wonder why their property data looks weird, why a sitemap got deleted, or why a client suddenly has full control of their domain verification.
So let’s cut the fluff. Here’s how to add a user to Search Console the right way in 2026, what each permission level actually means, and where people usually mess up.
You add a user to Google Search Console when you need another pair of eyes on performance data. That’s it. Could be an SEO freelancer auditing your site, a developer fixing indexing errors, a teammate running reports, or a client who wants to see their own numbers without asking you every week.
The tool is the backbone of technical SEO. It shows you clicks, impressions, average position, Core Web Vitals, indexing status and manual actions. Handing out access is normal. Doing it blindly is not.
There’s a catch most tutorials skip: Search Console permissions are tied to a Google account, not to a company. If that person leaves your team and you forget to revoke access, they keep seeing your data forever. That’s a real risk, not a theoretical one.
The three permission levels (and which one you should actually pick)
Before you click anything, understand the roles. Google gives you four, and the difference between them matters more than people assume.
- Owner (verified): Full control. Can add or remove users, change settings, submit sitemaps, and remove the property. If you’re the site owner, this is you. Don’t hand this to anyone casually.
- Owner (delegated): Same powers as a verified owner but without the DNS or file verification token. Useful for agencies managing a client property, but it’s still near-total control.
- Full user: Can see all data, submit sitemaps, use the URL Inspection tool and request indexing. Cannot manage users or change property settings. This is the sweet spot for 90% of cases.
- Restricted user: Read-only access to most reports. Perfect for clients, stakeholders or anyone who just needs to check numbers.
My rule: start restricted, escalate only when someone proves they need more. If they complain, ask them exactly what they can’t do. Nine times out of ten, «full user» solves it and «owner» was never necessary.
How to add a user to Search Console step by step
Log into Search Console with the Google account that owns or manages the property. On the top-left property selector, double-check you’re inside the correct domain. This is where people screw up most: they add a user to the wrong property and then spend an hour wondering why the client can’t see anything.
Once you’re in the right property, look at the left sidebar and click Settings. It’s the gear icon at the bottom. Then choose Users and permissions.
Hit the blue Add user button. A small panel opens asking for an email address and a permission level.
- Type the exact email tied to the Google account of the person you’re granting access to. Gmail, Workspace, whatever they use. A typo here means the invite goes nowhere.
- Choose the permission level from the dropdown. Remember: restricted for read-only, full for everyday SEO work, owner only if you truly trust them.
- Click Add. Google sends an email notification to that address.
Done. The user appears in the list immediately, and their access activates as soon as they log in with that Google account. No confirmation click required on their end, which is another reason to be careful with the email.
Adding users when you manage multiple properties
If you run several sites, you have two options. You can repeat the process site by site, which is tedious but precise. Or you can use a Domain property with a DNS verification, which covers all subdomains and protocols at once. That second route is what I recommend for anyone managing a brand with blog, shop and app under the same root domain.
One thing to know: users added at the domain level inherit access to every subdomain. So if you add a freelance developer to your main domain, they also see staging.yoursite.com and anything else under that root. Sometimes that’s fine. Sometimes it’s a leak.
For agencies, the cleaner setup is to have the client own the property and add the agency as a delegated owner. That way, if the relationship ends, the client revokes access in ten seconds and nobody loses the verification token.
Common mistakes when adding a user to Google Search Console
I’ve seen all of these. Each one has cost someone time or data.
- Wrong property: Adding the user to a URL-prefix property when you actually needed the domain property. The data looks different and the user gets confused.
- Typos in the email: Google doesn’t validate the address against a real account until someone logs in. A typo just sits there silently.
- Giving owner access to a contractor: They can now remove the property, delete users and break your verification. Don’t do it.
- Forgetting to revoke: Ex-employees, ex-freelancers, ex-agencies. Clean the user list every quarter. It takes two minutes.
- Sharing a single Google account: Never give multiple people the same login. You lose the audit trail and Google may flag suspicious activity.
And no, you cannot add a user with a non-Google email. It has to be a Google account. If your client uses Outlook, tell them to create a free Gmail just for this. It’s a five-minute annoyance that saves months of confusion.
What to check after you’ve added them
Once the user is in, verify three things. First, that the permission level matches what you intended. Second, that they can actually see the property when they log in. Third, that your sitemaps and indexing data are intact, because a full user can submit new sitemaps and request indexing, and that can change your reports fast.
If you’re delegating real SEO work, point them to the essentials: Page indexing, Sitemaps, Core Web Vitals and Manual actions. Those four sections cover 80% of what a technical SEO audit needs. Everything else is secondary.
Search Console isn’t just a dashboard. It’s the closest thing you have to a direct line with Google about how your site is being crawled, indexed and ranked. Treat access like you’d treat admin rights on your server.
The whole process of adding a user to Search Console takes under a minute. The decision of who gets what permission should take longer. Get that part right, and you’ll avoid the kind of mess that costs rankings, data, or a client relationship.
